How Long to Keep Site Records: Construction Document Retention Requirements

This guide covers the site diary and every other document type your team produces on site, from daily allocation sheets to weather logs. It explains the legal basis for each retention period, the contractual obligations under NEC4, and the commercial cost of getting it wrong. If you want to know what records to keep in the first place, start with our what to include in a site diary guide first, then come back here.

The Short Answer: Minimum Retention by Document Type

Don't skip this table. It's the reference you need when someone at your company asks "do we really need to keep that?"

The "safe recommendation" column is what I'd tell any QS on a complex NEC4 project. The "minimum" is what the law requires. There's a gap between them, and claims live in that gap.

Why Retention Periods Matter More Than Most QSs Think

Here's what actually happens when records disappear. Not theoretical risk: real commercial consequences I've seen play out on live projects.

A contractor on a £28M highway improvement scheme completed work in 2016. In 2023, the employer raised a defects claim. The contractor's site diaries from 2016 had been deleted from the project server during a system migration in 2021. No backup. The contemporaneous records that would have shown the work was inspected, approved, and signed off at the time? Gone. The contractor settled for £340,000 because they couldn't evidence what their team had actually done seven years earlier.

It wasn't a legal issue or a technical issue. It was a records issue.

The retention period question isn't an administrative box-ticking exercise. It's a risk management decision with direct commercial consequences, and most commercial teams don't think about it until the claim letter arrives.

The Limitation Act 1980: Your Core Legal Framework

The Limitation Act 1980 sets the window in which legal proceedings can be brought in England and Wales. For construction, there are two main categories you need to understand.

Simple contracts (signed, not executed as a deed): 6 years from the date the cause of action arose, typically from when the breach occurred or the defect should have been discovered.

Contracts executed as a deed: 12 years from the same starting point. Almost every major construction contract in the UK, including NEC4 ECC, is executed as a deed. Check your contract execution page. If both parties have signed as a deed (or a company has signed with a company seal or two authorised signatories), you're in the 12-year window.

The practical implication? If your project completed in January 2025, an employer could bring a claim against you as late as January 2037 under a deed contract. You need records that can support your position on that day.

The latent defects exception is where 15 years comes from. Under section 14A of the Limitation Act 1980, if a claimant couldn't reasonably have discovered the damage until a later date, they can bring a claim up to 3 years after discovery, subject to a longstop of 15 years from the negligent act. For a contractor, this means that even 14 years past completion, a newly discovered defect could trigger a claim with 3 years to run. The 15-year safe recommendation in the table above reflects that risk directly.

Scotland operates under a different framework: the Prescription and Limitation (Scotland) Act 1973. The prescriptive period is 5 years for most obligations, but certain obligations can prescribe after 20 years. If you work on Scottish projects, get specific legal advice on retention. Don't assume the English and Welsh rules apply.

NEC4 Contract Obligations: What the Contract Actually Requires

NEC4 doesn't contain a specific clause titled "document retention." What it does contain is a series of obligations that make site records essential to your commercial position, particularly on Options C, D, E, and F where the financial outcome depends entirely on records of Defined Cost.

Clause 52.2: Open Book and Defined Cost Records

Under NEC4 Options C, D, E, and F, the Contractor must keep records of its Defined Cost and allow the Project Manager to inspect them. Clause 52.2 states that the Contractor must keep such records as the Project Manager instructs and provide accounts and documents showing Defined Cost at any time.

There's no explicit retention period in clause 52.2 itself. The obligation runs for the duration of the contract and into the defects correction period. In practice, for Options C/D/E/F, you need to retain Defined Cost records for at least as long as the final account can be reopened: 12 years from the final assessment date on a deed contract.

I've seen audits triggered 8 years after project completion on Options C contracts. The contractor who couldn't produce their Defined Cost records had no defence against the disallowed cost claim. They paid back £1.2M in cost disallowances they could almost certainly have contested. The records simply weren't there.

Clause 61.3: The Eight-Week Time Bar and Record Dependency

The eight-week time bar under clause 61.3 is the most commercially dangerous provision in NEC4 for poorly kept records. Under clause 61.3, if the Contractor doesn't notify a compensation event within 8 weeks of becoming aware of it, the Contractor is not entitled to any change in Prices or Completion Date.

The dependency on site records is direct: the Contractor's awareness date is established by what the site diary says. If the diary records that the Contractor became aware of an instruction on 15 March 2025, the 8-week clock runs from that date, giving a notification deadline of 10 May 2025. If the diary doesn't record when the instruction was received, both parties are arguing about a date from memory. That's a dispute nobody wins cleanly.

This is a records issue masquerading as a clause issue. You can't take advantage of your full 8 weeks if you don't know when the clock started.

Clauses 63 and 64: Records Required for Assessment

When a compensation event is assessed under clause 63, the assessment must be prospective from the dividing date (the date the Project Manager should have notified the event, or the date the Contractor notified it). Records of actual costs and resources deployed up to that date form the factual foundation of the assessment.

After assessment and acceptance of a quotation, those records don't stop being important. If the assessment is later challenged, or if the Project Manager makes their own assessment under clause 64 (because the Contractor's quotation was not submitted or was not accepted), those contemporaneous cost and resource records become critical evidence. For the duration of the 12-year limitation period under a deed contract, they can be called upon at any time.

CDM 2015: The Records That Never Go Away

The Construction (Design and Management) Regulations 2015 create retention obligations that operate completely separately from the Limitation Act. They're not time-limited in the same way. They're tied to the life of the structure.

Regulation 12: The Health and Safety File

The principal contractor must provide the principal designer with information for the health and safety file. Once complete, the file must be handed to the client and kept available for as long as the structure remains in use. This isn't a 15-year obligation. It's permanent.

The health and safety file typically includes:

• As-built drawings and specifications
• Records of materials used, particularly hazardous materials
• Maintenance and operational requirements
• Emergency procedures
• Residual risks not eliminated during construction

The client becomes the custodian of this file on handover. But the contractor should keep copies. If a worker is injured in 2045 on a building you completed in 2025, questions will arise about how it was built. If you have no copy of the health and safety file, you're reliant entirely on what the client has preserved. That's not a position I'd want to be in.

Pre-construction information gathered under CDM 2015 Regulation 4, including asbestos surveys, ground investigation reports, and hazardous material assessments, should be retained permanently. The Control of Asbestos Regulations 2012 specifically requires that records of asbestos surveys, condition monitoring, and removal work are kept for the life of the building.

Insurance Requirements: The Clock You Didn't Know Was Running

Professional indemnity insurance and contractors' all risks insurance both create document retention obligations that practitioners consistently underestimate. I've rarely seen this discussed properly in commercial team inductions.

Most PI policies operate on a "claims made" basis: the policy responds to claims made during the policy period, regardless of when the work was done. This creates a retention problem: if you face a claim in 2035 for work done in 2025, your insurers will ask for contemporaneous records from 2025. If the claim involves allegations about site methodology or supervision, the site diaries from 2025 are your first line of defence.

The standard guidance from construction insurance brokers is to retain all project records for the duration of PI coverage plus 6 years. Given that many contractors maintain rolling PI cover indefinitely, this effectively means permanent retention of records for significant projects.

There's a practical shortcut that works for most contractors. Decide at handover which projects represent material risk (contract value above a threshold, complex ground conditions, high-specification finishes, public use buildings) and commit to 15-year digital retention for those. For smaller projects, 12 years is defensible for deed contracts, 6 years for simple contracts. The key is to make a deliberate decision at handover rather than letting records drift into deletion by default.

Employer Requirements: The Contract Conditions You Need to Check

Construction contracts often contain specific document retention obligations beyond what the law requires. Under NEC4, these can appear in the Contract Data (particularly if the employer is a public body subject to public procurement regulations) or in additional Z clauses.

Some common employer-specific requirements I've encountered:

Public sector contracts (Network Rail, Highways England, local authorities) frequently require records to be retained for a minimum of 7 years and provided on request. Some Network Rail contracts specify 10 years. These obligations sit alongside, not instead of, the Limitation Act requirements.

PFI and long-term contracts sometimes require records to be available for the entire concession period, which can be 25-30 years. If you're a subcontractor on a PFI scheme, you need to understand the head contract obligations, not just your subcontract.

Government framework agreements may include data retention schedules that comply with the Public Records Act 1958 and the Freedom of Information Act 2000. These requirements apply to the employer but can flow down through contract terms.

Always read your contract. Specifically, check:

1. Any schedule of contract data that references record keeping
2. Z clauses (NEC4 additional conditions)
3. The employer's requirements document
4. Any framework agreement that governs the contract

Digital Records: The Format Problem Nobody Talks About

Keeping records for 12-15 years is one thing. Keeping them in a readable format is another. These are genuinely different problems, and most organisations solve only the first one.

I've seen a project from 2009 where the site diaries were stored in a proprietary file format from a software company that no longer exists. The files physically exist on a backup server. Nobody can open them. For limitation purposes, they might as well not exist.

The practical rules for digital retention:

Use open or widely adopted formats. PDF/A (ISO standard archival PDF) is the gold standard for long-term document retention. Plain text (UTF-8), JPEG, and PNG are also reliable formats unlikely to become unreadable. Proprietary formats from project management software, even mainstream products, carry risk over 10-15 year horizons.

Separate storage from software. Your site diary software account and your archived records are not the same thing. If you cancel your subscription in 2030, you need to know that you've exported all historical records in a readable format. Don't rely on software vendors to retain your records for you.

Apply version control and metadata. Each archived record should carry a clear date, project reference, and document type. A PDF labelled "IMG_3847.pdf" is useless in litigation. A PDF labelled "2025-03-15_ProjectRef_SiteDiary_Block-C.pdf" is useful.

Test your backups. At least annually, verify that archived records from previous years can actually be opened and are complete. Backup corruption is more common than people realise, and discovering it 10 years later rather than 2 years later has serious consequences.

Three copies, two formats, one off-site. This is the standard 3-2-1 backup rule applied to project records. Three copies of every record, stored in two different formats, with at least one copy stored off-site or in a cloud environment that doesn't depend on your internal systems.

Common Mistakes: Why Records Disappear Too Early

The records that cause problems aren't always the ones nobody bothered to create. They're often records that existed and were destroyed before anyone knew they'd be needed.

1. Deleting records during system migrations. IT projects are the most common trigger for accidental record destruction I've seen. When a company migrates to a new document management system, old records get classified as "legacy" and deleted without any commercial review. Someone in finance or IT decides to archive and purge, without understanding that those files represent 12 years of potential litigation exposure. Every system migration should require sign-off from the commercial team before any construction project records are deleted. This should be a policy, not a conversation.

2. Treating record retention as a project cost. Digital storage is cheap. Genuinely cheap. Storing 10 years of site diaries for a £50M project in PDF format typically requires less than 50GB of storage, which costs under £5 per month in cloud storage. The commercial risk of not having those records is measured in hundreds of thousands of pounds. There is no economically rational argument for deleting project records early.

3. Confusing "project closed" with "retention period started." On some projects, especially framework contracts, there's ambiguity about when the limitation period begins. For most purposes, the clock starts from practical completion or from the date the cause of action arose (which could be later, for latent defects). "Project closed" on your internal CRM is not the trigger. Get legal advice if you're uncertain about when your clock starts.

4. Keeping the records but not the metadata. A box of site diaries with no clear labelling, project reference, or date ordering is technically retained but practically useless. Records need to be findable and legible under time pressure. When your commercial director gets a claim letter on a Friday afternoon, they need to pull the relevant site diaries for Q3 2022 within an hour. If that isn't possible, the records might as well not exist.

5. Subcontract records that never make it to head office. Subcontractors often keep their own site records that the main contractor never sees. Under NEC4 Options C and D, the head contractor is responsible for Defined Cost across the supply chain. If a subcontractor's records are needed to defend a disallowed cost allegation, and those records disappeared when the subcontractor moved offices, you have a serious problem. Your subcontract terms should include a records retention obligation that mirrors your main contract requirements. Most don't.

6. Assuming your software company keeps your records. I've seen this cause real commercial harm. A contractor assumed their site diary app was their archive. When the commercial manager left and the subscription was transferred to a new account, the historical data didn't transfer cleanly. Three years of site diaries from a completed project were inaccessible. Never treat a SaaS subscription as a records management solution.

Worked Example: The Cost of Early Deletion

Scenario: On a £42M reinforced concrete frame package (NEC4 Option C, executed as a deed, completed April 2020), the contractor's records manager ran a routine archive clearance in November 2025. The written policy said "retain project records for 5 years after project completion." That got the clearance to 2025. Records were deleted.

In March 2026, the employer raised a claim for water ingress into the structure, alleging defective concrete placing in 2019. The claim was for £890,000.

The contractor had no contemporaneous records of the concrete mix designs actually used (as distinct from specified), the supervision records for pours in the affected area, or the quality inspection records showing the work was accepted at the time.

Their position: "The work was done correctly, and the problem is a design issue." The employer's position: "The records don't exist, so you can't prove it."

The claim settled for £420,000. The contractor's legal team believed they had a strong defence on the merits. Without records, the risk of losing at adjudication was too high to take to a hearing.

The cost of retaining those records digitally from 2020 to 2026? Approximately £180 in cloud storage. The cost of deleting them? £420,000 plus legal fees.

Digital vs Paper: What Actually Holds Up

The legal status of digital records in UK construction disputes is settled. Digital records are admissible as evidence. They don't need to be paper. But they do need to be authentic, unaltered, and complete.

The practical differences between digital and paper that matter for retention:

Authenticity: Paper records with original signatures carry inherent authenticity. Digital records need to demonstrate they haven't been altered since creation. This means using software that timestamps records at creation and prevents backdating (or logs it clearly), or applying digital signatures or hash verification to archived PDFs.

Completeness: Paper records can be accidentally incomplete (pages missing) but can't be selectively deleted without physical evidence. Digital records can theoretically be manipulated. Good records management software creates an audit trail that shows when records were created, who accessed them, and whether they've been modified.

Legibility: Paper deteriorates. Digital records don't, but they can become unreadable due to format obsolescence (as discussed above). Archive PDFs rather than proprietary formats.

Accessibility: Paper records in a warehouse are hard to search quickly. Digital records can be retrieved in seconds if properly organised. For complex disputes, the ability to pull records from a specific date range or project section is a significant commercial advantage.

For large NEC4 projects, digital-first is the right approach, provided the format and backup discipline is right. See the site diary template and completion checklist for practical guidance on structuring records from day one in a way that makes long-term retention manageable.