From Project Record to Dispute File: What Should Be Preserved?

Construction disputes are decided on evidence, but project records are usually created for delivery—not for a future tribunal.

The site team records progress to manage tomorrow’s work. The planner updates the programme. Commercial staff certify subcontractors. Engineers revise drawings. Finance records cost. Contract managers issue notices.

Years later, the dispute team may need to reconstruct the same project from those systems.

The best time to build a dispute-ready record is therefore before there is a dispute.

1. Preserve the complete contract formation record

Keep the final executed contract and the documents that establish what the parties agreed.

This normally includes:

• signed agreement;
• General Conditions;
• Particular Conditions;
• Contract Data;
• specifications/Employer’s Requirements/Scope;
• drawings identified as contract documents;
• pricing schedules;
• bills;
• tender addenda;
• accepted tender;
• clarifications incorporated into the contract;
• amendments;
• guarantees/securities; and
• document hierarchy.

Also preserve negotiation material where legal counsel advises it may be relevant and permissible to retain.

A dispute team should never have to ask which version of the Particular Conditions was actually signed.

2. Preserve formal contractual communications separately

Maintain a reliable register and archive for:

• notices;
• instructions;
• determinations;
• certificates;
• claims;
• responses;
• notices of dissatisfaction;
• early/advance warnings;
• variation/change documents;
• reservation-of-rights letters; and
• dispute referrals.

These are not the same as ordinary correspondence.

Preserve proof of:

• transmission;
• receipt;
• recipient;
• date/time; and
• the version actually sent.

3. Preserve project correspondence in context

Emails and letters often establish the factual history behind the formal documents.

Keep:

• correspondence threads;
• attachments;
• transmittals;
• RFIs;
• responses;
• design comments;
• action trackers; and
• agreed communication platforms.

An isolated PDF attachment may be difficult to interpret without the email that explains why it was sent.

4. Preserve meeting records

Minutes can show what the parties knew and when they knew it.

Keep:

• progress meetings;
• design meetings;
• coordination meetings;
• commercial meetings;
• risk meetings;
• site walk records;
• action lists; and
• approved corrections to minutes.

Record attendees and issue dates.

Where a party disputes a minute, preserve both the minute and the contemporaneous objection.

5. Preserve daily and weekly site records

Contemporaneous site records can become some of the most persuasive evidence in a delay or disruption dispute.

Useful records include:

• daily reports;
• site diaries;
• labour by trade;
• equipment;
• work fronts;
• quantities;
• weather;
• access restrictions;
• inspections;
• incidents;
• deliveries;
• work stoppages;
• photographs; and
• supervisor notes.

The record should be factual enough that someone unfamiliar with the project can understand what occurred.

6. Preserve programmes in native format

A PDF Gantt chart is not a substitute for the native schedule database.

Preserve:

• tender programme;
• baseline;
• all official updates;
• native P6/MS Project files or equivalent;
• PDF outputs;
• schedule narratives;
• calendars;
• logic;
• constraints;
• codes;
• resource/cost loading;
• progress data;
• accepted/rejected status;
• reviewer comments; and
• schedule transmittals.

Do not overwrite prior updates. Forensic analysis may depend on understanding how the schedule changed over time.

The SCL Protocol and AACE forensic schedule guidance both reinforce the importance of transparent programme data and methodology.

7. Preserve cost records with an audit trail

For monetary claims, summaries are not enough.

Retain:

• cost ledger;
• cost codes;
• payroll;
• timesheets;
• invoices;
• purchase orders;
• subcontract payments;
• equipment records;
• material records;
• accommodation;
• travel;
• insurance;
• bond costs;
• utilities;
• site-office cost;
• proof of payment where relevant; and
• month-end reconciliations.

A strong quantum file lets the reviewer trace:

claim summary → cost schedule → ledger entry → source document

8. Preserve change and instruction records

For every potential change, keep:

• baseline scope;
• instruction;
• revised drawing/specification;
• change notice;
• quotation;
• estimate;
• negotiation record;
• programme impact;
• cost code;
• approval; and
• final change order/amendment.

Where work proceeds before price agreement, preserve contemporaneous labour, plant and material records.

9. Preserve design and technical evolution

Design disputes are version-sensitive.

Keep:

• drawing register;
• native design files where appropriate;
• issue status;
• revisions;
• calculations;
• comments;
• review/approval workflow;
• model versions;
• technical queries;
• non-conformance reports;
• inspection/test plans;
• test results;
• as-built records; and
• handover documentation.

The record should establish not only what the final design was, but how and when it changed.

10. Preserve visual evidence and metadata

Photographs and video can be powerful when their provenance is reliable.

Preserve:

• original file;
• capture date/time;
• location where available;
• photographer/source;
• unedited version;
• index describing subject; and
• link to relevant activity/event.

Do not rely only on images pasted into monthly reports if originals exist.

11. Preserve subcontract and supplier records

Main-contract disputes often require supply-chain evidence.

Retain:

• subcontracts;
• scope and flow-down provisions;
• instructions;
• notices;
• progress records;
• payment;
• variations;
• supplier delays;
• purchase orders;
• delivery records;
• lower-tier claims; and
• settlements.

A Contractor may need to prove not only that it paid a subcontractor, but why the underlying cost arose and how it relates to the main-contract event.

12. Preserve people knowledge before they leave

Projects lose knowledge when key personnel demobilise.

For material events, consider creating factual event memoranda while memories are fresh:

• role of the author;
• dates;
• what happened;
• documents relied on;
• decisions made;
• unresolved facts.

This is not a substitute for a witness statement, and legal teams should control privileged investigations. It is a way to avoid losing basic project knowledge.

Legal hold, privilege and preservation discipline

Once a dispute is reasonably anticipated, legal counsel should advise on formal preservation obligations.

Key controls can include:

• suspend routine deletion;
• identify relevant custodians;
• preserve mailboxes and collaboration tools;
• preserve originals and metadata;
• separate legally privileged material;
• prevent unauthorised alteration;
• document collection method; and
• maintain secure backups.

Do not “clean up” a file by deleting documents that appear unhelpful. Selective destruction can create serious legal and evidential problems.

Build an evidence index, not a document warehouse

A million files are not an evidence strategy.

Create an issue-based index linking each disputed proposition to records:

This makes disclosure, expert analysis and hearing preparation significantly more efficient.

Preserve first; interpret later

At project stage, the team does not need to predict the exact legal theory of a future dispute.

It needs to preserve enough reliable information that future reviewers can establish:

what the contract required, what happened, when it happened, who knew, what work was affected, what the schedule consequence was, what cost followed and what the parties did about it.

That is the bridge from a project record to a defensible dispute file.