All articles

Business Analysis

5

min read

SIPOC: set the scope before you start modeling

Simon Parmet Profile Picture

Simon Parmet

Cover: SIPOC, set the scope before you start modeling

A SIPOC is a one-page overview of a process: its Suppliers, Inputs, the Process in five or six high-level steps, its Outputs and its Customers. You make it before you model, to agree with the client where the process starts, where it ends and who is involved. It also helps decide which interviews to plan and what the process model needs to cover.

The question that derails the first workshop

The kickoff is going well. The client wants the claims process modeled, the sponsor has blocked two weeks, and the first interviews are in the calendar. Then the head of claims says: "So this includes the recovery from the other party's insurer, right?" The IT lead assumed it ended at payout. Customer service thought it started at the phone call, not at the registered claim.

Each of them has a different process in mind under the same name. If modeling starts before that is settled, the difference tends to surface during validation, when parts of the model turn out to be out of scope or missing.

A SIPOC is one way to settle this at the start.

What the five letters mean

  • Suppliers: who or what delivers something the process needs. A customer, another department, an external party, a system.

  • Inputs: what they deliver. A form, a document, a data record, a request.

  • Process: the work itself, in five or six steps at high level. Not the detail, that comes later in the model.

  • Outputs: what the process delivers. A decision, a payment, a letter, an updated record.

  • Customers: who receives the outputs. Internal or external, people or systems.

The method comes from Six Sigma and quality management (see ASQ on SIPOC), and in process modeling work it is mainly used as a short scope statement the client can review quickly.

How to fill in a SIPOC

A SIPOC is usually filled in together with the client, on a whiteboard or a shared screen. A common order is:

  1. Name the process and its start and end. One sentence each: "starts when a claim is registered, ends when the claim is paid or rejected and the file is closed." This is where the discussion from the kickoff belongs.

  2. Write the five or six process steps. Use verbs and stay at a high level. If the list grows much beyond seven steps, the scope may be too wide or the level of detail too fine.

  3. Fill in the outputs and customers. What comes out, and who receives it. Many practitioners fill in this side before the suppliers, because outputs are often easier to agree on.

  4. Fill in the inputs and suppliers. What the steps need, and where it comes from.

  5. Read it back out loud. "Suppliers X deliver inputs Y, we do these six steps, and customers Z receive outputs W." Points where people disagree are scope questions to note and resolve.

An example: handling a damage claim

For an insurer's claims process, scoped as "from registered claim to payout or rejection":

  • Suppliers: policyholder, claims portal, damage assessor, garage or repairer, policy administration system.

  • Inputs: claim form with photos, policy and coverage data, assessor's report, repair quote.

  • Process: register claim, check coverage, assess damage, decide on the claim, pay out or reject, close the file.

  • Outputs: claim decision, payment, decision letter, closed claim file.

  • Customers: policyholder, finance, garage or repairer, management reporting.

Recovery from the other party's insurer is not in the list. That makes the choice visible: recovery can become a separate process with its own SIPOC, or the end point can move and the scope grows. Either way, the client decides before modeling starts.

From SIPOC to process model

The SIPOC is not a process model, but it feeds directly into one:

  • The start and end become your start and end events. The model of the claims process starts at "claim registered" and ends at "file closed", nothing before or after.

  • The five or six steps become the backbone. Each one is a section of the model, or a subprocess if it is large.

  • Suppliers and customers who do work become lanes. Parties that only receive something, such as a letter, can be shown as external participants instead. See the swimlane diagram post for when that matters.

  • Suppliers and customers are your interview list. Each internal party in the SIPOC is a candidate for an interview. The process interviews post covers how to get what you need from them in an hour.

And later, when you derive a RACI matrix from the model, the roles in it can be checked against the parties in the SIPOC. A role that appears in one but not the other usually points to a scope change.

Common pitfalls

  • Too much detail in the P. A long list of steps turns the SIPOC into a process model in a table. Five to seven steps is the usual range.

  • No end point. "Handling claims" leaves the boundaries open. "From registered claim to closed file" makes them explicit.

  • Only internal parties. External parties such as the policyholder and the garage are suppliers too. Without them, it is easy to miss the points where the process waits on someone outside the organization.

  • Filling it in without the client. A SIPOC drafted alone and sent for approval tends to get less scrutiny than one built together in a session.

When you can skip it

For a small, clearly bounded process that everyone already describes the same way, a SIPOC adds little. If the client says "the expense claim process, from submission to reimbursement" and nobody disagrees, a one-sentence scope with a start and an end point is often enough.

A SIPOC is most useful when several departments are involved, when the process name means different things to different people ("the claims process", "onboarding") or when the scope determines a fixed-price quote.

What happens after the SIPOC

Once scope is agreed, the work moves to the interviews and the model, which is usually where most of the time goes: writing up each conversation, building the BPMN model, collecting what is still unclear and producing the documentation.

That is the part ModelMatic takes over. You upload the interview recordings, transcripts or existing documents for the scope you agreed on, and you get a BPMN model in which every step points back to its source, with open questions flagged for the next conversation. After validation, the SOP, RACI matrix and requirements come from that same model. At one consultancy, working out a process went from about 8 hours to about 1 hour.

The SIPOC itself remains work you do with the client. See what happens after it on the features page, or book a demo to see a process model built from an example interview.

Frequently Asked Questions

Find answers to the most important questions about ModelMatic.

What exactly is ModelMatic?

ModelMatic is an AI-driven platform that directly converts spoken language and documentation into professional BPMN 2.0 process models. We take over the work between interview and process model, from the write-up to the documentation, so business consultants and process analysts can focus on the analysis.

How much time does ModelMatic really save me?

Is my data safe with ModelMatic?

What kind of sources can I convert into a process model?

Does ModelMatic work with my current systems?

What if the AI makes a mistake in the model?

What does ModelMatic cost?

Where can I go with further questions?

Frequently Asked Questions

Find answers to the most important questions about ModelMatic.

What exactly is ModelMatic?

ModelMatic is an AI-driven platform that directly converts spoken language and documentation into professional BPMN 2.0 process models. We take over the work between interview and process model, from the write-up to the documentation, so business consultants and process analysts can focus on the analysis.

How much time does ModelMatic really save me?

Is my data safe with ModelMatic?

What kind of sources can I convert into a process model?

Does ModelMatic work with my current systems?

What if the AI makes a mistake in the model?

What does ModelMatic cost?

Where can I go with further questions?

Frequently Asked Questions

Find answers to the most important questions about ModelMatic.

What exactly is ModelMatic?

ModelMatic is an AI-driven platform that directly converts spoken language and documentation into professional BPMN 2.0 process models. We take over the work between interview and process model, from the write-up to the documentation, so business consultants and process analysts can focus on the analysis.

How much time does ModelMatic really save me?

Is my data safe with ModelMatic?

What kind of sources can I convert into a process model?

Does ModelMatic work with my current systems?

What if the AI makes a mistake in the model?

What does ModelMatic cost?

Where can I go with further questions?

Purple Gradient Background

The future of process modeling starts now

See how quickly a conversation or a document turns into a model your team can work with.

Purple Gradient Background

The future of process modeling starts now

See how quickly a conversation or a document turns into a model your team can work with.

Purple Gradient Background

The future of process modeling starts now

See how quickly a conversation or a document turns into a model your team can work with.

ModelMatic Banner Logo

ModelMatic converts interviews into editable process diagrams so the focus is on validating and innovating instead of manually modeling

Newsletter

Get tips, product updates, and insights into working smarter with AI.

© 2026 ModelMatic B.V. (CoC: 95586679). All rights reserved.

ModelMatic Banner Logo

ModelMatic converts interviews into editable process diagrams so the focus is on validating and innovating instead of manually modeling

Newsletter

Get tips, product updates, and insights into working smarter with AI.

© 2026 ModelMatic B.V. (CoC: 95586679). All rights reserved.

ModelMatic Banner Logo

ModelMatic converts interviews into editable process diagrams so the focus is on validating and innovating instead of manually modeling

Newsletter

Get tips, product updates, and insights into working smarter with AI.

© 2026 ModelMatic B.V. (CoC: 95586679). All rights reserved.