In emergency plumbing and maintenance services, customers do not experience your organisation as separate departments. They experience one journey: a call, a promise of help, an arrival, a diagnosis, a repair, and a signed-off job.
That journey is your value stream.
Value Stream Mapping (VSM) is a Lean method for visualising the sequence of activities and information flows required to deliver a product or service. It exposes the difference between value-added work and everything that delays, complicates or repeats the customer outcome. The U.S. Environmental Protection Agency’s Lean toolkit describes VSM as a method for identifying non-value-added time, designing a less wasteful future state and planning improvement activity.
For emergency trades, the method is particularly powerful. A business may appear busy while technicians spend too much time travelling, waiting for information, searching for parts, repeating visits or completing administration after the work is finished.
The fundamental purpose is not to make technicians rush. It is to create a more reliable flow so the right technician arrives with the right information and parts, resolves the fault safely, captures payment and closes the job with minimal rework.
1. Scope the Emergency Trades Value Stream Correctly
A useful map starts with a disciplined scope. Do not begin with “improve the business”; begin with one defined service family and one measurable customer outcome.
For this guide, the value stream begins when an after-hours emergency call enters the business and ends when the job is:
- Diagnosed accurately
- Repaired and tested
- Documented with photographs and notes
- Paid or approved for billing
- Signed off by the customer
- Closed in the operating system
The scope includes:
- Inbound after-hours call and customer identification
- Fault triage and urgency classification
- Job creation and dispatch
- Technician travel
- On-site diagnosis
- First-time repair
- Parts sourcing where required
- Testing and customer explanation
- Invoice creation and payment capture
- Customer sign-off and job closure
This scope should exclude unrelated activities such as planned maintenance, procurement strategy for the entire organisation and long-term account management.
A clear project charter should define the customer, process boundaries, baseline metrics and target outcomes. Lean 6 Sigma Hub’s guide to scoping Lean Six Sigma projects provides a useful framework for setting those boundaries.
2. Current-State Map: A Worked Emergency Plumbing Example
Consider a plumbing and emergency maintenance provider receiving 68 after-hours calls per week across four service vans. The following figures represent a realistic illustrative baseline collected from call records, dispatch timestamps, GPS data, job notes and invoicing reports.
| Current-state measure | Baseline |
|---|---|
| After-hours calls | 68 per week |
| Average dispatch time | 11.2 minutes |
| Average travel time | 34 minutes |
| Average on-site diagnosis | 26 minutes |
| First-time fix rate | 61% |
| Return visit rate | 39% |
| Parts available on first visit | 72% of jobs |
| Average invoice lag | 2.4 days |
| Technician utilisation | 54% |
| Management target utilisation | 75% |
The average call-to-arrival time is approximately 45.2 minutes, before diagnosis begins. However, this figure alone does not reveal the full flow problem.
A representative current-state sequence might look like this:
- Call received and basic details recorded: 6 minutes
- Triage and job classification: 5.2 minutes
- Waiting for dispatch confirmation or technician acceptance: 18 minutes
- Travel to site: 34 minutes
- On-site diagnosis: 26 minutes
- Waiting for parts on jobs without suitable stock: 41 minutes average
- Repair and testing: 52 minutes
- Customer explanation and paperwork: 15 minutes
- Invoice creation: completed 2.4 days later on average
The map reveals several important facts. First, the customer may wait longer for coordination and parts than for the repair itself. Second, the 39% return visit rate creates a rework loop that consumes van capacity and reduces availability for new emergencies. Third, only 54% of paid technician time is being converted into productive diagnosis, repair, testing or necessary customer communication.
Using the Process Cycle Efficiency formula:
PCE = Value-added time ÷ Total lead time
Assume the value-added work in this example is diagnosis, repair and testing: 78 minutes. If the total elapsed operating time, excluding the later invoice lag, is 197 minutes, process cycle efficiency is approximately 39.6%.
That is not a judgement on individual performance. It is a signal that the system contains substantial waiting, movement, parts and information waste. The Process Cycle Efficiency Calculator can help teams separate hands-on value from queues, transport, rework and administrative delay.
3. The Eight Wastes in Field Trades Services
Apply the DOWNTIME acronym directly to the emergency trades process:
- Defects: Incorrect addresses, incomplete fault descriptions, wrong parts, inaccurate diagnosis and missing customer approvals create repeat work.
- Overproduction: Preparing duplicate paperwork, creating unnecessary internal reports or dispatching more resources than the fault requires adds activity without increasing customer value.
- Waiting: Customers wait for triage, technicians wait for dispatch decisions, and technicians or customers wait for parts, access or approval.
- Non-utilised talent: Experienced technicians spend time re-entering information, searching for standard parts or solving avoidable scheduling problems instead of applying technical expertise.
- Transportation: Long cross-zone travel, depot trips and returning to collect parts increase fuel cost and reduce available capacity.
- Inventory: Understocked vans create return visits; overstocked vans carry slow-moving parts that consume space and capital.
- Motion: Technicians search through unstructured vans, walk repeatedly between the vehicle and site, or navigate multiple disconnected systems.
- Extra-processing: Duplicate data entry, manual invoice preparation, repeated customer calls and unnecessary approval steps extend lead time.
The key is to connect each waste to a measurable outcome. For example, poor van stock is not merely an inventory concern; it directly affects first-time fix rate, return visits, revenue capacity and customer confidence.
4. Build the Future State Around Reliable Flow
A future-state map should show how information, people, vehicles, tools and payment move with fewer interruptions. The following countermeasures are practical starting points.
Use fault-code triage scripts
Create concise scripts for common emergency categories such as burst pipes, blocked drains, no hot water, gas-related concerns where appropriately licensed, leaking toilets and failed pumps.
Each script should capture:
- Fault symptoms and urgency
- Property type and access conditions
- Isolation points or safety risks
- Photographs or video where appropriate
- Likely parts and specialist requirements
- Customer availability and payment method
This converts unstructured conversation into reliable input data for dispatch and preparation.
Standardise van stock using parts Pareto analysis
Analyse the previous 90 to 180 days of parts usage. If 20% of part categories account for 80% of emergency consumption, those high-frequency items should form the core standard stock.
Set:
- Minimum and maximum quantities
- Replenishment triggers
- Technician-specific exceptions
- Daily or weekly stock checks
- A controlled process for slow-moving specialist items
The objective is not to place every possible part in every van. It is to improve availability for the most probable failure modes while controlling inventory cost.
Introduce zone-based dispatch
Divide the service territory into practical zones and assign jobs using three rules:
- Safety and skill fit
- Parts and equipment fit
- Geographic proximity
A nearby technician without the required capability is not an efficient assignment. The best dispatch decision balances distance, competence, current workload and first-time-fix probability.
Create mobile job packs
A mobile job pack should contain the fault-code checklist, customer details, access notes, risk prompts, required photographs, parts used, test results, customer approval and sign-off fields.
This creates standard work without removing professional judgement. It also improves the quality of information available to the invoicing team.
Capture payment and sign-off during the same visit
Where commercial terms allow, technicians should capture payment, approval, photographs and digital sign-off before leaving site. Exceptions should be visible rather than hidden in an administrative queue.
Level demand across the week
A scheduling board should display call volumes, technician capacity, repeat visits, planned maintenance commitments and geographic demand. Use the data to identify predictable peaks and protect capacity for emergency work.
5. Current State Versus Future State
The following targets illustrate what a 90-day improvement programme could pursue. They are planning targets, not guaranteed outcomes.
| Key metric | Current state | Future-state target |
|---|---|---|
| Call-to-arrival time | 45.2 minutes | 35 minutes |
| First-time fix rate | 61% | 82% |
| Return visits | 39% | 15% |
| Invoice lag | 2.4 days | Same day or under 4 hours |
| Technician utilisation | 54% | 72–75% |
| Revenue per van per day | $1,180 | $1,520 |
| Customer satisfaction | 3.8/5 | 4.5/5 |
The improvement logic is straightforward. Fewer return visits release capacity. Better triage improves technician and parts matching. Faster payment capture reduces invoice lag. Zone-based routing reduces travel. Together, these changes improve flow without relying solely on adding vans or extending working hours.
6. A 90-Day Kaizen Sequence
Sequence matters. Attempting every improvement simultaneously can create confusion and make it difficult to identify which change produced the result.
| Wave | Days | Owner | Main actions | Expected impact |
|---|---|---|---|---|
| Wave 1: Stabilise | 1–30 | Operations Manager and Dispatch Lead | Confirm definitions, validate baseline data, introduce fault-code scripts, create daily visual metrics and standardise job-close requirements | Dispatch time reduced by 15–20%; stronger data quality |
| Wave 2: Improve flow | 31–60 | Fleet Lead and Senior Technicians | Complete parts Pareto, standardise core van stock, introduce zone-based dispatch and pilot mobile job packs with two vans | First-time fix improvement of 10–15 percentage points; lower travel and parts-related rework |
| Wave 3: Control and scale | 61–90 | Service Director and Finance Lead | Implement same-visit payment capture, level weekly demand, review utilisation, audit adherence and expand proven practices across the fleet | Invoice lag below 4 hours; utilisation approaching 72–75%; customer satisfaction above 4.5/5 |
Review the metrics weekly using run charts or control charts. If first-time fix improves but customer satisfaction declines, the team must investigate whether technicians are being pressured to close jobs too quickly. If utilisation rises while safety or quality performance worsens, the future state requires adjustment.
This is where Lean Six Sigma discipline matters. The baseline metrics guide explains why operational definitions, reliable data and before-and-after comparisons are essential for credible improvement.
Turn Emergency Service Complexity into Competitive Capability
Value Stream Mapping gives emergency trades businesses a shared view of how work actually flows: from the first distressed customer call to a verified, paid and signed-off job.
It helps leaders see where the process loses time, where technicians lose capacity and where customers experience avoidable uncertainty. More importantly, it converts broad intentions such as “improve dispatch” into specific actions: improve triage, standardise van stock, route by zone, digitise the job pack and close the commercial loop on site.
For professionals leading this work, Lean Six Sigma training provides the structured capability to define the problem, measure the baseline, analyse root causes, test improvements and sustain the gain. Explore Lean Six Sigma Green Belt online training to develop the practical skills required to lead data-driven service improvement projects.
Start your Lean Six Sigma certification journey today and learn how to turn service delays, repeat visits and wasted capacity into measurable operational performance.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma
