Daily reports and site diaries

Every evening at about five o'clock, Marcus Bell sits in the Westgate site office and completes the day's report. It takes him twenty minutes. Some days it records nothing remarkable: forty-two workers, clear weather, level 3 timber panels set on schedule. Other days it records a crane shutdown for wind, a failed inspection or a delivery that arrived with the wrong connectors. Marcus does not know, on any given evening, which of his reports will matter. He knows from experience that some of them will, and that nobody can tell in advance which ones.

The daily report is the backbone of the field record. It is the one document created every working day, by a person with first-hand knowledge, in a consistent format. Combined with the superintendent's diary, subcontractor reports, photos and delivery records, it gives a day-by-day account of the project that nobody can reconstruct later. This lesson covers what a daily report should contain, how it differs from a diary, how subcontractor reports fit in, and how to write and review reports that will stand up when they are needed.

What goes in a daily report

Division 01 of the specifications usually sets a minimum content for daily reports and says whether the owner or contract administrator receives copies. Brightwater's own template goes further than most specifications require, because the report serves Brightwater's interests as well as the owner's.

The delays section is where most reports are weakest. 'Waiting on drawings' tells a reader almost nothing. 'Drywall crew of 4 (Kestrel Interiors) unable to start level 3 east corridor, rooms 301 to 318, pending RFI-131 response on bulkhead height; crew reassigned to level 2 punch work from 08:00; level 3 start now forecast for Monday' tells a reader who, where, why, how long and what was done about it.

Daily report or diary?

The terms are sometimes used interchangeably, but on Westgate they are different documents with different purposes.

Marcus writes his diary in a bound notebook with numbered pages, in ink, and dates every entry. If he makes a mistake he strikes it through with a single line and initials it, so the original is still readable. Bound books with numbered pages are harder to challenge than loose sheets, because missing or inserted pages are obvious. Many superintendents now keep diaries in an app instead; the same principles apply, and the app should time-stamp entries and keep a history of edits.

A diary is not private just because it is internal. In litigation or arbitration in both countries, relevant documents in a party's possession are generally disclosable, and a diary full of frustrated comments about the owner, or admissions about Brightwater's own mistakes, will be read aloud. The rule Marcus follows is to write what he saw and heard, not what he thinks of people.

Subcontractor daily reports

Brightwater's subcontracts require every subcontractor to submit its own daily report by 09:00 the next working day. These reports feed Brightwater's records and protect both parties. They also reveal disagreements early: if Tallis Mechanical reports eight workers on level 2 and Brightwater's own count shows five, the discrepancy is raised the next morning, not discovered in a claim a year later.

• Use a common format, ideally submitted through the same platform, so reports can be compared and searched.
• Require names or crew lists, not just numbers, on days with extra work, standby or disputed conditions.
• Have Brightwater's superintendent or field engineer review and acknowledge each report, noting any disagreement in writing.
• Make clear in the subcontract that acknowledging a report means receiving it, not agreeing that extra payment is owed.

Weather records

Weather is one of the most common causes of delay and one of the most commonly disputed. A report that says 'rain' is weak. A report that records the time rain began and ended, the amount if a gauge is on site, the activities stopped and the conditions underfoot is much stronger. Brightwater supplements its own observations with official data.

For Westgate, Jun downloads daily weather records for the nearest Environment and Climate Change Canada station each month and files them with the daily reports. Where the contract allows extra time for weather only when conditions exceed what is normal for the season, historical climate normals for the same station are used to show what 'normal' means.

On-site observations matter because official stations can be kilometres away. A thunderstorm that soaks the site may miss the station entirely. A simple site weather station, or at least a rain gauge read at the same time each day, gives Brightwater its own data.

Writing reports that hold up

The value of a daily report depends on how it is written. Brightwater trains its field staff in six habits.

The 'quiet day' entry is easy to overlook. If a report is blank on days when nothing went wrong, a reader cannot tell whether nothing went wrong or nobody filled in the report. 'No delays' is a fact worth recording, and it makes the days with delays more credible.

Reports must be finished the same day. A report completed three days later from memory is not much better than a reconstruction and loses much of its weight. If something is learned after the report is signed, Marcus adds a dated addendum that says when and why it was added, leaving the original untouched.

Comparing subcontractor claims with daily reports is routine work, and it becomes much faster when report data are structured. Jun exports the workforce section of the reports and runs a check that compares claimed hours with recorded hours.

# Compare claimed standby hours with hours recorded in daily reports
reports = {  # date: (workers on site, productive hours elsewhere)
    '2026-05-11': (6, 0),
    '2026-05-12': (6, 0),
    '2026-05-13': (4, 12),
}
claimed = {'2026-05-11': 48, '2026-05-12': 48, '2026-05-13': 48}
rate = 96
total_claim = total_ok = 0
for day, (workers, productive) in reports.items():
    supported = workers * 8 - productive
    total_claim += claimed[day]
    total_ok += supported
    print(day, 'claimed', claimed[day], 'h  supported', supported, 'h')
print('Claimed $', total_claim * rate, ' Supported $', total_ok * rate)

2026-05-11 claimed 48 h  supported 48 h
2026-05-12 claimed 48 h  supported 48 h
2026-05-13 claimed 48 h  supported 20 h
Claimed $ 13824  Supported $ 11136

The comparison is not an accusation. Subcontractors often claim honestly from their own payroll records, which may include workers who were sent home or moved elsewhere. Matching the two sets of records quickly, while people still remember the days, lets differences be settled in a conversation rather than an argument.

Review, signature and storage

Every Westgate daily report is reviewed by Elena, the project manager, within two working days. She looks for missing sections, vague delay entries and any instruction that needs written confirmation or notice. Reports are signed electronically in the platform, which time-stamps the signature and locks the report. After locking, changes can be made only as addenda, which the platform records with their own time stamps.

Where the contract requires it, signed reports are shared with Arden Moss as the contract administrator and with the owner's project manager weekly. Brightwater exports a PDF of each month's reports and stores it outside the platform, as part of the project record it will keep for years after the job ends.