> Fetch the complete documentation index at: https://sopwow.com/llms.txt

---
title: "How to Document Insurance Agency Workflows"
description: "A practical order for documenting an insurance agency: start with COIs and endorsements, capture real runs in your AMS, and write the decisions down."
url: https://sopwow.com/guides/document-insurance-agency-workflows
---

*Guide: insurance agency operations*

# How should an insurance agency document its workflows?

> **Quick answer:** Start with an inventory of workflows by line of business and by role. Document first the ones that happen most often, cost the most when done wrong, and live in the fewest heads, which usually means certificates of insurance and endorsements. Have the person who does each task best record a real run. Handle carrier and account differences with decision tables instead of separate copies, name SOPs consistently, and review them whenever a carrier or the AMS changes.

An agency procedures manual rarely fails because nobody wrote anything. It fails because it was written once, by the wrong person, in the wrong order, and nobody opened it after the last system upgrade.

This guide is an order of operations that avoids those three problems. It works with a shared drive and a word processor. It does not need any particular software, and nothing in it depends on which agency management system (AMS) you run.

## What workflows does an agency actually have?

More than anyone guesses. Before you write a single procedure, build an inventory: one spreadsheet, one row per workflow. Give it columns for line of business, role, system used, how often it happens, and who knows how to do it well.

Then read it two ways. Sorted by line of business, it shows where the gaps are. Sorted by role, it becomes the training list for the next hire in that seat.

Here is a starting inventory by line. Your agency will add its own rows and cross some of these out.

| Line | Common workflows |
|---|---|
| Personal lines | New business entry, auto ID cards, driver and vehicle changes, mortgagee and lienholder changes, evidence of insurance for lenders, renewal review, non-pay cancellation follow-up, reinstatements, first notice of loss |
| Commercial lines | Certificates of insurance, additional insured and waiver requests, endorsements, market submissions, renewal remarketing, audit disputes, loss run requests, claims reporting |
| Benefits | Census collection, new group setup, enrollment, adds and terminations, carrier bill reconciliation, renewal quoting, open enrollment preparation, continuation notices |

And the same work viewed by role:

| Role | Workflows they usually own |
|---|---|
| CSR | Certificates, ID cards, policy change requests, payment and billing questions, cancellation and reinstatement follow-up, first notice of loss |
| Account manager | Renewals, remarketing, coverage reviews, endorsements that need underwriter approval, audit disputes, client onboarding in the AMS |
| Producer support | Prospect entry, submissions to markets, quote comparison packets, proposal assembly, handoff of a sold account to service |

Do not forget the agency-wide work nobody claims: carrier download exceptions, direct bill commission reconciliation, agency bill invoicing, new carrier appointments, and closing out a lost account. These are often the tasks only one person knows. If you want a ready-made starting list, see [the insurance workflows worth documenting first](https://sopwow.com/use-cases).

## Which workflows should an agency document first?

Score every row in the inventory on three things, each from 1 (low) to 3 (high):

- **Frequency.** How often does this task happen?
- **Error cost.** What goes wrong when it is done badly: a client exposure, an unhappy certificate holder, a carrier record that no longer matches the AMS, money misapplied?
- **Knowledge concentration.** How few people can do it without asking? One person scores a 3.

Multiply the three scores. Sort from highest to lowest. Document from the top.

For most agencies, certificates of insurance and endorsements land at or near the top, and for good reason:

- **Certificates of insurance** are frequent and time-sensitive, and the requirements change with every certificate holder. A certificate that describes coverage the policy does not provide creates a problem for the client, the holder, and the agency.
- **Endorsements and policy changes** touch the carrier, the AMS record, billing, and the client confirmation. A skipped step leaves the carrier's record and the agency's record disagreeing, and nobody notices until renewal or a claim.

Resist the urge to start with the rare, frightening task, such as the once-a-year carrier contract renewal. Write it down eventually. But frequent tasks give the people writing SOPs practice on work they know cold, and the finished procedures get used the same week.

## Who should record each workflow?

The person who does the task best, not the person who manages it.

Managers know what should happen. The CSR who issues certificates every day knows what actually happens: which carrier portal times out, which certificate holder always wants particular wording, which field the AMS silently clears when you save. That knowledge is the whole point of the SOP, and it only comes out when the expert does the real task.

"Best" means accurate and consistent, not fastest. The recorder does a real run on a real request, not a demonstration on a made-up account, and says out loud or writes down why each choice was made. The manager's job is review: read the draft, question anything that looks like a shortcut, and approve it.

If two people do the same task differently, you have found two procedures. Pick one person to record, have the other review, and settle the differences before anything is published. That conversation is often the most useful hour of the whole project.

Finally, have a third person, ideally someone newer, follow the draft cold. Every place they stop to ask a question is a gap in the document.

## How do you handle carrier and account differences?

With decision tables, not twelve copies of the same SOP.

The task "issue a certificate of insurance" is one task. What varies is a handful of conditions. If you write a separate SOP for every carrier and every demanding certificate holder, you will have a dozen documents that drift apart the first time anything changes. Write one SOP and put the variation in a table at the step where it matters.

An example for the certificate request step (illustrative; confirm against your own agency's rules):

| If the request... | Then... |
|---|---|
| Asks for additional insured status | Check the policy for a blanket additional insured endorsement. If there is none, request one from the carrier and do not issue until it is confirmed. |
| Asks for a waiver of subrogation | Check the policy for waiver language that applies to this holder. Same rule: no confirmed endorsement, no certificate. |
| Asks for primary and noncontributory wording | Confirm the policy form supports it. If unclear, route to the account manager. |
| Asks for limits higher than the policy carries | Do not issue. Route to the account manager or producer. |
| Comes from a holder already on file | Use the saved holder record and wording, and check it still matches the current request. |

Carrier differences work the same way. Keep one carrier reference table per line: where endorsements are submitted (portal, underwriter email, or download), who approves what, and whom to call. The SOP step then reads "submit the change the way the carrier table says", and when a carrier changes its process you update one row, not every SOP.

Account differences belong in the account itself. Most agency systems have a notes or special-handling area. Make "check the account's special-handling note" an early step, and keep the exceptions there.

Split into a separate SOP only when the steps change, not just the values. A benefits enrollment and a commercial endorsement are different procedures. Two carriers with different portals are usually one procedure and a table.

## How should agency SOPs be named?

Verb, object, system. A name that starts with what the person is about to do is the one they will search for.

- CL: Issue certificate of insurance in the AMS
- PL: Process a vehicle change in the carrier portal
- BEN: Add a new employee to a group plan
- ACCT: Reconcile a direct bill commission statement

A few rules make the library easier to search as it grows:

- Use the verb your staff actually use. If everyone says "cert", put "certificate (cert)" in the title once so both searches work.
- One task per SOP. "Renewals" is a category. "Prepare a commercial renewal review" is a task.
- A short line prefix (CL, PL, BEN, ACCT) keeps the list sorted by department.
- No dates, initials, or "final v2" in the name. Version and owner live inside the document.

## Where should agency SOPs live?

In one place everyone already opens, with one current version of each procedure.

A shared drive with folders by line and then by role works. So does an intranet page, a wiki, or a knowledge base. The tool matters less than four properties: people can search it, there is one current copy, only named owners can edit, and a copy is reachable when the AMS or the internet is down. A PDF set for business continuity is worth keeping.

Places SOPs should not live: attached to a random client file in the AMS, in someone's email, on a personal desktop, or in a binder nobody has updated.

One agency-specific rule: keep client data out of SOP screenshots. Record on a test account where you can, blur or crop real names and policy numbers where you cannot, and check every image before the SOP is published.

## When should agency SOPs be reviewed?

When something changes, with a yearly floor for everything else.

Calendar-only reviews miss the moments that break procedures. Tie reviews to these triggers instead:

- A carrier redesigns its portal, changes a submission process, or is newly appointed.
- The AMS gets an upgrade, a new module, or a replacement. If you are [planning an AMS migration](https://sopwow.com/guides/migrate-agency-to-new-ams), the review becomes a rewrite.
- A standard form gets a new edition, or a carrier changes an endorsement form.
- An error or near miss traces back to the procedure.
- The SOP's owner leaves or changes roles.

Every SOP should carry an owner and a "last confirmed" field. At least once a year, the owner opens it, follows it, and either confirms it or fixes it.

## Does documentation help with errors and omissions exposure?

It can make the agency's intended steps visible and consistent. It is not a shield.

Written procedures state what the agency expects to happen: the checks before a certificate is issued, how offers of coverage and client declinations are recorded in the file, how a change request is confirmed back to the client. That consistency is useful for training, for supervision, and for showing what the agency's process was.

What an SOP is not: legal advice, a compliance certification, or a guarantee of any outcome. A procedure that says one thing while staff do another creates its own problems, which is why the review triggers above matter.

Ask your E&O carrier or your counsel what they expect your procedures and file notes to show. They know your policy and your state. This guide does not.

## What does a 30-day documentation plan look like?

A month is enough to build the system and finish the first handful of procedures. How many you finish depends on how many people can record and review, so treat this as a template, not a promise.

| Week | Focus | Work | Output |
|---|---|---|---|
| 1 | Inventory and setup | Build the inventory by line and role. Score frequency, error cost, and knowledge concentration. Pick the top five. Assign a recorder and a reviewer to each. Agree on naming, storage, and a template. | Scored inventory, top-five list, folder structure, template |
| 2 | Certificates of insurance | The best certificate issuer records a real request. Draft the SOP with the certificate holder decision table. A newer staff member follows it cold. Fix the gaps. | Approved certificate SOP and decision table |
| 3 | Endorsements and policy changes | Record the most common change type per line. Build the carrier reference table for where changes are submitted. Review and test. | Approved endorsement SOPs, carrier table |
| 4 | Next on the list, plus a check | Record the next two or three workflows from the scored list, such as renewal preparation or new client setup. Set owners and review triggers for everything finished. | More approved SOPs, owner and trigger list, next month's list |

At the end of the month, rescore the inventory. Some tasks will have moved up because you learned something while writing the first ones.

## Where does SopWow fit?

SopWow is one way to do the recording and writing step. The person who knows the task does it once in their browser with the SopWow recorder running. SopWow drafts the SOP, asks about the decision points a recording cannot explain, such as why a certificate needed an endorsement first, and flags anything it added until a person keeps or removes it. Nothing is final until someone approves it.

It only records work in the browser. Steps in a desktop application, a remote desktop session, or Citrix are not captured and can be added by hand in review. More on [how SopWow works for insurance agencies](https://sopwow.com/industries/insurance-agencies).

## Frequently asked questions

### What goes in an insurance agency procedures manual?

One SOP per distinct task, organized by line of business and role. Each SOP names its owner, the system used, the trigger that starts the task, the steps, the decision points (usually as a table), and what "done" looks like. Carrier-specific details go in reference tables the SOPs point to.

### Should the agency owner or manager write the procedures?

Usually not. The person who does the task best should record or draft it, because they know what actually happens. The owner or manager reviews, resolves disagreements between staff, and approves.

### Should each carrier get its own SOP?

Only when the steps are genuinely different. Most carrier differences are values: which portal, which form, whom to call. Put those in a carrier reference table and keep one SOP per task. Separate copies drift apart quickly.

### How often should agency SOPs be updated?

Whenever something that affects them changes: a carrier portal, the AMS, a form edition, or the owner. On top of that, have each owner follow and confirm every SOP at least once a year.

### Do written procedures protect an agency from E&O claims?

No document guarantees that. Procedures make the agency's expected steps clear and consistent, which helps with training and supervision. Ask your E&O carrier or counsel what they expect your procedures and file documentation to show.

## Ready to document your first agency workflow?

Pick the task that scored highest, have your best person do it once, and turn that run into an SOP your whole team can follow.

[Start free: your first 3 SOPs](https://sopwow.com/login) · [See insurance workflows](https://sopwow.com/use-cases)