WoluTools
Find a tool

eDiscovery Production Validator

eDiscovery Production Validator Online: validate a production set before delivery day.

Turn a production archive into an exact missing-file and load-file QC register.

START HEREChoose documentsZIP, TAR, TAR.GZ
Choose documents Try prepared example
Maximum
5 archives · 64 MB total · 2,000 files and 128 MB once unpacked
File handling
Draft 2 hours · encrypted result 24 hours
FREE3 jobs a dayFree: up to 3 files, 50 pages, 10 MB · 2,500 load-file rows
PROUp to 200 jobs a day€12.99/month or €89.99/year
See plans

Larger files and productions need Pro. Failed jobs are never counted.

  • Prepared example is free
  • 3 free jobs a day
  • Cancel anytime
EXAMPLE RESULTSample data
Documents · 640
Bates gaps · 4
Twenty-one production defects need correctionHTML, protected production inventory and issue CSV files, technical JSON and manifest
Documents
640
Missing natives
17
Bates gaps
4
Formats, limits & file handling
Works with
ZIP, TAR, TAR.GZ
Limit
5 archives · 64 MB total · 2,000 files and 128 MB once unpacked
You receive
HTML, protected production inventory and issue CSV files, technical JSON and manifest
File handling
Draft 2 hours · encrypted result 24 hours

Turn a production archive into an exact missing-file and load-file QC register.

THREE CLEAR STEPS

From your documents to a usable result.

  1. 01
    Add your input

    Limits and supported formats are visible before you begin.

  2. 02
    Review the result

    The register lists missing natives, images and text, load-file errors and Bates gaps, each traceable to its path in the archive.

  3. 03
    Download

    Use your free job, plan or credits. Failed jobs are never counted.

Prepared result preview

See the decision before sharing a real file.

Turn a production archive into an exact missing-file and load-file QC register. This prepared example uses fictional data and the same evidence structure as the server export.

✓
Nothing is uploadedPublic demo only

Legal data delivery

Twenty-one production defects need correction

No evidence file is executed; parent-child attachment relationships are outside this version and every reported path issue remains traceable to the submitted package.

Actual prepared coverage: DAT, OPT, images, text and referenced natives

  • ErrorReferenced native missingABC00000422 · NATIVE\ABC00000422.xlsx
  • WarningBates sequence gapABC00000218 → ABC00000220
  • EvidenceReferenced text verifiedABC00000504 text path exists and its hash is recorded
Documents
640
Missing natives
17
Bates gaps
4
Show the verified package

HTML, protected production inventory and issue CSV files, technical JSON and manifest

Engine ediscovery-production-qc-v1 · rules concordance-opticon-ipro-2026-08-30

One focused workflow

From bounded input to evidence you can review

  1. Add the source.Accepted inputs are ZIP, TAR, TAR.GZ. The limit is 5 archives and 64 MB in total; once unpacked, a production may hold up to 2,000 files and 128 MB. Free jobs take up to 3 files, 50 pages and 2,500 load-file rows, with files up to 10 MB.
  2. Confirm the job.Every assigned source number, selected filename and setting stays visible before the confirmed SHA-256 input hash is accepted. Product-specific mappings remain explicit settings rather than guessed roles.
  3. Process in isolation.A one-job networkless sandbox receives only this job and cannot access accounts, queues, encryption keys or other customer storage.
  4. Review exact findings.Check DAT, OPT and LFP load files, referenced natives, images, text, Bates ranges and file hashes as one bounded package.
  5. Download the evidence.HTML, protected production inventory and issue CSV files, technical JSON and manifest Every output hash is covered by the coordinator-created manifest.

What this product does not claim

No evidence file is executed; parent-child attachment relationships are outside this version and every reported path issue remains traceable to the submitted package.

Clear answers

eDiscovery Production Validator FAQ

What should the production package contain?

A ZIP, TAR or TAR.GZ holding the load files and the folders they reference. DAT, OPT and LFP load files are read, with up to 100,000 rows and 2,000 archive members. Free jobs cover up to 3 files, 50 pages and 2,500 load-file rows per job, with files up to 10 MB.

Which defects are reported?

Natives, images or text referenced by a load file but missing from the package, Bates sequence gaps such as ABC00000218 followed by ABC00000220, and paths that do not resolve inside the package.

Are the produced documents opened or reviewed?

No evidence file is executed. Items are hashed and their presence verified; content is never read for responsiveness or privilege.

Are attachment families checked?

Not in this version. Parent-child relationships between a message and its attachments sit outside the current checks, so family integrity still needs a pass in your review platform.

Does a clean register make the production defensible?

No. It records that the load files and the referenced items are internally consistent. Defensibility, protocol compliance and legal sufficiency stay with the producing team.

Available now

Validate a production set before delivery day.

Inspect the fictional result now. Your own files run here without an account: 3 free jobs a day, or up to 200 a day with Pro.

Inspect prepared resultFind another tool