PRAESIDIUM

Discovery, with the receipts attached.

Collection through Microsoft’s own APIs. Ingestion that keeps every field. Analysis that joins productions against each other. Deliveries that log themselves. This is the part of the platform opposing counsel meets first.

The pipeline
STAGE · 01COLLECT

Purview, driven properly

Collections from Microsoft 365 run through the Purview API — the same mechanism forensic vendors use, without the vendor. Scope is defined explicitly per source location, the search and export parameters are preserved as artifacts, and the export summary is kept alongside the data. When someone later asks what was collected, from where, under what query, the answer is the record, not a recollection. A 692-gigabyte, 2.9-million-item tenant export has been completed this way in a single evening.

STAGE · 02INGEST

Every field survives

Concordance and IPRO load files are parsed in full: dates, Message-IDs, family relationships, attachment flags, hashes, source paths — not just the Bates number and custodian that most review platforms map before discarding the rest. Those fields are what make cross-production analysis possible later, which is exactly why it matters that they are kept.

STAGE · 03ANALYZE

Productions read against each other

Because everything sits in one queryable layer, the questions that win discovery fights become queries: sent items joined by Message-ID against the other side’s production. Bates continuity checked end to end. Custodian populations compared against export manifests. Gaps identified with citations rather than suspicions — and every analysis script preserved and offered, because a finding the other side can reproduce is a finding they cannot argue with.

STAGE · 04PRODUCE

Deliveries that testify for themselves

Productions go out under a SHA-256 manifest, through registration-gated links, from the platform’s own sending domain. Every access is logged — requesting party, address, timestamp — and the log is available to all counsel on request. A production save and a delivery are recorded as separate events, permanently. If a dispute ever turns on who received what and when, the answer already exists.

The standard this sets

Symmetry is the point.

Everything on this page applies to our own client’s data first. The same manifests, the same logs, the same preserved query parameters. A firm that can show its own work is entitled to ask the other side to show theirs — and equipped to check the answer.