You want to automate something, but nobody has written down how it works today. To document business processes before automation, spend one afternoon on six things per step: trigger, owner, tool, handoff, exception and finish line. Skip the polished diagram. This is the working page behind the small business workflow audit you may be running. A developer needs it to build the right thing. Many owners in Medford and across South Jersey carry these steps in their heads. Here is how to get them onto paper.
What "written down" means: six fields per step
Most advice says to map the process visually and stops. A flowchart with boxes and arrows looks tidy and still leaves out what breaks. A usable map answers six questions for every step.
- Trigger: what starts this step. A form submission, an email, a date, a phone call, a status change.
- Owner: the one person or role who is responsible. If two people say "me," write both and flag it.
- Tool: where the work happens. Name the real thing: a Gmail inbox, a QuickBooks screen, a shared spreadsheet, a paper job ticket.
- Handoff: what moves to the next person, in what form, and how they find out it arrived.
- Exception: what happens when the normal path fails. Missing info, a customer who changes their mind, a rush order.
- Finish line: how you know the step is done, in words a new hire could check.
Handoffs and exceptions are where workflows tend to leak. A step that works when everything is normal rarely needs fixing. The step that depends on someone remembering to forward an email does.
Pick one workflow and gather the evidence first
Do not map the whole company. Map the one workflow you ranked first. If you have not ranked yet, the scoring sheet that weighs lost revenue, not just hours saved will get you there. Mapping three workflows in one sitting produces three shallow maps.
Then collect evidence before anyone talks. Memory edits out the awkward parts. Pull together:
- The last five to ten real examples of the workflow, start to finish, including a messy one.
- Whatever you wrote in your breakdown log. If you kept one, the Q4 breakdown log already lists the moments things went wrong.
- Screenshots or exports from each tool involved: the inbox, the spreadsheet, the booking calendar, the invoice screen.
- Any templates, canned replies, checklists or sticky notes people actually use.
The sticky notes matter most. A note taped to a monitor is a process step nobody wrote down.
The afternoon in four passes
Block three to four hours and invite the people who do the work, not only the person who supervises it. The operator who runs the system daily should be in the room, because they will have to explain it to everyone else later.
Pass one: walk one real case, out loud
Pick a recent job and have the person who touched it first narrate what they did. Write one line per action. Do not correct them or improve anything yet. If they say "then I usually check," ask what they check and where. "Usually" is an unwritten rule, and you want it on paper.
Pass two: fill in the six fields
Go back through each line and add trigger, owner, tool, handoff, exception and finish line. Expect blanks. A blank in the handoff column means work moves by habit. That is a finding, not a failure of the exercise.
Pass three: walk it again with a messy case
Take the ugly example from your evidence pile. Where did the clean map stop matching reality? Add those branches as exceptions. Expect the real process to have more forks than the one described at the start.
Pass four: mark time, waiting and rework
Next to each step, note roughly how long it takes and how long work sits waiting before the next person picks it up. Mark any step that gets done twice. Use your own rough numbers, labeled as estimates. You are looking for the longest wait, not for precision.
A capture sheet you can copy
A spreadsheet is enough. One row per step, one column per field. Here is a made-up example for a service business turning a quote request into a scheduled job. It is an illustration of the format, not a real client's process.
| Step | Trigger | Owner | Tool | Handoff | Exception |
|---|---|---|---|---|---|
| Request arrives | Website form submitted | Office manager | Shared Gmail inbox | Forwarded to estimator by email | Form sent to spam; caller leaves voicemail instead |
| Site estimate | Estimator reads forward | Estimator | Paper notes, phone camera | Notes typed into a spreadsheet at day's end | Notes lost; photos never saved |
| Quote sent | Spreadsheet row complete | Owner | Word template, email | PDF attached to reply | Customer asks for changes by text |
| Job scheduled | Customer replies "yes" | Office manager | Wall calendar | Crew told verbally | Crew double-booked; no reply after quote |
Read the Handoff column top to bottom. Every handoff is an email, a retyping or a spoken message. Those are the places an automation, or a system built around your process, can take over. The last row shows how one gap, no follow-up after the quote, hides in the Exception column.
Exceptions decide what you build
An automation that handles the normal path and drops the rest creates new work. Someone has to catch what it misses. So for each exception, decide one of three things and write it in the sheet.
- Automate it. The exception is predictable and the fix is mechanical. A reminder when a quote sits unanswered, for example.
- Route it to a person. The system flags it and a named human decides. Anything involving money, a complaint or a judgment call belongs here.
- Leave it alone. It happens rarely and handling it by hand costs less than building for it.
This is also where you decide what a human reviews. Say an AI step drafts a reply or sorts an inbox. Write down who reads the output before a customer sees it. Write down what they do when it is wrong. A build brief that cannot name that person is not finished.
Keep the exception list honest. Ask one question for every row: "What did we do the last time this went wrong?" The answer is usually a workaround that lives in one person's head.
A recipe is already a written process
We built Meez, an AI recipe and cooking app that takes a pasted recipe link and turns it into a timer-driven Cook Mode. Meez is a product, not a client operations project, so it does not show how to audit a business. It does show something useful about your map. A recipe works as software input because it is already a process written down: ordered steps, quantities, timers and a clear finish. Your quote-to-job workflow can be built the same way once it has that structure. Without it, the software has nothing reliable to follow.
Software only automates what is explicit. Take "the estimator knows which jobs need a second visit." That has to become a written condition before anything can act on it.
Turn the map into a build brief
When the sheet is full, you have most of a brief. Convert it with four short edits.
- Circle the handoffs that depend on memory. These are your first candidates.
- List every tool by name, and note whether you can export its data. A tool you cannot export from changes the plan.
- Write each exception's decision: automate, route to a person, or leave alone.
- Add the finish line for the whole workflow, in one sentence, so everyone agrees what "fixed" looks like.
With that in hand, the choice between process change, subscription and custom build gets much easier. The sheet shows which steps a template tool can cover and which need your own rules. Our post on choosing between a subscription and a custom build for the workflow you ranked first walks through that decision.
For scale, look at WRAPT, the wholesale operations platform we built. It runs a nine-stage pipeline from lead to delivery, with a client portal and a support hub. A system like that starts as a list of stages, owners and exceptions. Your version will be smaller, but the starting document looks the same.
What this exercise will not tell you
A process map shows how work flows. It does not tell you what the fix costs, how many hours you will save or whether the result will pay off. Those need a scope and a quote. We also cannot tell you from outside your business which step to fix first; that is what ranking is for.
The map can go stale. Tools change, people leave, a new exception shows up. Date the sheet and recheck it when the workflow changes. And the exercise may show that the process itself is the problem. If two people do the same step differently, agree on one way first. Automating a disagreement just makes it faster.
Frequently Asked Questions
How do I document business processes before automation if I have no time?
Map only the workflow you ranked first, and use one real recent case rather than every variation. A single afternoon with the people who do the work is enough for a first pass. Capture trigger, owner, tool, handoff, exception and finish line for each step, then refine the map as new exceptions appear.
What should a process document include for an automation project?
It should list each step in order. For each one, record the trigger, the person responsible, the tool used and how work passes on. Add what happens when something goes wrong and how you know the step is done. Note whether each tool lets you export its data. That is the core of a build brief.
Do I need flowchart software to map a process?
No. A shared spreadsheet with one row per step and one column per field works well, and it is easier for non-technical staff to edit. A diagram can come later if you want one for training. The detail in the columns matters more than the drawing.
Who should be in the room when we map a workflow?
Include the people who do the work day to day, plus whoever owns the outcome. Supervisors often describe the intended process, while the operators know the workarounds. The person who will run the finished system daily should attend, since they will explain it to the rest of the team.
Next step
Once the sheet is filled in, your January numbers get easier to set. Our guide to sizing your January systems budget covers that part. If you want to know what building around the sheet would take, bring it to us, even half finished. We will tell you what we would automate, what we would route to a person and what we would leave alone. Start with our AI workflow automation service.
Sources
Every outside claim in this article links to where it came from. These open in a new tab.