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

---
title: "SOP Use Cases: COIs, Endorsements, Renewals and More"
description: "The workflows worth documenting first: certificates of insurance, endorsements, renewals, claims intake, client onboarding, billing, and more."
url: https://sopwow.com/use-cases
---

*Workflow catalog*

# Which workflows should you turn into SOPs first?

> **Quick answer:** Start with the tasks that score highest on three things: how often they happen, how much a mistake costs, and how few people can do them. In an insurance agency that usually means certificates of insurance, endorsements, renewals, claims intake, new business setup, and cancellations. In any back office it means client onboarding, billing follow-up, vendor setup, month-end work, new-hire system setup, and anything a system migration will touch.

Most teams pick their first SOP badly. They pick the task someone complained about last week, or the one that is easiest to write. Neither is the task that hurts most when it goes wrong.

This page gives you a scoring rule, then a catalog of workflows that tend to score high: insurance agency work first, then workflows every back office shares.

## How do you decide which workflow to document first?

Score each candidate task from 1 to 3 on three factors, then multiply the scores.

| Factor | Score 1 | Score 2 | Score 3 |
|---|---|---|---|
| **How often it happens** | A few times a year | Monthly | Weekly or daily |
| **Cost of a mistake** | Annoying, quick to fix | Rework, and the client notices | Money lost, a coverage gap, a missed deadline, or a regulator's question |
| **How few people can do it** | Most of the team | Two or three people | One person |

The highest product goes first. A 27 is a weekly task with real consequences that exactly one person knows how to do. That is the SOP you write this month.

Two adjustments help:

- **Rare but single-person tasks move up.** A year-end task scores low on frequency, but if one person does it and it goes wrong, nobody remembers how to fix it. Record it the next time it happens.
- **Tasks about to change move down.** If you are replacing the system the task runs in, document it now only if you need it for the migration itself. Otherwise, record it again after cutover.

Record the real task, on a real day, done by the person who already does it. A staged demo skips the exceptions, and the exceptions are why you wanted an SOP in the first place.

## Which insurance agency workflows are worth documenting first?

SopWow started in insurance agency back offices, and these six workflows score high in almost every agency. Each one runs through carrier portals and the agency management system (AMS), and each one hides decisions that a click-by-click guide leaves out.

For each workflow below: what the task is, the decision points SopWow asks about during review, and why the task breaks when it lives in one person's head. The agency view, including AMS migration, is on [SopWow for insurance agencies](https://sopwow.com/industries/insurance-agencies).

### Certificate of insurance issuance

**The task.** A client, or someone the client works with, asks for proof of coverage. The CSR checks the policy, fills in the certificate holder, adds any requested wording, issues the certificate, and saves a copy to the client record.

**Decision points to capture:**

- Is the policy active, and do its limits meet what the holder's contract requires?
- Is the holder asking for **additional insured** status? If so, does the policy already include a blanket additional insured endorsement, or does the carrier need to add one before the certificate can say so?
- Is a **waiver of subrogation** requested, and is it actually endorsed on the policy?
- Does the request include wording (such as primary and non-contributory) that needs someone senior to check the policy first?
- Who can issue it: any CSR, or only the account manager?

**Why it breaks without an SOP.** Certificates are frequent and look routine, so new staff learn them fast. What they miss is the rule behind the routine: a certificate shows coverage, it does not create it. A certificate that shows additional insured status the policy does not provide is an errors and omissions problem waiting to happen.

### Policy endorsements

**The task.** The insured changes something mid-term: a new vehicle or driver, a new location, a higher limit, a changed payroll estimate. Staff take the request, submit the change to the carrier, confirm it went through, and update the AMS.

**Decision points to capture:**

- Does the agency have authority to bind this change with this carrier, or does it need underwriter approval first?
- Is the change submitted in the carrier portal, or requested by email with documents attached?
- Does the change produce a premium adjustment, and is the policy agency billed or direct billed?
- Which documents need reissuing afterward: ID cards, certificates, lienholder notices?

**Why it breaks without an SOP.** Endorsements fail quietly. The request gets submitted but never confirmed, or the carrier processes it but the AMS still shows the old vehicle. Nobody notices until a claim or an audit.

### Renewals

**The task.** Ahead of each expiration date, staff review the account, confirm what has changed, decide whether to renew as is or shop the account, deliver the renewal, and record the result.

**Decision points to capture:**

- How far ahead of expiration does work start, and does that differ for personal and commercial lines?
- What premium increase, or what change in the client's exposure, triggers remarketing?
- What happens when the carrier sends a non-renewal notice instead of a renewal offer?
- Who calls the client, and when does silence from the client become a decision someone must escalate?

**Why it breaks without an SOP.** Renewals run on dates. When the one person who tracks them is out, dates slip, and a slipped date can mean a lapse in coverage.

### Claims intake and first notice of loss

**The task.** A client reports a loss. Staff gather the facts, report it to the carrier (first notice of loss, or FNOL), record the claim number in the AMS, and tell the client what happens next.

**Decision points to capture:**

- Which policy is likely to respond, and does more than one apply?
- Is the loss urgent (injury, ongoing property damage) so that it goes to the carrier's phone line rather than the portal?
- What facts must be collected before reporting, and what can follow later?
- What staff may say to the client about coverage, and what goes to the carrier or a licensed person instead?

**Why it breaks without an SOP.** Claims arrive when the client is stressed and the usual person may be away. A new hire with no procedure either delays the report or says something about coverage they should not. Phone steps happen outside the browser, so add them by hand during review.

### New business and client setup

**The task.** A policy is sold. Staff create or update the client record, enter or download the policy into the AMS, attach documents, set the billing type, and assign the producer and service team.

**Decision points to capture:**

- Is this a new client or a new policy on an existing account, and how do you check for duplicates?
- Is the policy agency billed or direct billed?
- Does the carrier download the policy into the AMS, or does it need entering by hand?
- Which documents are required in the file before the account is considered complete?

**Why it breaks without an SOP.** Every later workflow depends on this one. A client record set up wrong makes every certificate, endorsement, and renewal on that account harder.

### Cancellations

**The task.** A policy ends early, because the client asked or because the carrier is cancelling (often for non-payment). Staff process the request, confirm the effective date, and notify everyone who needs to know.

**Decision points to capture:**

- Is this client-requested or carrier-initiated, and does it need a signed request?
- If the client is moving coverage, is the replacement policy confirmed in force before this one ends?
- How does this carrier calculate return premium, and who tells the client?
- Which certificate holders, lienholders, or mortgagees need notice?

**Why it breaks without an SOP.** Cancellations are less frequent than certificates, so staff do them from memory. A missed replacement check leaves a client uninsured. A missed notice leaves a lender or certificate holder relying on coverage that ended.

## Which workflows matter in every back office?

These six show up in almost every office that works in a browser, whatever the industry. The decisions differ by firm; the pattern of one person knowing the exceptions does not.

### Client onboarding

The first week with a new client sets up every task that follows.

- **Accounting firm:** send the engagement letter, create the client in the practice management system, invite them to the document portal, and decide which services and deadlines apply.
- **Law firm:** run intake, run the conflict check, open the matter, and decide who approves a matter that flags a possible conflict.

### Billing and collections follow-up

The follow-up rules (how long to wait, when to call, when to escalate) usually live in one person's head.

- **Medical office:** work denied or unpaid claims in each payer portal, and decide which denials to correct and resubmit versus appeal.
- **Staffing firm:** chase overdue client invoices, and decide when an account moves from reminder to hold.

### New vendor or carrier setup

Setup is where a bad record enters the system, so the checks matter more than the clicks.

- **Freight brokerage:** set up a new carrier, check authority and insurance, and decide what to do when a document is missing or expired.
- **Construction or home services office:** set up a new subcontractor, collect the tax form and certificate of insurance, and decide who can approve work before paperwork is complete.

### Month-end tasks

Monthly tasks are frequent enough to matter and rare enough to forget.

- **Bookkeeping firm:** reconcile accounts, review uncategorized transactions, and decide which variances need a client question before close.
- **Property management office:** post rent, reconcile the trust account, prepare owner statements, and decide how to handle a partial payment.

### New-hire system setup

Getting a new person into every system is a checklist nobody writes down until someone starts without access.

- **Staffing firm:** create accounts in the applicant tracking system and client portals, and decide which access depends on role or client.
- **Nonprofit:** add staff or volunteers to the donor database and shared tools, and decide what level of donor data each role can see.

### System migration

A migration is the moment you find out how much of the work was never written down.

- **Insurance agency:** move to a new AMS, and decide how each old workflow maps to the new system before cutover.
- **Accounting firm:** switch practice management or document portal systems, and record how the new system handles each client workflow afterward.

Document the current workflow before the switch, then record it again in the new system after cutover.

## What should you do after you pick the first workflow?

Record it the next time it happens, in the browser, with the person who already does it. SopWow writes the draft, asks about the branch points listed above, and flags every claim it added until a person approves it.

If you want to write the first one by hand instead, the steps are in [how to write an SOP someone can follow on day one](https://sopwow.com/guides/how-to-write-an-sop), and [the free SOP template](https://sopwow.com/templates) has sections for triggers, decision points, and exceptions.

## Frequently asked questions

### How many workflows should we document first?

Start with the top three by score. That fits the free trial, which covers your first 3 SOPs, and it is enough to see whether the procedures get used. Add more once those three are in someone else's hands.

### Who should record the workflow?

The person who already does the task well. They know the exceptions. SopWow asks them about the decisions afterward, so they do not have to narrate while they work.

### What if part of the workflow happens outside the browser?

SopWow records browser work only. Phone calls, desktop applications, remote desktop sessions, and paper steps are not captured. Add those steps by hand during review, before you approve the SOP.

### Can one SOP cover every carrier or client?

Usually not. A recording is one path through the workflow. SopWow documents the branch points, so small differences fit in one SOP. When the steps themselves differ, for example a different carrier portal, record a separate SOP for each.

### Will SopWow tell us whether our procedure is compliant?

No. SopWow writes down how your team does the work. It does not check the procedure against any law, regulation, carrier rule, or accreditation standard. Your own review covers that.

## Ready to document your highest-scoring workflow?

Pick the task that scored highest, record it the next time it comes up, and review what SopWow writes. Your first 3 SOPs are free, with no card required.

[Start free: your first 3 SOPs](https://sopwow.com/login) · [Browse industries](https://sopwow.com/industries)