Pre Construction Meeting for General Contracting

Open the contract, project handoff summary, and any owner communications to see what topics must be addressed before construction starts (for example, communication protocols, submittal procedures, safety requirements). Note any contract-required meeting topics.

List the decisions you need from the owner and design team to move forward, such as approval of communication channels, site access hours, parking arrangements, and any special inspection or testing requirements.

Meet briefly with the project manager, superintendent, and pre-construction lead to ask what they want to get out of the meeting (for example, clarity on design expectations, logistics constraints, or open RFIs). Add these to your list.

Separate the list into items that absolutely must be resolved or aligned at this meeting and items that can be addressed later if time runs short. This will guide your agenda structure.

Draft a one-paragraph statement describing the purpose of the preconstruction meeting and the main outcomes you are aiming for. Use this as the anchor for your agenda and invitation message.

Store your objectives list and statement in a “Preconstruction Meeting” folder in the project directory so you and others can reference them while planning and preparing materials.

Based on the contract and objectives, list the organizations that should attend: owner/client, architect, key engineers, general contractor team (project management, superintendent, safety, pre-con), and possibly key consultants (for example, commissioning, testing).

Within each organization, decide which individuals should attend. Aim for people who can speak for their group and make decisions or at least commit to getting answers quickly.

Decide who will act as meeting lead, who will present schedule and logistics, who will cover safety, and who will take minutes and track action items. Confirm that each person understands their role.

Reach out informally or check calendars for the owner’s main contact and the architect’s project manager to see what dates and times generally work for them. Avoid scheduling without understanding their availability.

Identify people who might benefit from attending but are not critical (for example, certain subcontractors or internal support staff). Mark them as optional so you can include them without making attendance mandatory.

Create a simple attendee and role list and save it in the “Preconstruction Meeting” folder. This list will be used when sending invitations and building the agenda.

Use your company’s standard preconstruction meeting agenda or, if one does not exist, outline typical sections such as introductions, project overview, schedule, communication, submittals, safety, logistics, quality, and next steps.

Using your objectives list, add specific topics that must be covered for this project (for example, occupied facility constraints, night work, special inspections, commissioning requirements). Place “must cover” items earlier in the agenda.

Next to each agenda item, assign a person responsible for leading that topic and estimate how much time it should take. Make sure the total agenda fits within a reasonable meeting length (often 1.5–3 hours).

Add short Q&A segments after major sections and reserve a brief period near the end for any additional questions or items not covered elsewhere.

At the top of the agenda, include date, time, location or meeting link, dial-in information, and a list of expected attendees or organizations.

Save the agenda as a dated document (for example, “Precon Meeting Agenda – 2026-02-10 – Draft”) in the project folder. Plan to update it after internal review before sending to external parties.

Based on your understanding of key attendees’ availability, propose two or three possible meeting slots that allow enough time for a full agenda. Try to avoid obvious conflicts like holidays or known major events.

Send a short message to the owner’s primary contact and the architect’s project manager with your proposed options. Ask them to confirm which option works best or propose an alternative if needed.

Once a date and time are agreed, reserve an appropriate conference room with screen and audio, or create a video meeting link with dial-in details. Test the link to ensure it works.

Update the agenda with confirmed date/time and any minor adjustments, then save it as the current version (for example, “Precon Meeting Agenda – 2026-02-25 – Final”).

Create a calendar event including the agenda and any key pre-reading materials (for example, project overview, high-level schedule). Invite all required and optional attendees, and ask them to review the agenda beforehand.

Monitor who accepts or declines. If any critical person cannot attend, consider whether you need to reschedule or if a delegate can attend. Communicate any changes promptly and update the invite and agenda if needed.

Based on the agenda, create a slide or section outline including: project overview, team introductions, schedule milestones, communication plan, submittal/RFI procedures, safety expectations, site logistics, quality control, and next steps.

Collect current schedule snapshots, site plans, logistics sketches, communication protocols, and any relevant procedures. Use the latest approved information to avoid presenting outdated details.

Build slides that are clear and not overly dense. For site logistics and safety, include simple diagrams of site access, fencing, laydown, and emergency routes. Prepare handouts if needed for complex topics (for example, submittal workflow diagrams).

Have the project manager and superintendent review the slides and materials to check for accuracy and practicality. Adjust any content that is unclear or does not match how the project will actually be run.

Decide whether attendees will receive printed handouts or digital copies. Prepare enough printed sets or arrange to email a PDF pack shortly before or after the meeting.

Before the meeting, load the slides onto the meeting room computer or test screen sharing in the virtual platform. Make sure file names are obvious and easy to find so you can move through the presentation smoothly.

Book a 30–60 minute internal prep huddle a day or two before the main preconstruction meeting. Invite the project manager, superintendent, pre-construction lead, safety representative, and anyone presenting major sections.

Review each agenda item and slide section together. Confirm who will speak to each topic and in what order. Make notes on any areas where you expect tough questions or deeper discussion.

Discuss how you will respond to likely questions about schedule flexibility, change management, scope boundaries, or site constraints. Agree on consistent answers so different team members do not give conflicting information.

Note any questions you cannot yet answer clearly. Assign someone to gather missing information or confirm details (for example, specific inspection procedures or owner’s preferred communication format) before the main meeting.

Confirm who will bring a laptop, who will manage screen sharing, and how you will handle remote participants. Test the meeting link or room equipment briefly if possible.

At the end of the prep huddle, recap any follow-up tasks, who owns them, and deadlines. Ensure all materials will be ready and everyone knows when to arrive for the preconstruction meeting.

Be in the room or online 10–15 minutes early. Set up the projector or screen share, test audio, and lay out sign-in sheets or printed materials if used. Greet attendees as they arrive.

Begin by welcoming everyone, having participants briefly introduce themselves and their roles, and stating the meeting objectives. Confirm that the agenda works for everyone and adjust only if absolutely necessary.

Move through agenda items in order, keeping an eye on time. Gently steer discussions back on topic if they digress. For complex issues that cannot be resolved quickly, create a parking lot item and assign a follow-up instead of derailing the whole meeting.

Invite questions at logical points, especially after explaining important procedures like RFIs, submittals, safety, and logistics. Restate key expectations in plain language to confirm understanding.

At the end of each major section, verbally recap any decisions made and actions agreed upon. Confirm who is responsible and, if possible, the target timeframe for each action.

End by reviewing the main outcomes of the meeting, outlining immediate next steps (for example, updated schedule, action item log, follow-up meetings), and thanking everyone for their participation. Confirm how and when minutes will be distributed.

Start from a standard minutes template that includes sections for attendees, agenda items, discussion summaries, decisions, and action items. This keeps notes organized and easy to read.

As the meeting proceeds, capture key points under each agenda item. Focus on decisions, commitments, and issues raised rather than trying to transcribe every word.

When a decision is made, write it down in simple, complete sentences, including any conditions or caveats. Note who agreed and any deadlines attached to the decision if relevant.

Whenever follow-up work is identified, add an action item with a clear description, the responsible person or organization, and a target date if one was discussed. Avoid vague actions without owners.

Right after the meeting, review your notes and fill gaps while the discussion is fresh. If something is unclear, ask the project manager or another attendee for clarification before finalizing the minutes.

Save the draft minutes document in the project folder under a clear name (for example, “Precon Meeting Minutes – 2026-02-25 – Draft”) ready for review and distribution.

Have the project manager quickly review the draft minutes for accuracy and completeness. Make any edits they request, especially for decisions and commitments that could affect contractual matters.

If there are many actions, create a simple action log table that can be updated over time, rather than leaving actions buried only in the minutes. Link this log to the minutes for context.

Export or save the minutes as a PDF so formatting is preserved and the document cannot be easily altered. Ensure the file name clearly shows the meeting date and “Final” status.

Send the minutes and any separate action log to all meeting attendees and other key stakeholders who need to stay informed. In the email, briefly highlight major decisions and critical action items.

Attach or upload the minutes to the meeting records or document section of your project management platform so anyone on the team can find them later.

Note the date the minutes were issued and to whom, either in the minutes file or in a simple meeting log. This creates a record in case there are future disputes about what was communicated and when.

Take all action items from the minutes and add them into your preferred tracking tool (spreadsheet, project management system, or action log). Include description, owner, due date, and status fields.

Verify that each action item has a clearly named owner. If any owner was not present in the meeting, inform them of the action and confirm they understand what is needed and by when.

Schedule a short recurring review (for example, weekly) to go through the action log with the project manager and, as needed, other team members. Update statuses and remove items that are completed.

For actions that pass their due dates without completion, follow up directly with the owner to understand what is blocking progress and what support they need. Adjust dates or reassign ownership if appropriate.

When an action item results in a change to a plan (for example, updated logistics plan, revised schedule, or clarified procedure), make sure those documents are updated and shared with the team.

Before site mobilization, check that all critical preconstruction action items are completed or have a clear plan in place. Note any remaining open items in a short summary so the field team understands what is still in progress.