Lesson objective

Build a map of a listing, lead or transaction workflow from records and observation rather than the written procedure, including undocumented steps, workarounds and exceptions.

Plain-language explanation

Why this matters now

Module 1 showed why an AI-assisted task becomes a different thing once many agents and coordinators run it. The first practical step in controlling that system is to see it. Most brokerages have a written procedure for taking a listing, working a lead or coordinating a file to closing. Very few have a picture of how that work actually runs on an ordinary Thursday, and the two are rarely the same.

AI makes the gap expensive. A tool placed on the written procedure will be placed on steps that no longer happen, and it will miss the steps that do: the coordinator's personal checklist, the agent who texts photos to the listing coordinator instead of uploading them, the team leader who re-reads every contract with a handwritten change. Automate the wrong picture and you remove the undocumented checks that were quietly keeping the work right.

Professional guidance (voluntary framework): NIST's AI Risk Management Framework (AI RMF 1.0, January 2023) says that, after instituting its GOVERN outcomes, "most users of the AI RMF would start with the MAP function" and then continue to MEASURE or MANAGE, iteratively. NIST's Cybersecurity Framework 2.0 (February 26, 2024) has a comparable starting function, IDENTIFY, among its six Core Functions (GOVERN, IDENTIFY, PROTECT, DETECT, RESPOND and RECOVER). Both are voluntary, neither binds a brokerage, and NIST states that AI RMF 1.0 is being revised. They are useful here only as structure: understand the work and what it depends on before deciding how to control it.

A question to sit with

Your listing procedure has nine steps. Ask the three listing coordinators to describe what they actually do between the listing appointment and the listing going live, and count the steps. What does it tell you if they each describe a different number, and which version would an AI tool be built on?

What goes wrong

Mapping the manual instead of the work. The written procedure describes the work as someone intended it on the day it was written. People have since added checks, skipped steps that seemed redundant and built workarounds for tools that changed. A map copied from the manual is a map of the past.

Missing the invisible checks. The most important controls are often undocumented: an experienced coordinator who always compares the tax record's square footage with the appraisal the seller supplied, or an agent who never publishes remarks without re-reading them on a phone. Nobody wrote these down because they were habits. Automation removes them silently.

Ignoring the exceptions. The main path handles most files. The exceptions (a pre-1978 home, a listing the seller wants held from public marketing, a buyer who is touring by live video from another state, a contract with handwritten changes) carry most of the risk, and they are where a tool built on the main path fails.

Letting one person describe the whole workflow. A managing broker describes the workflow she supervises; a coordinator describes the one she performs. Neither alone is the map.

Mapping only people, not systems. A workflow runs through the CRM, the transaction platform, the MLS input form, email, text messages and a shared drive. Every place data moves between systems is a place it can change, lag or be lost.

The practical answer

Build the map from three kinds of evidence and reconcile them. The method is an AI Coalition Network recommendation, not a legal or professional requirement.

Evidence How to collect it What it catches
Records Pull 10 to 20 recent completed files and read their timestamps, documents and messages in order What actually happened, including steps nobody mentioned
Observation Sit with a coordinator or agent for a morning, or ask them to narrate a live file Workarounds, personal checklists, copy-and-paste between systems
Interviews Ask each role separately: "What do you do when something is missing or wrong?" Exceptions and informal escalation

Record each step in the same shape. For every step, write down:

Field Example
Step Draft listing remarks
Actor (role, not name) Listing coordinator
Input Verified property data sheet, photos, seller's feature list
Output Draft remarks in the MLS input form
System Transaction platform, MLS input form
Check performed Listing agent reads draft against property data sheet
Record left Approval timestamp in the platform
Rule attached Advertising rules; fair housing; the local MLS's rules
AI involved now or planned Drafting tool, planned
Exceptions Seller-supplied square footage differs from county record

Mark three kinds of step differently. Main-path steps, exception steps and control steps (steps that exist only to catch errors) should look different on the page. Control steps matter most, because they are the ones automation tends to remove.

Walk every exception to its end. For each exception, trace what happens until the file is back on the main path or leaves the workflow. Many exceptions end with "the coordinator asks the team leader", and that informal path is often the brokerage's real escalation route.

Record every system boundary. Wherever data moves from one system to another, note how: automatic sync, export and import, copy and paste, or retyping. Each is a place a tool could introduce, or fail to catch, a change. Professional guidance (voluntary framework): CSF 2.0 states that it "does not prescribe how outcomes should be achieved"; knowing which systems and suppliers the work depends on is the kind of understanding its IDENTIFY and GOVERN functions describe, but the method is yours.

Keep timings honest. Where the map shows a deadline or delay, record where it comes from: a signed contract, a statute you have checked, your local MLS's rules or your brokerage's own practice. Local MLS submission deadlines, delay periods and state disclosure periods differ, so a map built for one office's MLS or one state cannot be copied to another. Lesson 3 covers the rule attachment points.

Map before you change anything. Resist the urge to redesign while mapping. The map records the current state; Module 3 tiers the steps and Module 4 writes the procedure.

Remember this

  • Map the work as it runs, from records, observation and separate interviews, not from the written procedure.
  • Undocumented checks are the controls automation removes first; find and label them.
  • Exceptions carry most of the risk; walk each one to its end.
  • Record every system boundary and how data crosses it.
  • NIST's MAP and IDENTIFY functions are voluntary structure, not requirements; the map is the brokerage's own.

Real estate example

Ashgrove & Vale Realty is a fictional brokerage with two offices and a transaction coordination team of four. The managing broker, Leontyne Park, plans to introduce an AI tool that drafts the weekly buyer and seller status updates coordinators now write by hand. The vendor's implementation guide asks for the brokerage's workflow, and the operations lead, Hollis Remy, starts to send the written coordination procedure: eleven steps from executed contract to closing. Leontyne asks him to map the work first. Hollis reads 18 recently closed files in order, sits with two coordinators for a morning each, and interviews the coordinators and three agents separately. The map he builds has 19 steps on the main path and six exception paths. Three findings change the project. First, one coordinator keeps a personal spreadsheet of every contingency date, which she checks every morning against the platform's task list; the platform had twice shown the wrong date after a contract amendment. Second, agents often agree changes with the other side by phone, and the coordinator learns of them only when the amendment arrives, sometimes days later, so a status update drafted from the platform alone would describe a deal that no longer exists. Third, on files with a pre-1978 home, the coordinator checks that the lead-based paint disclosure and pamphlet were delivered before the contract was signed, a step missing from the written procedure. Hollis sends the vendor the map, not the procedure, and marks the three findings as controls the new tool must not remove.

Responsible-use warning

Do not hand a vendor, or an AI tool, your written procedure and call it the workflow. The manual omits the undocumented checks that experienced staff perform and the exceptions where most errors arise. A tool built on the manual will skip real steps and automate steps nobody performs. Build the map from records, observation and separate interviews, and treat any map drawn only in a meeting room as a draft until real files confirm it.

Human-review requirement

The broker, or the supervisor the broker delegates, owns the map and signs it off as an accurate picture of current work before any redesign begins. Each role on the map confirms its own steps, including the ones nobody wrote down. The licensee responsible for each output confirms the check that precedes release. Where a step touches legal effect, settlement figures or a seller's disclosure, the map shows the attorney, closing agent or seller as the owner, not the tool or the coordinator.

Practical exercise

Use fictional or anonymised material only. No real client, property, agent or transaction.

  1. Choose one workflow: taking a listing to live, working a website lead to a first appointment, or coordinating a file from executed contract to closing.
  2. Write down the steps as your written procedure describes them, and count them.
  3. Take (or invent, if you have none) ten completed fictional files and list the steps each actually shows, in order, with the system used at each step.
  4. Interview two roles separately with the question: "What do you do when something is missing or wrong?" Record every exception they describe.
  5. Build the map using the ten fields in this lesson for each step, and mark main-path, exception and control steps differently.
  6. Walk each exception to its end and note whether it relies on an informal escalation.
  7. Mark every system boundary and how data crosses it: sync, export, copy and paste, or retyping.
  8. List every step that exists in practice but not in the written procedure, and every step in the procedure that no longer happens. Name the role that should confirm each finding.
  9. Mark the map "draft" until two people who do the work have checked it against real files, and record their roles and the date.

Knowledge check

  1. Why should a workflow map be built from records and observation rather than the written procedure?

    Answer guidance: The written procedure describes the work as it was intended when written. Records and observation show the steps people actually perform, including undocumented checks, workarounds and exceptions, which a tool built on the manual would remove or miss.

  2. What is a control step, and why does it deserve special attention on the map?

    Answer guidance: A control step exists only to catch errors, such as a coordinator comparing county square footage with the seller's appraisal. Such steps are often undocumented habits, and automation tends to remove them silently.

  3. How do NIST's MAP function and CSF's IDENTIFY function relate to a brokerage's workflow map?

    Answer guidance: They are voluntary framework functions that start risk work by understanding the context and what the work depends on. They give useful structure but bind no brokerage and prescribe no mapping method.

  4. Why must the source of every deadline or delay on the map be recorded?

    Answer guidance: Deadlines come from different places: the signed contract, a checked statute, the local MLS's rules or brokerage practice. Local MLS deadlines, delay periods and state disclosure periods vary, so a timing copied from another office or state may be wrong.

Sources and further reading