A plain-English guide

BPMN vs CMMN vs DMN: choose the right model

BPMN describes the route. CMMN holds work that changes with the situation. DMN describes the rule used to reach a decision. Most organisations need more than one, and this practical comparison shows where each belongs.

BPMN · Route: Repeatable work with a known sequence; CMMN · Case: Evolving evidence and available work; DMN · Rule: Explicit inputs, conditions and results. Give each model a clear responsibility. Choose a process, adaptive case or decision rule for the job.

The short answer

Start with what makes the next step happen

A practical comparison of BPMN, CMMN and DMN
ModelUse it whenWhat it makes visible
BPMN-based processA defined route, event or result determines what happens nextActivities, events, gateways, waits and responsibility
CMMN-based caseNew evidence or professional judgement determines what work is appropriateCase information, available work, planning and milestones
DMN-aware decisionKnown inputs should produce a result through explicit rulesInputs, rule logic and outputs

One example

Consider a serious customer complaint

The complaint itself may need a case because the facts, people involved and appropriate response are not known at the start. The case keeps the evidence and gives an authorised person suitable work to choose from.

Some parts are repeatable. A privacy check, acknowledgement or refund approval may follow a defined process. Those parts can run as BPMN-based processes from the case.

A rule may decide whether the complaint must be escalated. That logic belongs in a decision, where the inputs and outcome can be reviewed without tracing the whole process or case.

Whose name is on the certificate?

You’re setting up a new supplier and their insurance certificate expired last week. You email them for a current copy and put the application on hold. That’s an exception you can plan for in BPMN: when the replacement arrives, check it and carry on.

The supplier sends it through the next morning. The dates are fine. It’s the name at the top that makes you stop. The certificate names the parent company, but your purchase order names its subsidiary. You ring the supplier. “Yes, the order’s with us,” they say, “but it’s the parent company’s crew doing the work.”

The fictional purchase order names Kōwhai Field Services Ltd, the subsidiary. The current insurance certificate names Kōwhai Group Ltd, its parent.
The certificate is current. Does it cover the company doing the work?

What would you check next? You might ask the site manager which crew they’re expecting. Their answer might settle who’s doing the work, or it might send you back to the contract. Once you know who’s turning up, you can check whether the insurance covers them.

That investigation is the part I’d model as a CMMN case. The reviewer keeps the documents and findings together and follows up on what they learn. The rest of onboarding stays as it was: the application is still on hold, and the person who normally approves suppliers still makes the call.

Want to try this with a process you know? Download Pūnaha and sketch a supplier check using fictional details. A good one to start with is the check that looks straightforward on your flowchart but usually ends in a phone call.

How to choose

Listen to how people describe the work

“First we do this, then we wait for that”

You are probably describing a process. Use BPMN-based modelling when the normal route and its exceptions can be made explicit.

Read the BPMN guide

“It depends on what we find”

You are probably describing a case. Use CMMN-based case management when evidence and judgement change the work that should happen next.

Read the CMMN guide

“These are the rules we apply”

You are probably describing a decision. Use a DMN-aware model when known inputs should produce an explicit result.

Read the DMN guide

Using all three

Connect the models at clear points

The models are easier to understand when each one has a limited job.

  1. 1

    Open the case

    Start the work as a case because the final route depends on what is discovered.

    CMMN-based case
  2. 2

    Collect evidence

    Add documents, facts and events to the case record.

    Case information
  3. 3

    Run a standard check

    Invoke a repeatable sequence for retrieval, validation and human review.

    BPMN-based process
  4. 4

    Apply the rule

    Use the known inputs to produce a routing or escalation result.

    DMN-aware decision
  5. 5

    Choose the next work

    Return to the case, where the result becomes part of the situation an authorised person considers.

    Human judgement

Where models go wrong

A bigger diagram is not always a better answer

Many modelling problems begin by asking one notation to carry everything.

A process becomes hard to maintain when dozens of gateways try to predict every professional judgement. A case becomes vague when repeatable checks are left as manual instructions. A decision becomes difficult to govern when the rule is buried inside routing lines or application code.

Keep each model small enough to explain. Connect them where a process task, case task or decision task has a clear input and result.

Too many gateways

The process is trying to imitate judgement that belongs in a case.

Too much manual work

The case is repeating steps that should be a published process.

Rules nobody can find

The decision is hidden in code, conditions or informal guidance.

How this works in Pūnaha

Separate models, connected execution

Published definitions

Processes, cases and reusable workflows have controlled versions, so running work remains tied to the definition it started with.

Process and decision tasks

A case can invoke repeatable work or defined decision logic and bring the result back into the case.

Durable state

Supported waits, events and case lifecycle state remain available beyond one browser session.

Execution history

The result can be viewed in the context of the process run or case in which it was used.

Explore workflows

Enterprise search evaluation

Use the same evidence-led approach when comparing enterprise search software, access and workflow control.

Compare enterprise search

Questions people ask about the three models

Can one solution use BPMN, CMMN and DMN?

Yes. A case can call a repeatable process and a decision. The important part is to give each model a clear responsibility.

Does CMMN replace BPMN?

No. CMMN-based cases suit evolving work. BPMN-based processes suit repeatable work. They are often most useful together.

Does DMN define the workflow?

No. DMN describes decision logic. BPMN describes process flow, and CMMN describes adaptive case work.

Does Pūnaha claim formal standards conformance?

No. Pūnaha provides supported standards-aware modelling and interchange, but this site makes no formal BPMN, CMMN or DMN conformance or certification claim.

Product documentation

Check the supported process and decision behaviour

Read the BPMN and DMN product guide for the supported modelling and decision options. Use the model-selection questions above to decide how those pieces fit the work.

Bring work that never fits the neat flowchart

We can separate the repeatable route, the changing case and the decision rules, then show how they work together.

Share this page

Send this resource to a colleague

Use your device’s sharing options or copy the permanent page address.

Share on LinkedIn
Pūnaha app icon

Install Pūnaha

Keep Pūnaha close at hand

Use your browser’s installation option to add Pūnaha to this device.

  1. Open your browser menu.
  2. Choose Install app or Add to Home Screen.