When a placement is questioned — by the client, by a carrier, by an E&O insurer, by a regulator — the questions are always the same. What did you know? What did you recommend, and why? Who decided? When did the client agree? InsightPlacement answers them from one place: the placement’s decision record.
What goes on it
| Entry | What it holds |
|---|---|
| A controls run | Each time the controls run (at Analyze, at an answer), a decision with every control that fired: the rule, its version, the outcome (warn, refer, block) and the evidence values |
| An agent’s prepared decision | What was prepared, by which agent, at which level, the reasons and the facts it rested on |
| A person’s answer | Accept, change, reject or ask — by whom, when, with their note and any change they made — signed |
| The client’s sign-off | A decision of its own: the proposal, who signed on the client’s side, who recorded it, the total |
| The audit trail | Every create and change on the placement’s rows: submissions, markets, quotes, proposals, bind orders |
accept, change,
reject, ask"] --> D S["Client sign-off"] --> D D --> V["Verdict:
proceed, refer, block"]
A verdict, ranked
Each controls run has a verdict: the most severe outcome among its hits. A block outranks a refer, which outranks a warn. The supervisor agent reads the verdict: a refer becomes a prepared sign-off for the role the rule names; a block means no bind order is prepared until it clears.
One placement’s record, read back
For the illustrative hotel group renewal described in the premium-jump post:
| Section | Hit | Outcome |
|---|---|---|
| Control | PREMIUM_JUMP v1: program change +38.5% (over 25%) | refer |
| Agent | Supervisor: practice leader sign-off prepared (L1) | refer |
| Agent | Compliance: FL diligent-effort affidavit prepared, 3 admitted declinations (L1) | refer |
| Person | Submission version 1 approved by the placement broker | proceed |
| Person | Proposal version 1 finalised | proceed |
| Client | Client sign-off (when recorded) | pass |
Read top to bottom it is the placement’s story: what fired, what was prepared, who decided, and when the client agreed. Each line links to the rule version or the prepared decision it came from.
Signed, and replayable
Answers are signed: the record stores who acted, as a human or as an agent on someone’s behalf, and when. Because the controls are versioned rules and the engines are deterministic, a run can be replayed: the same rows through the same rule versions give the same hits. That is what makes the record evidence rather than a log.
The same record across the suite
The decision record is a platform package, not an InsightPlacement feature. InsightAdvocate keeps one per claim, InsightCW one per claim on the carrier side, InsightUW one per submission. A practice running more than one product audits them the same way.
