A pre-con meeting agenda is a structured list of topics and discussion points used to align all parties before a construction project begins, typically covering scope, schedule, safety, and communication protocols. This meeting, often called a pre-construction or pre-job conference, is the critical bridge between contract signing and field work, ensuring everyone from the owner to subcontractors understands their roles and the project’s ground rules.
Purpose and Importance of the Pre-Con Meeting
The pre-construction meeting is not a formality; it is a risk-management tool. Its primary purpose is to prevent misunderstandings, delays, and disputes by establishing clear expectations before work starts. For the general contractor, it is a chance to introduce the project team, confirm the schedule is realistic, and verify that all necessary permits and insurance are in place. For the owner, it is the opportunity to meet the key players, understand how communication will flow, and clarify how changes will be handled. For subcontractors, it clarifies site logistics, safety requirements, and payment procedures. Skipping this meeting or treating it as a quick chat is a common mistake that often leads to confusion about change orders, payment timelines, and safety protocols later on.
Who Should Attend
The attendee list should include anyone with decision-making authority or a direct role in daily project execution. A typical list includes:
- The project owner or owner’s representative
- The general contractor’s project manager and superintendent
- The project architect or design representative
- Key subcontractors (electrical, plumbing, HVAC, etc.)
- The health and safety officer
If the project is large or complex, the meeting may be split into two sessions: one for management-level topics (contracts, schedule, financials) and one for field-level topics (safety, logistics, daily coordination). In smaller projects, a single meeting with all parties is sufficient. The key is that every attendee should have the authority to make commitments on behalf of their company.
Core Agenda Items
A well-structured agenda should be distributed in advance, so participants can prepare. The following items are the backbone of any pre-con meeting:
- Project Scope Review: Walk through the contract documents, drawings, and specifications to confirm everyone’s understanding of the work. Highlight any areas that are ambiguous or have changed since bidding.
- Schedule and Milestones: Review the overall project timeline, including start and completion dates, major milestones, and any phasing requirements. Discuss how delays will be reported and what constitutes a valid reason for an extension.
- Communication Protocols: Establish the chain of command for daily questions, Requests for Information (RFIs), and change orders. Define who approves what and the expected response times.
- Safety and Site Rules: Review the site-specific safety plan, emergency procedures, and any relevant OSHA requirements. Confirm that all workers have the required training and that the site is secure.
- Quality Control and Inspections: Identify which inspections are required, who schedules them, and what documentation is needed. Discuss the process for addressing deficiencies.
- Payment and Billing Procedures: Clarify the schedule of values, how pay applications are submitted, and the timeline for payment. Also discuss how change orders will be priced and approved.
- Logistics and Site Access: Cover parking, deliveries, storage areas, temporary utilities, and housekeeping rules. Also discuss working hours and noise restrictions.
Each item should be discussed with enough detail that all attendees leave with a clear understanding of their responsibilities. It is common to assign action items during the meeting, with a designated person and a due date for each.
Common Problems and How to Avoid Them
Even with a solid agenda, pre-con meetings can go sideways. One frequent issue is the meeting being too long or too detailed, causing attendees to lose focus. To avoid this, keep the meeting to under two hours if possible, and stick to the agenda. Another common problem is the absence of key decision-makers. If the owner’s representative cannot approve a change order, the meeting’s value drops significantly. Make attendance mandatory for all parties with approval authority. A third issue is the meeting becoming a design review session. If design questions arise, note them and schedule a separate design meeting rather than derailing the pre-con. Finally, a lack of follow-through is a major pitfall. The meeting minutes should be distributed within 48 hours, and all action items should be tracked until closed.
Pre-Con Meeting Template
| Agenda Item | Discussion Points | Action Item | Owner | Due Date |
|---|---|---|---|---|
| Scope Review | Confirm all drawings and specs | Resolve ambiguities | PM | Before start |
| Schedule | Milestones, phasing, delays | Update master schedule | Superintendent | Week 1 |
| Communication | Chain of command, RFI process | Distribute contact list | PM | Day 1 |
| Safety | Site rules, emergency plan | Conduct orientation | Safety Officer | Before start |
| Quality | Inspection schedule | Book inspections | QC Lead | Week 1 |
| Payment | Schedule of values, billing | Submit first pay app | Accountant | Month 1 |
| Logistics | Parking, deliveries, storage | Post site rules | Superintendent | Day 1 |
Sample (fictional): For a small office renovation, the PM would list “Confirm HVAC layout” under scope, assign it to the HVAC sub, and set a due date of the following Friday.
How to Prepare and Run the Meeting
Preparation is the key to a successful pre-con. The general contractor should send the agenda at least a week in advance, along with any relevant documents like the master schedule and safety plan. During the meeting, use a projector to display the agenda and take notes directly on it, so everyone can see what is being recorded. This keeps the meeting transparent and helps avoid disputes about what was said. After the meeting, send a formal set of minutes that includes all decisions, action items, and a list of attendees. These minutes become a reference document for the entire project. It is also wise to schedule a follow-up meeting for complex projects, perhaps after the first month, to address any early issues.
Frequently Asked Questions
What is the difference between a pre-con meeting and a kickoff meeting?
They are often the same thing, but a kickoff meeting is more general and may be held with a larger audience to celebrate the start of a project. A pre-con meeting is more focused on operational details, contracts, and logistics. In practice, many projects combine the two into one comprehensive meeting.
How long should a pre-con meeting last?
For a typical project, 1.5 to 2 hours is sufficient. Larger, more complex projects may require a half-day, especially if there are multiple phases or many subcontractors. The key is to keep the meeting focused on the agenda and not let it drift into unrelated discussions.
Can a pre-con meeting be held virtually?
Yes, virtual pre-con meetings are common, especially for projects with remote stakeholders. Video conferencing works well for discussions, but you must ensure that all documents are shared in advance and that the meeting is recorded for those who cannot attend. However, a virtual meeting may be less effective for site-specific logistics, so a site walk-through might be scheduled separately.
What happens if a subcontractor does not attend the pre-con meeting?
Attendance is usually mandatory per the contract. If a subcontractor misses the meeting, the general contractor should reschedule or hold a separate orientation for that sub. It is not acceptable to proceed without the sub understanding the site rules and schedule, as that could lead to safety or coordination issues.
Is a pre-con meeting required by law?
In many jurisdictions, a pre-construction meeting is required for public works projects or for projects with certain safety requirements, such as those involving hazardous materials. For private projects, it is not typically a legal requirement, but it is almost always a contractual requirement. Even if not required, it is a best practice that saves time and money.