The 10-Minute Morning Briefing Every Site Foreman Should Run

What is a daily site standup?

A daily site standup is a short, standing meeting held at the start of each working day, usually lasting no more than ten minutes. The foreman gathers the crew and subcontractor leads at the start of the shift, runs through what was completed yesterday, what is planned for today, and flags anything that might block progress before anyone picks up a tool. It is not a review meeting, not a formal briefing, and certainly not a problem-solving session. It is a sync — a way to make sure every person on site is working from the same current picture instead of the version in their own head from yesterday afternoon.

Why does a weekly check-in leave too much room to go wrong?

A weekly meeting catches problems at the worst possible time: after they have already had five days to compound. A trade that lost half a day on Tuesday because the foreman did not know the slab was not ready has now lost nearly a week of knock-on time before anyone says a word about it. On a tight six-month build, that kind of silent drift accumulates into weeks of delay without a single dramatic event to point to. The daily standup shrinks the window between something going wrong and someone knowing about it to less than 24 hours, which is usually still early enough to fix without significant cost.

What should a daily site standup actually cover?

Keep it to four things. First, a quick round on what was completed yesterday — one sentence per trade or task, not a full account. Second, what each group is doing today, stated in enough detail that dependencies are obvious: if the plumber is working in the bathroom, the tiler cannot start there, and both need to know that at 7 am rather than 11. Third, anything that is not available or not ready that will block work — materials that have not arrived, a decision still pending, a section of slab still curing. Fourth, a one-sentence coordination point: who needs access to the same area and in what order. That structure fits comfortably in ten minutes for most SME sites.

A worked example: Khun Somchai's five-minute morning on a townhouse build

Picture a foreman managing a 12-unit townhouse build with four active trades on any given day. On a Tuesday morning Somchai opens SiteBoard on his phone and scans yesterday's on-site progress updates: Block A second-floor slab shows 100 percent complete, Block B shows 65 percent with a note that a pour was paused for rain. He then runs the standup: the concrete crew is finishing Block B today, the block-work team is moving to Block A now that the slab is done, and the electrician cannot start first-fix until block work is two days ahead. That five-minute scan plus five-minute sync stops two trade crews from arriving at the same section and losing two hours untangling priorities before noon.

How to keep the standup to exactly 10 minutes

The standup dies when it becomes a problem-solving session. Apply one rule: if something needs more than 30 seconds of discussion to resolve, park it and handle it one-on-one after the standup ends. The foreman's job is to facilitate, not perform. Starting at the same time every morning — 7 am on most Thai sites — and keeping it standing with no chairs creates the physical cue that this is not a meeting to settle into. A consistent format, the same four questions in the same order every day, means experienced crew members know what to prepare and the whole thing clicks into a rhythm within a week.

What does a missed standup actually cost?

The cost is hard to see precisely because it comes from small frictions. A plasterer who does not know the ceiling board went up yesterday prepares the wrong room, loses an hour, and must re-sequence the afternoon. A tiling subcontractor who arrives with materials for a section that is not ready waits half a day at full day-rate. A concrete pour happens without the site manager knowing, so the photo record and timestamp are missing when a crack dispute arises three months later. None of these is a single disaster, but across a six-month project they add up to days of avoidable cost that no single invoice ever captures.

Does the daily standup replace the weekly site meeting?

No — they solve different problems. The daily standup is tactical: it makes sure the next eight hours happen the way they should. The weekly meeting is strategic: it compares where the project actually stands against the Gantt, identifies drift that has accumulated over the week, and makes decisions about resourcing and replanning for the weeks ahead. Running both costs under 30 minutes a week in total and gives you two separate chances to catch problems at different timescales. A project with only a weekly meeting still gets ambushed by daily friction; one with only a daily standup never steps back to check whether the whole plan is still on track.

How does reviewing yesterday's on-site progress updates help before the standup?

The single most useful thing a foreman can do in the two minutes before the standup starts is check yesterday's progress updates in SiteBoard. When the crew logs percentages and photos the evening before, the foreman arrives already knowing which tasks moved, which stalled, and what the current percent complete is across active sections. That preparation turns the standup from a guessing session into a confirmation session: the foreman states what the data shows, the crew corrects or confirms, and the meeting is tighter because the baseline is already visible rather than assembled from memory mid-meeting.

How do I get my foreman to actually run the standup every day?

Start by running it yourself for the first two weeks. The foreman will copy the format once they see it working. Keep it strictly to ten minutes — overrunning even once creates the expectation that the meeting will eat into work time, which is the fastest way to lose buy-in. Pair the standup habit with the on-site progress update habit: the updates logged the evening before make the morning standup smarter, and a smarter standup makes the crew more willing to log updates because they see the direct return. Once both habits are running, the Gantt planning view in SiteBoard reflects reality almost in real time, which means anyone can answer the question "where are we today?" without a single phone call.

Does a small two-person crew still benefit from this?

Yes, and the format is even simpler. On a small residential build with two or three workers, the standup is just the foreman saying out loud: here is what we finished yesterday, here is what we are doing today, and here is what we need to watch for. That takes three minutes, not ten. The benefit is not the meeting format itself — it is the habit of stating the plan explicitly at the start of each day rather than assuming everyone remembers yesterday's intentions. Explicit beats assumed on any site, regardless of size. The act of saying it out loud surfaces gaps before they cost money.