Preconstruction Meeting Agenda: Align Scope, Constraints and Site Responsibilities

A preconstruction meeting agenda should expose unresolved constraints before crews and equipment arrive. The meeting is not a ceremonial kickoff. It is a decision forum for confirming scope, interfaces, information readiness, site logistics, controls, responsibilities, and the first sequence of work.

Use this agenda before initial mobilization or adapt it for a major work package. It is general operational guidance, not legal, contractual, engineering, or safety advice.

Define the decisions the meeting must produce

Write desired outcomes at the top of the invitation. Examples include confirming the first work area, resolving a drawing discrepancy, approving a communication route, assigning permit preparation, and identifying conditions that prevent start.

Separate decisions from updates. If an item needs no discussion or choice, include it in the pre-read. Invite people with authority and relevant knowledge; a room full of representatives who must “check later” creates delay rather than alignment.

Copyable preconstruction meeting agenda

Project / work package:
Date, time, location, and chair:
Purpose and required decisions:
Attendees, roles, and authority:
1. Scope, exclusions, and acceptance criteria
2. Current drawings, specifications, submittals, and RFIs
3. Contract milestones and short-term sequence
4. Site access, logistics, deliveries, storage, and welfare
5. Trade interfaces and simultaneous operations
6. Safety, environmental, permit, and emergency arrangements
7. Quality plan, inspections, tests, evidence, and hold points
8. Communication, document control, and change process
9. Risks, constraints, assumptions, and unresolved items
10. Decisions, actions, owners, dates, and start conditions

Add document revision numbers and links. A meeting based on obsolete drawings can create false confidence.

Confirm scope and acceptance boundaries

State what is included, excluded, provided by others, and not yet authorized. Break broad scope into work areas, systems, or deliverables. Clarify who accepts completed work and which evidence supports acceptance.

Avoid resolving contractual ambiguity through casual wording in minutes. Record the question, interim safe position, responsible contractual route, and deadline. If a decision changes scope, use the formal change process rather than treating meeting agreement as automatically sufficient.

Prepare a short boundary statement for each major work package. It should identify supplied materials, temporary works, builder’s work, testing, protection, making good, and final documentation. Read the boundary across adjacent packages, not in isolation. A missing responsibility often appears only when two scope descriptions are compared. Where ownership remains unresolved, record the interface as a start constraint rather than allowing both parties to assume the other will complete it.

Review information readiness

Create a readiness table before the meeting:

“Submitted” is not “approved,” and “discussed” is not “issued.” Use precise status labels and identify which missing information blocks work.

Align schedule and work sequence

Review contractual milestones, near-term activities, access dates, lead times, inspections, and dependencies. Focus on the next executable window rather than reading the entire programme aloud. Ask what must be true before each first activity starts.

Record assumptions separately from commitments. If the schedule assumes an approval by Friday, name the assumption and consequence. The construction daily report template can later capture actual progress and constraints against this agreed starting logic.

Test the proposed sequence against physical reality. Ask where materials will be stored, how completed work will be protected, which inspection must occur before concealment, and whether access remains available for following trades. Include mobilisation, setup, curing, testing, cleaning, and demobilisation where they affect other work. These transition activities are easy to omit from a high-level programme even though they determine whether the next team can start safely and productively.

Plan access, deliveries, and site logistics

Confirm gates, working hours, delivery booking, lifting or unloading arrangements, traffic and pedestrian routes, storage, temporary services, welfare, security, waste, and neighbour or occupant interfaces. Walk the site when a drawing cannot convey the real constraint.

Use the construction site inspection checklist to structure a physical review. Record conditions with photos only where authorized, captioned, and stored under project rules.

Surface trade interfaces and responsibilities

Map who hands what to whom. Typical interfaces include builder’s work, penetrations, supports, power, controls, testing, protection, access, and ceiling or wall closure. Assign one accountable owner to resolve each interface, even when several parties contribute.

An interface table reduces the common failure where everyone assumes another party owns the gap.

Address safety and environmental controls competently

Review relevant risk planning, methods, permits, isolations, emergency arrangements, rescue, public protection, environmental controls, and supervision. The meeting can confirm readiness and ownership, but it does not replace formal risk assessment, competent review, permits, training, or task briefings.

Use the toolbox talk template for focused crew communication and the contractor site induction principles only through an existing published site-check route; do not infer that attendance alone proves competence. Urgent hazards must be escalated immediately, not parked in minutes.

Define quality evidence and hold points

Agree inspections, test plans, samples, mock-ups, witness points, hold points, records, and acceptance authority. State what cannot be covered or progressed until inspection occurs. Include notice periods and the location of approved forms.

Use a construction punch list template near completion, but do not defer known quality requirements until closeout. Early evidence requirements influence how work is sequenced and photographed.

Establish communication and change control

Confirm which platform is authoritative, naming conventions, response routes, meeting cadence, document control, RFI handling, and formal notice channels. Distinguish urgent operational escalation from contractual communication.

Record key choices in a decision log template. Meeting minutes should identify the decision, basis, authority, date, affected scope, and review trigger—not rewrite the entire discussion.

Agree a response hierarchy for genuinely urgent questions. The route should identify who receives the first notification, who can issue an interim instruction, how that instruction is documented, and when the controlled record must follow. This avoids two opposite failures: field teams waiting unnecessarily for routine clarification, or acting on an informal message that no authorized person has reviewed. Make escalation times realistic for nights, weekends, and restricted-access periods.

Create a reviewable draft from an authorized project discussion. Kuno can support consented capture and draft notes; accountable project professionals must verify technical, contractual, and safety-sensitive content. Explore Kuno

Close with start conditions and accountable actions

Read back decisions and actions before ending. Every action needs one owner and a due date. Mark conditions as “open,” “satisfied,” or “not applicable” only with evidence and authority.

Example closeout:

Decision: Initial work area is Level 2 east corridor, subject to access release.
Open condition: Drawing response RFI-014 and permit approval required before installation.
Action: Design lead to issue response by 21 July; site manager to confirm permit status by 22 July.
Constraint: Delivery route shared with façade contractor from 09:00 to 11:00.
Next review: Readiness check at 15:00 on 22 July. No start authorization inferred from these minutes.

Distribute draft minutes promptly with a defined correction window. Keep the approved record linked to its source documents and use the meeting follow-up guide to prevent actions disappearing between meetings.

Final readiness check

Before mobilization, verify that scope, drawings, approvals, access, logistics, controls, competence, permits, inspections, communication routes, and first actions align. If reality differs, pause and reassess rather than forcing the meeting record to fit.

Keep the agenda decision-led and the record human-owned. Use Kuno only for authorized, appropriately disclosed capture, and verify all names, dates, revisions, commitments, and permissions before relying on the draft. See Kuno for project notes