The internal pre-construction planning session: half a day that makes the plan
The estimate handover is over and mobilization is approaching. The superintendent is drawing a trailer layout while the purchaser is calling suppliers from a different version of the schedule. Everyone is working, but the assumptions have not been tested together.

Run the internal preconstruction planning meeting as a half-day working session that produces connected decisions, not a round of updates. Bring the project manager, superintendent, estimator and the people responsible for purchasing and safety together with the same baseline information. Work through logistics, the schedule, buyout, staffing, approvals and risks in a deliberate order. Give every unfinished output one owner and a due date before anyone leaves.
Prepare the working agenda
- Collect the handover inputs. Circulate the priced scope, assumptions, issued information and known exclusions before the session. Ask each participant to identify the decisions their part of the plan depends on.
- Start with the physical site. Have the superintendent show the proposed access, storage, temporary facilities and work fronts on one plan. Ask the estimator and safety lead to challenge assumptions, including interfaces still awaiting assessment.
- Test the schedule skeleton against that layout. Identify the first activities and what must be available for them. Record conflicts between the intended sequence and the site arrangement rather than hiding them in separate documents.
- Work backward to purchasing decisions. Ask the purchaser what information and release decisions each early package needs. Distinguish a supplier forecast from a confirmed commitment and assign the missing checks.
- Name the people and approvals needed. Check who will cover the opening phase, who applies for each relevant approval and who confirms unresolved requirements with the authority or designer.
- Finish with outputs and owners. Read back the agreed decisions, the documents to update and the remaining questions. Set a return check for unresolved items so mobilization is not based on silence.
Common mistakes
- Holding the session without the priced assumptions, so people discuss different versions of the job.
- Letting each discipline produce a separate plan without checking the interfaces.
- Recording an unresolved question as an agreed decision because time is running out.
Checklist
What the session should leave behind
- One agreed site layout to develop.
- An opening sequence with its dependencies.
- A dated purchasing decision list.
- People assigned to the opening phase.
- Approval questions with named applicants.
- Unresolved risks with owners and return dates.
Check your understanding
The group agrees that the access arrangement probably works, but nobody has checked it with the responsible lead. Is that a finished output?



