The preconstruction meeting: agenda, attendees, and a checklist you can copy

By Adam Chandler, founder of Pangea · August 27, 2026

A preconstruction meeting is the meeting held after a construction contract is awarded and before work starts, where the owner, the designer, the contractor, and — on public work — the reviewing agency agree on how the project will actually be run. It settles who has authority, how communication and submittals flow, what the site rules and schedule are, and what paperwork has to be in hand before anyone mobilizes. It typically runs an hour or two, it is led by the contractor's project manager or the agency's construction engineer, and its real output is the minutes.

That last point is the one most teams underrate. Nothing is built at a preconstruction meeting. What gets created is a shared set of expectations, and the only version of those expectations that survives to month four is the one somebody wrote down and sent out.

What is a preconstruction meeting?

It is the handoff between the contract and the jobsite. The contract says what will be built and for how much. The preconstruction meeting decides the operating procedure: who calls whom, how many days of notice an inspection needs, where trucks enter, which submittals are due first, and what the contractor has to produce before the first shovel moves.

It goes by several names — preconstruction conference, precon, kickoff, pre-work meeting. On federal and municipal projects "preconstruction conference" is usually the formal term, and the agenda is a standing form the agency hands you rather than something you write. On private commercial work it is closer to a project kickoff, and the contractor sets the agenda.

What separates it from the recurring OAC meeting that follows is scope. The precon is about process and is held once. The OAC meeting is about progress and is held every week or two for the rest of the job.

When is the preconstruction meeting held?

After award, before mobilization — and on most public projects, before the notice to proceed is issued. The Michigan Department of Transportation states the rule plainly for its projects: preconstruction meetings must not be conducted prior to award. Holding one earlier means negotiating with a party that may not end up holding the contract.

The practical window is the gap between award and the start date. Two weeks is comfortable. One week is common. Less than that, and the items the meeting is supposed to unblock — permits, insurance certificates, the trench safety plan, the traffic control plan — do not have time to actually get resolved before they are needed.

The meeting also feeds directly into the notice to proceed. On agency work the NTP is frequently held until the precon has happened and the conditions raised in it are satisfied, which makes the meeting a gate rather than a formality.

Who attends a preconstruction meeting?

The rule of thumb: everyone with authority to commit, plus everyone who will be called at 6 a.m. when something goes wrong. Typically that is:

• The owner or their representative — the person who can approve a change in direction, and who will receive the notices the contract requires.
• The general contractor's project manager and superintendent — the PM runs the meeting on private work; the superintendent is the one who has to live with whatever gets agreed about access, hours, and staging.
• The design team — architect and engineer of record, who explain design intent and confirm how submittals and RFIs will be routed and how fast they will be answered.
• Key subcontractors — the trades that go first (site, utilities, concrete) and any trade with a long-lead package. Bringing every sub to a precon wastes forty people's morning.
• The agency, on public or permitted work — the construction inspector, plan review engineer, public works staff, and often a traffic engineer.
• Specialists as warranted — safety officer, materials testing lab, surveyor, utility company representatives, and the commissioning agent on complex buildings.

Two roles are worth naming explicitly at the table because ambiguity about them causes most first-month friction: who is authorized to direct changed work, and who receives official notice. Say both out loud, and put both in the minutes with names and contact details.

What goes on a preconstruction meeting agenda?

Here is a full agenda you can copy. It follows the structure that municipal and federal agency forms converge on, trimmed to what applies on a typical commercial or site-development job. Delete what does not apply; do not add items you have no intention of tracking.

1. Introductions and contacts

• Sign-in sheet — name, company, role, phone, email.
• Key personnel by name: owner's rep, PM, superintendent, engineer of record, inspector, safety lead.
• Chain of command and who has authority to direct changed work.
• Where official notices are sent, and in what form.

2. Project scope and documents

• Confirm the drawing and specification set everyone is building from, by date and revision.
• Where the approved plans and standard details will be kept on site.
• Who maintains the as-built or record set, and how often it is updated.
• Known unresolved design items and when answers are due.

3. Contract administration

• Contract dates: start, substantial completion, final completion, and liquidated damages if any.
• Insurance certificates, bonds, and any prevailing wage or reporting requirements — confirm received, not "in process."
• Permits: which are issued, which are pending, and who is responsible for each.
• Easements and right-of-way, including anything offsite or on adjacent property.

4. Schedule

• Baseline schedule review, with milestones and phasing.
• Mobilization plan and the actual first day of work.
• Working hours, permitted work days, and holiday restrictions.
• Long-lead items and the dates their submittals must be approved by.
• Weather-day definition and how it gets documented.

5. Communication and document flow

• Which channel carries what: email for the record, phone for urgency, the project platform for formal transactions.
• RFI procedure and the turnaround the design team commits to. (Start the RFI log at the precon, not at the first RFI.)
• Submittal procedure, review stamps, and resubmittal expectations — the submittal log should be seeded here with the long-lead packages.
• Meeting cadence going forward: day, time, attendees, and who writes the minutes.
• Distribution list for minutes and how corrections get made.

6. Site logistics

• Construction entrance and exit, haul routes, and delivery restrictions.
• Laydown and staging areas, crane and equipment placement.
• Parking, sanitary facilities, temporary power, water, and fencing.
• Site security, lighting, and after-hours access.
• Housekeeping, dust control, and debris disposal.

7. Utilities, testing, and inspections

• Existing utility locates: who calls, how far in advance, and how private utilities are handled.
• Advance notice required before each inspection, and who schedules it.
• Which work may not be covered or backfilled before inspection.
• Materials testing: the lab, who pays, test frequencies, and where results go.
• Utility shutdowns and the notice owed to neighbors or tenants.

8. Safety, traffic, and environmental

• Site-specific safety plan, orientation requirements, and PPE rules.
• Trench safety plan and excavation procedures.
• Traffic control plan, lane closures, and the notice required for a road closure.
• Erosion control and stormwater plan, plus who inspects and documents it.
• Emergency procedures, nearest hospital, and the incident reporting chain.

9. Changes, payment, and closeout

• Change procedure: who can initiate, what backup is required, and the approval chain.
• Pay application format, cut-off date, schedule of values status, lien waiver requirements, and retainage.
• Closeout expectations set now, not later: O&M manuals, warranties, attic stock, as-builts, and training.
• How the punch walk will be called and who attends it.

10. Open items and action assignment

• Every unresolved item, with an owner's name and a due date.
• Confirmation of the next meeting.

If you only enforce one rule about this agenda, make it the last section. A precon that ends without named owners and dates on the open items has produced a pleasant conversation and nothing else.

What does a city or public-works preconstruction conference add?

Considerably more procedural detail, and most of it is enforceable. Agency agendas are checklists the inspector works through line by line, and the items are specific in a way private agendas rarely are.

The City of Celina, Texas pre-construction conference agenda is a representative example of the genre. It runs eight pages and covers, among other things: 24-hour advance notice to the city engineer before construction starts; a prohibition on open-cutting public streets; a trench safety plan signed and sealed by a professional engineer; 48-hour notice to residents and business owners before a water shut-off; seven calendar days' lead time to request a temporary road closure; independent materials testing paid for by the contractor, at stated frequencies, with only signed original reports accepted; contractor-paid inspector overtime for Saturday and holiday work; and a final walk with the city inspector that generates the punch list before acceptance.

Federal work follows the same pattern with different subject matter. The Bureau of Land Management's sample preconstruction meeting agenda for right-of-way projects devotes whole sections to environmental compliance monitoring, biological and cultural resource protocols, deviation request procedures, and worker environmental awareness training — items that would never appear on a private tenant-improvement precon.

The lesson for anyone building in an unfamiliar jurisdiction: get the agency's agenda form before the meeting and work through it in advance. Every blank on that form is something you will be asked for in front of an audience.

Preconstruction meeting vs. preconstruction services vs. kickoff meeting

These three get used interchangeably and mean different things.

The meeting is easy. The record is the hard part.

A preconstruction meeting generates a dense hour of commitments: the inspector wants 48 hours before any pour, the architect will turn RFIs in five business days, the owner's rep is the only person who can direct changed work, the utility contractor cannot start until the offsite easement is recorded. Four months later, when a pour gets rejected or an RFI sits for two weeks, the answer to "what did we agree to?" is either in a document or it is a disagreement.

Most teams handle this by asking whoever is least busy to type the minutes, which means the minutes arrive on Thursday, are missing the two side conversations that mattered, and are never reconciled with the schedule or the logs. The research on this is not flattering: FMI and PlanGrid's Construction Disconnected study estimated the cost of bad data and poor communication in US construction at roughly $177 billion a year in labor, with the average person spending about five and a half hours a week just looking for project information.

Pangea is an AI notetaker built for project-based firms rather than for meetings in the abstract. It records the conversation — including in-person ones, with a phone on the table and no bot joining anything, which matters for a precon held in a trailer or at a city counter — writes the minutes in your firm's format, and files the meeting, its decisions, and its documents to the correct project automatically. When someone asks in November what notice the inspector required, you ask the project rather than the person who was in the room, and get an answer with its source cited. It will not fill out the agency's agenda form for you. It makes sure the commitments made against that form are still retrievable when they matter.

It is worth a look if your project knowledge currently lives in three people's memories. There is a 14-day free trial with no credit card, and it is aimed at the coordinator role — the person expected to keep the minutes, the logs, and the PM software all telling the same story.