What Belongs in an Insurance Broker Compliance Evidence File?

Update note

Published as a new source-grounded guide to case-centred compliance evidence.

Why this matters

ASIC describes AFS licensee obligations across conduct, competence, supervision, compliance, risk management and adequate resources. NIBA’s Code describes standards that span the insurance journey, including advice, service and complaints. Those authorities do not turn a generic software checklist into a legal answer for every brokerage. They do show why traceable records matter. A scattered collection of PDFs can hide whether a document was current, whether a client answered a question, whether a gap remained open or whether a draft was approved. A case-centred file makes those distinctions visible and gives supervisors, compliance reviewers and broker teams a practical surface for checking the work.

Key points to carry into the work

Start with case identity: client, matter, case type, scope, owner, reviewers and the relevant dates.
Keep source material intact and distinguish a client statement, an extracted field, an AI suggestion and a human conclusion.
Record missing, overdue, disputed and not-applicable items rather than making an incomplete case look finished.
Link the final communication or output to the evidence version and human approval that released it.

The evidence-file path

01Identify the case
02Collect source material
03Track gaps
04Record decisions
05Approve the outcome
06Preserve the trail

Build the file in six reviewable layers

1. Case identity and scopeRecord the client and entity, the new-business, renewal, endorsement, claim or complaint context, the requested service, the responsible broker, any separate reviewer and the opening date. Preserve the agreed scope and terms of engagement where relevant. A reviewer needs to know which work this file is meant to evidence before deciding whether it is complete.

2. Instructions and known factsKeep the client’s instructions, structured fact-find responses, relevant circumstances, declared changes and unanswered questions. Record who supplied each fact and when. If information changes, retain the prior version and the reason for the update instead of silently replacing history.

3. Source documents and communicationsAttach or reference schedules, policy wordings, renewal notices, proposals, declarations, emails, meeting notes and other material used in the work. Capture enough metadata to identify the source and version. A summary should link back to the source rather than becoming a detached substitute for it.

4. Requirements, gaps and tasksMap the brokerage’s applicable requirements to the evidence currently present. Show missing, awaiting, overdue, not-applicable and satisfied states with an owner and next action. A requirement should not become complete simply because a document exists; the responsible person must decide whether that document answers the requirement.

5. Analysis and human decisionsRecord market strategy, alternatives considered, advice or recommendation records where applicable, conflicts, exceptions, approvals and reasons. Make any AI-extracted fact or drafted suggestion visibly provisional until a named person reviews it. Keep overrides and rejected suggestions because they can explain how the final judgement was reached.

6. Outcome, delivery and follow-upPreserve the approved proposal, advice record, disclosure, endorsement instruction, claim communication or complaint response that left the brokerage. Record the version, approver, recipient, channel and time, then capture acknowledgements and follow-up tasks. This closes the chronology without pretending that software has certified the outcome.

Where Insia fits

Compliance Case Manager is being developed as a case-centred workspace for collecting email and documentary evidence, organising it against requirements, surfacing missing items, recording source-linked AI suggestions and human decisions, and preparing a timestamped evidence pack. Its current status is private validation. The output is a Draft Readiness Preview for review, not a compliance certificate. Broker CRM can keep related conversations and ownership visible, while Quote Desk can link the quote case that generated relevant evidence.

Keep the boundary clear. Insia does not determine the legal or licence obligations that apply to a brokerage, certify compliance, give legal or financial advice, approve a broker’s work or replace a responsible broker, licensee, compliance reviewer or adviser. A template should be tailored to the brokerage’s authorisations, policies, record-retention rules and case type. Product availability and connections must be confirmed for the proposed scope.

Checklist

Can a reviewer identify the case, scope, owner and current status?
Does every material fact retain a person, time and source?
Are missing and not-applicable items distinguished from completed requirements?
Are AI suggestions separated from verified facts and human decisions?
Is the released outcome tied to a version, approver and delivery record?

Sources and scope

Sources support the external context in this guide. Current product capability and availability are explained on the linked Insia product page.

Common questions

Is a document folder the same as a compliance evidence file?

No. A folder may hold useful documents, but an evidence file also needs case identity, chronology, requirements, source relationships, gaps, ownership, human decisions, approvals and the final outcome. The brokerage decides which elements are required for its work.

Does a complete checklist prove compliance?

No. A checklist can support consistent review, but a tick does not prove that evidence was sufficient, current or correctly assessed. A responsible person must review the substance and apply the brokerage’s obligations and procedures.

Should every email be copied into the file?

Not automatically. Preserve communications that are relevant to instructions, facts, evidence, decisions, disclosures, approvals or the outcome. Apply the brokerage’s privacy, retention and access rules so irrelevant personal information is not collected without purpose.

Put the context to work

Turn this evidence task into a visible case.

Discuss how the evidence, requirements and human decisions in this guide could become a reviewable Compliance Case Manager workflow. This starts a product conversation and does not guarantee pilot access.

Discuss Compliance Case Manager