How to Map a Business Process Before Automating It
Follow an enquiry-to-invoice example with owners, decisions, exceptions and a downloadable workflow worksheet.

The practical answer
Map one real job from input to completion. Record each owner, handoff, decision, exception and source system before choosing what to remove, improve or automate.
Put your workflow questions into a broader roadmap that reflects your business goals and the resources available. Explore Tech Clarity.
A useful process map shows who does the work, which information they need, where a decision happens and what happens when the normal path breaks. Start with one real job and trace it from request to completion with the people who handle it.
Map one enquiry from arrival to invoice #
The following is an illustrative service-business workflow, not a delivered client result. Compare it with what your team actually does before borrowing it.
- 1. Receive enquiryResponsible: Office coordinatorRecord contact details and requested work once. Give it an enquiry ID. If essential information is missing, return a clear request and keep the enquiry open.
- 2. Check scopeResponsible: Person responsible for deliveryDecide whether the job is suitable. A declined request receives a response and closes; an uncertain request goes to a person for clarification.
- 3. Prepare and approve quoteResponsible: Estimator and authorised approverSave the scope version and price. Approval beyond an agreed limit goes to the designated approver; the software does not invent that limit.
- 4. Record customer decisionResponsible: Office coordinatorOnly an accepted current quote creates a job. A changed scope returns to quoting. A declined quote closes without creating work.
- 5. Deliver and confirmResponsible: Job ownerTrack work and completion evidence. An unresolved issue keeps the job open and identifies who follows up.
- 6. Prepare invoice handoffResponsible: Finance reviewerCheck the completed scope, approved variations and billing details. If the accounting connection fails, keep one retryable handoff rather than creating duplicate invoices.
Record what each handoff needs #
| Handoff | Required input | Completion evidence | Exception owner |
|---|---|---|---|
| Enquiry → estimator | Enquiry ID, requested work and contact route | Estimator accepts or declines responsibility | Office coordinator resolves missing information |
| Quote → job owner | Accepted quote version and agreed dates | Job created once with its owner | Estimator reviews changed scope |
| Job → finance | Completion approval and billable items | Invoice reference linked to the job | Finance reviewer checks a failed or ambiguous submission |
Then add the systems used at each step. If the same contact is entered into a form, spreadsheet and accounting system, decide which record is authoritative and who can correct it. A diagram alone does not resolve conflicting data.
Measure waiting separately from working #
Observe a representative sample. Suppose quote preparation takes 20 minutes but waits two days for approval. Those are different problems: automating ten minutes of typing will not remove the approval delay. Record touch time, waiting time, rework and the number of jobs affected. The numbers here are illustrative; use your own observations.
Choose the smallest useful change #
First remove unnecessary steps. Agree owners and decision rules. Next, consider a form that validates required fields, a reminder to an approver, or a monitored invoice handoff. Keep uncertain scope decisions with a person. AI may help summarise a long enquiry, but it should not silently approve work or determine a price.
Test the exceptions before automating #
- An enquiry arrives twice.
- The customer changes the scope after accepting a quote.
- The approver is away.
- The external service times out after accepting the request.
- A staff member without permission attempts to approve the job.
For each test, agree the expected status, who receives the task, and how work resumes. Include a manual fallback and an audit record where the business needs one.
Download the workflow mapping worksheet (CSV). Open in a spreadsheet or text editor; the example rows are illustrative.
A completed first map should let someone new explain the normal journey and its main exceptions without relying on the owner’s memory. The companion guide explains why this preparation matters.
A useful companion: Workflow Mapping Worksheet.
Other articles worth reading

Conditional Logic in Workflows: Practical Automation Ideas for NZ Businesses

When Automation Disappoints: A Practical Review

