eDiscovery Services for England and Wales Disputes: Comparison

Choose by the workstream carrying the most risk

Shortlist Computerforensicslab when forensic custody leads the brief, Everlaw when review technology is central, or SOS Systems when broad lifecycle support is required; these are documented capabilities, not independently tested results.[2][3][5]

Whichever provider is selected, divide the engagement into preservation, collection, processing, legal review and production. Give each workstream defined inputs, outputs, acceptance tests, responsibilities and change controls.

Confirm the governing disclosure regime

Record the court, track, claim type and orders first. PD57AD governs disclosure in the Business and Property Courts of England and Wales, subject to exclusions and orders.[6] Elsewhere, establish whether CPR Part 31 and related practice directions apply to the particular proceedings.[7] PD31B ordinarily applies to multi-track proceedings unless otherwise ordered.[8]

Under PD57AD, the Disclosure Review Document supports identifying, discussing and seeking agreement on Extended Disclosure under Models C, D and E.[6] Under PD31B, the Electronic Documents Questionnaire supports discussion of electronic disclosure, with completion and exchange addressed by its provisions and any order.[8] Confirm which document and timetable the matter requires.

Solicitors should retain decisions on applicability, scope, proportionality, relevance, privilege and production format. The provider should execute and report against those decisions. The cited pages do not give complete descriptions of Models B and C, model-specific thresholds or procedural deadlines.

Turn the DRD or questionnaire into testable work packages

Use the draft or completed DRD—or the Electronic Documents Questionnaire where applicable—as the scope record. Map every source and proposed search method to a task, owner and deliverable.[2][4]

• Collection: identify the custodians, systems, devices, cloud accounts and repositories to be acquired, with the permitted collection method.[1][2][3]
• Processing: define format conversion, filtering, de-duplication, indexing, text extraction, OCR and required metadata extraction.[1][5]
• Review: state who will assess relevance, responsiveness, privilege and confidentiality, and which decisions must be escalated to solicitors.[3][5]
• Production: identify the approved population, delivery format, metadata, searchable text and load files.[1][5]

For each package, specify inputs, included sources, date ranges, methods, exclusions, dependencies, outputs, acceptance tests, exceptions, owners, timetable and change control. Record assumptions about volume, accessibility, mobile devices, backups, deleted data and third-party repositories because proportionality considerations include volume, complexity and archive-retrieval cost.[1][2][4]

Require written approval before adding custodians, restoring archives, changing searches or adopting a more expensive collection method.

Set preservation and collection acceptance tests

Define the preservation population by issue, custodian, date range, system, device, cloud account, backup source and relevant third party.[1][2][3] Under PD57AD, a person who knows it is or may become a party must take reasonable preservation steps. These include suspending relevant deletion, notifying relevant employees or former employees in the specified circumstances and taking reasonable steps concerning third-party-held material. Legal representatives must advise clients and obtain written confirmation of the required steps.[6] PD31B separately addresses preservation once litigation is contemplated.[8]

Require the following deliverables:

• Preservation pack: hold notices, delivery and acknowledgement records, IT configuration changes, affected systems and dates, and records showing which email purges, message auto-delete settings and backup overwrite cycles were suspended.[1][2]
• Collection register: each custodian and source, collection method, operator, date, volume, transfer route, exceptions and completion status. The documented collection methods include forensic imaging, targeted searches and specialist tools intended to retain source metadata.[2][5]
• Integrity and custody evidence: hash records, chain-of-custody logs and evidence of encrypted transfer. Computerforensicslab describes hash-based integrity and chain-of-custody workflows.[2]

Set an escalation route for suspected deletion or tampering, encryption, damaged media and non-standard devices. Computerforensicslab distinguishes these situations from conventional disputes involving accessible data and cooperative custodians.[2] Ask bidders for sample preservation, collection, hash and custody reports before appointment.

Separate processing quality from legal review

Define processing outputs for de-duplication, filtering, indexing, format conversion, text extraction, OCR and every agreed metadata field.[1][5] Require a processed-data inventory, metadata map, de-duplication method, family-handling rules and exception reports covering encrypted, corrupt, unsupported or non-searchable files.

Test searchable text and OCR on a representative sample before approving full processing. Ask bidders to show how processing failures are identified, reported and corrected. Require a reconciliation of received, processed, excluded and failed items so an apparently searchable review set does not hide unreadable material.

Use a separate review protocol covering responsiveness, issues, privilege, confidentiality, escalation, reviewer training, quality-control sampling, email threads, near-duplicates, document families, languages and non-standard formats.[1][3] Record the agreed review methodology, validation approach and responsible legal decision-maker; do not rely on a historic case summary as the operative disclosure rule.

Solicitors should decide whether TAR or predictive coding is suitable. The provider should supply auditable search, processing and review records.[3][5]

Specify privilege handling and production format

Agree a privilege protocol before review begins. Name the decision-maker, redaction operator and escalation route, and define how potentially privileged families will be quarantined and checked. Privilege-log fields can include author, recipient, date and privilege type, recording the basis of the claim without revealing privileged content.[1]

PD57AD paragraph 13.1 defaults to native electronic copies preserving metadata, unless otherwise agreed or ordered.[6] PD31B separately addresses early format cooperation and native production, subject to agreement or direction.[8] Translate the applicable rule and protocol into a document-type specification, including justified exceptions and redactions; a supplier’s preferred format does not decide the legal requirement.

Native files retain functionality, formulas and metadata but may expose hidden data or tracked changes. TIFF or PDF images are static and can be paired with searchable text, but lose some native functionality.[1]

The production specification should cover:

• required metadata, searchable text, load-file structure, document identifiers, family links, redaction treatment and hidden content;[1][5]
• a production manifest, exception list, validation report and solicitor approval before delivery;
• role-based access, encryption at rest and in transit, and immutable audit trails;[2][3][4]
• sample load files, manifests, audit logs and redacted exports for compatibility testing.

Compare the providers on three deciding capabilities

Computerforensicslab

• Forensic collection and custody: Describes forensic imaging, targeted collection, hash-based integrity and chain-of-custody workflows, including matters involving suspected deletion, tampering or difficult devices.[2]
• Review technology: Describes processing, document review, analytics and TAR validation.[2]
• End-to-end production support: Its documented workflow covers collection, processing, review, analytics and TAR validation.[2]

Everlaw

• Forensic collection and custody: Describes cloud-source connectors, access controls and audit trails, but the cited page does not state whether forensic imaging, hash reports or chain-of-custody artefacts are included.[3]
• Review technology: Describes predictive coding, GenAI summarisation, Boolean, proximity, wildcard and fuzzy search, metadata filters, email threading, near-duplicate detection, concept clustering and visualisation.[3]
• End-to-end production support: Its documented platform capabilities cover document-review technology, access controls and audit trails.[3]

SOS Systems

• Forensic collection and custody: States that forensic collection forms part of its service.[5]
• Review technology: Describes processing, review technology and analysis support.[5]
• End-to-end production support: Says it assists UK law firms from preservation through presentation, including production support.[5]

Only the SOS Systems page expressly addresses UK law firms.[5] Confirm availability, delivery model and England-and-Wales experience before appointment.

What to confirm with each provider

The cited provider pages do not publish comparable prices or complete terms for contract length, cancellation, overages, hosting, retention or exit exports.[2][3][5] Put each of the following in the quotation, contract or exit schedule:

• Charges: collection, processing, hosting, users, review, production, professional services, exports and deletion, including payment triggers and scope-change charges.
• Hosting and service: hosting location, UK data-centre availability, data residency, subprocessors, incident handling and service levels. Relevant documented controls include restricted access, encrypted transfer, encryption at rest and in transit, audit trails and data-processing arrangements.[2][3][4]
• Retention: retention during and after the matter, suspension of deletion, final deletion timing and the form of deletion certificate.
• Exit: native files, images, searchable text, metadata, load files, coding, redactions, privilege logs, audit trails and technical documentation. Define formats, validation, delivery method, timetable, assistance and migration or egress charges.

Make appointment conditional on a deliverables test

Score bidders against the work packages, required artefacts, security controls, commercial terms and exit schedule. Ask the preferred bidder to demonstrate a sample workflow covering collection records, custody evidence, processing exceptions, review history and production export.

Appoint the provider only after the solicitors approve the responsibility schedule, disclosure scope, privilege workflow, production specification, change controls and exit terms in signed documents. Missing custody records, undefined exports or an attempt to transfer legal decisions to the provider should be resolved before work begins.

References

1. eDiscovery for Law Firms: A Complete Process Guide [2025] (v7labs.com)
2. E-discovery in law: a complete guide for UK litigation (computerforensicslab.co.uk)
3. Document Review – Everlaw (everlaw.co.uk)
4. eDiscovery compliance: a UK guide to legal and data protection obligations | Forensic Control (forensiccontrol.com)
5. Exploring the eDiscovery Lifecycle from Identification to Data Production | News | SOS Systems (sossystems.co.uk)
6. Justice UK — Practice Direction 57AD: disclosure in the Business and Property Courts (justice.gov.uk)
7. Justice UK — CPR Part 31: Disclosure and Inspection of Documents (justice.gov.uk)
8. Justice UK — Practice Direction 31B: Disclosure of Electronic Documents (justice.gov.uk)