The R&W underwriter will exclude what the buyer already knows. Insurance diligence is one of the places the buyer learns it. InsightDueDiligence and InsightDealDesk are two products, often run by two teams, so the findings travel between them as a signed, versioned contract: reviewed findings out of diligence, likely exclusions into the placement.
| From | InsightDueDiligence: an engagement linked to a deal (for example the illustrative Project Fieldstone → DEAL-2026-0003) |
|---|---|
| To | InsightDealDesk: the R&W placement on that deal, its data room and its exclusion agent |
| What travels | Findings a person approved or changed, in R&W-relevant categories only |
| Contract | diligence_findings.v1 (JSON Schema; InsightDealDesk’s copy is canonical and a test compares the two) |
| Transport | POST {DEAL_BASE_URL}/api/deal_intake/diligence-findings, signed with HMAC-SHA256 in X-Insight-Signature |
| Who decides | A deal broker presses Share; the report agent only prepares it, capped at L2 |
| When not configured | Held in the outbox; nothing leaves the product |
| Outcome | Each finding lands once (idempotent on its fingerprint) as a known issue on the deal’s data room, citing InsightDueDiligence |
The path of one finding
by an agent"] --> R{"Reviewed?"} R -- "approved / changed" --> C{"R&W-relevant
category?"} R -- "pending / rejected" --> X["Stays in diligence"] C -- yes --> P["In the payload"] C -- no --> X P --> S["Signed POST"] S --> L["InsightDealDesk lands it
as a known issue"] L --> EX["Exclusion agent reads it
with the deal's own diligence"] style P fill:#e6efff,stroke:#2563eb style L fill:#e7f8f1,stroke:#10b981 style X fill:#f4f6ff,stroke:#8089a8
The categories that travel are the ones an R&W underwriter cares about. On the diligence side a
coverage gap and a subsidiary not on the program both map to coverage_gap; tail and
run-off needs to tail_needed; large losses to claims_history; contingent
liabilities to litigation when they come from a suit and known_issue
otherwise. Program and intelligence findings stay in diligence. InsightDealDesk lands categories it recognises — known issue, coverage
gap, tail needed, red flag, diligence gap, claims history and litigation — and skips the rest.
The exchange
What the payload carries
// diligence_findings.v1 (shape; values illustrative) { "schema": "diligence_findings.v1", "sent_at": "2026-11-03T15:04:05Z", "source": { "product": "insightdiligence", "workspace_guid": "…", "pack": "insurance_program" }, "target": { "deal_guid": null, "target_key": "meridianfieldworks.example", "target_name": "Meridian Fieldworks Holdings LLC" }, "findings": [ { "fingerprint": "…", "category": "tail_needed", "severity": "high", "title": "Directors & officers is claims-made: a tail is needed at closing", "citations": [ { "label": "Directors & Officers policy — Harborline Specialty, p.1" } ] } ] }
The product identifier inside the contract is the stable machine name; the display name changed, the contract did not.
Rules on both sides
| Rule | Why |
|---|---|
| Only reviewed findings | A pending finding is an agent’s opinion; an approved or changed one is the practice’s. |
| Signed body | t=<unix>,v1=<hmac-sha256 of "t.body"> with a shared secret held as a secret reference; a bad signature is a 401. |
| Idempotent per finding | The fingerprint is stable, so sharing twice lands nothing new, and a finding a broker has already reviewed in InsightDealDesk is never overwritten. |
| Matched, not guessed | By the deal’s guid, else by the target’s lookup key; no match is a 404 and the hand-off stays on record as not landed. |
| Held when unconfigured | No endpoint or no secret: the row is written as held and nothing leaves. A 503 on the other side means the same. |
A hand-off’s life
Step by step on an illustrative deal
High findings approved: the D&O, cyber and EPL tails, the unnamed Mexican subsidiary, the TCE finding.
Prepares “Share findings with the R&W placement”: six reviewed findings would travel.
Accepts. The payload is built, the outbox row written, the POST signed and sent.
The deal is matched; six findings land on its data room as known issues citing InsightDueDiligence.
Reads them alongside the deal’s own schedules and diligence reports when it predicts the deal-specific exclusions to expect.
Goes into the underwriting call knowing which exclusions are coming and why.
Two records, one set of facts
Each product keeps its own decision record. What they share is the reviewed finding with its citations and fingerprint, so “where did this exclusion come from?” has a one-click answer on the InsightDealDesk side.
Questions we get asked
Does InsightDealDesk send anything back?
Not under this contract. The hand-off is one way: reviewed diligence findings into the placement.
Can we use InsightDueDiligence without InsightDealDesk?
Yes. Without an endpoint the share is held and the report stands on its own.
