For legal teams
Review it, redact it, bundle it, hand it over — and be able to say how.
For litigators, chambers, in-house teams, estates and executors: the whole of a matter in one archive — what was received, what was collected, what was produced — with the defensibility that a hearing demands.
What you will use
- Legal discovery. Intake of load files with every fault an exception; review with coding, batches and a keyboard-driven screen; search with proximity and wildcards; threads; quality-control samples; outputs read back before they are offered; the list of documents or the privilege log.
- Redaction that fails closed. Marks on the page, approval, a rasterised copy re-recognised and asserted clean — or refused, and the refusal says why.
- Court bundles. Pagination from one, bookmarks, a linked index, text on every page, eleven rules verified on every build, a supplement for late additions.
- Holds and provenance. A hold freezes what must not change; provenance names who held what, from when; every act is on the audit chain.
- Jurisdiction profiles. England and Wales civil by default, with the United States and a generic profile; vocabulary, coding fields and outputs follow the profile.
- A licence that never stops what runs. If maintenance lapses, every module you had on keeps working.
modules: Legal discovery, Court bundles, Provenance (included) · roles: reviewer, review lead, case administrator, bundle editor
An archive that understands what it keeps.
The same archive, the same guarantees.
Thirty days with every module, no card, wherever you choose to run it. How it works · What leaves your archive