Site meeting design: making responsibilities clear
Admin · 22 October 2026
Illustrative image. Photo by Cherrydeck on Unsplash. Unsplash License.
A site meeting earns its place when it helps the project make decisions or coordinate work that participants cannot resolve effectively on their own. A recurring calendar invitation does not establish that purpose. Meetings can become a sequence of status reports in which everyone speaks but nobody leaves with a clearer commitment. Designing the meeting around decisions and responsibilities makes its value easier to assess.
For project managers and supervisors, the task is to connect the right people, current evidence and a defined outcome. Some questions belong in a short coordination conversation; others need technical review or formal authority. A good meeting process recognises those boundaries and provides a route for the issue rather than attempting to solve every matter in the room.
Give the meeting a specific purpose
State what the meeting is intended to produce. This could be agreed near-term commitments, decisions on open interfaces or a review of consequential exceptions. Avoid defining the purpose merely as discussing progress. A clear output helps the chair decide what belongs on the agenda and helps participants prepare the information required.
Review recurring meetings periodically. If the intended decisions now happen elsewhere, change or remove the duplication through the project’s management arrangements. A meeting should not continue unchanged solely because it existed at mobilisation. Its format and frequency need to reflect the current work and interfaces.
Identify the decision owners
For consequential items, establish who can make the decision and what input they need. Attendance by an organisation does not mean its representative has authority to approve every request. If the relevant decision maker cannot attend, agree how the matter will be referred and by when. The meeting can still prepare a recommendation without presenting it as approval.
Distinguish accountable ownership from contribution. Several disciplines may need to provide information, but one named person should coordinate the response to an action. A broad allocation to all contractors leaves the next step unclear. Record contributors where necessary and identify the person responsible for assembling the outcome.
Prepare issues with enough evidence
Ask participants to describe the issue, its consequence and the decision or support required. Include relevant references and current information rather than a large unstructured attachment. The people receiving the request should be able to understand why the matter is on the agenda and what they can reasonably do about it.
Check whether essential information is available before expecting a decision. The chair should not pressure participants to approve an arrangement they have not had an appropriate opportunity to assess. Where evidence is incomplete, define the action to obtain it and the effect on the programme. An honest unresolved status is more useful than ambiguous consent.
Separate reporting from coordination
Use concise pre-read information for routine status where the project arrangements allow. Reserve discussion for exceptions, dependencies and decisions. Reading a report aloud can consume time without changing anyone’s understanding. At the same time, do not assume a pre-read was understood; identify the specific points requiring confirmation or challenge.
A hypothetical weekly meeting includes ten packages, each giving a general progress account. One unresolved handover affects several of them but receives little attention. Reframing the agenda around the shared handover gives the participants a common problem to resolve. The useful outcome is a coordinated next step, not equal speaking time for every package.
Use precise action statements
An action should identify the output, owner and required date. Replace vague wording such as liaise with the supplier with the question to be answered or information to be obtained. The owner needs to know what completion looks like. A date should connect to the affected work rather than default to before the next meeting regardless of consequence.
Record dependencies between actions. If one person’s response needs another’s input, make that relationship visible. This helps the chair identify why an action is not progressing and direct escalation appropriately. Without it, the same item may be repeatedly marked overdue while the owner lacks the information or authority to complete it.
Keep decisions distinct from observations
Participants may express a preference, raise a concern or recommend an option without making an authorised decision. The record should preserve those distinctions. A comment that an arrangement appears workable is not necessarily permission to procure or install it. Clarify the intended outcome before the meeting moves on.
The APM overview of change control provides general context for evaluating changes to an approved basis. Construction meetings should remain connected to the actual governance and contractual procedures. A minute should not casually substitute for a required approval or instruction through another route.
Chair the discussion toward a usable outcome
Keep the conversation focused on the issue and evidence, while allowing appropriate challenge. If a topic requires specialist investigation, identify that need rather than force a technical conclusion from people not competent to make it. The chair’s role is to organise a clear route to resolution, not personally answer every question.
At the end of a consequential item, summarise the decision or action and ask the responsible participants to confirm the understanding. This can reveal differences while the relevant people are together. It is easier to correct an ambiguous statement then than after several teams have acted on different interpretations.
Include people joining between meetings
When a new package lead arrives, explain the meeting’s purpose, current actions and decision boundaries. Give them the relevant current record and ask whether inherited actions are understood. Do not assume that an organisation’s continued attendance means every representative has received the same context. A short mobilisation conversation can prevent the meeting reopening old issues unnecessarily or treating an unresolved action as accepted by someone who has not yet seen its basis. Keep the responsibility for continuity with the relevant manager rather than depend on informal briefings.
Issue a record people can use
Produce the record through the agreed project process and provide a route for corrections. Stable issue references help participants follow an item across meetings. Keep significant decisions, actions and unresolved matters easy to find. A lengthy transcript can obscure the very responsibilities the meeting was meant to clarify.
Link to controlled information rather than attach changing copies without a clear status. APM’s configuration management overview provides relevant context for version traceability. The practical requirement is that the record identifies which information participants reviewed, not merely a document title that now refers to something different.
Review closure against evidence
At the next appropriate review, confirm whether actions produced the required output. An email sent may be an activity rather than completion of the original question. If the response reveals another issue, record that development and its owner. Avoid closing items simply to reduce the length of the action list.
Look for recurring deferrals. They may indicate missing authority, an unrealistic date or a wider resource problem. Escalate the underlying matter through the proper management route. Repeating the same action with another date does not create a credible plan when the condition preventing completion remains unchanged.
Useful site meetings leave people with a clearer understanding of what they own and what others must provide. They connect evidence to decisions, preserve the limits of authority and follow actions through to a defined outcome. Reviewing those practical results helps the project maintain meetings that support delivery rather than merely occupy a place in the weekly diary.
Ask participants periodically which agenda items help them act and which create duplication. Use that feedback with the meeting’s stated purpose to adjust the format, while preserving any records and formal processes the project requires.
