Business Process Mapping for Small Teams: Example and Worksheet

A useful process map needs to show more than the steps people take. It should reveal who owns each stage, what information lets the work move to the next person, and what happens when someone cannot proceed. Those handoffs are often where an otherwise sensible workflow gets stuck.

For a small team, start with a table covering the trigger, owner, input, handoff, and exceptions. Turn it into a flowchart later if the branching decisions are difficult to follow. The example below tracks a routine property-maintenance request from intake through invoicing.

Start with one specific process

“Manage maintenance” is too broad to map usefully in an afternoon. “From a tenant’s nonemergency repair request to a checked contractor invoice” has a recognizable beginning and end. The word nonemergency matters: urgent hazards or legally regulated repairs may need a separate route with different authority and response requirements.

State the start event, the intended finish, and the people who touch the work. Pull a few recent examples of the actual process, including one that went wrong. Follow the records, not just the procedure the manager thinks everyone follows. If employees make a decision in a phone call or chat, that belongs on the current-state map too.

Map the handoffs in a simple table

Here is a worked example for a small property-management office. It is illustrative; the approval limits and service commitments must come from the business’s real agreements.

Stage	Who owns it	What they need	What the next person receives
1. Record request	Office coordinator	Address, issue, contact details, permission to access where applicable	Ticket with a reference number and reported problem
2. Triage	Property manager	Ticket, property details, urgency and relevant authorizations	Approved normal route or escalation for urgent/unclear cases
3. Assign repair	Coordinator	Approved scope and contractor availability	Contractor receives location, task and access arrangements
4. Record completion	Contractor	Work order and any authorized changes	Completion note, unresolved issues, and approved changes
5. Check outcome	Property manager	Completion record and confirmation where needed	Approved closeout or a return to the contractor
6. Match invoice	Accounts	Approved work order, final scope, invoice	Invoice queued for payment or returned for clarification

The important discovery may be between stages 4 and 5. If the contractor sends the completion note to the coordinator’s personal phone, the property manager may have no reliable way to approve the closeout. Your map should say which system or record is authoritative, not simply that people must communicate.

Show the decisions, not only the happy path

Many first attempts at process mapping are neat straight lines because everyone describes what normally happens. Add a decision where an employee needs permission or where work can stop.

The diagram should make the hold state visible. If the team cannot answer who owns an unresolved repair, that is a process problem worth fixing. Avoid filling the map with unlikely branches just to make it look thorough.

If you need a conventional flowchart, a box usually represents an action, a diamond a decision, and arrows show direction. A swimlane version places actions beneath each responsible role, making the handoffs easier to see. The American Society for Quality’s flowchart guide explains the common elements. You do not need special software for a six-stage process.

Find the wait, the rework, and the ownerless step

Ask three questions as you walk through the map. Where does a job wait for a decision? Where does information have to be entered again? Where does the current owner stop working before the next owner knows it is ready?

Measure only what helps you choose a fix. On a few actual cases, note when a request arrived, when approval was given, when the contractor finished, and when accounts received a complete record. Compare the work time with waiting time. If invoices sit for days after repairs are done, making the contractor faster will not solve the billing delay.

Look for exceptions that create repeat calls, such as an incomplete address, unapproved extra work, or a missing completion note. If several cases share the same problem, you may need a root cause analysis before choosing a solution.

Write the improved map, then test it on a real case

Don’t treat a proposed map as the current process. Label your original view As it works today and the changed version Proposed. Suppose the repair closeout is frequently lost between people. A sensible improvement is to require the contractor to attach the completion note to the work order and assign the property manager a clear review state.

Test the improved route on one ordinary repair and one with unfinished work. The coordinator should know who is waiting, the manager should see the evidence needed to decide, and accounts should receive the correct approved scope. If a missing field or system permission blocks any of them, correct that issue before telling the entire team the new process is live.

Once the handoffs are settled, create a short SOP for the repeated task or a detailed work instruction for the confusing software screen. Keep those task-level instructions linked from the map rather than burying every click inside it.

Copyable process map worksheet

Use one row per meaningful step, with an exception or next owner where work might stop. Start from a recent real transaction and fill in the columns with the employees involved.

Step / trigger	Owner	Input required	Output / next owner	If blocked
[What starts this step?]	[Role]	[Record or decision]	[Evidence and handoff]	[Stop, owner, next action]
[Second step]	[Role]	[Record or decision]	[Evidence and handoff]	[Stop, owner, next action]
[Final check]	[Role]	[What proves ready?]	[Completed state]	[Where it returns]

Put the current copy where the team can reach it. Name the person who owns changes to the map and review it when a handoff, approval rule, tool, or role changes. For a complete documentation register and update routine, see Process Documentation for Small Businesses. If employees need practice with the new workflow, use the training rollout guide.

Back to Operations.