Ten Minutes Is Enough for a Site Briefing

When you arrive on site, everyone starts with their own story. Who promised what, what problem happened yesterday, what is urgent now — it all pours out at once. Opening a long meeting from the start often leaves the information less organised than before. I narrow the scope with a ten-minute briefing first.

Align four things first

There are four things to confirm in a short briefing.

1. Purpose — what this meeting is here to confirm today
2. Current state — what is actually finished and what remains
3. Blockage — why we cannot move to the next step
4. Next action — who checks what, by when

Speaking in that order reduces the way talk wanders off. Confirm only as much of the past as you need, and write down separately anything that cannot be decided today.

Leave words, not sentences

While listening you do not have to write down every sentence. Instead, record the exact terms used on site — names, dates, quantities, the person responsible — things that become awkward later if they are wrong. Mark the rest as "needs checking".

A good record is not one where you wrote the most. It is one where the next person does not have to ask the same question again. At the end of the briefing, read the notes aloud and confirm the terms with the people involved.

One last sentence

Close the briefing like this.

Today we confirm A, B shares the result by C. D is not decided yet.

That sentence is enough of a starting point, even without minutes. The speed of a site depends less on the volume of talk than on how clear the next action is. Creating the shared certainty that everyone saw the same scene for those ten minutes — that is the job of a short briefing.