
SIPOC Generator and Complexity Calculator
Map suppliers, inputs, process, outputs and customers in one view. Score the complexity, find every handoff and set a realistic improvement timeline before the project starts.
What a SIPOC diagram does
SIPOC gives you a one page view of any process. The letters stand for Suppliers, Inputs, Process, Outputs and Customers. You build it before you map anything in detail, so the team agrees on the boundaries first.
This version lets you list several suppliers, inputs, outputs and customers against every process step. It then counts the unique entries and scores the complexity.
Why teams use SIPOC
- Sets the start point and end point of the process in writing
- Shows who supplies the work and who receives it
- Builds shared understanding before the first improvement meeting
- Exposes gaps where an input has no owner
- Feeds directly into value stream mapping and process mapping
- Gives sponsors a scope document they can approve
How to enter several items in one cell
Two entry methods
One item per line
Press Enter after each item. Each line counts as a separate entry.
Comma separated
Type items on a single line separated by commas, for example: Supplier A, Supplier B, Supplier C.
Both methods work in the same cell. The calculator counts unique entries across every row, so repeated names are counted once.
How the complexity score works
The formula
Score = (Unique suppliers x 2) + (Unique inputs x 3) + (Process steps x 5) + (Unique outputs x 3) + (Unique customers x 2) + (Handoffs x 5)
Process steps and handoffs carry the heaviest weight because they drive cycle time and defect risk more than the number of parties involved.
| Score | Band | What it means for your project |
|---|---|---|
| Under 50 | Low complexity | Simple process. Suits a kaizen event or a rapid improvement week. |
| 50 to 119 | Moderate complexity | Standard business process. Plan three to six months with a part time team. |
| 120 to 199 | High complexity | Cross functional process. Use full DMAIC and dedicate resources. |
| 200 and above | Very high complexity | Enterprise process. Split into sub projects and secure executive sponsorship. |
How handoffs are detected
The rule
A handoff is counted when none of the customers in one row appear as suppliers in the next row. The work has left one group and landed with a group that was not named as a receiver.
Handoffs are where queues form, context gets lost and rework starts. Every handoff you remove takes time and risk out of the process.
Using the calculator
Step 1. Name the process
Give the process a specific name and record the owner. Vague names produce vague SIPOCs.
Step 2. Fill one row per major step
- Suppliers. Who provides the inputs for this step. Include internal teams and systems.
- Inputs. Materials, data, approvals and tools the step needs.
- Process. The step itself, written as a verb and an object.
- Outputs. What the step produces, including documents and records.
- Customers. Who receives each output.
Step 3. Generate and read the score
Select Generate SIPOC. The Results tab shows your diagram, the complexity score, the contribution of each factor and a handoff table. Export the workbook to share it.
Pro tips
- Aim for five to seven rows. More than that and you are process mapping, not scoping.
- Build it with the people who do the work, not from a procedure document.
- Name systems as suppliers when they feed the step, for example the ERP or the ticketing tool.
- List the output that nobody wants, such as a rework queue. It often reveals the real problem.
- Check the handoff table first. Handoffs give the fastest return in most projects.
- Use the score to set the timeline you promise the sponsor.
Common mistakes
- Writing task level detail instead of major steps
- Mixing up inputs with suppliers, or outputs with customers
- Leaving out internal customers such as finance or compliance
- Recording only physical materials and ignoring information flows
- Signing off the SIPOC without the process participants in the room
- Treating a high score as a reason to stop rather than a reason to plan properly
Load sample data
Each dataset shows several suppliers, inputs, outputs and customers per step. The software sprint example lands in the very high band so you can see the colour coding.
Process details
Entry tip. Put one item per line, or separate items with commas. Both work in the same cell.
| Suppliers | Inputs | Process step | Outputs | Customers | Action |
|---|
Complexity analysis
Fill in the Calculator tab and select Generate SIPOC. Your diagram, complexity score and recommendations appear here.

