A defensible claim needs a connected record
Construction projects generate large quantities of information, but a large document set is not necessarily a persuasive record. The central question is whether the material allows a reviewer to understand what happened, when it happened, what work was affected, why completion moved and how the claimed consequence was calculated.
The strongest records are connected. A notice identifies the event. An instruction or contemporaneous communication explains what changed. The programme shows the affected sequence and critical path. Site records confirm what occurred in the field. Resource and cost records support the claimed commercial effect.
Where those links are missing, the analysis may depend too heavily on later recollection, broad assertions or documents created after positions have hardened.
The purpose of project records is not simply to prove that a problem existed. They should help establish cause, criticality, entitlement and consequence.
Baseline and updated programmes
The programme is usually central to a delay claim because it provides the planned sequence, logic, durations, constraints and path to completion against which later events can be assessed.
A defensible programme record normally includes the accepted or contractually relevant baseline, periodic updates in native format, progress status dates, actual start and finish dates, remaining durations, logic changes, constraints and narrative explanations for material revisions.
Native programme files are particularly important. A printed bar chart may show dates, but it often does not reveal the underlying logic, float, calendars, constraints or changes between updates.
- Retain each issued programme update in its native scheduling format.
- Preserve the corresponding PDF or issued report for document-control purposes.
- Record the data date and the progress information used in each update.
- Explain material changes to logic, duration, constraints and sequencing.
- Keep recovery and mitigation programmes separate from the original baseline and clearly identify their purpose.
- Maintain a change log so later reviewers can distinguish genuine updating from retrospective adjustment.
Daily site records
Daily records provide the contemporaneous field evidence behind the programme. Their value depends on specificity. A statement that work was delayed is less useful than a record identifying the activity, work area, planned operation, actual condition, instruction, labour, plant and resulting effect.
Records should be completed consistently and close to the time of the events. They should not be limited to exceptional days, because normal-progress records provide an important comparison when productivity, access or sequencing later becomes disputed.
- Work areas and activities undertaken.
- Labour by trade, shift and subcontractor.
- Plant and equipment deployed, idle or unavailable.
- Weather and its actual effect on specific operations.
- Access restrictions, permits, inspections and hold points.
- Materials, information and design releases received or outstanding.
- Instructions, changes, rework and disrupted work fronts.
- Photographs cross-referenced to date, location and activity.
Instructions, changes and design information
A delay event often develops through several documents rather than one clear instruction. A request for information may identify a design problem, meeting minutes may record the proposed response, an email may authorise temporary action and a formal instruction may follow later.
A defensible record preserves that full chronology. It should identify when information was required, when the issue became known, what response was requested, when a workable decision was received and whether further clarification or redesign followed.
Document registers should retain superseded drawings and revisions. Without them, it can be difficult to establish what information was available to the project team at a particular time.
Contractual notices and reservations
Notices do more than preserve contractual rights. When prepared properly, they create a contemporaneous account of the event, anticipated effect, contractual basis and action required from the receiving party.
The notice record should include the original notice, supporting updates, responses, requests for further particulars and any later change in the event's expected effect. A generic notice issued without follow-up may preserve less evidential value than a concise notice that is updated as the facts develop.
The project team should also distinguish notices from routine correspondence. Important contractual communications should be identifiable, searchable and linked to the relevant event and programme activity.
Meeting minutes and decision logs
Meetings often contain the most important project decisions, but minutes can become unreliable when they are issued late, record only conclusions or fail to identify responsibility and required dates.
A useful decision record identifies the issue, available options, information considered, decision-maker, agreed action, responsible party and required completion date. Objections or corrections to minutes should be issued promptly rather than raised for the first time during a dispute.
Decision logs are particularly helpful where mitigation, resequencing or temporary solutions are considered. They show what was reasonably known at the time and why an option was adopted or rejected.
Photographs, video and digital evidence
Visual records can confirm physical conditions, access, progress, congestion, incomplete predecessor work and the sequence of operations. Their usefulness depends on reliable context.
Photographs should retain original metadata where possible and be indexed by date, location and activity. Selected images pasted into a later claim document are less persuasive when the underlying files, sequence and provenance cannot be checked.
Drone surveys, progress scans, common-data-environment records and digital inspection systems can provide valuable evidence, but access permissions, export formats and retention periods should be addressed before the project closes.
Resource and productivity records
Where disruption or acceleration is alleged, records should show how labour and plant were planned, deployed and affected. Global monthly totals may not establish which activity consumed the resources or why productivity changed.
Timesheets, allocation sheets, plant logs, work-package records and quantity-progress data should use consistent identifiers. The objective is to compare resources and output over relevant periods and work conditions, not simply to show that total cost increased.
- Identify the affected operation
Define the activity, area, trade or work package said to have been disrupted.
- Establish the resource input
Use reliable labour, plant and shift records linked to that operation.
- Measure the output
Record installed quantities, completed units, work fronts or another suitable production measure.
- Record the changed condition
Identify congestion, resequencing, restricted access, repeated mobilisation, design change or other alleged cause.
- Test alternative explanations
Consider learning effects, workforce changes, supervision, rework, procurement and contractor-controlled inefficiency.
Cost and prolongation records
Additional time on site does not by itself prove the amount of a prolongation claim. The claimed cost should be reconciled to accounting records and assessed against the relevant delay period, contractual basis and actual expenditure.
Useful records may include cost ledgers, payroll, invoices, plant charges, accommodation, utilities, insurance, bonds, site establishment, supervision and subcontractor accounts. Cost codes should remain consistent enough to connect expenditure to the project and period under review.
Budgets and tender allowances can provide context, but actual cost records usually require separate analysis. Claimed amounts should also account for avoided cost, concurrent causes, non-compensable periods and costs that would have been incurred in any event.
Document control and authenticity
A credible record system preserves more than the final document. It maintains the original file, issue date, author, recipient, revision, transmittal and relationship to superseded material.
Native files, email headers, common-data-environment audit trails and revision histories can become important where the timing or authenticity of a document is disputed. Teams should avoid overwriting programme files, spreadsheets and reports without preserving the issued version.
The record-retention plan should also address staff departures, subcontractor close-out, access to cloud platforms and the export of information before licences or project systems are closed.
Common record weaknesses
- Programmes issued only as PDFs, without native files or logic-change records.
- Daily reports that repeat generic wording and do not identify affected work.
- Photographs without dates, locations or original files.
- Notices that are not updated as the event develops.
- Meeting minutes issued late or left uncorrected.
- Resource records that cannot be linked to activities or quantities.
- Cost ledgers that use inconsistent codes or combine unrelated expenditure.
- Retrospective chronologies prepared without references to contemporaneous documents.
- Important records held only in individual inboxes or personal devices.
A practical minimum record system
A project does not need an elaborate forensic database from day one. It needs a system that teams will use consistently and that links the principal records through common event, work-package and programme identifiers.
- Maintain an event register
Record the event, date first known, contractual notice, responsible person, affected activity and current status.
- Preserve monthly programme evidence
Retain native updates, PDFs, narratives, progress data and change logs.
- Standardise daily reporting
Use defined work areas, activity codes and resource fields rather than free-form narrative alone.
- Link commercial records
Connect notices, instructions, cost codes and subcontractor records to the same event identifiers.
- Review the record monthly
Check missing files, unexplained programme changes, outstanding notices and evidence gaps while they can still be corrected.
Final thoughts
A defensible delay claim is built during the project, not reconstructed entirely after completion. The most valuable records are created as part of good project management: reliable programmes, specific daily reports, clear decisions, timely notices and cost information that can be reconciled.
Good records do not guarantee entitlement, and poor records do not automatically defeat a legitimate position. They do, however, determine how confidently the facts can be tested, how efficiently advisers can work and how clearly the matter can be explained to a decision-maker.