Insights
A SIPOC gives a team one agreed picture of a process before anyone tries to fix it. Here is what each column means, how to run the workshop, a template to copy and a worked order to cash example.
By Christopher Fagan, Managing Partner, PEF Consulting Partners
Delivered for and alongside
















SIPOC stands for suppliers, inputs, process, outputs and customers. It is a one page table that maps a process at a high level: who provides what, the five to seven main steps, what comes out and who receives it. Teams use it to agree a process’s scope and boundaries before measuring or improving it.
It is deliberately simple, and that is the point. Many process problems start with people describing the same process in different ways, and a single shared map makes those differences visible in an hour rather than three weeks into a project.
In this article
Before anyone measures a process, automates it or outsources it, they need to agree what the process is. Where does it start and stop? Who feeds it, and who depends on what it produces? Those questions sound basic, but the first workshop on an improvement project often reveals that finance, operations and IT each have a different answer.
The diagram gives everyone the same frame. It is short enough to fit on one slide, so a sponsor can read it, and structured enough to show where the handoffs and dependencies sit. It also tells you who needs to be in the room for the next stage of the work.
Many teams add requirements next to the inputs and outputs, describing what good looks like for each. An invoice is an output; an invoice that is accurate, on time and matches the delivery note is a requirement. That extra detail is where improvement targets usually come from.
The technique is usually traced to the total quality management movement of the late 1980s. Six Sigma later made it a standard tool in the define phase of DMAIC, the cycle of define, measure, analyse, improve and control. In define, the team agrees the problem, the process and its boundaries before collecting any data, and a one page map from suppliers to customers is the quickest way to get there.
You do not need a Six Sigma programme to use it. It works just as well at the start of a system implementation, a shared service design or an outsourcing decision, anywhere people need to agree on a process before they change it.
A first version takes about an hour with the right people: someone who does the work, someone who receives the output and whoever owns the process. Work through it in this order.
Starting in the middle, with the process, is the usual advice because it anchors the conversation. Some teams prefer to start from the customer and work backwards, a variant sometimes called COPIS, which keeps attention on what the customer actually receives. Either order works, as long as the map gets finished.
Above the table, write one line that sets the boundary: this process starts when a named event happens and ends when another does. Then fill in the process column first, work outwards to outputs and customers, and finish with inputs and suppliers.
| Suppliers | Inputs | Process | Outputs | Customers |
|---|---|---|---|---|
| Who provides each input? Internal teams, external organisations or systems | What the process needs to start and run, and what good looks like for each | Five to seven main steps, verb and noun, from the agreed start to the agreed end | What the process produces, and what good looks like for each | Who receives each output, internal and external |
| Supplier 1 | Input 1 | Step 1 (start) | Output 1 | Customer 1 |
| Supplier 2 | Input 2 | Step 2 | Output 2 | Customer 2 |
| Supplier 3 | Input 3 | Step 3 | Output 3 | Customer 3 |
| Supplier 4 | Input 4 | Step 4 | Output 4 | Customer 4 |
| Supplier 5 | Input 5 | Step 5 (end) | Output 5 | Customer 5 |
The rows do not need to line up. Each column is a list in its own right, and one supplier can provide several inputs or one output can go to several customers.
This worked example is hypothetical: a building products wholesaler selling on account to trade customers. The boundary runs from a customer order being received to the cash being allocated against the invoice. For a fuller description of the process itself, see our guide to order to cash.
| Suppliers | Inputs | Process | Outputs | Customers |
|---|---|---|---|---|
| Trade customer | Purchase order with items, quantities and delivery address | 1. Receive and enter the order | Confirmed sales order | Trade customer |
| Sales team | Price list and agreed discounts | 2. Check credit and price the order | Order released or held | Warehouse |
| Credit control | Credit limit and account status | 3. Pick, pack and despatch | Delivery note and despatched goods | Trade customer |
| Warehouse | Available stock | 4. Deliver and capture proof of delivery | Signed proof of delivery | Finance team |
| Carrier | Proof of delivery | 5. Raise and send the invoice | Accurate invoice | Trade customer |
| Customer’s bank | Payment and remittance advice | 6. Collect payment | Payment received | Finance team |
| 7. Allocate cash and chase overdue accounts | Cash allocated, aged debt report | Credit control, management accounts, auditors |
Even at this level, the map raises useful questions. Credit control appears at both ends: it supplies the credit limit at the start and receives the aged debt report at the end, so if that report is late or wrong, tomorrow’s credit decisions are made on stale data. Invoicing depends on proof of delivery coming back from the carrier, and when that input is slow or incomplete, invoices wait and so does the cash. Those two points are where a team would start measuring.
The approach transfers well to an energy supplier’s meter to bill process, and the differences are instructive. Suppliers include industry parties as well as internal teams: metering and data services, industry registration systems and the pricing team. Inputs are meter readings or half hourly consumption data, tariffs and rates, and customer account details. The process runs from reads received, through validation and estimation, to bill calculation, exception review and issue, and the outputs go to collections, finance and regulatory reporting as well as to the customer.
What a meter to bill map usually exposes is how many inputs arrive from outside the supplier’s control, and how much of the process exists to cope with inputs that are late, missing or wrong. That exception handling is where cost and complaints build up. To put a number on it, try the billing exception cost calculator, and for background on the process, read energy billing explained.
Billing is also where weak handoffs turn into money. Christopher Fagan led the recovery of a £160m+ billing imbalance that surfaced at a Big Six energy supplier once its Kraken migration was live, and problems on that scale are rarely visible from inside any one team, which is exactly why a shared view of the whole process matters.
Use it at the start of any process improvement, system implementation or outsourcing decision, whenever people need to agree which process they are talking about. It is particularly useful when a process crosses several teams or organisations, because nobody owns the whole of it and each team sees only its own part. It also makes a good first artefact for a newly appointed process owner.
It is the wrong tool when you need detail. It will not show decision points, rework loops, waiting time or who does each step; for that you need a swimlane process map. Nor will it diagnose causes. Once the map has shown where the problem sits, a fishbone diagram or a wider root cause analysis is the natural next step.
A one page map opens the work rather than closing it. It frames the measurement and analysis that follow, it helps define process ownership in a new operating model and it shows where a process meets its neighbours, such as procure to pay on the supply side. At a higher level, a value chain analysis shows how the main processes of a business fit together and which of them matter most to cost and competitive position.
Our operational excellence work often starts with exactly this kind of shared picture. The difference is what happens next: we stay to redesign the process with your team and build the change into systems and ways of working, rather than handing over a map and leaving.
A SIPOC is a one page, high level map of a process. The letters stand for suppliers, inputs, process, outputs and customers. It lists who provides what to the process, its five to seven main steps, what it produces and who receives the results. Teams use it at the start of improvement or system projects to agree the scope and boundaries of a process.
SIPOC stands for suppliers, inputs, process, outputs and customers. Suppliers provide the inputs, the process turns them into outputs through a handful of main steps, and customers receive the outputs. Many versions also record requirements for the inputs and outputs, describing what good looks like. Read in reverse, starting from the customer, the same tool is sometimes called COPIS.
Agree the name and boundaries of the process first: what starts it and what ends it. Then list five to seven high level steps, followed by the outputs and the customers who receive them, then the inputs and the suppliers who provide them. Add requirements where you can, and test the draft with people who supply or receive the process but were not in the workshop.
Yes. SIPOC is a standard tool in the define phase of the Six Sigma DMAIC cycle, where a team agrees the problem, the process and its boundaries before collecting data. It is usually traced back further, to the total quality management movement of the 1980s, and it is widely used outside Six Sigma in lean, process redesign and system implementation work.
A SIPOC is a scoping tool. It shows a process in five to seven steps, with its suppliers, inputs, outputs and customers, on one page. A detailed process map, usually drawn in swimlanes, shows every step, decision, handoff and loop, and who does each one. Most teams build the SIPOC first and use it to decide which part of the process to map in detail.
Related reading: Fishbone diagram, Root cause analysis, Order to cash explained and Operational excellence.
We can run the mapping workshop with your team, find where the handoffs fail and help you fix them in the process and the system, not just on paper.
Book a confidential conversation
Sources: Pande, P. S., Neuman, R. P. and Cavanagh, R. R., The Six Sigma Way, 2000; George, M. L., Rowlands, D., Price, M. and Maxey, J., The Lean Six Sigma Pocket Toolbook, 2005
Written by Christopher Fagan
Managing Partner, PEF Consulting Partners
Christopher has led systems and transformation delivery for 19 years, including the National Grid separation, the £9bn Energy Bills Support Scheme and the BP Pulse EV charging rollout.
Where next