On This Page
> resources > docs > BPMN building blocks > End Event

End Event

What an End Event Is

A BPMN 2.0 End Event marks the conclusion or termination of a business process. It signifies the point at which the process is complete, and no further actions occur after the end event. In BPMN diagrams, the End Event is shown as a bolded circle and can signal different types of process endings, such as normal completion or an error condition. You can add end events to your own diagram — start a free trial to model the outcomes of a process you know.

Model every way your process can end

Describe how your process can finish and the AI models each outcome as its own end event.

Try an example

Before you click

You create a free ProcessMind account first, no credit card needed. Your description is saved and the model is generated automatically right after, so it opens ready to edit or export.

  1. 1 Create a free account
  2. 2 Your description becomes a BPMN model
  3. 3 Edit, auto-layout and export it

Free account · No credit card · BPMN 2.0 export

See how the AI BPMN generator works

Key Points about End Events

  • Visual Representation: A thick-bordered circle.
  • Types of End Events:
    • Message End Event: Sends a message when the process finishes.
    • Signal End Event: Broadcasts a signal to other processes or systems when the process ends.
    • Error End Event: Indicates that the process has ended due to an error.
    • Terminate End Event: Immediately stops all activities in the process, terminating the entire process instance.
    • Escalation End Event: Indicates an escalation has occurred, which requires handling at a higher level.

End Events have no outgoing sequence flows, as they represent the final point of the process. They play a critical role in signaling the result of the process and ensuring the flow is properly completed.

An end event marks the end of a process. The process is complete once all the steps outlined in the diagram are executed, culminating at the end event. Since a process may have different results, such as success or failure, you can use multiple end events to indicate various outcomes. For example, if an order is successfully processed, the process ends with a successful completion. If the card details are incorrect, resulting in a transaction failure, no receipt is generated, and the order is considered unsuccessful.

ProcessMind BPMN 2.0 end event symbol showing process completion and outcome

In this example, the final outcomes differ, even though both are categorized as end events. When a process includes multiple end events, each must be distinctly named to avoid confusion.

All Events with Their Corresponding Symbols

Start Intermediate End
Type
Normal
Event Sub process
Event Sub process non-interrupt
Catch
Boundary
Boundary non-interrupt
Throw
None
Message
Timer
Conditional
Link
Signal
Error
Escalation
Termination
Compensation
Cancel
Multiple
Multiple Parallel

Generate a Custom BPMN Model

Model every way your process can end

Describe how your process can finish and the AI models each outcome as its own end event.

Try an example

Before you click

You create a free ProcessMind account first, no credit card needed. Your description is saved and the model is generated automatically right after, so it opens ready to edit or export.

  1. 1 Create a free account
  2. 2 Your description becomes a BPMN model
  3. 3 Edit, auto-layout and export it

Free account · No credit card · BPMN 2.0 export

See how the AI BPMN generator works

Related Documentation

Design better processes. Build a connected architecture. Stay in control.

Get instant access with no credit card and no waiting. Turn the way your organization works into clear, connected process designs.

Build your process architecture, define ownership and controls, and align roles and responsibilities across every level.

Start your free trial and create one reliable foundation for governing, managing, and continuously improving your processes.

Get Your Free Trial Today