5 Things Every Site Diary Should Include to Protect Your Profits

The Site Diary's True Purpose

Site diaries serve a purpose far beyond administrative compliance. They're the foundation of commercial protection—the contemporaneous record that supports claims, defends against disputes, and substantiates payment applications.

But not all site diaries are created equal. A diary that captures weather and workforce counts provides minimal value. A diary that captures the five essential elements becomes a commercial asset.

1. Quantities of Work Completed

Every diary entry should specify what was actually completed, in measurable terms. Not "earthworks continued" but "1,250m³ of material excavated from area B, stockpiled at location C."

This specificity serves multiple purposes:

Payment Justification

When your QS compiles payment applications, they need quantities. Vague progress descriptions require follow-up and estimation. Specific quantities enable direct compilation.

Productivity Analysis

Quantities completed, combined with resource records, enable productivity calculation. Without measured outputs, productivity becomes guesswork.

Dispute Evidence

If progress becomes contested, dated records of completed quantities provide objective evidence. "We completed 1,250m³ on 15th March" is defensible. "We made good progress" is not.

Best Practice

Use consistent measurement units aligned with contract requirements. Cubic metres, tonnes, linear metres, square metres—whatever the contract specifies. Consistency enables comparison and aggregation.

2. Delays and Events Impacting Progress

Every event that affects progress should be documented: weather disruptions, late deliveries, equipment failures, design changes, access restrictions. Capture not just what happened, but why and what impact it had.

Contemporaneous Evidence

Delays documented on the day they occur carry evidential weight. Delays reconstructed weeks later become disputed versions of events.

Contract Linkage

Connect delay events to contract terms. Under NEC4, compensation events have specific definitions. Under JCT, relevant events trigger extensions. Diary entries should use contract-aligned language.

Claim Foundation

Every delay claim you'll ever submit starts with a site diary entry. Without dated records of cause and effect, claims become arguments about recollection. With dated records, they become evidence-based submissions.

3. Resources Used

Document the resources deployed: labour by trade and number, plant by type and hours, materials by quantity and location. This isn't just timekeeping—it's the foundation of cost monitoring and claim substantiation.

Labour Records

Who was on site? What trades? How many? Where were they deployed? This data enables labour cost tracking and supports claims for additional resources.

Plant Records

What equipment was on site? Was it working or idle? Where was it deployed? This data reveals utilisation efficiency and supports plant-related claims.

Material Records

What materials were delivered? Where were they used? What's the running consumption? This data enables material cost control and identifies waste or theft.

4. Site Conditions and Weather

Environmental conditions affect both work capability and commercial entitlement. Record them systematically.

Weather Data

Temperature, precipitation, wind conditions—whatever affects work. Some contracts trigger compensation events based on weather thresholds. Without recorded data, these claims become impossible.

Ground Conditions

What did you encounter? Did it match expectations? Unforeseeable ground conditions are often compensable, but only with dated records of what was actually encountered.

Access and Working Conditions

Was the site accessible? Were working areas available? Constraints that affect progress need documentation to support delay claims.

5. Variations and Instructions

Every change to scope, every instruction that differs from contract, every direction that triggers additional work—capture it in the diary with full details.

Instruction Records

Who gave the instruction? When? What specifically was instructed? Was it verbal or written? Diary records of verbal instructions create the contemporaneous evidence that supports variation claims.

Scope Changes

What changed from the original scope? Why? What additional work resulted? These records prevent the common problem of completed variations that never get billed.

Authorisation Trail

Who authorised the change? What was their authority to do so? Clear authorisation records prevent disputes about whether changes were properly instructed.

The Integration Requirement

These five elements don't exist in isolation. They connect to form a coherent picture:

• Quantities completed relate to resources deployed (productivity)
• Delays explain why quantities fell short of plan
• Resources support claims for additional costs
• Conditions explain delay causes and trigger entitlements
• Variations capture scope changes and instructions

When diary entries link these elements together, they create a narrative that's difficult to challenge and easy to defend.

What This Means for Your Projects

Your site diary is either working for you or working against you. Incomplete records leave money on the table and disputes undefended. Complete records accelerate payments, substantiate claims, and protect your position.

The investment is minimal: a few minutes of thoughtful daily recording. The return is substantial: protected margins, faster payments, and defensible positions.

What's not written down might as well not exist. Make sure the important things get captured.