The first real meeting between the government team and the contractor team. Set the tone, align on how the contract will actually be administered, and walk out with a clean written record everyone can point to later.
A preconstruction conference is a formal meeting held after contract award, before the contractor mobilizes and begins physical work, where the government team and the contractor team walk through how the contract is going to be administered. It is part orientation, part alignment, part written record.
The focus of the meeting is the mechanics of the contract as it already exists: who talks to whom, what paperwork flows when, how submittals get routed, how invoices get processed, how safety gets handled, how changes get requested, how quality control gets documented. The contract terms stay the contract terms. Partnering sessions, design reviews, and contract modifications all have their own forums and should not ride along on the precon agenda.
The clause that makes contractor attendance at a preconstruction conference mandatory is FAR 52.236-26, Preconstruction Conference. It is prescribed at FAR 36.522 and is used in solicitations and contracts for construction when the contracting officer determines a preconstruction conference is necessary.
The clause is short. It requires the contractor to attend a preconstruction conference at a time and place designated by the contracting officer, after contract award and prior to the start of work. That is the full contractual hook. Everything else about how the meeting is run is a matter of practice, spec section, and local procedure.
Many construction contracts also carry a project meetings spec section that separately requires the contractor to participate in a preconstruction conference and sets more detailed expectations about agenda items and documentation. That spec section, when it exists, is usually the more operationally useful reference during the meeting itself. Check the project specifications on your specific contract.
The right people at the preconstruction conference are the people who will actually administer the contract. Not proxies, not stand-ins, not optional delegates. The point of the meeting is to align decision-makers, so decision-makers need to be there.
| Role | Side | Why they need to be there |
|---|---|---|
| Contracting Officer | Government | Only person who can speak for the contract. Runs the meeting or delegates that role deliberately. |
| Contracting Officer's Representative (COR) | Government | Day-to-day point of contact. Needs to hear everything first-hand, not second-hand. |
| Project Engineer / Resident Engineer | Government | Technical authority on site. Answers design and field questions that come up during the meeting. |
| Contractor Project Manager | Contractor | Owns the project for the contractor. Commits to schedule and process in the meeting. |
| Contractor Superintendent | Contractor | Runs the field. Needs to hear site-specific rules, access, security, safety firsthand. |
| Quality Control Manager | Contractor | Owns the QC plan and inspection process. Needs to commit to the QC workflow in front of the CO. |
| Site Safety and Health Officer | Contractor | Owns safety. Walks through the Accident Prevention Plan and activity hazard analyses. |
| User / Installation Representatives | Government | Facilities, civil engineering, security, safety, environmental. Anyone whose operations the work affects. |
Key subcontractors are often invited, at least the ones with significant scope and schedule weight. They can be excluded to keep the meeting tight, but their absence should be a deliberate choice, not an oversight.
An agenda is a discipline. It keeps the meeting moving, it keeps topics from getting skipped, and it gives the minutes a clean spine to hang on later. Walk through the items in order, document each one, move on.
A reasonable baseline agenda for a federal construction preconstruction conference:
Minutes are the authoritative record of the preconstruction conference. If something is not in the minutes, for all practical purposes it did not happen at the meeting. That is why minutes need to be taken carefully, distributed promptly, and finalized deliberately.
Good minutes capture the agenda structure, the names and roles of attendees, the key points discussed under each agenda item, any action items with owners and due dates, and any open items still pending. They do not try to transcribe the conversation word for word. They summarize the substance and capture commitments.
The typical workflow is that draft minutes go out within a few business days of the meeting, the contractor has a short window to review and comment, any disagreements about what was said or decided get resolved, and then the CO finalizes and distributes. Once finalized, the minutes become the reference point if a dispute later turns on what was said at the precon conference.
The preconstruction conference is one of those events where the failure modes are predictable once you have seen them a few times.
| Mistake | Why it hurts |
|---|---|
| Treating it as ceremony. Skipping the substance because everyone is excited the contract is awarded. | The meeting is the last easy chance to align before mobilization. Skipping the substance means the alignment happens later, under pressure, in the middle of a problem. |
| Wrong people in the room. Sending a delegate instead of the actual decision-maker. | Commitments made by someone who cannot commit are not commitments. The meeting has to be redone in substance even if not in name. |
| No written agenda. Winging it and hoping the conversation covers everything. | Items get skipped. Minutes are hard to structure. The contractor has no way to prepare. |
| Letting it drift into direction. The CO says something in the meeting that amounts to telling the contractor to do something different from the contract. | That is a constructive change. It creates a claim posture and documents it in the meeting minutes. Keep direction in formal channels. |
| Loose minutes. Failing to capture what was decided, or failing to distribute for comment. | The record becomes contested. If the meeting turns into a dispute exhibit later, bad minutes hurt the government. |
| Confusing it with other meetings. Running a partnering session, a design review, or a progress meeting under the precon label. | Different purposes, different rules, different attendees. Combining them muddies the record and weakens each meeting. |
There is no government-wide mandatory form for a preconstruction conference. No SF, no DD Form, no standard template prescribed by the FAR. The contractual hook is FAR 52.236-26, and the operational requirement usually comes from a project meetings spec section if the contract has one. Neither prescribes a specific document format.
The typical documentation package from a precon meeting is a written agenda, a sign-in sheet, meeting minutes, and any handouts or references distributed at the meeting. Many installations have local templates for precon minutes. Those are helpful and should be used when available, but the absence of a mandatory form means the CO has latitude in how the meeting is documented. Use that latitude to produce clear, complete, finalized minutes.
Fictional project used throughout the sample: Ironcrest Construction, Contract W91234-26-C-0055, Building 742 Roof Replacement. Award date 10 April 2026. Preconstruction conference set for 24 April 2026, 0900 local, Building 100 Conference Room B.
Date: 24 April 2026, 0900–1130
Location: Building 100, Conference Room B
Chair: Contracting Officer, Jamie Ruiz
The following is an excerpt from the finalized minutes of the same meeting. Notice how decisions and commitments are captured without converting discussion into direction.
Five scenarios on preconstruction conferences. Pick the best answer and check it.
You are reviewing a small construction contract for a minor repair project and want to confirm whether the contractor is contractually required to attend a preconstruction conference. Which clause answers that question?
The preconstruction conference is scheduled for Monday at 0900. On Friday afternoon, the contractor PM sends a note saying she cannot attend and will send a junior site coordinator in her place. The coordinator was not previously identified as a decision-maker on the project and has no authority to commit the contractor to schedule or process decisions. What is the best CO response?
Midway through the preconstruction conference, the contractor PM raises a technical spec section and asks whether the government will accept an alternate approach that would reduce cost and shorten schedule. The alternate is within the contractor's capability but would require modifying the specification. What is the right way to handle it at the meeting?
Three months into performance, a dispute arises over whether the contractor was directed at the preconstruction conference to use a specific sequencing approach that is now causing schedule impact. The contractor insists the direction was given verbally. The government insists no such direction was given. The meeting minutes are silent on the sequencing issue. What is the practical effect?
A senior PM at the installation suggests running a full day partnering workshop and labeling it the preconstruction conference, with facilitated exercises on team dynamics, conflict resolution, and shared goals, and with only brief coverage of the contract administration agenda. The idea is to save time by combining both events. What is the concern from a contracting officer perspective?