Keep WhatsApp Records 6–15 Years for UK Builders' Compliance

Discover the legal requirements for retaining WhatsApp project messages in the UK construction industry, from standard six-year claims to 15-year Golden Thread obligations.

By James Shorter ·

Keep WhatsApp Records 6–15 Years for UK Builders’ Compliance

Builders reviewing a project message on smartphone

Keep substantive WhatsApp project messages for at least six years, and up to 12 to 15 years on higher risk or long-term building work, because that is the window most claims and building liabilities can surface. The moment someone makes a decision or instruction over WhatsApp, capture it into your formal, searchable project record. WhatsApp chats count as electronic documents under the Civil Procedure Rules, so treat them that way from day one.

TL;DR:

  • Substantive WhatsApp project messages should be retained for at least six years for standard claims, and up to 15 years for high-risk or long-term building projects.
  • Deleting messages does not eliminate legal disclosure risks, as deleted but recoverable messages remain disclosable under court rules.
  • Automating message capture at the moment decisions are made ensures reliable, metadata-rich records that meet legal and Golden Thread requirements.
  • Retention policies should be clearly documented, with designated responsible persons and specific retention bands aligned with project risk and scope.
  • For small domestic projects, a six-year retention period is usually sufficient, whereas high-risk buildings require a longer archive period to meet regulatory standards.
BRCKS
brcks.io
Turn WhatsApp Into Project Records
BRCKS captures WhatsApp decisions, variations and RFIs in one searchable project record, with audit trails and the right project context.
Visit BRCKS

Table of Contents

Why the law and standards make WhatsApp part of your project record

WhatsApp messages are not a casual aside from your project paperwork. Under Part 31B of the Civil Procedure Rules, electronic communications, including text messages and their metadata, are disclosable in court proceedings if relevant, even when someone has deleted them but they remain recoverable. That means a WhatsApp message agreeing a variation carries the same legal weight as a signed instruction.

The ICO goes further: it advises against using messaging apps as your primary records system at all. Auto-delete settings and cleared chats do not exempt you from disclosure duties, so anything substantive needs to move into a formal system.

For higher risk buildings, the Golden Thread guidance sets the bar higher still: project information must be secure, version-controlled, searchable and ready to hand over to the next owner or regulator. A WhatsApp thread scrolling off someone’s phone fails that test outright.

A few points worth holding onto:

  • CPR disclosure duties apply to WhatsApp whether or not a message has been deleted, as long as it is forensically recoverable.
  • The ICO treats messaging apps as unsafe primary records and expects substantive decisions to be transferred elsewhere.
  • Golden Thread expectations require electronic, auditable and transferable project information for higher risk buildings.
  • Local authority retention schedules often mandate long retention periods for construction and ownership records, which is a useful benchmark even outside building control.

How long should you actually keep WhatsApp project messages?

Legal exposure, not habit, should set your retention clock. The Limitation Act 1980 gives most contract and tort claims a six year window, but certain building related claims can run to 15 years. That gap between six and 15 years is exactly why a blanket “keep everything forever” approach is overkill for some projects and dangerously short for others.

Six to fifteen year retention timeline

Most UK contract and tort claims fall under a six year limitation window, with specific building related claims extending to 15 years under the Limitation Act. That six year figure is your baseline for standard domestic and small commercial work.

In practice, three retention bands cover most projects:

  • Operational (3 years): day to day site chatter, logistics, scheduling, nothing that touches cost or design decisions.
  • Standard (6 years): variations, instructions, RFIs, anything that could feature in a contractual dispute.
  • Archive (12 to 15 years): structural work, higher risk buildings, anything with long tail liability or Golden Thread obligations.

Record the band you have chosen against each project, and get sign-off from whoever holds commercial responsibility. That single line in your project pack turns a vague habit into a defensible policy.

How to capture, archive and index WhatsApp conversations

Capturing a message after the fact rarely works. By the time a dispute surfaces, someone has changed phones, cleared storage, or simply forgotten the context. The fix is to capture at the point the decision is made, not at the point you need it.

  1. Capture at source: export, forward or integrate the message into your project record the moment an instruction, variation or decision happens on WhatsApp, not weeks later.
  2. Preserve the metadata that matters: sender, recipient, timestamp, project code, site location, attachments and who owned the decision. Text alone is weak evidence without this.
  3. Choose automation over manual copying: manual screenshots lose timestamps and threading and are easy to forget under pressure; an automated capture system logs everything as it happens, which scales across multiple sites and subcontractors without relying on memory.
  4. Store with version control: encrypted backups, role-based access so only the right people can edit, retention flags tied to your chosen band, and a documented disposal route when the retention period ends.

Pro Tip: Treat every WhatsApp message that mentions cost, time or design as a variation until proven otherwise, and capture it before you reply.

Manual capture has a place on very small jobs, but it depends entirely on someone remembering to do it every single time, which is where most paper trails fall apart. Automating the transfer from WhatsApp into a structured, searchable project record removes that dependency and keeps metadata intact, which the ICO’s discussion paper on messaging and records flags as the practical route to meeting disclosure duties without racking up legal costs chasing down old phones. Our guide to site communication workflows walks through this in more detail for teams still relying on scattered threads.

Deleted or ephemeral messages: what the disclosure rules say

Deleting a WhatsApp message does not make it disappear from a legal standpoint. Under CPR Part 31B, a message that has been deleted but remains forensically recoverable is still disclosable, and courts expect parties to search mobile phones, backups and cloud storage as part of a proportionate disclosure exercise. Deleting evidence deliberately once a dispute looks likely can lead to sanctions or an adverse inference against you, which is a worse outcome than the message itself would ever have been.

If you discover a relevant message is missing:

  • Preserve the device and stop using it for anything that might overwrite data.
  • Note down the timeline of what was said and when, from memory and from any surviving context such as replies that reference it.
  • Tell whoever is handling the dispute or your solicitor immediately, rather than trying to reconstruct it yourself.
  • Check backups, including cloud backups, before assuming the message is genuinely gone.

The better fix sits upstream of all this: make capture mandatory for site instructions and variations as they happen, so there is nothing left relying on a disappearing message in the first place.

Project record retention checklist and policy template

A short, written policy beats a good intention every time. Keep it to one page and pin it to your project induction pack.

  1. Capture triggers: any message covering cost, time, design, access or safety gets captured immediately.
  2. Metadata fields: sender, recipient, timestamp, project code, site, attachments, decision owner.
  3. Storage location: a named, searchable project record, not a personal phone.
  4. Retention band: operational, standard or archive, chosen at project start.
  5. Responsible person: name the person who owns capture and review for each project.
  6. Review date and disposal route: set a date to check retention compliance and a documented way to dispose of records once the period ends.

For a domestic refurbishment, standard (6 year) retention is usually enough. For a higher risk building handover, archive (12 to 15 years) aligns with Golden Thread expectations and gives the next owner a record that actually holds up, as covered in our handover documentation guide.

What two decades on site taught me about message capture

What two decades on site taught me about message capture — overview diagram

Twenty years of building taught me that disputes rarely hinge on who was right. They hinge on who can prove it. A verbal instruction over WhatsApp feels informal at the time, right up until it becomes the only evidence either side has six months later.

The fix is not asking subbies to change how they talk to you. It is capturing what they already send, automatically, so nothing depends on someone remembering to forward a screenshot. Start with one project, run a short induction so the team understands why capture matters, and lead by example by capturing your own messages first. Teams that do this see fewer disputed variations and far less time lost chasing down who said what.

— James

How BRCKS keeps your WhatsApp messages as proper project records

We built the software so you keep messaging the way you already do, including WhatsApp through a dedicated business number, while every decision gets filed where you can find it later. Messages feed straight into site diaries, RFI logs and photo records, searchable in plain English, which saves time that used to go on hunting through old chats.

BRCKS

  • Metadata, timestamps and attachments are preserved automatically, not copied by hand.
  • Every variation and instruction carries an audit trail, with retention flags matched to the band you choose.
  • Subcontractors and clients join free, so capture does not depend on everyone buying extra software.

Plans start from £40 per seat per month billed annually. Have a look at BRCKS for builders or check pricing to see how it fits your next project.

FAQ

How long should builders keep WhatsApp messages for a project?

Keep substantive project messages for at least six years to cover the standard limitation period for contract and tort claims, extending to 12 to 15 years for higher risk or long term building liabilities. The retention band should be set at project start and recorded in your project pack.

Are WhatsApp messages legally admissible as evidence?

Yes. Under the Civil Procedure Rules, WhatsApp messages are treated as electronic documents and are disclosable if relevant to a dispute, including deleted messages that remain forensically recoverable.

Can I just delete old WhatsApp messages to reduce risk?

No. Deleting messages once a dispute is foreseeable can lead to sanctions or an adverse inference against you under disclosure rules, and recoverable deleted messages remain disclosable regardless. The safer route is capturing instructions into a formal record at the time, not deleting them later.

Who is responsible for retaining WhatsApp project records?

Responsibility should sit with a named person on each project, usually the site or project manager, rather than being left to whoever happens to receive the message. That person owns capture, storage and the eventual review and disposal of records.

Does WhatsApp retention apply to small domestic jobs too?

Yes, though the retention band can be lighter. A standard six year retention period usually covers domestic refurbishment work, while higher risk or structural projects need the longer archive band to meet Golden Thread expectations.

Sources

Recommended


How BRCKS Can Help

Managing long-term compliance across fragmented WhatsApp chats is a significant risk for any UK construction firm, but BRCKS simplifies this by centralising all project communication in one secure location. By moving your team’s dialogue into our platform, you ensure that every decision and document is automatically archived and easily searchable for the required statutory period. This transition not only protects your business from future legal disputes but also creates a more organised, professional environment for your daily operations. We invite you to explore how BRCKS can safeguard your project history and streamline your compliance workflow today. Learn more at BRCKS and explore our full feature set.


Sources