Subcontractor Hours Versus the Site Diary: What to Compare and Where AI Should Stop
Short answer: When a builder pays subcontractors for time, claimed hours should agree with the site diary, which records who was on site, what they did and any delays. AI can read both and highlight days, names and tasks that do not line up. It cannot tell whether a disagreement is a mistake, a different recording habit or a dispute, and it should not be used to accuse anyone. The decision table below shows which checks suit automation and which need a conversation.
Why the two records disagree
A site diary is written by the site manager, often at the end of a long day, from memory and a quick look round. A subcontractor's timesheet or daywork sheet is written by the subcontractor, who counts travel, waiting time and set up differently. Some mismatch is normal. Real problems look different: hours claimed on a day nobody was seen, a gang of four billed when the diary shows two, tasks that do not match any instruction.
The usual check is a manager reading both on a Friday evening. It gets skipped when the week was hard. A machine reading both costs nothing in patience, which is its main advantage.
What each record must contain for a comparison to work
Site diary entries (daily):
- Date and weather or conditions affecting work
- Names or companies on site, with approximate arrival and departure
- Work areas and tasks
- Deliveries, visitors and instructions given
- Delays, with cause
Subcontractor claim (weekly or per job):
- Worker names, days and hours
- Task or area worked
- Any instruction reference, such as a variation or daywork order number
- Materials or plant used, if claimed
If the diary names only companies and the claim lists individuals, the comparison can check days and headcount, not names.
Decision table: what to check and who acts
| Check | Suitable for AI? | If it fails |
|---|---|---|
| Claimed day appears in the diary with that company present | Yes | Person asks the site manager and subcontractor |
| Claimed headcount does not exceed diary headcount | Yes, with tolerance | Ask for clarification, not penalty |
| Claimed hours within reasonable range of diary arrival and departure | Partly; diary times are rough | Person decides if the gap matters |
| Task description matches work recorded that day | Partly; wording varies | Person reads both entries |
| Claimed daywork has an instruction or order reference | Yes | Refer to the person who authorised work |
| Hours on a day with recorded weather stoppage | Yes, flag only | Discuss whether work continued indoors |
| Overtime or weekend rates applied correctly | Rule check against agreement | Contract owner confirms |
| Whether the work was good or defective | No | Site manager inspects |
| Whether a payment should be withheld | No | Contract decision, possibly legal advice |
A workable process
- Digitise the diary. If the diary is paper, photograph pages daily. If it is a note on a phone or an app, export weekly.
- Collect claims in a standard layout. Provide subcontractors with a simple sheet so that days, names, hours and instruction references are in the same columns each time.
- Extract to rows. The AI reads both documents into tables: one row per day per company, with headcount and notes.
- Compare with rules. Code checks days present, headcount, daywork references and totals. The language model's job ends at reading and summarising text.
- Write the query list. For each mismatch, the output states what each record says in plain words, with a link to the page image. It uses neutral phrasing: "the diary does not mention this company on Tuesday", not "the subcontractor claimed a day they did not work".
- Resolve and record. The site manager or contracts manager answers each query and writes a resolution note. Corrections to the diary are dated, not overwritten.
- Release for payment through your normal approval route.
Handling the awkward findings
Imagine the diary says two bricklayers on Wednesday and the claim lists three. Possible explanations: the third arrived after the diary entry was written, was a labourer not noted, or did not attend. The sheet to the site manager should list these possibilities, not choose one. The person who was there knows. Treat the tool as a way to prompt memory while the week is fresh, not as evidence for a dispute.
If a pattern builds, such as repeated headcount differences with one subcontractor, take it to a calm commercial conversation, with the log of past queries and resolutions as the factual basis. If the disagreement becomes a formal dispute over payment, rely on your contract and professional advice rather than automated outputs.
Data and fairness considerations
Timesheets name individual workers. Take care what you send to an external AI service, and check the provider's terms for retention and training as of November 2026. Tell subcontractors that their sheets are compared with site records; transparency avoids a sense of surveillance and tends to improve both records. For tax status questions about whether a worker is a subcontractor or an employee, and for reporting duties, use the Canada Revenue Agency's official guidance and your accountant, not an AI summary.
An illustrative week
This is an invented example. A carpentry subcontractor claims forty hours for two workers across five days. The diary shows the company on site Monday to Thursday only, and on Friday the diary notes a site closure for a delivery issue. The query list shows two items: Friday claimed hours and a task described as "framing level 2" on Thursday when the diary says "framing level 1". The site manager recalls the crew travelled to another site on Friday to collect material, and agrees a half day. The Thursday description turns out to be a typo. Both are resolved in a few minutes, with notes.
Making the diary better, which helps everything
The most effective improvement is a diary template with names and times in a fixed place. A few minutes of structure each afternoon improves any comparison, human or AI, and protects you when someone later asks what happened on a particular day.
FAQ
Can AI read handwriting in a site diary?
Neat block writing often works; rushed notes in poor light often do not. Set a confidence threshold, and have a person transcribe unreadable entries.
Should subcontractors see the query list?
Sharing the neutral list of items needing clarification is usually fair and quick. Keep your own internal commentary out of it.
Does this replace a quantity surveyor or contracts manager?
No. It prepares information. Valuation, variations and payment decisions remain professional work.
What if the diary is incomplete?
Then the comparison is weak. Treat missing diary entries as a process problem to fix first, not as a reason to doubt claims.
If you would like help setting up a diary and timesheet comparison that suits how your sites run, we are happy to hear about it through our enquiry page.