Business process mapping examples for trade and construction firms

Most owners can tell you how a job should go, but fewer can tell you where a job actually sits on a Thursday afternoon, or why a quote that went out a fortnight ago never turned into work. A process map answers that. These business process mapping examples are written for trade and construction firms, so the steps are the ones your office already runs: the enquiry, the survey, the quote, the variation and the invoice.

None of this needs software. A sheet of paper and the person who does the work will get you most of the way. If you want us to do it with you, that is the Map step of how we run the office for a firm.

What a business process map is

A business process map is a drawing of how one piece of work moves through your business, from the thing that starts it to the thing that finishes it. It names each step, the person who owns it, and every handover between people. The American Society for Quality lists the uses plainly: to understand how a process is performed, to communicate it, to study it for improvement and to document it (ASQ, flowcharts).

For a trade firm, the useful part is the handovers. Work rarely stalls while someone is doing a step. It stalls between steps. For example, the survey notes sit in a van, or the quote waits for a supplier price nobody chased.

The three kinds of map worth knowing

A SIPOC diagram is a one-page outline of a process. ASQ describes it as a high-level view of the process "as is", best drawn before a flowchart, when a team first needs to agree what the process includes (ASQ, SIPOC). For most trade firms the swimlane map is the one to draw, because nearly every job crosses from the office to the site and back. The University of Notre Dame's business analysis guide calls it a cross-functional or deployment flowchart, and notes that it is useful for spotting delays, duplicated work and points where a process can fail (University of Notre Dame, swimlane diagram).

BPMN (Business Process Model and Notation) is the formal standard, kept by the Object Management Group, with its own symbols for events, gateways and tasks (OMG, BPMN). It is useful if software will run the process later. For a first map of your own office, boxes and arrows are enough.

Example 1: from enquiry to booked survey

The first process map example is made up for this post. A homeowner fills in the form on a heating firm's website at 9pm asking about a new boiler. Here is the path, with the owner of each step.

1. 01Customer sends the enquiry (form, call or WhatsApp). Owner: customer.
2. 02Office reads it the next morning. Wait: overnight, plus however long the inbox sits.
3. 03Office rings back, asks the job questions and checks the area. Owner: office.
4. 04Office offers survey slots from the diary. Wait: until the surveyor confirms which days are free.
5. 05Survey booked and the customer gets a confirmation. Owner: office.
6. 06Surveyor visits and takes photos and measurements. Owner: surveyor.

The map shows two waits that nobody owns: the overnight gap before anyone reads the enquiry, and the gap while the office checks the surveyor's days. Both are fixable without a new hire. A shared diary removes the second one. A first reply that goes out the same evening covers the first, which is what enquiry handling is for.

Example 2: from survey to signed job

Made-up example. A roofing firm has surveyed a job and now has to price it.

1. 01Surveyor hands over notes, photos and measurements. Wait: until the notes leave the van.
2. 02Estimator asks a supplier for a materials price. Wait: until the supplier replies.
3. 03Estimator builds the quote and the owner checks the margin. Owner: owner.
4. 04Office sends the quote to the customer.
5. 05Office follows up if there is no answer. Wait: often forever, because no step says when.
6. 06Customer accepts, pays a deposit if you take one, and the job goes into the diary.

A common weak point in quote maps is step five. A follow-up that depends on someone remembering is a step with no owner. Writing "office rings on day 3, emails on day 7" on the map turns it into a step someone can do. The supplier price in step two is the other usual wait, and it is the one our supplier quotes work looks at.

Example 3: a variation on a construction job

Made-up example. On a house extension, the client asks the site foreman to move a doorway. This is the map construction firms most often get wrong, because the work happens before the paperwork.

Drawn out like this, the risk is plain: the doorway moves at step one and the approval arrives at step five, if at all. The fix most firms land on is a rule on the map itself: no change starts until step four has gone out, even as a text with a photo. Our page on variations covers how we set that up.

Example 4: from job done to paid

Made-up example. An electrical firm finishes a rewire.

1. 01Electrician marks the job done and uploads the certificate and photos.
2. 02Office checks the job sheet against the quote and any approved variations.
3. 03Office sends the invoice with a link to pay.
4. 04Office checks for payment and sends a reminder if it has not arrived by the due date.
5. 05Payment lands and the office marks the job paid.
6. 06Office asks the customer for a review.

The common gap here is between steps one and three. If the invoice waits for the end of the month, the whole job waits with it. Putting "invoice goes out the day the job is marked done" on the map is a small change that the map makes obvious.

How to map your own process in an afternoon

1. 01Pick one process that costs you money when it stalls. Quote to signed job is a good first choice.
2. 02Get a recent real job file for it, with private details removed. Work from what happened, not from how it should go.
3. 03Sit down with the people who handle each handover. The office lead and one person from site is usually enough.
4. 04Write each step on its own line or sticky note, with the person who owns it.
5. 05Mark every point where the job waits, and how it gets moving again.
6. 06Draw it as a swimlane: one row per person, steps in order left to right, and an arrow at each handover. The Minnesota Department of Health's guide puts it simply: a swim lane map has three elements, time, people and tasks (MDH, swim lane map).
7. 07Ask the people who do the work whether the map matches what happens. Fix it until they say yes.

What to do with the map once you have it

Look at the waits first, because a wait with no owner is the cheapest fix in the whole business: give it an owner and a time, and it usually shrinks. Then look at the steps that are pure copying. For example, retyping survey notes into a quote, or matching variations to an invoice by hand. Those are the steps worth handing to software, and only once the map shows they are stable.

That order matters. Automating a process nobody has mapped tends to make a messy process run faster. It is why the Map step comes before any connection or build in how we run the office, and why the map is checked by your office lead before anything else is scoped.