Construction site evening report: what a manager needs to see every evening

A site evening report is a daily summary that shows the manager on a single page what was done on each site at the end of the day, how many people worked and what remains open. Without a report, the manager learns the state of the day through a phone chain: calls the site manager, the site manager calls the foreman, and the foreman tells what he remembers. As the evening wears on, the chain breaks and the decision is left to the next morning. In the end the manager either decides with missing information or postpones the decision. The gap grows with the number of sites: the number of people who can be called stays fixed, while the number of sites that need calling grows.

A good report does not only give information; it also sets the order in which to look. In this article we explain how a manager should read the report and what the evening report in SahaSesi AI contains.

The manager’s reading order

1. Occupational health and safety incidents. These come before everything else. In SahaSesi AI an occupational health and safety incident appears in red at the very top of the evening report; the manager sees it the moment the page opens.
2. The site with no record. Silence is information too. The report shows a site that sent no record at all that day with a “no record received” note. The cause may be a signal problem or some other hitch; either way, the site that needs a question is identified.
3. Person-days. How many people worked that day is the first figure to compare against the planned crew.
4. Work done. Work records ordered by block and floor; the plain-text equivalent of progress.
5. Open defects and material requests. They show what will be chased tomorrow and which work is still not closed.
6. Weather. The report is prepared with the site’s weather for the day; low output or a work stoppage is often explained by this line.

How is a sample report read?

The summary below belongs to a fictional site taken from the product’s demo data:

• Heading: Evening report, 19:00, Çamlıca Konutları, Blocks A and B.
• Figures: 38 person-days, 6 work records, 2 open defects.
• Work: Block B, 3rd floor column formwork finished; Block A, 2nd floor slab rebar tied; 40 m of perimeter drainage pipe laid.
• Open defect: Block A, 2nd floor stair railing.
• Warning: No record received for Kartal Ofis Binası.

At a glance the manager draws the following from this page: work is progressing in two blocks, one defect is still open, and there is no word from one site. The next question is obvious: call the foreman at Kartal Ofis Binası. If person-days are low, look at the weather line; if the weather does not explain it, look at the work records. The report does not spare the manager from asking questions, but it lets them put the right question to the right person. In the phone chain, reaching the same result would mean calling the foremen and site managers of three sites; here the information arrives without calling, at the same hour and in the same layout.

A good report does not make you ask questions; it shows the question that needs asking.

How is the report produced and how is it finalised?

The text, voice messages and photos that foremen send on WhatsApp during the day are separated into records by type; the records line up in the daily report automatically. The office checks the records in the panel, and when the site manager approves, the daily report is locked and later changes can only be made by a manager. At 19:00 it reaches the managers as a single PDF split by site, by WhatsApp and e-mail; past reports also stay in the panel, so finding the report for a day last week does not mean searching through messages. On the office side the “Today” screen updates the record, person-day, request and occupational health and safety counters instantly during the day; the evening report is the closing summary of data that has already been followed through the day.

What does the report’s reliability depend on?

The content of the report is only as accurate as the messages that come from the site. AI can misunderstand a message; that is why every record is read back to the foreman as “Saved: …” and can be corrected, and records that cannot be confidently understood land in the “awaiting review” list in the office. Even so, we recommend that your office checks timesheet and occupational health and safety records before using them. The report does not replace checking; it shortens it. The weakest point of the report is often the message that was never written. That is why the “no record received” line and the timesheet reminder are complementary parts of the report; giving foremen a simple habit such as “send one summary message at the end of the day” improves the report at least as much as the product does.

Taking the report into the meeting

• Open the morning meeting with the open defect and “no record received” lines of yesterday’s report; that way the meeting is spent closing what is open, not telling who did what.
• Make occupational health and safety incidents the first item on the meeting agenda. The report already puts them at the top; let the meeting follow the same order.
• Place the person-day figure next to the weekly plan. If there is a deviation, look for the cause first in the weather, then in the work records.
• Share the report with site managers too; seeing their own site’s record on the same page encourages messages to be written regularly.

To find out how the evening report would look for your own sites, you can look at the sample screens on the SahaSesi AI page and request a pilot meeting.