An E&O file is a story told after the fact: what the broker knew, when, and what the client was told. Usually it is reconstructed from emails. In InsightProofing it is written as the work happens, on the check’s decision record, and the proofing record report is built from it.

What the record holds

EntryWhat is kept
Agent runsEach step’s facts, the model and prompt used, tokens, cost, time, and what it prepared.
Control hitsEach proofing control that fired, its effect (block, refer, warn) and the values it read.
Prepared decisionsThe ask, the facts behind it, the level, and who answered, how and why.
ResolutionsEach check accepted, raised, corrected or waived — with the person and the reason.
CorrectionsEach request: sent when, by whom, due when, acknowledged, corrected or waived.
DeliveryThe summary as signed, by whom and when.
flowchart LR R["Agent runs"] --> DR[("Decision record
per check")] C["Control hits"] --> DR P["Prepared decisions
and answers"] --> DR X["Corrections"] --> DR S["Delivery signature"] --> DR DR --> PR["Proofing record report
(E&O file)"] DR --> CD["Client delivery summary"]

Two reports from one record

The client delivery summary has three sections: your coverage, what changed at renewal, and the documents checked. The proofing record has documents and reading, proofing results with forms and tower, and the renewal comparison. Both are built from the approved findings, so a finding nobody approved does not appear in what the client reads.

Delivery · delivered
A delivered illustrative general liability policy
Delivered: signed on the decision record, with what changed and the correction the carrier made before delivery — an additional insured missing from the policy.
Findings · what the agents found
What the agents found on an illustrative general liability renewal
What the agents found: each finding with its severity, the agent that raised it, the cited pages and Approve for the client summary.

Who did it, and on whose behalf

Every change carries an audit row: the actor, and whether the actor was a person or an agent — and if an agent, which one, at what level, and approved by whom. “The system did it” is never the answer.

For the account team

Approve findings for the client summary as you go; the summary is built from what you approved.

For broker IT

insight_decisions sign-offs and hits; an audit row with actor kind, agent code and autonomy level.

For practice leadership

The proofing record is the artefact to show a client, an auditor or an E&O insurer.

Questions we get asked

Where does the record live?

In the check’s tables in your own database, alongside the audit trail — not in a vendor’s cloud.

Keep reading