Lesson objective

Map a new business, renewal or service workflow as staff actually perform it, including undocumented steps, carrier-specific variations and exceptions, from real activity history rather than the procedures manual.

Plain-language explanation

Why this matters now

Module 1 ended with a rule: map before you manage. This module builds the map. It is the least glamorous part of any AI project and the part most often skipped, because everyone believes they already know how the work runs. The procedures manual says so, the account managers say so, and the vendor's demonstration assumed so.

The map that matters is not the one in the manual. It is the one in the activity history, the shared inbox and the personal spreadsheet an account manager keeps of which carriers need a phone call before their renewal offer can be trusted. An AI-assisted step inserted into the manual's version of the workflow will be inserted into a process that does not exist.

Carrier variety is the main reason reality drifts from the manual. The Big "I" 2024 Agency Universe Study, conducted by Zeldis Research in cooperation with Future One with 1,269 respondents and reported by IA Magazine on September 26, 2024, found that agencies are appointed with an average of 17 carriers and that dealing with multiple carrier interfaces was agents' No. 1 technology issue. A renewal workflow is therefore not one workflow. It is one workflow with as many variations as the agency has carriers that behave differently.

Professional guidance (voluntary framework): the NIST AI Risk Management Framework (AI RMF 1.0, NIST AI 100-1, January 2023) says that, after instituting its GOVERN outcomes, "most users of the AI RMF would start with the MAP function", and that MAP, MEASURE and MANAGE can be applied in system-specific contexts and at specific lifecycle stages. It is voluntary, binds no agency, and NIST states that 1.0 is being revised. It is a useful structure, not a requirement: understand the context before measuring or managing the risk.

A question to sit with

Your procedures manual describes a personal auto renewal in five steps. How many steps does it actually take for your three largest carriers, which of those steps exist only in one person's head, and what happens to a renewal when that person is on holiday?

What goes wrong

Mapping the manual. The manual records the process someone intended, often before the last system change. Steps that no longer happen stay on the page; steps that were added to cope with a carrier's new portal never reach it.

Mapping the best performer. The account manager asked to describe the process is usually the one who does it best. Their version includes judgement they apply without noticing, and omits the shortcuts others take under pressure.

Leaving out the exceptions. A renewal that goes through cleanly is the easiest to map and the least informative. The non-renewal notice, the underwriting referral, the mid-term change that crosses the renewal date and the client who moves states are where errors live, and an AI tool will meet them too.

Averaging away carrier variation. "Download the renewal and compare" hides that one carrier's download omits endorsements, another's renewal offer arrives only as a PDF in the portal, and a third changes the policy number at renewal. A map without a carrier column hides the steps most likely to break a tool.

Missing the informal steps. Sticky notes, a personal list of clients who want a call rather than an email, a text to the producer's phone, a habit of checking the prior year's file for a manuscript endorsement. None is written down; several are the real controls.

Mapping at the wrong grain. "Prepare renewal" is too coarse to show where a tool would fit. "Click the fourth tab" is too fine to be maintained. The useful grain is one step per change of person, system, document or decision.

The practical answer

Define the edges first. Write the trigger and the end point in one sentence each. For a personal lines renewal: "Trigger: the renewal appears on the agency's expiration list 60 days out. End point: the renewed policy is confirmed in the management system and the client has received what the agency sends at renewal." Anything outside those edges belongs to a different map.

Build the map from evidence, in this order. This method is an AI Coalition Network recommendation, not a legal or professional requirement.

  1. Pull recent closed items from the activity history: at least three for each carrier that handles the work differently, plus every exception type you can find.
  2. Walk through each item with the person who actually handled it, screen by screen, asking "what did you do next, and why?"
  3. Shadow a live session during a busy period, not a quiet one.
  4. Read the manual last, and mark every difference between it and what you observed.
  5. Show the draft map to the people who do the work and ask what is missing. Their corrections are the most valuable part.

Record each step with the same columns.

Column What to record
Step A short verb phrase, one per change of person, system, document or decision
Who The role, and whether the person is licensed for the relevant line
System The management system, a carrier portal, email, a rater, a spreadsheet, paper
Input The document or data the step starts from, and where it comes from
Output What the step produces, and where it goes
Carrier variations Which carriers change this step, and how
Exceptions What can divert the item here, and roughly how often in your sample
Informal controls Anything done that is not written down
Time Observed minutes, marked as observed or estimated

Draw it in lanes. A swimlane map, with one lane each for the client, service staff, account managers, producers, each distinct carrier behaviour and any tool, makes handoffs visible as lines crossing lanes. Every crossing is a place where context can be lost, which Module 1 showed is where scale creates risk.

Add a carrier variation grid. For workflows touching many carriers, keep a grid beside the map.

Step Carrier A (fictional) Carrier B (fictional) Carrier C (fictional)
Receive renewal terms Overnight download PDF in portal only Download, but endorsements missing
Confirm endorsements From download Read from PDF Open the portal endorsement schedule
Policy number at renewal Unchanged Unchanged New number issued
Underwriting questions Rare Portal message Email to the account manager

Each cell that differs from the first column is a place where a tool built on one carrier's pattern could fail.

Map the three workflow families separately. New business, renewal and service start from different triggers and cross the licensing line at different points.

Family Typical trigger Where the licensing line tends to fall
New business An inquiry, referral or lead Gathering information may be administrative; discussing coverage, quoting and recommending are licensed work
Renewal The expiration list Preparing documents may be administrative; explaining changes, comparing options and recommending are licensed work
Service A client or carrier request Recording a request may be administrative; any change to coverage, and any discussion of it, is licensed work

Lesson 3 of this module marks those points precisely, under the state's own law.

Keep the map owned and dated. The map is a controlled document like the prompt library: one owner, a date, a version, and a trigger to update it when a carrier changes its portal, the agency changes its system, or an exception becomes common.

Remember this

  • Map from the activity history and the people doing the work, then read the manual last.
  • Carrier variation is the main reason reality drifts from the manual; keep a carrier grid beside the map.
  • Exceptions and informal steps are where errors, and many real controls, live.
  • Use one step per change of person, system, document or decision.
  • The map is a controlled document: owned, dated and updated when carriers or systems change.

Insurance example

Fenwick & Oduya Agency is a fictional personal lines agency. Its manual describes a homeowners renewal in five steps: download the renewal, compare with the expiring policy, note changes, email the client, file. Operations lead Imogen Sarrazin wants to add an AI-assisted comparison step, and first maps the workflow. She pulls 30 closed renewals from the last two months, 10 each from three fictional carriers, and walks through them with the two account managers who handled them. The map that emerges has eleven steps, not five. For Brambleton Mutual, the overnight download is complete. For Aldermoor Casualty, the download omits endorsement changes, so account manager Jonah Petrakis opens the portal endorsement schedule for every renewal, a step in no manual. For Copperline Home, the renewal offer arrives only as a PDF in the portal. Four of the 30 renewals went to an underwriting referral, and in each case the account manager held the client email until the producer had spoken to the client. Jonah also keeps a personal list of 19 clients who have asked for a call, not an email, when their premium rises by more than a set amount. That list is the agency's only record of those requests. Imogen shows the draft map to the team, and they add a twelfth step: checking whether a mid-term change made after the renewal was generated has carried into the renewal. She marks the Aldermoor endorsement step and Jonah's list as informal controls the tool must not remove, records "underwriting referral: 4 of 30" as an exception count from a small sample, dates the map and names herself as its owner. The AI comparison will be designed for the twelve-step process, not the five-step one.

Responsible-use warning

Do not map the workflow from the procedures manual, from the vendor's demonstration or from one expert's description alone. Each shows the process someone intended or the best version of it, and each leaves out the carrier workarounds, exceptions and informal steps that actually protect clients. A tool designed for a tidy map removes the untidy steps without anyone deciding to. Build the map from closed items and the people who handled them, and read the manual last.

Human-review requirement

The people who do the work review the draft map, because only they can say what is missing. The licensed producers for each line confirm where the map shows licensed work: discussing, comparing, quoting, recommending and changing coverage. The operation owner signs off the map as the version the redesign will use, dates it and owns updating it. Agency principals confirm the map is what the agency will be held to, since a mapped informal control that is later removed is a decision, not an accident.

Practical exercise

Use a fictional agency, fictional carriers and invented account histories only. No real client, policy or carrier material.

  1. Choose one workflow: a personal auto renewal, a small commercial new business submission, or a mid-term vehicle change. Write its trigger and end point in one sentence each.
  2. Invent six closed items for it, two for each of three fictional carriers, including at least one exception.
  3. Write out, for each item, what the person handling it did next and why, as if walking through the activity history with them.
  4. Draw the swimlane map with lanes for the client, service staff, account managers, producers, each carrier behaviour and any tool.
  5. Record each step using the columns from this lesson: step, who, system, input, output, carrier variations, exceptions, informal controls and time.
  6. Build the carrier variation grid and circle every cell that differs from the first carrier.
  7. List every informal control you found and write what would happen to the client if a tool removed it.
  8. Compare your map with a short, invented five-step manual version, and list every difference.
  9. Tally each exception you found across your six items, state the sample size beside each count, and write the map's owner, version number and the event that would trigger its next update.

Knowledge check

  1. Why should the procedures manual be read last when mapping a workflow?

    Answer guidance: The manual records the process someone intended, often before the last system or carrier change. Reading it first anchors the map to that intention, while reading it last lets you mark every difference between it and what actually happens.

  2. What is a carrier variation grid, and why does it matter for an AI project?

    Answer guidance: It is a table beside the map showing how each carrier changes a step, such as a download that omits endorsements. Every cell that differs from the first carrier is a place where a tool built on one carrier's pattern could fail.

  3. What grain should a workflow map use?

    Answer guidance: One step per change of person, system, document or decision. Coarser steps hide where a tool would fit, and finer ones, such as individual clicks, cannot be maintained.

  4. Why do informal controls matter when a tool is introduced?

    Answer guidance: Steps such as a personal list of clients who want a call, or manually checking a portal because a download is incomplete, are often the real protections. If the map omits them, the tool removes them without anyone deciding to.

Sources and further reading