Browse the curated construction delays hub for civil subcontractor field documentation tactics.
On Tier 1 roads, rail, defence, and energy civils, your site diary is often the first document a client planner or lawyer opens when an Extension of Time (EOT) is disputed. If the diary is vague, your delay notice may still be valid - but you will fight uphill to prove causation, concurrency, and cost impact.

Below is a practical standard for civil subcontractor site records that aligns with how major projects audit delay evidence.
Daily diary structure that survives scrutiny
- Work front and activity ID (chainage, structure number, zone, or WBS reference).
- Planned versus achieved quantity in contract units.
- Resources deployed by crew and plant ID.
- Constraints encountered (access, predecessor incomplete, design clarification, services conflict, weather).
- Directed changes including who issued them and how they were communicated.
- Time lost in discrete blocks with start and finish times.

How to write EOT-supporting notes, not opinions
Favour observable facts: formwork could not continue when predecessor backfill was not signed off, with standby from 06:40 to 14:10. Avoid vague labels unless tied to a specific breach of access or information duties your contract covers.

Concurrency and other trades
Where multiple trades share a window, record who held the critical path for your activity and any direction to vacate or wait. This helps advisers separate excusable delay from concurrent non-compensable periods.

Pair the diary with contemporaneous attachments
Link photos, permits, docket scans, concrete tickets, and emails to the same date and work front. The goal is a chain a reviewer can follow without calling your supervisor for oral evidence.
Where you need a same-shift PDF to sit beside the diary, generate one with the free Dayworks Docket Generator so labour, plant, and instructions are captured in a consistent layout before they are filed or emailed to the head contractor.
Speed up compliant capture with DelaySolve
If engineers are duplicating notes between paper diaries, WhatsApp, and spreadsheets, errors creep in and notices slip. DelaySolve gives civil subcontractor teams a single mobile-friendly workflow to log delays, attach evidence, and export structured records aligned to how Tier 1 contractors expect claims to be presented.
Many teams pair DelaySolve with the Dayworks Docket Generator for ad-hoc dayworks so foremen always have a free, on-brand PDF path while longer delay packs are assembled.
Summary
- Treat the diary as a legal-adjacent record, not a personal journal.
- Always connect delay text to programme activities and units.
- Keep notices, diaries, and attachments consistent on dates and locations.
- Use the free dayworks generator when you need a printable docket the same day as the delay event.

