How to Run a Construction Site Meeting That Actually Saves Time

Site meetings are a standard part of construction project administration. They're also one of the most reliably unproductive rituals in the industry — too long, too unfocused, and too rarely followed up.

A well-run site meeting is a decision-making forum. A poorly run one is a status update that everyone already knew.

The purpose of a site meeting

A site meeting has three legitimate purposes:

Resolving issues that can't be resolved by correspondence
Making decisions that require multiple parties in the room
Creating a formal record of decisions, instructions, and outstanding items

Status updates — where each trade reports what they did last week — are not a legitimate purpose of a formal site meeting. They belong in a site report, not a meeting.

A format that works

Attendees: Keep the attendee list to people who are either making decisions or directly responsible for items on the agenda. A meeting with twelve people where four are relevant is a four-person meeting with eight observers who will check their phones.

Pre-circulated agenda with items numbered: Distribute the agenda at least 24 hours before the meeting. Items should be numbered, and each should be tagged as: decision required, information only, or update only. This lets attendees prepare and gives the chair a basis for keeping the meeting on track.

Time-boxed agenda: Allocate a specific time to each item. A one-hour meeting with eight agenda items and no time allocation will run for two hours with three items unresolved.

One-week look-back, two-week look-ahead: The substantive programme discussion should cover two things: what actually happened in the past week against what was planned, and what needs to happen in the next two weeks. The two-week look-ahead is where resource and sequencing decisions are made.

Outstanding items register: Every meeting generates outstanding items — questions, approvals pending, information required. These should be recorded in a register that's carried from meeting to meeting, with an owner, a due date, and a status. Items that appear on the outstanding items register for three consecutive meetings without resolution are a signal that something is stuck.

Minutes within 24 hours: Minutes issued a week after the meeting have lost most of their value. The decisions made in the meeting need to be documented while they're still fresh, and instructions need to be confirmed in writing before the relevant work proceeds.

What makes site meetings go wrong

No pre-circulated agenda: If attendees don't know what's being discussed, they can't prepare. Meetings without agendas become conversations.

Decisions deferred to the next meeting: "We'll discuss that next week" is a programme risk. If a decision is needed before the next meeting to keep the work moving, it needs to be made before the next meeting.

Meeting minutes as a narrative: Minutes that read as a story of the meeting provide poor records. Minutes should be structured — agenda item, discussion summary, decision, action item with owner and due date.

Too many attendees with no voice: Every person in the meeting room whose presence is irrelevant to the agenda items makes the meeting less efficient. Observe this principle consistently and attendance lists shrink to the right size.

The link between meetings and programme

The most efficient construction meetings are the ones that directly drive programme outcomes. When the two-week look-ahead produces specific commitments — Trade A will complete slab prep by Wednesday, Trade B will mobilise Thursday, the structural engineer RFI will be answered by Tuesday — the meeting has a direct connection to what happens on site.

When the two-week look-ahead produces vague statements — "we'll try to get the slab done" — the meeting has no connection to programme management. It's just talk.

Meeting facilitation and site administration is part of our Project Oversight and Full PM Partnership services. Get in touch if you'd like to discuss how we structure site meetings on active projects.