How Long to Retain Project Records on UK Projects

A completed installation can still create a live commercial problem years later.

The client queries a variation. An insurer asks for evidence. A new project team wants to know why a detail differs from the original drawing. A contractor needs to establish who approved a change before manufacture began.

When considering how long to retain project records, the useful answer is not simply “six years”. It is: retain a complete, usable decision history for as long as someone may reasonably need to establish what was agreed, what changed, what evidence was provided and what was accepted or challenged.

For high value bespoke construction, fit out, joinery and specialist fabrication, that history can be more valuable than any individual drawing or email.

A folder full of files does not help much if nobody can connect a site instruction to the revised scope, the photographs, the acceptance and the invoice.

How long to retain project records in the UK

There is no single retention period that suits every project.

Your contract, the legal basis on which it is executed, warranty obligations, insurance requirements, tax rules and the nature of the works can all matter. A short office fit out and a complex residential joinery package may have very different risk profiles, even where both are delivered by the same business.

In England and Wales, an action founded on a simple contract is generally subject to a six year limitation period from the date the cause of action accrued. Actions upon a specialty can be subject to a 12 year period. Agreements executed as deeds are therefore one reason businesses should not assume that six years is an appropriate universal retention period.

The applicable limitation period depends on the claim and circumstances. A retention policy should not be based on those headline periods alone.

Some building related claims can involve substantially longer statutory periods. The Building Safety Act 2022 introduced a 15 year limitation period for certain claims relating to damage or defects in buildings and, for certain claims under section 1 of the Defective Premises Act 1972 where the right of action arose before the relevant commencement date, a 30 year period can apply.

These are specialised regimes. They should not be interpreted as a blanket requirement to retain every construction project record for 30 years.

There can be other reasons to preserve records for longer. Product and workmanship warranties may extend beyond practical completion. Professional indemnity, public liability or latent defect insurance arrangements may create particular documentation requirements. Building safety, maintenance, compliance, fire stopping, testing and traceability information can also remain relevant long after the installation team has left site.

Accounting and tax records have their own retention requirements. These should not be confused with the evidence needed to explain a contested instruction, variation or disputed acceptance.

Keeping an invoice for tax purposes is not the same as keeping the approvals, drawings, photographs and correspondence that establish why the invoice became due.

This article provides operational guidance, not legal, tax or insurance advice. Businesses should have their contracts, insurance arrangements and regulatory obligations reviewed by appropriate professional advisers and turn those requirements into a retention schedule their teams can actually follow.

Start with the commercial risk, not a storage limit

The wrong question is often:

“How long do we have to keep this?”

A better question is:

“What would we need to show if this project were challenged in five, eight or 12 years?”

Consider a specialist joinery package.

Manufacture starts following an amended drawing issued after a site meeting. The client representative gives approval verbally. Months later, the completed item is said to be outside the agreed scope.

If the record consists of “Sent you the photos on WhatsApp mate”, both parties have a problem.

The contractor may have done exactly what was instructed. The client may genuinely believe a different arrangement was approved. Neither position is strengthened by an incomplete trail.

A defensible project record connects the original requirement, the proposed change, its cost or programme consequence where relevant, the authority behind the decision, the evidence of delivery and the acceptance or challenge that followed.

Retention is therefore not simply an IT or storage decision. It is part of project governance.

Retention preserves information. Governance preserves what that information meant, who acted on it and what happened next.

What a retained project record should contain

Retaining every duplicate email indefinitely is not a sound records strategy.

It creates search costs, confusion and potential data protection issues without necessarily preserving the decisions that matter.

The objective should be to retain the material project record in a structured form, together with enough context to interpret it later.

For a high value bespoke project, the core record will usually include:

• the agreed scope, contract documents, drawings, specifications and acceptance criteria;
• controlled revisions, site instructions, requests for information and agreed variations;
• evidence of manufacture, delivery, installation, testing and completion, such as dated photographs, delivery notes and certificates;
• approvals, rejections and challenges, together with sufficient information to identify the relevant person, party or project role;
• payment applications, valuations, invoices, payment confirmations and records of outstanding conditions; and
• relevant correspondence where it explains a material decision rather than merely repeating information stored elsewhere.

The key is context and attribution.

A photograph without a project reference, date, location or explanation may provide useful background, but it can be weak evidence.

An approval that does not identify what scope or acceptance criteria were being considered may create more uncertainty than it resolves.

Retain the record of change, not just the final version

Final drawings matter.

They are not enough on their own.

In bespoke work, some of the most expensive disagreements concern the journey between the first drawing and the final result.

A ceiling level changes after setting out. A client requests a different veneer after material procurement. An architect issues a revised detail while manufacture is already under way.

Each change may be entirely reasonable.

Each can also affect cost, programme, quality, sequencing or responsibility.

If you retain only the final PDF, you may lose the basis for the decision.

The questions years later become:

Who requested the change?

What was proposed?

When was the consequence explained?

What evidence supported it?

Who responded?

What happened next?

A proper retained record preserves those answers alongside the final deliverable.

This is why append only and tamper evident records can have practical value. They do not make either party automatically right. They make it harder for important project history to be quietly rewritten after the relationship has become difficult.

Bespea is designed around this principle, creating a structured, traceable record of project decisions, evidence, acceptance and challenge while keeping human authority explicit and without replacing the tools teams already use to deliver the work.

Set different retention periods by record type

A sensible retention policy does not need to be complicated, but it should distinguish between records serving different purposes.

The governed decision history, contract documents, material change records and completion evidence may justify a longer retention period.

Routine working notes, duplicated communications and superseded drafts with no continuing evidential or decision value may have a shorter lifecycle, subject to applicable contractual, regulatory and legal requirements.

The policy should also define when the retention period begins.

Depending on the record and obligation, the relevant trigger might be practical completion, final account, expiry of a warranty, the end of an insurance period or another legally relevant event.

For projects with phased handovers, different packages may also have different relevant dates.

Automatic deletion rules should not remove material evidence while a claim, complaint, insurer notification, adjudication, investigation or formal challenge is live or reasonably anticipated.

A retention schedule therefore needs a clear hold process.

Someone must be able to stop scheduled deletion, identify the relevant records and preserve them intact.

Make records usable when the project team has moved on

A record retained for 12 years is useful only if somebody can understand it in year 12.

People leave businesses. Email accounts close. Cloud folders are reorganised. Software changes. The person who “knows the whole story” may no longer be available to explain it.

Use consistent project identifiers, naming conventions and version controls.

Preserve the relationship between a variation request, its supporting evidence, the decision that followed and the commercial consequence where relevant.

Record the project role and party associated with material decisions, not simply a person's name without context.

Where evidence is exported or shared, preserve enough provenance to understand its source and when it was created or submitted.

Access matters as much as storage.

Not everyone should be able to alter a project record, and not every external party should automatically see every commercial detail.

Controlled access, explicit permissions and portable evidence packs are usually more useful than sending a compressed folder containing hundreds of unlabelled attachments.

A practical retention policy for specialist contractors

For each project, nominate an owner for the final project record before work starts.

That person does not need to chase every photograph or approval personally, but someone should be accountable for ensuring the project reaches close out with a usable record.

Build the process around a straightforward governed sequence:

Define the scope and milestones.

Set the acceptance criteria.

Capture and submit evidence against the work.

Record explicit acceptance or challenge.

Establish whether the agreed conditions relevant to payment readiness have been evidenced.

This creates a commercial trail as work progresses rather than attempting to reconstruct an archive under pressure after an invoice has been challenged.

At close out, preserve a controlled snapshot of the material project record.

Include the final scope, material change history, key decisions, evidence of completion, outstanding matters and relevant payment position.

Apply the retention periods required by your contracts, advisers and applicable obligations. Record the planned review or disposal date. If a dispute, claim or credible issue arises, place the relevant records on hold.

The objective is not to keep everything forever.

It is to keep the right things for the right period, in a form that allows a client, contractor, adviser or insurer to understand the same project history:

what was agreed, what changed, what evidence was provided, who made the relevant decisions and what happened next.

That is how a project record remains useful long after the site has been cleared.