Manager IDD · Workflow

Manager due diligence for teams that need source-backed financial judgment.

A versioned pipeline from admitted GP materials to a manager IDD memorandum, IC pack, LPA redline, and risk register — every claim anchored to the documents that support it.

Closed-system workflow. Source-backed outputs. Versioned review.

Engagement console

Source intake through review state

Illustrative

Source intake

  • S-014 · PPM.pdfadmitted
  • S-021 · LPA.pdfadmitted
  • S-028 · DDQ.xlsxscanning

Workflow stage

fee reconcile

Stage running · citations required

Evidence anchors

[S-014 · p.42 ¶3][S-021 · cl. 8.2][S-028 · tab 3]

Open risks

Key-person concentration

severity · high · cited

Draft artifact

Manager IDD memorandum · v3 draft

schema valid · 47 claims cited

Review state

Partner review

Awaiting challenge before lock

audit · memorandum.draft.v3 · 2026-05-24T14:32:01Z · engagement

Fund diligence breaks down when the evidence path does not survive partner review.

Manager due diligence draws on a wide source envelope — PPM, LPA, side letters, DDQ responses, audited financials, track record workbooks. Analysts extract fees and returns in parallel; partners redline the LPA against House standards; the IC reads a pack that must not drift from the memorandum. When sources are fragmented, contradictions stay buried, and the final artifact may not preserve the reasoning path.

  • Fee schedules in the PPM disagree with side-letter terms — surfaced late or not at all
  • Track record figures are duplicated across workbooks without a single cited source
  • LPA redlines are drafted without quoting the underlying clause text
  • IC packs are rewritten separately from the memorandum and drift on key facts
  • Partner review depends on individual analyst habits rather than a repeatable standard

Who uses this workflow

Built for senior finance teams who need committee-ready artifacts — not chat transcripts.

Family office CIO

Use casePrimary or follow-on fund commitment

Moment of needA GP asks for capital before the IC meets

OutputManager IDD memorandum and IC pack

Allocator analyst

Use caseManager re-up diligence

Moment of needThe question is what changed since the last commitment

OutputDelta redline against prior LPA and track record

Fund-of-funds partner

Use caseMulti-manager underwriting

Moment of needFee schedules and side letters must reconcile before terms are signed

OutputFee reconcile report and risk register

Investment committee

Use caseCommittee preparation

Moment of needPartners need a defensible read before capital is committed

OutputIC pack derived from the same source spans as the memorandum

Admitted source envelope

Source materials enter the engagement as a controlled register — scanned, classified, and scoped before the workflow runs.

Source register for this workflow

Source register

Pending admission · scanner gate

6 sources
SourceDescriptionStatus
Private placement memorandum (PPM).01
Limited partnership agreement (LPA) and any prior side lettersLimited partnership agreement (LPA) and any prior side letters.02
Diligence questionnaire (DDQ) response.03
Audited fund financials, where availableAudited fund financials, where available.04
Track record workbook, by vintage and by dealTrack record workbook, by vintage and by deal.05
Team biographies.06

Workflow process

A versioned pipeline — each stage records what happened, what you can review, and what output it produces.

Stage pipeline

Topological DAG · runtime enforced

7 steps
FEE EXTRACTTRACK RECORDFEE RECONCILERISK REGISTERLPA REDLINECONTRADICTIONCHECKSYNTHESIZE
Workflow · MANAGER-DD · 7 steps · cited
  1. 01

    Admit source materials

    PPM, LPA, side letters, DDQ response, audited financials, track record workbook, and team biographies enter the engagement envelope.

    Recorded
    Source hash, admission timestamp, and chain-of-custody row per document.
    Review
    Principal confirms the GP packet is complete before the workflow runs.
    Output
    Admitted source register scoped to the engagement.
  2. 02

    Extract fees and track record

    fee_extract reads the PPM and LPA for the canonical fee schedule; track_record extracts IRR, MOIC, and DPI by vintage and by deal.

    Recorded
    One fee object and one return series per cited source span.
    Review
    Analyst verifies extract coverage against the data room index.
    Output
    Canonical fee schedule and track record table.
  3. 03

    Reconcile fees and enumerate risks

    fee_reconcile checks the headline economics against side letters; risk_register reads financials and track record together for severity-ordered risks.

    Recorded
    Divergence callouts and risk entries with rationale citations.
    Review
    Partner challenges any fee delta not tied to a quoted clause.
    Output
    Fee reconcile report and typed risk register.
  4. 04

    Redline the LPA

    lpa_redline marks the LPA clause-by-clause against the House standard side-letter positions.

    Recorded
    Each redline entry quotes the underlying clause text and cites its span.
    Review
    Partner accepts, redlines, or removes positions that lack citation.
    Output
    LPA redline against House standard.
  5. 05

    Surface contradictions

    contradiction_check reads fee, return, and risk extracts side-by-side and surfaces inconsistent descriptions across documents.

    Recorded
    Contradiction callouts written to the draft — never silently resolved.
    Review
    Partner decides how each contradiction is addressed in the memorandum.
    Output
    Contradiction register on the memorandum cover.
  6. 06

    Synthesise the memorandum and IC pack

    synthesize composes executive summary, section narratives, and IC questions from upstream node outputs.

    Recorded
    Memorandum draft version, schema validation result, and citation map.
    Review
    Partner reads the draft against source spans before sign-off.
    Output
    Manager IDD memorandum and IC pack from a single fact set.
  7. 07

    Lock and preserve the audit trail

    The signed memorandum version is locked; exports and share links render from the locked artifact.

    Recorded
    memorandum.locked audit event with version id and timestamp.
    Review
    Partner name on the document — the system supports, not replaces, judgment.
    Output
    Locked, committee-ready artifact with defensible record.

Workflow outputs

Committee-ready artifacts — each with a named reviewer and a defensibility standard.

  • Manager IDD memorandum

    25–40 pages structured to the House reading template, with every factual claim citing a source span by hash.

    Reviewed by
    Partner or principal before sign-off
    Defensibility
    Claims re-verify against source hash at read time; changed sources flag red.
  • Investment committee pack

    Derived from the same source spans as the memorandum so the two cannot drift.

    Reviewed by
    IC chair and deal team
    Defensibility
    Single fact set renders both documents; disagreement requires an explicit edit.
  • LPA redline

    Clause-by-clause comparison against the House standard side-letter positions.

    Reviewed by
    Partner and counsel
    Defensibility
    Each position quotes the underlying LPA clause; uncited redlines are refused.
  • Risk register

    Severity-ordered risks with rationale citations from audited financials and track record.

    Reviewed by
    Partner and risk committee
    Defensibility
    Every risk entry ties to a cited source span; missing evidence surfaces as an exception.

Every material claim is reviewable against the source that supports it.

Manager DD treats citation as a contract, not a formatting choice. Fee objects, return series, redline positions, and risk entries each point to a source chunk by hash. Review versions are preserved; partner comments and changes are recorded before the memorandum is locked.

  • Span-level citation — a claim on page 42 of the PPM cites that table, not the document title
  • IC pack and memorandum share one citation map — they cannot disagree without an explicit edit
  • Contradictions across documents are callouts, not silent resolutions
  • Locked versions are immutable; a new commitment cycle starts a new version

Diligence OS supports investment judgment. It does not make investment decisions, provide investment advice, or guarantee risk detection.

Why not generic AI

Prompt-based tools produce inconsistent outputs with weak provenance. This workflow runs a structured process with an admitted source envelope and a versioned review path.

Comparison of generic AI tools and Diligence OS for this workflow

Starting point

Generic AIChat-first

Diligence OSWorkflow-first

Process

Generic AIUser-defined prompts

Diligence OSVersioned process

Provenance

Generic AIWeak provenance

Diligence OSSource-span citations

Across documents

Generic AIOne file at a time

Diligence OSThe full set reconciled; contradictions surfaced

Review

Generic AIHard to review

Diligence OSPartner review states

Outputs

Generic AIInconsistent outputs

Diligence OSRepeatable artifacts

Memory

Generic AINo durable workflow memory

Diligence OSAppend-only audit trail

Committee use

Generic AIDifficult to defend

Diligence OSCommittee-ready outputs

Fund-specific artifacts

Generic AIGeneric summaries

Diligence OSLPA redline + fee reconcile + IC pack

Business value

Institutional outcomes — not productivity slogans.

  • Compress manager diligence cycles without lowering the evidence standard
  • Improve partner leverage — analysts produce cited drafts, partners challenge and sign
  • Standardize LPA redline quality against the House standard, clause by clause
  • Preserve institutional memory across re-ups and manager relationships
  • Reduce missed contradictions between PPM, side letters, and track record workbooks
  • Create a defensible record the IC can read in full before capital is committed

Security and control

Closed by construction — each engagement runs inside a dedicated chamber with an append-only audit trail.

  • Closed-system workflow — each engagement runs in an isolated chamber
  • Engagement-level isolation with row-level tenant scoping
  • Source-controlled review — partners read drafts against the audit log
  • No training on customer documents — ever, by anyone
  • Citation-backed artifacts with hash-verified source spans
  • Versioned workflow history preserved on every run
  • Audit trail on reads, retrievals, model calls, and locks
  • Reviewer traceability — partner review recorded before sign-off

Request an introduction

Diligence OS is introduced through a controlled evaluation process. No public signup. No self-serve access.