How to map a business process so automation actually sticks

Bottom line: A process map for automation needs triggers, owners, systems, and exceptions — not a pretty diagram nobody updates.

Clarity beats BPMN. Australian SMBs ship faster with a numbered doc the bookkeeper and ops lead both sign off on.

Step 1: Name the process and outcome

One outcome per map: "Quote to invoice for residential maintenance" — not "sales."

Step 2: Define start trigger and end state

Start: customer accepts quote. End: invoice paid and job closed in Xero. Ambiguous ends break bots.

Step 3: List each step with owner and system

Who does it, which tool, typical duration. Include phone calls and whiteboards — they are steps.

Step 4: Mark decision points and exceptions

Deposits, variations, credit notes, GST-free clients, and rush jobs need branches. Discover exceptions before build, not in production.

Step 5: Identify system of record per field

One owner for customer identity, job value, and status. Automations sync from owner to consumers.

Step 6: Review with finance and operations

Bookkeeper or BAS agent signs off before anything touches Xero or MYOB.

Template you can copy

1. Trigger: ___
2. Step / Owner / System / Minutes: ___
3. Exception: ___ → Human path: ___
4. End state: ___

FAQ

Need BPMN software?
No. Numbered list or simple swimlane is enough.

How detailed?
Detailed enough that someone new could follow on a quiet week.

When to hire help?
When maps cross three-plus systems or touch revenue recognition. Operational redesign covers this.

A written map is all you need to bring to a free 30-minute call if you want the handoffs fixed.