A construction site diary pays for itself when the crew can fill it in within five minutes at the end of the day and the office can use what they record. In the short video above, we describe the trade: a few minutes on site each day in exchange for days of chasing in the office at month-end. It only works if the tool is easier than the paper it replaces.
In the video
- If the site crew spends five minutes at the end of each day logging what they did (a quick note, a couple of photos, which job they worked on), the office team avoids days of chasing at the end of the month.
- The way we put it: five minutes on site, three days saved in the office. Capture it once, at the source.
- It only works if it's dead simple for the crew, which is why the tool matters.
- Dashpivot, Fieldwire, even a shared Google Form: whatever you use, it has to work on a phone, work offline, and take less time than filling out a paper form.
- If it's harder than paper, no one will use it. If it's easier, they will, and everything downstream (claims, costing, reporting) gets faster as a result.
What's happening here
At the end of a day on site, the people who know what happened are standing right there. They know which job they were on, who was on the crew, what got done, what was delivered, what held them up and what the client asked for. A week later most of that is gone, and by month-end the office is rebuilding it from texts, photos and memory.
The trade in the video is about when the information gets recorded. Five minutes while it's fresh is cheap. The same information pieced together weeks later costs far more, and it's less accurate. The QS chasing evidence for a claim, the payroll officer chasing hours and the accounts team trying to work out which job a delivery belonged to are all paying for information that wasn't written down at the time.
What to record at the end of each day
Keep the entry short. A good end-of-day diary entry covers:
- The job, picked from a list, so it uses the same job number as the office
- Who was on site and roughly how long, if hours aren't captured another way
- What was done, in a line or two, tied to a stage or cost code where that's useful
- Photos of progress, problems and anything covered up
- Deliveries, with a photo of the docket
- Instructions and changes, especially anything that could become a variation
- Delays, with the reason: weather, waiting on another trade, access, materials
Most of these are taps and photos rather than typing. If a field doesn't get used by anyone in the office, take it out. Every extra field makes the five minutes longer.
The three tests a site diary tool has to pass
It works on a phone. Not a laptop in the site office and not a paper form that someone scans later. The supervisor already has a phone in their pocket.
It works offline. Plenty of sites have patchy coverage. The entry should save on the phone and send itself when there's signal, without anyone having to remember.
It's quicker than paper. This is the one that decides whether it gets used. If the app needs more steps than the old diary book, the crew will go back to the book, or skip it. Test it with the people who'll use it, at the end of a long day, before you roll it out.
Products like Dashpivot and Fieldwire are built for this, and many job management systems include a site diary. For a small team, a shared form can be enough to start. The choice matters less than whether the crew finds it easier than what they do now.
Why the office doesn't always get the benefit
A site diary on its own doesn't remove the chasing. We often see diaries that are filled in faithfully but kept in their own app, and the office still re-types hours into payroll, re-keys deliveries against jobs and searches the diary by hand at claim time.
That happens for two reasons. The diary uses different job names or codes from the job and accounting systems, so nothing lines up. And the information stops before it's needed: it sits in the diary app instead of flowing to the places that use it. Each system becomes a data silo, holding information others can't reach, and someone in the office ends up doing double entry (typing the same thing into a second system) to bridge the gap.
Capturing once means the diary entry is the record. Hours go to the job and to payroll, the docket photo is there when the supplier's invoice arrives, and the instruction goes onto the variation register. That's the part that turns five minutes on site into days saved in the office.
What it looks like when it's fixed
At the end of the day, the supervisor picks the job, ticks the crew, adds two lines and four photos, and is done in a few minutes. The next morning the PM can see yesterday's progress on every job without a phone call. On claim day, the QS filters the diary by job and date and has the evidence. When the supplier's invoice arrives, the docket is already attached to the job. At month-end, nobody is asking the site what happened three weeks ago.
Rolling it out
- Start with one crew or one job, not the whole business.
- Ask the supervisor what the old paper diary had that they'd miss, and what they'd happily drop.
- Set the job list from the same job numbers the office uses.
- Decide who in the office uses each field, and remove fields nobody uses.
- Agree a time: last thing before leaving site, every day.
- Show the crew what happens to their entries, such as faster claims and fewer phone calls.
- After a month, check what the office still has to chase and adjust.
Frequently asked questions
What should a construction site diary include?
The job, who was on site, what was done, photos, deliveries, instructions or changes, and delays with reasons. Keep it to what someone in the office or the PM will use. Shorter entries filled in every day beat detailed entries filled in occasionally.
Is a shared form good enough, or do we need a proper app?
A shared form works for a small team if it runs on a phone, saves offline and records the job consistently. As you grow, a dedicated site diary or job management system usually handles photos, offline use and approvals better. Either way, what matters is that the entries reach your job and accounts systems without being re-typed.
What if the crew won't use it?
Usually it's slower than paper, asks for too much, or nothing visible happens with the entries. Cut the fields, test it with them, and show them the phone calls it saves. If it's genuinely easier than the book, they'll use it.
How does a site diary help with claims and job costing?
Dated, job-tagged entries give the QS evidence for progress claims and variations, and hours and deliveries recorded against the job feed job costing sooner. We cover the claim side in Your QS Should Not Be a Detective, and the job cost side in our guide to seeing job profit sooner.
Make the five minutes count
If your crew already records the day but the office still chases, the gap is usually in how the diary connects to everything else. Book a free initial chat and we'll look at where your site information goes after it's captured.