Discover · Production

A production the receiving side loads without a phone call

Concordance DAT and Opticon OPT load files, family-aware Bates numbering that continues across rolling volumes, natives under their Bates numbers, extracted text with redactions in force, and a chain-of-custody report — with no document cap.

Where it starts

The scope is agreed — a saved search, a matter, a public-records request. Producing it is one workflow from the same screen, whether the requesting party is opposing counsel or a records requester.

How it runs

01
Cut the volume from the query
The production is defined by the search that selects it — the query travels, not a list of ids, so the scope stays reproducible when someone asks how the set was drawn.
02
Number families together
Bates numbers are family-aware — attachments follow their parents, always; that cannot be switched off — with a configurable prefix and zero-padding, continuing across rolling volumes so ACME-004813 in volume two follows volume one.
03
Write the load files
Concordance DAT with the real ASCII 20/254/174 delimiters and Opticon OPT image cross-references. Formula injection is neutralised in load files while the exact value is preserved where the log needs it.
04
Attach the disclosure
Privilege log, redaction log, domain-exclusion log with its stated basis, and the chain-of-custody report — the volume explains its own withholdings.
05
Hand over a manifest, not a mystery
MANIFEST.csv names every file and every attachment's parent. Ad-hoc exports (PST, EML, PDF, HTML, CSV) carry a READ_ME stating they are not a production — the two artifacts are never confusable.

Why it holds up

Productions have no document cap; ad-hoc exports cap at 50,000 and say so rather than silently truncating.

EML exports are the archived bytes, byte-exact; PST is written natively — no Outlook in the pipeline.

Redacted documents are produced as text only and recorded as withheld natives — the native never leaks around the redaction.

Every export and production is a ledger event, attributable and timestamped, tied to the verified chain of custody.

What you hand the regulator

A workflow that ends on a screen isn’t finished. This one ends in a document.

The production volume

One directory the receiving side loads on the first try — and that you can regenerate identically when the court asks how it was made.

loadfile.dat (Concordance) · images.opt (Opticon)
NATIVES/<bates> · TEXT/<bates>.txt with redactions in force
privilege_log · redaction_log · domain_exclusion_log
chain-of-custody report · MANIFEST.csv naming every family

Adjacent workflows

Privilege & Redaction Search & Term Hit Reports FOIA & Public Records

See it run on your data scenario

The demo form asks which workflows you want to see — name this one and we’ll stage it.

Book a Demo All workflows

How it runs

Cut the volume from the query

The production is defined by the search that selects it — the query travels, not a list of ids, so the scope stays reproducible when someone asks how the set was drawn.

Number families together

Bates numbers are family-aware — attachments follow their parents, always; that cannot be switched off — with a configurable prefix and zero-padding, continuing across rolling volumes so ACME-004813 in volume two follows volume one.

Write the load files

Concordance DAT with the real ASCII 20/254/174 delimiters and Opticon OPT image cross-references. Formula injection is neutralised in load files while the exact value is preserved where the log needs it.

Attach the disclosure

Privilege log, redaction log, domain-exclusion log with its stated basis, and the chain-of-custody report — the volume explains its own withholdings.

Hand over a manifest, not a mystery

MANIFEST.csv names every file and every attachment's parent. Ad-hoc exports (PST, EML, PDF, HTML, CSV) carry a READ_ME stating they are not a production — the two artifacts are never confusable.