How to write a daily construction site report: sections and a sample structure

It is 7.30 pm. Someone at the office lines up the six WhatsApp messages the foreman sent during the day, a phone note and a blurry photo taken of a notebook, to piece together an answer to the manager’s question: “what happened on site today?” The report does not come easily, because every piece of information sits somewhere else and some of it is missing. The next day, the same story starts again. A daily site report is an internal tracking record that shows, on one page, the work done on a site that day, the headcount, materials, open defects and incidents. The hard part is not writing it; it is filling in the same sections, in the same order and in full, every day.

The short answer: divide the report into fixed sections, fill each one from records collected during the day, and have one person close it in the evening. The table below gives these sections and sample rows; you can copy it straight into Excel.

What sections does a daily site report have?

How do you record weather and headcount in a daily site report?

Writing “rainy” is not enough for the weather; what matters to the reader is how the weather affected the work. Which task was affected and during which hours; did work stop or just slow down? A sentence such as “Concrete pour postponed between 10.00 and 13.00 due to rain” is the most useful kind of record in any later discussion about delays. You can take the weather data from a weather service, but it is the foreman’s observation that really describes the effect on work.

Record headcount not as a single total but by crew and person. Put your own staff and each subcontractor crew on separate rows, with full day, half day and overtime shown separately on each row. If your company counts a half day as 0.5, every report must use the same rule: if 12 people worked a full day and 4 people a half day, the total is 12 + 4 × 0.5 = 14 person-days. If you also keep a column for who reported the figure and at what time, the question “who gave us this number?” is easy to answer at the end of the month.

How does the foreman’s message become a report row?

The hardest part of writing the report is putting information that arrives from the site in loosely worded sentences into the right section. The four fictional messages below show where they land in the same day’s report:

Keep one thing in mind: a report is a record, not a commentary. “Work is going well” carries no information; “Block B, 3rd floor column formwork finished” does. Since the manager will skim the report, think about the order too: incident and OHS records go at the top, followed by open defects and materials, with the detailed work list at the end.

How do you build up the report step by step during the day?

1. Morning: Open the site, date and weather row; carry over yesterday’s open defects and pending requests to the report.
2. During the day: Have every piece of information from the foreman written down in one place; messages, voice notes and photos should not end up in different places.
3. Afternoon: Collect the headcount crew by crew; remind any crew that has not reported.
4. Evening: Fill in the sections according to the table and ask the foreman about any unclear rows.
5. Closing: Have one person review and approve the report; after approval, only an authorised person makes changes.
6. Next morning: Carry unresolved defects and undelivered materials over to the top of the new report.

What happens if the daily site activity report is compiled by hand in Excel?

With one site, one foreman and a dedicated person for the report, Excel works perfectly well; a simple table like the one above is enough for the office to close the day comfortably. The trouble starts where the work grows:

• Information arrives scattered; part of the same task stays in WhatsApp, part of it on the phone.
• File versions multiply; nobody knows which one is the latest report.
• A site that sends no records becomes invisible; an empty row does not show the difference between “nobody wrote anything” and “there was no work”.
• Defects are carried from report to report by hand; once one is forgotten, nobody knows whether it was closed.
• Photos go into the report, but only the person who took them knows which task they belong to.
• With several sites, compiling becomes the longest job of the day.

If you decide to stay with Excel, put three rules in writing: name the file with the date every day, keep the sections in a fixed order and store the file as read-only after approval. These three rules prevent most of the “which is the latest report?” and “who changed this?” questions, but they do not remove the work of transferring messages into the table.

How does SahaSesi AI prepare the daily report?

SahaSesi AI sorts the text, voice messages and photos that foremen and crew leads send to a single WhatsApp number into work log, timesheet, material, defect and incident records; the site team does not install an app. The flow is as follows:

1. The foreman writes or leaves a voice message; the record is read back to the foreman as “Logged: …”, and if it is wrong, the foreman corrects it.
2. A message that cannot be confirmed lands in the office’s “awaiting review” list; no record is silently lost.
3. The day’s records line up in the daily report automatically; the report is prepared with the site’s weather information for that day.
4. Once the site chief checks and approves it, the daily report is locked; only a manager can make later changes.
5. Every evening at 7 pm, a single PDF with a section per site goes to managers by WhatsApp and email; past reports stay in the panel.

The report also shows separately any site that sent no records that day. The bot cannot read messages in WhatsApp groups; information written in a group is recorded once it is sent to the bot with “Forward”. SahaSesi AI is being rolled out with the first construction sites through a pilot programme.

Checklist before closing the report

• Is there a row for every active site and every subcontractor, or is it marked “no records received”?
• Are headcounts split into full day, half day and overtime?
• Is the effect of the weather on work written down?
• Have open defects been carried over with the person responsible, and closed ones marked as closed?
• Are material requests and deliveries on separate rows?
• If there was an incident or safety non-conformity, is it at the top of the report?

If you would like to see your daily report built from WhatsApp records on your own site, you can schedule a pilot call on the SahaSesi AI page.