{"id":541,"date":"2026-02-25T10:19:54","date_gmt":"2026-02-25T10:19:54","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/cmmn-vs-bpmn-when-to-use-which\/understanding-cmmn\/cmmn-basics-case-plan-structure\/"},"modified":"2026-02-25T10:19:54","modified_gmt":"2026-02-25T10:19:54","slug":"cmmn-basics-case-plan-structure","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/cmmn-vs-bpmn-when-to-use-which\/understanding-cmmn\/cmmn-basics-case-plan-structure\/","title":{"rendered":"CMMN Fundamentals and Case Plan Structure"},"content":{"rendered":"

Imagine a healthcare provider assessing a patient\u2019s condition. The diagnosis isn\u2019t a fixed path\u2014more like a dynamic investigation where each decision opens new options. That\u2019s where CMMN shines: not as a rigid flow, but as a flexible case plan. Most people think of modeling as following a set sequence, but real-world work often unfolds unpredictably.<\/p>\n

My 20 years in process architecture taught me that many fail not from misunderstanding CMMN, but from treating it like BPMN. The key is not structure, but adaptability. CMMN isn\u2019t about controlling every step\u2014it\u2019s about empowering knowledge workers to make decisions based on context.<\/p>\n

This chapter breaks down how CMMN case plans are built using stages, tasks, milestones, and case files. You\u2019ll learn how these elements work together to support adaptive, real-life scenarios without over-engineering. By the end, you\u2019ll know how to design a CMMN case plan that reflects reality, not rules.<\/p>\n

Core Components of a CMMN Case Plan<\/h2>\n

At the heart of every CMMN model is the case plan. It\u2019s not a flowchart but a living blueprint for how a case evolves. Think of it as a battlefield command center\u2014where conditions change, and decisions adapt in real time.<\/p>\n

1. Stages: Organizing the Case Lifecycle<\/h3>\n

Stages represent major phases in a case, like \u201cInitial Assessment,\u201d \u201cInvestigation,\u201d or \u201cResolution.\u201d They\u2019re not tasks\u2014they\u2019re containers that group related work.<\/p>\n

They help structure the big picture. A case might have a stage for \u201cClinical Review\u201d and another for \u201cTreatment Planning.\u201d In practice, these aren\u2019t fixed. A stage can remain open until all required tasks are met.<\/p>\n

Key advantage: Stages allow you to control visibility and sequencing without hardcoding every path. You can activate a stage only when criteria are met, and deactivate it if conditions change.<\/p>\n

2. Tasks: Actionable Work Items<\/h3>\n

Tasks are the actual work to be done. They can be manual, automated, or delegated. Unlike BPMN, CMMN doesn\u2019t force a strict sequence\u2014tasks can be completed in any order.<\/p>\n

For example, in a claim investigation, tasks like \u201cVerify policy coverage,\u201d \u201cReview medical records,\u201d and \u201cInterview claimant\u201d can be executed in any order. The case moves forward when all tasks in a stage are completed\u2014or when a sentry triggers progress.<\/p>\n

Tasks can have entry and exit criteria. These aren\u2019t just validation rules\u2014they\u2019re signals that let the case \u201cknow\u201d when it\u2019s safe to proceed.<\/p>\n

3. Milestones: Tracking Progress and Triggers<\/h3>\n

Milestones are not events\u2014they\u2019re markers of completion. They help measure progress and trigger conditional logic.<\/p>\n

For example, a milestone like \u201cAll evidence collected\u201d can be used to activate a new stage or trigger an automated alert. When the milestone is reached, the case can move forward even if not all tasks are finished.<\/p>\n

Unlike BPMN, where milestones are rarely used, CMMN relies on them to manage uncertainty. They act as checkpoints without dictating sequence, making them ideal for knowledge work.<\/p>\n

4. Case Files: Central Repository for Information<\/h3>\n

Case files hold all data relevant to a case\u2014documents, notes, metadata, and references. They\u2019re not just storage; they\u2019re the foundation of decision-making.<\/p>\n

Each task may create or update a file. For example, a \u201cMedical Review\u201d task might add a report to the case file. That report then becomes input for other tasks.<\/p>\n

Case files support dynamic data access. Unlike BPMN, which often assumes fixed inputs, CMMN lets the case evolve as new data emerges.<\/p>\n

How Stages and Milestones Enable Adaptive Planning<\/h2>\n

The real power of CMMN lies in how stages and milestones interact. They\u2019re not just labels\u2014they\u2019re dynamic tools that enable adaptive case management.<\/p>\n

Consider a customer dispute. You can\u2019t predict whether the resolution will take one call or three. But with CMMN, you can define a stage \u201cCustomer Contact\u201d with exit criteria: \u201cCustomer agrees to review evidence.\u201d That condition can be met at any time\u2014by email, chat, or call.<\/p>\n

Here\u2019s how it works:<\/p>\n