At a contractor's office, what happens on site does not reach the office in time. How the daily report, the work approval and the interim account link into one chain.
Key takeaways
- A daily site report that does not arrive the same day is not a report but a reconstruction.
- An extra not approved in writing before it is done is an extra that lands on you.
- An interim account nearly always stalls on missing documentation rather than on a commercial dispute.
- Site photographs are the cheapest evidence there is, and they are usually linked to nothing.
- The link between the daily report, the approval and the account is all that separates payment on time from an argument.
At a contractor's office every operational problem is the same problem: what happened on site did not reach the office in time and in a form you can rely on. From that follow interim accounts that stall, extras that never get paid, and disputes settled by whoever remembers better.
The site report: why it arrives late
A site manager finishes the day tired, and the report is the last thing. When it means filling in a long form on a computer, it slips to the next day - and is then written from memory, without accurate figures.
What changes this is not discipline but length. A report that can be completed from a phone in two minutes arrives; a fifteen-minute report does not. Five fields suffice for most sites: how many people were there, what was done, what caused delay, what is needed tomorrow, and photographs.
What has to be in the daily report
- Date and site.
- Actual headcount, by trade.
- What was done, in quantities rather than only a description.
- Delays and their cause - weather, material that did not arrive, waiting for an approval.
- Work done outside the contract, if any.
- Photographs with location and date.
The fifth item is the one that returns money. Work done outside the contract and not recorded the same day is almost never paid, because the proof rests on memory. That same item, once recorded, becomes a line on an account.
Work approvals: the single rule that saves the most
The scenario repeats: the client asks for a change on site, the site manager does it rather than stop work, and later it turns out the client remembers the request differently - or not at all.
The operational rule is simple and hard to apply: no extra is carried out without written approval, even a short message setting out what, how much, and who approved it. It looks rigid toward a client, and in practice it is what prevents the unpleasant conversation at the end.
What makes it possible is that the approval takes thirty seconds. A standard message template, sent from site and confirmed back, is all that is required - and where a signed document is needed, there is depth in electronic signatures for a business.
The interim account: why does it stall?
| The reason | What would have prevented it |
|---|---|
| Quantities not matching the measurement | A daily report carrying quantities |
| An extra with no approval | Written approval before the work |
| No evidence the work was done | Photographs linked to the stage |
| Missing supporting documents | A standing list per account |
| A breakdown not in the client's required format | An agreed template up front |
The last row surprises many contractors and is among the most common: the account is entirely correct and is rejected because it is in the wrong format. Agreeing a template at the start of the project saves a full round every month.
Materials and ordering: the second gap
After documentation, the second thing costing money at a contractor's office is ordering. Material ordered late stops a whole crew, and material over-ordered sits on site and sometimes disappears.
What prevents both is the same thing: a materials list by stage, built once at the start of the project and updated from the daily report. When the report says what was done, you can know what will be needed next week without asking.
The other side of this is who approves. An order placed by whoever is on site with no agreed ceiling is a source of surprises on the supplier account, and a simple rule - a ceiling above which approval is required - solves it without holding up work.
Photographs: the cheapest evidence there is
On a construction site nearly every dispute can be settled with a photograph - the condition before, an intermediate stage, a defect that was corrected, or work that was done and then covered over. The problem is not that nobody takes photographs; it is that they sit in somebody's phone gallery with no link to a project or a stage.
All that is needed is that the photograph lands in the same place as the daily report, with a date on it. From there it can be found by day, and that is enough to answer nearly any question asked six months later.
What comes off site and where it goes
| Created on site | Where it must reach | What happens when it does not |
|---|---|---|
| Daily report | The project file, same day | Quantities reconstructed from memory |
| A change request from the client | Written approval before the work | An extra that will not be paid |
| Photographs | The same file, with a date | No evidence of what was covered over |
| Material delivery notes | The project file | A dispute over quantities supplied |
| Worker hours | The payroll system | Gaps in pay and in cost |
| A defect that was corrected | Before and after documentation | A claim that returns at handover |
The fourth row is almost always forgotten, and it is the one that settles quantity arguments: a delivery note for material that arrived on site is the proof it was supplied, and it usually stays with whoever took it at the gate.
What to measure at a contractor's office
- The share of daily reports submitted the same day.
- The number of extras carried out without prior approval.
- Average time from submitting an interim account to its approval.
- The number of rounds until an account is approved.
The fourth number is the best measure of documentation quality. An account approved in one round means everything was there; three rounds mean the office reconstructed afterwards what the site never sent - and that is exactly the time that can be saved.
Sources
Frequently asked questions
Do you need dedicated site management software?
Not to start. A form sent from a phone into a spreadsheet, with a photo folder by date, solves most of the problem - and it also teaches you which fields are genuinely required before choosing a system.
What do you do when a client refuses to approve an extra in writing?
That is a commercial decision, and what matters is that it be made before the work rather than after. One-sided documentation - a message sent describing the request - beats nothing, but it is not a substitute for approval.
How long should project documentation be kept?
How long retention is required, contractually or legally, goes to a lawyer and the accountant. Operationally, project documentation is worth a great deal after handover, because claims arrive late.
Who should complete the daily report?
Whoever is on site, not whoever sits in the office. A report filled in at the office from a phone call loses exactly what makes it valuable - the quantities, the photographs and the delays at a level of detail only somebody who was there knows.
Keep reading
Related service
MVP Development
Turn an idea into a validated product in weeks, not months.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.