Capabilities
Everything an engagement can do.
A Diligence OS engagement is more than a memorandum. It admits and enriches a data room, tells you what is missing, answers questions against the sources, runs a versioned workflow, holds the draft to a reviewer’s standard, and releases a record that cannot drift. Every capability below is live today.
Outside-the-room enrichment
Pull a manager's SEC and Form ADV filings, recent news, and corporate-registry records into the engagement as first-class, citable sources — not pasted text.
Diligence checklist
Uploads are classified against the checklist for the engagement type, so you can see at a glance what has been provided, what is still outstanding, and what does not apply. Override any classification by hand.
Ask the data room
Put a question to the corpus and get an answer that cites the exact source spans it rests on. Questions the documents cannot support are refused, not guessed — interrogation with provenance, never a chat that invents.
Memorandum editor and version history
Principals edit the draft field by field. Every edit creates a new version with a full model-versus-House trail and a diff. An edit that adds a claim without a citation strips its evidence and blocks the lock until it is grounded.
01
Admit the data room
Sources enter a controlled envelope. Every file is fingerprinted, scanned, and tied to the engagement before any analysis runs.
- Upload and connect
- Bring in PDF, Word, Excel, PowerPoint, and email, or import directly from Box, SharePoint, and Intralinks. Folders and zip archives expand on arrival.
- Outside-the-room enrichment
- Pull a manager's SEC and Form ADV filings, recent news, and corporate-registry records into the engagement as first-class, citable sources — not pasted text.
- Fingerprint and chain of custody
- Each source is hashed with SHA-256 on arrival. That hash becomes the identity of every citation that depends on it, and every re-extraction is recorded against the source.
- Content scanning
- Every file passes a scanner that quarantines malicious payloads — and, when a House requires it, macro-bearing documents — before extraction.
02
Work the data room
Before a memorandum, get oriented. See what the room contains, what is missing, and what it says — with every answer tied back to a source.
- Diligence checklist
- Uploads are classified against the checklist for the engagement type, so you can see at a glance what has been provided, what is still outstanding, and what does not apply. Override any classification by hand.
- Ask the data room
- Put a question to the corpus and get an answer that cites the exact source spans it rests on. Questions the documents cannot support are refused, not guessed — interrogation with provenance, never a chat that invents.
- First look and red-flag reads
- Run a short, cited first read or a focused red-flag scan over the room before committing to a full workflow.
03
Run a versioned workflow
Eight workflows turn admitted sources into citation-anchored artifacts. Each runs the same stages every time, with citation requirements at every step.
- Eight controlled workflows
- Manager due diligence, direct IDD, operational due diligence, co-investment, secondaries, governance, tax structuring, and risk analysis — each a versioned pipeline, not a prompt session.
- Risk registers and contradiction checks
- Stages extract facts, reconcile figures against the model, build a risk register, and surface contradictions across documents before the committee meets.
- Refusal over invention
- A claim that cannot be cited is refused rather than asserted. The evidence standard does not bend to fill a section.
- Sector fixtures
- A fixture calibrates a workflow to an asset class — its own document set, its own thresholded risk flags, and a Releasability Score that grades a memorandum against the standard for that sector. Energy and data centres is live; four more are in development, one a month.
04
Review, edit, and lock
A draft is the start of partner judgment, not the end. Read the evidence, rerun a step, edit the prose, and lock a version that cannot drift.
- Review console
- A reviewer sees the draft against its citation coverage and flags, and can rerun any single workflow step without restarting the run.
- Memorandum editor and version history
- Principals edit the draft field by field. Every edit creates a new version with a full model-versus-House trail and a diff. An edit that adds a claim without a citation strips its evidence and blocks the lock until it is grounded.
- Immutable lock
- Locking a memorandum freezes the version. The committee pack and any share link are generated from the locked version alone.
05
Release and account for it
Outputs leave the room as committee-ready artifacts, and everything that happened stays on the record.
- Committee-ready export
- Generate a typeset PDF of the locked memorandum for the investment committee.
- Controlled share links
- Mint read-only links to a locked memorandum with an expiry. Every open is counted and logged against the engagement.
- Append-only audit trail
- Intake, scans, retrieval, model calls, reviews, locks, exports, and shares are all recorded against the engagement in an append-only ledger.
Each of these runs inside a single-tenant chamber, against an admitted source envelope, with every claim pointing back to a source span by hash. It is a controlled system, not a chat session — read how that is enforced under trust principles.