Most construction problems do not begin on the day concrete is poured. They begin earlier: in a drawing that was never checked against another discipline, a soil report nobody opened, or two teams working from different assumptions. By the time the gap shows up on site it has become rework, idle crews or a disputed variation.

Pre-construction planning is the cheap place to find those gaps. Before a work package is released, everyone involved should be able to say what is being built, to which drawing, in what order, and who answers the question when the site does not match the paper.

Start with what the project actually knows

Gather what exists: architectural and structural drawings, survey levels, soil reports, utility information, access constraints and the client's requirements. Then sort it honestly. A level taken from an old survey, a utility route 'as per owner' and a soil condition assumed from the next plot are different kinds of information, and they deserve different labels.

Anything unconfirmed should be written down as a question with an owner and a date, not quietly treated as a fact. That list is often the most useful page in the whole planning pack.

  • Mark each input as confirmed, provisional or missing.
  • Give every open question an owner and a due date.
  • Check survey and report dates against the current layout.

Check where the disciplines meet

Architecture, structure and building services pull on each other. A beam that clears the plan can collide with a duct, a shaft placed for the plumber can cut into a slab edge, and an opening moved late can change a load path. Overlay the drawings before release and mark every conflict.

Then walk the sequence on paper: crane and material access, temporary works, propping and curing, and the points where trades cross each other. A layout can be technically correct and still hard to build if nobody has thought about how it gets built.

  • Overlay architectural, structural and services drawings.
  • Identify inspection and hold points before work is covered up.
  • Confirm access, storage and temporary works for each stage.

Keep one controlled set

A single issue register beats several informal folders. Record which drawing revision governs which package, take superseded sheets out of site packs, and log approved changes as they happen. At handover those records also explain why the building differs from the first drawing, if it does.