The Pre-Construction Meeting: A Working Agenda That Catches Problems Before They Cost Money
The pre-construction meeting — sometimes called the preconstruction conference or kickoff meeting — is the formal alignment meeting before construction starts. Owner, architect/engineer, GC, and key subs meet to review the project, confirm understanding, establish communication protocols, and commit to how the project will run. Done well, it surfaces misalignments that would otherwise emerge as disputes three months later.
A perfunctory pre-construction meeting — showing up to check a contract box — is a missed opportunity. The meeting is the one time all the key parties are together with fresh attention, and the issues that aren't addressed there tend to surface inconveniently later.
The core attendee list for a substantive pre-con meeting:
Pre-construction meeting attendees
- Owner or owner's representative (decision-maker for the owner)
- Architect or engineer of record
- Key design consultants (structural, mechanical, electrical if the project warrants)
- GC's project executive (senior decision-maker)
- GC's project manager (day-to-day lead)
- GC's superintendent (field lead)
- Major subcontractors' project managers (mechanical, electrical, structural typically; others as the project requires)
- Jurisdictional inspectors or contacts for large or public projects
- Bonding and insurance representatives for bonded projects
The meeting is most productive when the attendees have authority to make commitments, not just gather information. A project executive who attends and commits to procedural approaches is more valuable than a coordinator who attends and reports back.
Start with scope confirmation. Walk the contract documents, confirm what's in and what's out, and surface any areas where participants have different understandings. On a $15M project, it's routine to find 3-5 scope ambiguities at the pre-con meeting — things that the contract arguably covers or arguably doesn't, that different parties interpreted differently.
Resolving these at pre-con — either by clarifying the contract, by change order, or by written agreement noting the interpretation — is cheaper than resolving them mid-project when the misalignment has already caused work to be performed under contested interpretations.
Review the baseline schedule. Confirm key milestones (mobilization, foundation complete, enclosure, substantial completion, occupancy). Walk through the long-lead items (equipment, materials) and confirm procurement lead times align with the schedule. Identify risks to the schedule and discuss mitigation.
Submittal-driven scheduling gets specific attention here. For every long-lead equipment item, trace backward: when does it need to be on site → when does it need to ship → fabrication lead time → submittal approval needed by → submittal submission needed by. Missing submittal deadlines is one of the most common causes of schedule slippage, and the chain from delivery to submittal is what determines the real schedule discipline.
Communication topics for the pre-con agenda
- RFI protocol — format, submission method, routing, response timeframe
- Submittal protocol — format, expected turnaround, review team composition
- Change order process — who initiates, how proposals are priced, approval thresholds, timing
- Daily reports — format, distribution, who reviews when
- Weekly meetings — schedule, attendees, standard agenda
- Emergency contacts — after-hours contacts for owner, architect, GC, key subs
- Notice requirements — written notice protocols for time extensions, DSC claims, and similar
- Electronic tools — project management platform (Procore, PlanGrid, etc.), access provisioning, training
The goal is to surface any disconnects in expectations. If the GC expects 14-day submittal turnaround and the architect expects 21 days, confirm which the contract requires and how it'll be enforced. If the owner wants daily photo updates and the GC hadn't planned to provide them, resolve it at the pre-con.
Pay application mechanics deserve explicit discussion:
Pay application topics for pre-con
- Billing cycle (typical: monthly with specific cutoff dates)
- Review timeline (days for architect review, days to owner payment)
- Format (AIA G702/703, or custom format)
- Schedule of values review and approval status
- Backup requirements (lien waiver forms, certified payroll on prevailing wage jobs, stored materials documentation)
- Retention percentage and release mechanics
- Lien waiver forms (what form is required, from what parties, conditional vs unconditional timing)
- Stored materials billing rules (on-site only, or off-site allowed; bonded or unbonded)
Pay application disputes are one of the most common sources of mid-project friction. Aligning on the mechanics at the pre-con prevents months of push and pull about what backup is required, what lien waiver form is acceptable, and how long review should take.
One specific discussion that pays off: walk through the first expected pay application in detail at the pre-con. What will it bill? What backup is needed? What review process will it go through? This exercise tends to surface procedural ambiguities before any real money is at stake.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Safety Program
Review the project's safety program. Confirm who has overall safety responsibility (typically the GC). Review incident reporting procedures, near-miss protocols, site-specific hazards (fall protection, excavation, confined space, traffic control), and sub-level safety obligations.
Confirm OSHA posting requirements, weekly or daily toolbox talks, personal protective equipment (PPE) standards, and authority to stop work for safety reasons. On projects with specific safety overlays (wrap-up insurance requirements, owner safety standards), those get walked through too.
Site logistics — where trucks enter, where materials stage, where crews park, where the office trailer goes, where dumpsters sit — need concrete decisions. A sketch showing the site layout agreed at pre-con prevents later arguments about where subs can set up.
Site logistics topics
- Truck access and circulation
- Staging and laydown areas by trade or phase
- Office trailer, material storage, and toilet locations
- Crane or hoisting location (if applicable)
- Traffic control (street closures, pedestrian protection, delivery windows)
- Utilities (temporary power, water, telephone, internet)
- Security and fencing
- Material deliveries and acceptance protocol
- Parking (workers, visitors, owner representatives)
- Waste management and debris removal
Confirm that all required insurance certificates, additional insured endorsements, and bonds are in place — or on a specific schedule to be in place before work begins. This is often the pre-con meeting's most immediate action item: any missing coverage or bond must be resolved before mobilization.
On wrap insurance projects (OCIP/CCIP), walk through enrollment status for each sub, the monthly reporting protocol, and the claims procedure. Confirm that subs not yet enrolled will enroll before starting work.
A productive pre-con meeting produces specific outputs:
Outputs from a well-run pre-con
- Meeting minutes distributed to all attendees within 48 hours
- List of action items with owners and dates
- Resolved scope ambiguities (via clarification memos or change orders)
- Confirmed baseline schedule with agreed milestones
- Written communication protocols (email contacts, PM platform accounts, meeting schedules)
- Signed agreement on specific procedural points discussed
- Calendar of upcoming events (first pay app submission, first weekly meeting, inspection schedule)
- Insurance and bond verification status
The pre-construction meeting is the project's highest-leverage alignment opportunity. A thoughtful agenda walking through scope, schedule, communications, pay applications, safety, site logistics, and insurance catches misalignments when they're cheap to resolve. A checkbox-exercise pre-con that doesn't address substance produces projects full of avoidable mid-project friction. The meeting is a few hours of senior-level time; done well, it saves dozens of hours of downstream dispute resolution.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts