BPMN Message Events: Internal vs External Communication

Misusing BPMN message events for internal communication is one of the most common process modeling mistakes. It clutters the workflow diagram and breaks with BPMN's core design principle: message events are for communication between pools , not within them. The Common Confusion: Can I Use Message Events Within a Pool? The short answer: no. Message events are strictly for communication between different participants (different pools), not for coordination within a single pool. This separation is central to BPMN diagrams. A participant (shown as a pool) represents an independent entity — like a company, vendor, or external system. Communication across pools uses formal messages to mirror the real world: contracts, APIs, service calls, or emails. Inside a single participant, activities are under common control. Coordination here is direct — no need for formal messages. That's why BPMN reserves message events for cross-pool interactions only. Why BPMN Enforces This Separation By keeping a