Agency operations
E&O defensibility for independent agencies
What an errors-and-omissions allegation actually turns on, why the file matters more than the memory, and the practices that change the outcome.
An errors-and-omissions allegation usually arrives attached to a loss, and it usually says a version of the same thing: I didn’t have the coverage I needed, and nobody told me I could have had it.
Not fraud. Not incompetence. A gap, discovered at the worst possible moment, followed by a reasonable question about who was supposed to have raised it.
What decides how that conversation goes is rarely what the agency did. It is what the agency can demonstrate.
The scope of this article
Worth stating plainly before anything else: the legal standards that govern an agent’s duty to a client differ by state, sometimes substantially, and your own E&O policy has its own requirements and reporting obligations.
Nothing here is legal advice or a substitute for your carrier’s guidance. What follows is operational — the practices that make a file demonstrate what happened, which is useful under any standard.
What allegations are actually about
In broad terms they cluster into a small number of shapes.
A coverage was not offered. The most common. Flood, umbrella, UM/UIM, water backup, replacement cost, business use on a personal policy. The loss happens, the coverage would have responded, and it was never on the table.
A limit was inadequate. The coverage existed; the amount did not. Frequently a limit set years earlier that nobody revisited while the exposure grew.
A change was requested and not made. A vehicle added, a driver removed, an address changed. This one is about execution rather than advice, and it is the shape where a contemporaneous record of the request matters most.
A representation was made that turned out to be wrong. “You’re fully covered.” Language that felt reassuring at the time and reads as a promise afterwards.
Notice that three of the four are about communication, not about placement. The agency’s technical work was usually fine. What is contested is what was said.
What makes a record carry weight
Not all documentation is equal, and the differences are consistent.
Contemporaneous beats reconstructed. A note written the week of the conversation is a different object from one added after a loss. Management systems timestamp entries, and everyone reading the file will see which is which. Late documentation can be worse than none, because it invites a question about why it appeared when it did.
Specific beats general. “Discussed coverage options with client” establishes nothing. “Recommended umbrella; quoted; client declined, cited cost; declination sent [date]” establishes what happened. Name the coverage, the recommendation, the response, the date.
Client-acknowledged beats internal. An internal note says the agency believes it happened. A signed or acknowledged document says the client received it. The gap between those two is large.
Plain language beats jargon. A declination the client could not have understood does not demonstrate that the client was informed. Form numbers work against the purpose of the document.
Consistent beats occasional. A single well-documented file among a hundred silent ones raises an obvious question. A uniform practice is itself evidence, because it establishes what the agency does routinely rather than what it did once.
That last point is the strongest argument for building documentation as a workflow rather than a habit. Systematic practice is defensible in a way that individual diligence is not.
The practices that change the outcome
Most of these are the practice standards, viewed from the risk-management side rather than the client side. That overlap is not coincidental — the standards were written from both.
Document every declined recommendation. The single highest-value practice. It directly addresses the most common allegation shape.
Never say “fully covered.” No policy covers everything, and the phrase is heard as a warranty. Say what is covered and what is not.
Disclose exposures you cannot place. Telling a client about flood when you have no flood market is worth more, defensively, than almost anything you can sell them — and it is a standard.
Confirm requested changes in writing. A short confirming email after any coverage change turns a disputed instruction into a record, and it takes seconds.
Offer reviews on a schedule and log the offers. It addresses the inadequate-limit allegation directly: the limit was not revisited because the client declined the opportunity, and there is a dated record of the opportunity.
Match UM/UIM to liability by default. Removes a defaulted decision that the agency would otherwise be answering for.
Train consistently. Documentation that depends on which producer handled the file produces exactly the inconsistency described above.
When something goes wrong
Two operational points, and they are the ones agencies most often get wrong under stress.
Report to your E&O carrier when your policy requires it, not when you have decided how serious it is. Late notice is a coverage problem on your own policy, and the judgement about severity is not yours to make unilaterally.
Do not modify the file. Adding, editing or backdating anything after an allegation converts a defensible position into an indefensible one, regardless of the merits of the underlying claim. Write new, clearly dated notes if you need to record something now — but never touch what is already there.
The relationship to certification
The Client First standards are, from one angle, an E&O programme with a consumer-facing name.
Written declinations, documented annual reviews, matched UM/UIM, replacement cost explained in writing, exposures disclosed even when not sold, honesty at the claim — each of those is a client-protective commitment, and each of them also produces exactly the record that answers the most common allegation.
That is not a marketing coincidence. An agency that genuinely operates this way is both easier to defend and better to buy insurance from, and the artefacts are the same in either direction.
What to check in your own agency
Pick five files at random from two years ago — not recent ones, where memories are still fresh.
For each, try to answer from the file alone: what did we recommend, what did they decline, what did we disclose, and when did we last offer a review.
Whatever you cannot answer is what you would not be able to answer in a dispute either. That gap is the whole exercise, and it is knowable today rather than in three years.
Related reading
- 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.
- The standards
The Client First practice standards
Eight practice standards and seven ethical ones. What each commits an agency to, and why they are written as procedures rather than intentions.
- Agency operations
Building a renewal review workflow
How to run an annual coverage review across a whole book without adding headcount — the trigger, the agenda, the log, and the exception report.
- Agency operations
Lead response time and what it costs
Why the first agency to call usually wins, what actually causes slow response in a small agency, and how to fix it without hiring anyone.