§ Guide

The Missing Evidence Problem

This guide, 'The Missing Evidence Problem', addresses the challenges faced by UK lawyers, in-house counsel, and investigators when evidence is absent.

Ref · E-D · 2026 · §LIBClass · ConfidentialJuris · England & WalesStatus · Active

Guide · 17 pages · 22 min read · Published 2026-08-30

This guide, 'The Missing Evidence Problem', addresses the challenges faced by UK lawyers, in-house counsel, and investigators when evidence is absent. It covers how to prove what should exist, find where it went, and litigate the gap. The guide details investigating missing evidence in three moves: proving it existed, explaining its absence, and pursuing it where it still survives. It distinguishes routine loss from destruction, maps where missing material survives, and outlines the legal framework for preservation duties and their breach. Practical sections include litigating the gap, source architecture, worked examples, common mistakes, technical limitations, and questions to ask. It also provides a checklist, red flags, and guidance on when to involve a digital forensic expert. This resource is essential for anyone dealing with the absence of expected evidence in UK legal contexts.

Read this guide on your phone, browse guides by topic or go back to the full PDF library.

§ Credit and source

Published by Computer Forensics Lab on 2026-08-30. Original material of the practice, free to read, cite and download. See every guide's author and source.

§ Full text of The Missing Evidence Problem

Download the PDF

Prefer a PDF that matches this page exactly? Download the current text as a PDF, generated from the wording shown here, including any later corrections.

The Missing Evidence Problem

MISSINGEVIDENCE · A GUIDE FOR UK LAWYERS The Missing Evidence Problem Proving What Should Exist, Finding Where It Went, and Litigating the Gap COMPUTER FORENSICS LAB

§ ABOUT THE AUTHOR PREPARED BY COMPUTER FORENSICS LAB E-DISCOVERY TEAM

§ CONTENTS In this guide 01 Executive summary 02 The problem in plain English: gaps have causes, and causes leave evidence 03 Proving existence: the traces that show what was once there 04 Innocent or engineered: distinguishing routine loss from destruction 05 The recovery map: where missing material survives 06 Preservation duties and their breach: the legal framework 07 Litigating the gap: applications, inferences and remedies 08 Source architecture: where else the evidence lives 09 Worked examples 10 Common mistakes and technical limitations 11 Questions to ask · Suggested wording 12 Checklist and red flags · When to involve a digital forensic expert 13 Frequently asked questions 14 Glossary · References · Disclaimer · How a specialist laboratory can assist

§ 01 · ORIENTATION Executive summary THE HEADLINE POINT: MISSINGEVIDENCEISINVESTIGATEDINTHREEMOVES: PROVEIT EXISTED, EXPLAINITSABSENCE, ANDPURSUEITWHEREITSTILLSURVIVES: WITHTHE LITIGATIONCONSEQUENCESFLOWINGFROMWHATTHOSEMOVESESTABLISH

§ 02 · FIRST PRINCIPLES The problem in plain English: gaps have causes, and causes leave evidence

§ 03 · THEOUTLINEOFTHEVANISHED Proving existence: the traces that show what was once there

§ 04 · READINGTHECAUSE Innocent or engineered: distinguishing routine loss from destruction

§ 05 · THE RECOVERY MAP The recovery map: where missing material survives

§ 06 · THEDUTYCLOCK Preservation duties and their breach: the legal framework

§ 07 · THECONSEQUENCES Litigating the gap: applications, inferences and remedies

§ 08 · THEWIDERMAP Source architecture: where else the evidence lives EVIDENCE RECYCLE PRESERVATION SURVIVING SYSTEM DUPLICATES / DEVICE REFERENCES BOOKKEEPING COUNTERPARTS RESIDUE BACKUPS / POLICY / STORES FILE

§ 09 · IN THE WILD Worked examples EXAMPLE1 · THEFORTNIGHTTHATFELLSILENT EXAMPLE2 · THEPHONEINTHERIVERANDTHECLOUDTHATREMEMBERED EXAMPLE3 · THEGAPTHEPOLICYEXPLAINED

§ 10 · WHEREITGOESWRONG Common mistakes and technical limitations Common mistakes Technical limitations

§ 11 · INTERROGATORIES & DRAFTING AIDS Questions to ask · Suggested wording Ask your client Ask your opponent Ask your e Discovery / forensic provider SUGGESTED WORDING · PRESERVATION AND LOSS - EXPLAN AT I ON REQUEST

§ 12 · QUICK CONTROL Checklist and red flags · When to involve a digital forensic expert The missing-evidence checklist Red flags When to involve a digital forensic expert

§ 13 · COMMON QUESTIONS Frequently asked questions The other side says the documents were deleted under a retention policy. Is that the end of it? Can deleted material really be recovered, or is that television? How do we prove something existed if it no longer does? When does the duty to preserve actually start? Will a court really draw an adverse inference? We have discovered our own client's gap. What now?

§ 14 · REFERENCE Glossary Sources and authoritative references DISCLAIMER

§ HOW A SPECIALIST LABORATORY CAN ASSIST Working with Computer Forensics Lab Speak to a forensic examiner, not a salesperson. INSTRUCTTHELAB NEWENQUIRIESEMAILE - DISCOVERY

§ Common questions

Frequently asked questions

The other side says the documents were deleted under a retention policy. Is that the end of it?
Only if the policy story survives testing: the policy's terms and dates, its execution logs, the duty clock (§6) and the selectivity check (§4) either corroborate the account or contradict it: Example 3 shows the version that holds, Example 1 the version that does not. Ask for the records with §11's request; policies that ran as claimed can always produce them.
Can deleted material really be recovered, or is that television?
Both, honestly: recycle stores, versions, backups, duplicates and counterparts recover a great deal inside their windows (Examples 1-2), while properly wiped media and expired cloud stores are genuinely gone: §5's map with
How do we prove something existed if it no longer does?
From the estate's redundancy: quoting replies and thread structures, file-system and sync bookkeeping, counterpart copies, platform counters, and volume analysis (§3): traces that outline the item precisely enough to litigate. Counterpart copies are the gold standard: the deleted email's recipient rarely deleted it too.
When does the duty to preserve actually start?
On contemplation of proceedings, not service: PD 57AD's duty (with its hold-notice and suspension obligations) is engaged when litigation is reasonably in prospect, and the certificate later signs for compliance: which is why the contemplation date is investigated, not conceded, in every gap dispute. Material expiring before that date is retention; after it, the questions begin.
Will a court really draw an adverse inference?
On a proven record, yes: destruction evidenced, timed against the duty, with recovery exhausted: the inference calibrated to what the file shows: and on suspicion alone, no: §7's whole architecture exists because courts punish demonstrated conduct, not gaps as such. Build Example 1's schedule; skip Example 1's indignation.
We have discovered our own client's gap. What now?
Investigate it exactly as you would an opponent's: existence, cause, recovery: then preserve everything about the investigation, take conduct advice where §4's findings warrant it, and ensure the certificate and any witness evidence state the position accurately: the honest, evidenced account (Example 3's defence) is both the ethical course and, in practice, the winning one. What converts a gap into a catastrophe is almost never the loss; it is the account of it that unravels. cflab. u k · e-disc ove r y. u k ©2026 Computer Forensics Lab Ltd ·cflab.uk ·e-discovery.uk ·info@cflab.uk ·+44 (0)20 7164 6915 Page 15 of 17
§ Related documents
Instruct the practice

Bring us in early. Defensibility is built, not retrofitted.

Whether you are responding to a regulator, preparing for disclosure, or scoping an internal investigation, start the chain of custody with a short, confidential conversation.

WhatsApp