Client First Certified

Agency operations

Documentation that protects your agency

The small number of records that decide how an errors-and-omissions conversation goes, and how to produce them as a by-product of work you already do.

By Tyler Woodall , Co-founder, Client First Certified Published August 4, 2026

There is a version of this topic that treats documentation as paperwork — a defensive tax on real work, resented and skipped whenever the week gets busy.

That framing is why most agencies do not do it. It is also wrong in a specific way: the records that matter are almost all by-products of conversations that already happened. The agency did the work. It just did not leave anything behind.

The distinction worth internalising is that an undocumented recommendation and a recommendation that was never made are indistinguishable three years later, and the person deciding which one occurred will not be you.

The four records that matter

Most agency documentation effort is spread thinly across everything. It is more effective concentrated on four things.

What was recommended. The proposal, showing what the agency put forward — including options the client did not take. A proposal listing only what was sold documents a transaction, not advice.

What was declined. The declination letter. This is the highest-value record an agency produces and the one most often absent.

What was disclosed. Exposures the agency identified and told the client about, including ones it could not place. Flood is the recurring example.

What was offered and when. The annual review offer, logged whether or not it was accepted.

Between them, those four answer the questions that actually get asked: did you tell them, what did you tell them, when did you tell them, and what did they say.

The four records, the question each one answers, and the work that produces it. None of them require a separate task if the workflow emits them.

Why memory-based systems always fail

Not because producers are careless. Because of how the incentives fall in time.

The record is needed at the moment of maximum time pressure — the sale is closing, the client wants to be finished, and the next call is waiting. The benefit arrives, if at all, years later and to somebody who may not be in the room.

Any process where the person under pressure has to choose to do extra work for a deferred and uncertain benefit will erode. Not immediately — gradually, starting with the busiest week and never recovering.

So the only durable approach is one where the record is not a choice. It falls out of the action that closes the business, or it does not exist.

Making records fall out of the workflow

Four concrete moves, in rough order of leverage.

Derive the declination from the proposal. If the proposal already lists what was recommended and the binding record shows what was taken, the difference is the declination. Generating that document should be a button, not a writing task.

Bundle it into the delivery package. The declination goes out with the policy documents, as part of a package the client is already expecting to receive and acknowledge. It stops being an unusual extra request and becomes part of how the agency delivers.

Accept acknowledgement, not just signature. An e-signature, a reply email, a dated note of a verbal acknowledgement followed by a confirming email — all of these are records. Requiring a wet signature guarantees the practice dies within a quarter.

Run an exception report, weekly, owned by one person. Which files bound in the last week have no declination attached? Which clients are past their review window with no logged offer? The reports are the enforcement mechanism. Without them, adoption is invisible and therefore optional.

What good documentation actually looks like

Three properties, and they are not the ones people expect.

Contemporaneous. Written at the time, not reconstructed. A note added to a file after a claim is worth substantially less than one written the week of the conversation, and everyone reading it will know which it was.

Specific about the coverage, not the conversation. “Discussed coverage options” documents nothing. “Recommended umbrella at [limit], client declined, cited cost” is a record. The coverage, the recommendation, the response, the date.

Written in plain language. A declination the client cannot understand does not demonstrate that the client was informed. Form numbers and jargon undermine the very thing the document exists to prove.

The part that is not defensive

If documentation were only about liability, agencies would be right to resent it. It is not.

It makes the next conversation better. Walking into a review knowing exactly what the client declined last year, with the date, turns a generic check-in into a specific agenda. That is a better call for both sides and it converts more often than any prospecting activity.

It survives staffing changes. A producer leaves and the file goes with them, unless the file is the record. Agencies with good documentation lose people without losing relationships.

It makes the claim conversation possible. The hardest obligation in the practice standards — telling a client the truth when a loss is not covered, including what would have covered it — is far easier when the file already shows the coverage was offered and declined. Without that record, the honest conversation feels like an admission, which is exactly why it does not happen.

It is the certification. The Client First standards are auditable precisely because they resolve into artefacts. An agency that has built the documentation habit has done most of the work of certification already.

Where to start

If you are starting from nothing, start with the declination letter and nothing else.

It carries more weight than the other three combined, it connects to four separate practice standards, and building it forces you to fix the proposal upstream — because you cannot derive a declination without a record of what was recommended.

Get that one working, run the weekly exception report for a quarter, and add the review log after. Trying to implement all four at once is how documentation programmes fail.

What to check in your own agency

Pull five recent files and try to answer, from the file alone: what did we recommend, what did they decline, what exposures did we disclose, and when did we last offer a review?

If you find yourself relying on somebody’s recollection for any of the four, that is the gap — and it is the same gap that will be there in three years, when the recollection is the only thing left.