New: Compliance Platform for Brokers, with the Insurance Brokers Code of Practice built in.Broker Code built in

See the platform
Book a demo
Article

How to Audit Broker Files: A Step-by-Step Guide

How to audit insurance broker files step by step: what to check, how many files to review and how to cover more files with less manual work.

Why broker file audits matter more in 2027

On 1 January 2027 the new Insurance Brokers Code of Practice takes effect. It grows from 12 sections to 14, with new chapters on conflicts of interest and on keeping client records. It expects brokers to write notes of their dealings at the time, not afterwards. Any client can also ask what their broker is paid and get the answer in dollars. Obligations that need new systems or training have 12 months to be met in full.

The Insurance Brokers Code Compliance Committee (IBCCC) is already looking at the same ground. Its 2025 Annual Data Report counted 5,417 breaches of the Code. Renewal timeframe failures made up nearly half of them. The IBCCC also noted that brokers often found these failures through file audits, where exclusions, fees and changes to cover had not been properly explained.

So the client file is now the main evidence. If something is not on the file, it is hard to show it happened. Most brokerages know this. The hard part is time. A careful manual review takes hours a file, so few files get checked.

This guide shows how to audit a broker file step by step, and how to check more files without adding hours.

How do you audit a broker file?

To audit a broker file, you check that it shows the broker did what their AFSL obligations, the Insurance Brokers Code of Practice and the brokerage's own procedures require. You write each requirement as a yes or no question. You look in the file for evidence. You record every gap so it can be fixed.

What does a broker file audit check?

A broker file audit looks at the whole life of a client file, from the first contact to renewal, claims and complaints. The main areas are:

  • Client details. The client's details are complete, correct and the same across the file.
  • Client type. The file records whether the client is retail or wholesale, and the right documents went out for that type.
  • Needs and objectives. The file records what the client asked for and why.
  • Recommendation. The cover recommended matches the client's recorded needs, and the file gives the reasons.
  • Disclosure. The required documents were given, and the duty of disclosure was explained, where they apply. Remuneration was disclosed where it applies.
  • Renewals. Changes to cover, price or terms were explained to the client.
  • Complaints and breaches. Anything that looks like a complaint or a breach was recognised, logged and escalated.
  • Vulnerability. Signs that a client may be vulnerable were noted and acted on.
  • File notes. Notes are made at the time, dated and clear, and show what was said and agreed. The 2027 Code gives record-keeping its own chapter.

Not every check applies to every file. A wholesale client file, for example, does not need the same disclosures as a retail one.

An example: one renewal file

This example is made up. It is not a real client and not a real result.

A broker renews a small business client's property cover. The file holds a renewal notice, a phone note that reads "client happy to renew", and the new policy. An audit asks four questions of it.

QuestionResultWhy
Was the renewal notice sent within the Code's timeframe?FailThe notice is dated two days before the policy expired
Were the changes to cover explained?FailThe excess went up, but nothing shows the client was told
Is there a note made at the time?PassThe phone note is dated and names the broker
Was the client's need for cover reviewed again?PassThe note records that the sum insured was checked

Two fails, and each has a clear fix. Send renewal notices earlier. Record every change to cover and when the client heard about it. A careful reviewer would find the same things. The problem is not skill. It is the hours it takes to do this on every file.

How to audit a broker file in six steps

  1. Decide what you are checking against. List your AFSL obligations, the Insurance Brokers Code of Practice and your own procedures. Turn each into a yes or no question, such as "Does the file record the client's needs?"
  2. Choose the files. Sample across brokers, products, client types and dates. Include renewals, claims and files with complaints. Do not only pick the tidiest files.
  3. Gather each file in one place. Pull the documents, emails and notes together before you start. A check cannot pass if the evidence is somewhere else.
  4. Answer each question pass or fail. Mark the place in the file that shows the evidence. A pass needs evidence. Opinion is not enough.
  5. Record the gaps. Group them by type and by broker. One gap is a one-off. The same gap on many files is a pattern.
  6. Fix, follow up and retest. Correct the file, coach the broker and update the procedure. Check whether any breach must be reported. Retest a new sample later to confirm the fix worked.

A second person, who did not work on the file, should do the review. That keeps the result fair.

Want these questions ready to use? Download our broker file audit checklist.

How many files should you audit, and how often?

No single number fits every brokerage. Base it on risk. Review more files for newer brokers, higher-risk products and any area where you have already found gaps.

Time sets the limit when you audit by hand. A manual review takes at least 2 to 3.5 hours per file. Twenty files is 40 to 70 hours of work. That is why manual audits stay small, and why a small sample can miss a pattern.

Set a regular schedule, such as monthly or quarterly. Also review again after a change: a new broker, a new product, a new process or a new code.

Curium's broker file audit uses AI to check each file. Each file takes five minutes at most, and files are audited as they arrive. In use, it has saved at least 78% of human review time. That lets you review more files than you could by hand.

Common gaps in broker files, and how to close them

The IBCCC's data points to renewals first, and to explanations that were never confirmed as understood. The gaps below are what a file review typically looks for. They are examples, not results from any client.

GapHow to close it
The renewal notice went out lateSet a reminder well before expiry and record the date the notice was sent
Changes at renewal were not explainedRecord what changed and when the client was told
The client's needs are not recordedAdd a short needs section to the file template and make it required
The reasons for the recommendation are missingAdd one line that links the cover to the client's needs
A required disclosure document is missing or undatedSend it at first contact and save a dated copy to the file
A complaint or breach appears in the notes but was never loggedLog it, link it to the file and check whether it must be reported
Signs of vulnerability were noted but nothing followedRecord the action taken, or the reason none was needed

Auditing broker files with Curium

Most brokerages know what a good file looks like. Time is the bottleneck. Curium's broker file audit checks each file against a framework and gives a pass or fail for every check, with the evidence from the file. The result rests on evidence, not on one reviewer's judgement.

  • Your framework or ours. It runs on Curium's framework, or Curium configures it to yours. Curium also keeps the AFSL and Insurance Brokers Code obligations up to date.
  • Fast. Each file takes five minutes at most, and files are audited as they arrive.
  • Set up once. The first run is tuned to your file format and definitions, then checked. After that each file takes minutes.
  • Data you can use. You can track results as files arrive, run your own analysis on the data, and ask for any report through Curium's MCP layer, which lets you question your audit data in plain language.
  • Connects to your systems. You do not need to connect them to start. You can connect your client systems later.

Book a demo to see the broker file audit on your own file format.

Broker file audit: common questions

How many broker files should I audit?

There is no single number. Base it on risk, and review more files where you have found gaps. Start with a sample that covers each broker, product and client type.

How often should I audit broker files?

Many brokerages review on a regular schedule, such as monthly or quarterly. Review again after any change to people, products, processes or codes.

Who should audit broker files?

Someone who did not work on the file. A second person or the compliance team keeps the review fair.

What if the audit finds a breach?

Record it, check whether it must be reported and within what time limit, and fix the file. Then look for the same problem on other files.

Author:

Tetiana George, CEO of Curium, Co-Chair of Insurtech Australia and member of ASIC Digital Finance Advisory Committee. LinkedIn Profile.