It's 5:40 on a Thursday and the site supervisor is finishing the daily site report on the bonnet of the van. Crew on site, hours worked, what got delivered, what didn't, the two hours lost waiting for the concrete pump. They send it to the project manager by email, like every day.
The project manager runs four sites and gets four of these every evening, plus the subcontractors' timesheets. Most say the same thing: a normal day. But somewhere in Tuesday's report from the east site was 14 hours of unplanned overtime and a skip charge nobody had agreed to. It was in the email. Nobody read that far.
A daily site report is a routine submission. The trouble is it's treated as either all routine or all important, so people either skim every one or check every one. What you want is for the ordinary days to file themselves, and the exceptions to land in front of someone.
What a daily site report needs
Whatever you build it with, a good construction daily report is short enough to fill in on a phone in five minutes. It needs:
- Which project, and the date. Picked from a list, so every report sits against the right job.
- Who was on site. Your own crew and subcontractors, with their hours. Ask for overtime hours separately; don't make someone work it out from the total.
- What was done. A line or two against the programme: "Second-floor slab poured, east stair formwork struck."
- Deliveries and materials. What arrived, and anything ordered on site that wasn't on the plan, with its cost.
- Delays. Hours lost and why: weather, late delivery, waiting on another trade, access, drawings.
- Health and safety. Was there an incident or near miss? Yes or no, and what happened.
- Photos. Progress, deliveries, anything damaged. Photos settle a lot of arguments later.
- Weather. It's the first thing anyone asks about when a delay claim comes up.
Everything on that list is there because someone later needs it: the project manager for the programme, the QS for costs, the H&S lead for incidents, and everyone when a dispute comes up months later.
Which reports need a sign-off
Most days should need no one's approval. A report that says "normal day, no overtime, nothing extra ordered, no incidents" should be saved and left alone.
A report should go to someone for sign-off when it contains something they'd want to know about today. Agree a short list of triggers with your project managers, for example:
- Overtime above a set number of hours across the crew.
- Unplanned spend, such as materials ordered on site or plant hire, above a set amount.
- Delay above a set number of hours.
- Any incident or near miss, whatever the numbers.
Write the limits down and put them in the form's help text, so supervisors know what will be flagged. A sign-off isn't a telling-off; it's the project manager seeing the overtime before it's on the invoice, not after.
How to build it in stepbase
There's no ready-made template for this one, but it takes one Table, one Form and a short Workflow. You can also describe it in a sentence on the stepbase home page ("daily site report; overtime over 8 hours, extra spend over 500 or any incident goes to the project manager to sign off") and let it draft the app, then check it against the steps below.
- Make a Projects Table. One row per job, with the project name, the site address and the project manager's email. This is what the Form picks from and what decides who signs off.
- Build the Daily Site Report Form. Add Project as a choice from the Projects Table, then Date, Work done, Overtime hours, Unplanned spend, Delay hours, Delay reason, Incident or near miss? (yes or no), Weather and a Photos field. To list each crew member or subcontractor with their hours, use a table field so the supervisor can add a row per person.
- Show the incident questions only when they apply. Use conditional logic so What happened? and Who was involved? appear only when Incident or near miss? is yes. A normal day stays a short form.
- Add one Rule after the Form. In the Form's Workflow, add a Rule with two paths. Needs sign-off if overtime is above your limit, or unplanned spend is above your limit, or delay is above your limit, or there was an incident. Everything else takes the default path, Filed, and goes straight to an Outcome.
- Add the sign-off Step. On the Needs sign-off path, add a review Step for the project manager. Assign it with a Table lookup: find the project picked on the form in the Projects Table and use its project manager's email. Each report goes to the right person without anyone setting it up per site.
- Give the Step two Actions. Signed off and Needs follow-up, each leading to its own Outcome. In the Step's instructions, tell the project manager what to check: the reason for the overtime, whether the spend was agreed, what's being done about the incident.
- Set a deadline on the sign-off. If a report is still waiting after a day, hand the Task to a contracts manager or a second project manager, so nothing sits while someone's on leave.
- Share the Form with the supervisors. Send them the link or put the QR code in the site cabin. The Form works in a phone browser, with no app to install. Supervisors need a signal to submit, though; there's no offline mode.
Every report, filed or flagged, lands as a row in the Form's Table. Put a chart on a Page grouped by project, such as overtime hours per site this month, and the project managers have the trend as well as the exceptions.
Making it fit your sites
- Different limits per project. If a large job tolerates more overtime than a small one, add a column for the limit to the Projects Table and compare against it, rather than writing one number into the Rule.
- Subcontractor hours. Keep them in the same report's table field, with a column for the company, so you can check their invoice against the hours your supervisor recorded.
- Health and safety copied in. Add an Automation that emails your H&S lead whenever a report says there was an incident, alongside the project manager's sign-off.
- The history stays with each report. Who submitted it, who signed it off and when are all in the report's history, which is what you'll want when a delay claim or a dispute comes up.
Start with one site
Run it on one project for two weeks. Keep the email as a fallback, and watch which reports get flagged. If almost everything is flagged, your limits are too low; if nothing is, they're too high. When the project manager notices they only open the reports that need them, roll the Form out to the next site. Only the Projects Table changes.
Describe your daily report at stepbase, and build it with your own triggers and your own words.