Write an SOP with the E&O checkpoints built in

Act as an operations lead at an independent agency writing a standard operating procedure. Write it so a new CSR can follow it on day one, with the errors-and-omissions checkpoints marked.

Task: [NAME THE TASK]
How we do it today, in my words: [PASTE OR DESCRIBE]
Systems involved: [AMS NAME, CARRIER PORTALS, EMAIL, PHONE]
Where it has gone wrong before: [INCIDENTS OR NEAR MISSES, OR "NONE KNOWN"]
Who does it and who checks it: [ROLES]

Produce, in order:
0. ASSUMPTIONS. Any bracket I left unfilled, anything ambiguous, and what you assumed instead. Write "none" if there were none
1. Purpose and when this SOP applies, three lines
2. The steps, numbered, each one action with the system it happens in. After any step that creates or changes coverage, dates, or client instructions, an E&O CHECKPOINT line: what to verify, what to document and where, what to do if the check fails, and who to tell (the checker I named), so a failed check has a next step
3. What gets documented in the client file at the end, as a list
4. The three most likely errors and the step that prevents each
5. Review date and owner
6. WHAT I SHOULD CONFIRM FIRST. Every carrier rule, deadline, or system behavior you assumed

Rules:
- Anything you inferred rather than were told goes in "WHAT I SHOULD CONFIRM FIRST" instead, never in both places
- No step may depend on memory. If information is needed, the step says where it is read from
- No legal advice, no state-specific regulatory claims; where a state rule may apply, the checkpoint says "confirm the state requirement" instead of stating one
- Hard limit: 550 words for the whole response. If you cannot fit it, cut the least useful section and say which one you cut

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response, every section filled in, nothing deferred to a follow-up. If a required input is missing, ask for it once before starting; otherwise proceed and record the assumption in section 0.

Notes: R42 build; insurance set. Tuned to vendor prompting guidance.