Site meeting: how to prepare it well and follow up on decisions
Site meeting: how to prepare the agenda, run the discussion and track decisions to keep progress smooth and limit change orders.
💡 In brief
The site meeting is the regular operational meeting that sets the pace of a construction project’s progress. Usually held every week, it brings together the MOE, MOA, OPC and contractors to review progress, clear blockages and settle technical decisions. Its quality directly determines whether the schedule and budget are met. Well prepared, well run and well followed up, it keeps the job site flowing; botched, it breeds misunderstandings, change orders and delays. This article sets out the method for preparing the agenda, running an effective meeting, producing useful minutes and tracing decisions between two meetings.
The site meeting is the regular operational meeting that sets the rhythm of a construction project. It is the moment when the lead designer, the project owner, the OPC and the contractors come together to review progress, clear blockages and settle technical decisions. Its quality directly determines whether the schedule, the budget and the quality of execution are respected. The project lead is its linchpin, and running the meeting is as demanding as managing the technical side of the job site itself.
What is a site meeting and what role does it play in a project?
A site meeting is a regular, periodic meeting that gathers the stakeholders of a construction project on site or in a dedicated room. It serves three combined purposes. The first is to share the actual progress of the works against the planned schedule. The second is to collectively settle the technical decisions that stakeholders cannot make alone. The third is to record the commitments made so that they are honored by the next meeting.
The frequency depends on the phase and size of the job site. On most projects, the weekly meeting is the rule throughout the execution period. On large projects, a meeting every two weeks may complement the weekly contractors’ meeting. Ad hoc meetings are added whenever an urgent decision, a substantial change or a technical conflict requires it.
The attendees vary according to the agenda. The lead design team is always present and chairs the meeting. Contractors holding contracts active during the week are invited. The project owner attends regularly or occasionally depending on needs. The SPS coordinator, the OPC and the inspection body join according to the rhythm of their respective missions.
Summary table of typical site meeting participants
| Participant | Role in the meeting | Main topics covered | Attendance |
|---|---|---|---|
| MOA | Decides on strategic and budgetary matters | Approval of variant choices, change orders, programming | Recurring or occasional |
| MOE | Chairs the meeting and writes the minutes | Technical follow-up, compliance with the project, clearing of reservations | Always |
| OPC | Manages the schedule and coordination between contractors | Progress, milestones, overlapping work, revised schedule | Always |
| Contractors | Report on progress and flag blockages | Technical difficulties, pending decisions, resources | Trade by trade |
| Inspection body | Checks regulatory compliance | Reservations, technical inspection observations | Occasional |
| SPS coordinator | Monitors risk prevention on the job site | Safety, overlapping work, working conditions | Recurring |
How to prepare an effective site meeting
Prepare a structured agenda
A good meeting is 80% preparation. The agenda must be sent to all participants 48 hours before the meeting. Its typical structure is built around the following items:
- Approval of the previous minutes and follow-up of ongoing actions
- Progress by trade, with contractors’ feedback on weekly milestones
- Blocking points identified in advance and decisions expected
- Documents to present or validate (drawings, technical notes, material data sheets)
- Coordination between contractors for the coming week and the overlapping-work zone
- Any other business flagged by participants at least 24 hours beforehand
Set the calendar and sync with the schedule
The meeting must follow a predictable cadence. A fixed weekly slot (for example Tuesday at 9 a.m. on site) makes it easier for everyone to commit and avoids repeated calendar conflicts. A 30-minute site walk before the meeting gives the lead designer a concrete view of progress and feeds the discussions in the meeting room. Synchronization with the reference schedule is the other requirement: every milestone delay must be taken into account and reflected in the project Gantt chart. This systematic update prevents cumulative gaps that end up invalidating the entire planned schedule.
How to run the meeting and produce useful minutes
Disciplined facilitation and controlled duration
A weekly meeting lasts between 60 and 90 minutes depending on the size of the project. Beyond that, attention drops and the quality of decisions suffers. The chair keeps to time by announcing the planned duration of each item right from the start. Digressions are noted for later handling, not pursued during the meeting.
Three facilitation rules keep the meeting productive. First, giving the floor item by item in a predefined order avoids spontaneous interjections that disrupt the discussion. Second, stating each decision aloud and having the stakeholders concerned explicitly confirm it prevents misunderstandings. Third, clearly distinguishing topics that can be decided in the meeting from those requiring further investigation avoids stalling the meeting on an unsolvable point.
Structure of good minutes
The site meeting minutes are the written record of the commitments made. They must be circulated within 48 hours to remain fresh and keep their contractual character. Their typical structure follows the agenda, with for each item discussed: a reminder of the context in one or two sentences, the decision taken or the ruling validated, the person or people responsible for implementation, and the expected deadline.
The minutes name those present and those excused, mention the documents handed over during the meeting and attach the validated documents as appendices. What is not written down does not exist: the rigor of the drafting determines the legal value of the document in the event of a later dispute. Minutes signed by the MOE and tacitly accepted by the other parties (no comment within the allotted time, generally 8 days) become enforceable.
How to follow up on decisions between two meetings
Action plan and progress indicators
The action plan is the operational extension of the minutes. It aggregates the list of ongoing commitments, their owner, their deadline and their status. Kept up to date between two meetings, it directly feeds the “follow-up of previous actions” item of the next meeting.
The most effective practice is to turn every meeting decision into a concrete task. A decision that remains a mere sentence in the minutes is unlikely to be acted on. The same decision converted into a task, with a named owner, a precise deadline and a tracked status, becomes an enforceable commitment. On a collaborative platform, this conversion happens directly: the chair creates the task at the moment the decision is recorded, assigns it to the stakeholder concerned and sets the expected date. The task immediately appears in the owner’s workspace, who updates its progress as things move forward.
This logic of creating tasks linked to decisions removes the gap between the meeting and the action. Each task stays attached to the decision that generated it, which preserves context and makes later decisions easier. At the next meeting, the follow-up is based on the real status of the tasks, not on approximate recollections. The OPC thus has a reliable view of what has progressed, what is blocked and what remains to be handled.
Progress indicators complete this follow-up. Progress by trade, expressed as a percentage, gives a quantified view. Gaps against the forecast show the delays to be made up. Milestones met or missed over the current month flag difficulties to anticipate. These indicators feed the project lead’s dashboard and form the basis of communication with the project owner.
Traceability of decisions and approvals
Some meeting decisions lead to the production or validation of technical documents: revised execution drawings, amended calculation notes, data sheets for substituted products. Each decision must result in a formal deliverable, itself validated through an approval circuit. To understand this validation process and how it fits between the lead design team and the project owner, see our article on works approval and architect approval in BIM projects.
The traceability of these approvals is essential. On a complex job site, several hundred documents go through successive approvals. Without a management tool, finding the history of a decision becomes impossible and exposes you to later disputes. An ISO 19650-compliant DMS meets this need by timestamping every revision and every validation.
Which digital tools to make your site meetings smoother
Live data entry from the field
Mobile tools transform the productivity of job site teams. A site manager who enters observations directly on a tablet from the site, rather than noting them on paper and retyping them in the office in the evening, saves several hours a week. To equip these field uses, the mobile app dedicated to job site teams allows this live entry from the site.
The other advantage of live entry is immediate enforceability. A timestamped, digitally signed observation is formal evidence that is hard to contest after the fact. This discipline reduces disputes in meetings and speeds up decision-making.
Document centralization and notifications
Document centralization prevents project documents from being scattered. A drawing shared as an email attachment, copied several times and modified without traceability quickly becomes a source of errors. A centralized platform with a single version repository ensures that every participant works on the right document.
Connectors between tools reinforce this centralization by eliminating re-entry. For job site minutes, the integration between the there drafting solution and the Kroqi platform illustrates this gain concretely. The minutes produced in there are sent directly to a Kroqi collaborative project, with no manual PDF export, no manual upload and no re-entry from one tool to the other. Drafting the document and centralizing it thus happen in a continuous chain, which reduces wasted time and the risk of error between producing the minutes and distributing them to the stakeholders concerned.
Notifications complete this centralization. A stakeholder informed in real time of a drawing update, an assigned decision or published minutes can react immediately without waiting for the next meeting. This fluidity shortens decision times and limits prolonged blockages.
How BIM transforms the dynamics of meetings
The model as a shared visual aid
BIM enriches the running of a site meeting without breaking with existing practices. The digital model projected during the meeting complements the 2D drawings, which remain the reference medium for many stakeholders and many operations. Rather than pitting the two formats against each other, a modern platform lets you move from one to the other, find in the 3D model the area viewed on a drawing, and conversely generate a section or a 2D view from the model.
This interplay between 2D and 3D reflects the reality of the field. Most stakeholders still work day to day with two-dimensional drawings, which they master perfectly. 3D does not replace this use: it adds a layer of shared understanding, particularly useful for complex topics or for stakeholders less familiar with reading technical drawings. The strength of a good platform lies in its ability to let the two formats work together without forcing an abrupt switch.
This shared visualization has three advantages. First, it makes discussions understandable for all stakeholders, including those who find it harder to interpret a technical drawing. Second, it avoids location ambiguities, since you point directly at the element concerned, whether on the 2D drawing or in the model. Third, it eases decision-making by showing the spatial consequences of a decision before it is made.
Collaborative annotation and validation workflow
Annotations on the model are formalized using the BCF (BIM Collaboration Format) standard. A remark made in a meeting becomes a BCF issue positioned precisely on the element concerned, with a text, an author, a date and a status. All stakeholders receive this issue in their working tool and can reply, propose a solution or mark it as resolved. To understand how this workflow fits between project stakeholders, see our article on the BIM workflow between architects, engineering offices and MOE.
The combined effect of the shared model and the BCF workflow transforms the traceability of decisions. Where a Word document listed decisions in text form, BIM anchors each decision in the geometry of the building. The minutes are still produced, but they are now backed by a layer of information directly linked to the model, usable all the way into the operation phase.
Want to see Kroqi in action?
Leave us your details: a member of the team will get back to you for a demo or to answer your questions.
