An R&W underwriter will ask about the target’s insurance: is the program adequate, are there large open losses, does a claims-made policy need a tail at closing? In most practices that answer sits in a separate insurance due diligence report, written by a different team, that the placement broker reads as a PDF.
InsightDueDiligence and InsightDealDesk share the platform, so the answer travels as data. Reviewed findings from an insurance due diligence engagement arrive on the deal as known issues, each citing the diligence it came from, and the exclusion agent reads them like any other. This post follows one such hand-off. The engagement, deal and figures are illustrative.
| Actors | Diligence broker (InsightDueDiligence), deal broker (InsightDealDesk), practice leader |
|---|---|
| Trigger | The report agent in InsightDueDiligence prepares “share with the R&W placement”; a broker accepts |
| What travels | Reviewed findings in R&W-relevant categories: known issue, coverage gap, tail needed, red flag, diligence gap, claims history, litigation |
| Contract | diligence_findings.v1 — a signed POST to /api/deal_intake/diligence-findings |
| Matching | By deal id when the engagement knows it, else by the target’s lookup key |
| Outcome | The findings land on the deal’s data room as known issues, cited to InsightDueDiligence; the next Analyze reads them |
The flow
insurance program review"] --> R["Findings reviewed
by a broker"] R --> RA["Report agent prepares
share with the placement"] RA --> OK{"Broker
accepts?"} end OK -->|yes| P["Signed POST
diligence_findings.v1"] subgraph DEAL["InsightDealDesk"] P --> V{"Signature valid,
deal matched?"} V -->|yes| L["Known issues on the
deal's data room"] L --> X["Exclusion agent reads them
on the next Analyze"] end style P fill:#fef3c7,stroke:#b45309 style L fill:#e8f8f4,stroke:#22c1a4
Step by step
Only reviewed findings travel. A pending finding stays in InsightDueDiligence.
The R&W-relevant findings are gathered into the hand-off. Sharing is capped at ask-first.
Accepting signs the body with the shared secret and posts it. With no endpoint configured, it is held in the outbox and nothing leaves.
The X-Insight-Signature header is checked (HMAC-SHA256 over timestamp and body, five-minute tolerance). A bad signature is a 401; no matching deal a 404; not configured a 503.
Each finding lands on the deal’s data room as a known issue citing InsightDueDiligence. Idempotent on the finding’s fingerprint: a resend lands nothing twice, and a finding a deal broker has already reviewed is never overwritten.
On the next Analyze the landed issues are inputs like any schedule disclosure, and appear in the submission’s known issues.
Approves, changes or rejects each landed finding in the Findings zone.
Who talks to whom
What the body looks like
// POST /api/deal_intake/diligence-findings X-Insight-Signature: t=<unix>,v1=<hmac> { "schema": "diligence_findings.v1", "sent_at": "2026-10-28T14:02:11Z", "source": { "product": "insightdiligence", "workspace_guid": "…", "pack": "insurance_program" }, "target": { "deal_guid": null, "target_key": "example-target.example" }, "findings": [ { "category": "tail_needed", "severity": "high", "title": "D&O run-off needed at closing (illustrative)", "fingerprint": "…" } ] }
An abridged, illustrative body. The JSON Schema is shared by both products and a test compares the two copies.
Idempotency and review, as a state machine
| Agent | What it prepared | What it cites | Who decides |
|---|---|---|---|
| Report (InsightDueDiligence) | Share R&W-relevant findings with the placement | Reviewed findings | Diligence broker |
| Exclusion (InsightDealDesk) | Landed issues as likely exclusions | Findings citing InsightDueDiligence | — |
| Submission | Known issues section includes them | Findings | Deal broker |
On the deal desk
The insurance diligence is in the placement as findings to review, not a PDF to reread.
For IT and architecture
Signed with insight_integrations.signing; idempotent on fingerprint; contract under docs/contracts in both repos.
For practice leaders
Two teams, one record: the diligence and the placement agree on what was known, and when.
Questions we get asked
Do we need both products?
No. InsightDealDesk works on its own data room. With InsightDueDiligence the insurance program review arrives as data.
What if the deal was not created yet?
The receiver answers 404 and the sender keeps the hand-off; it can be resent once the deal exists.
