What is a process event?
A process event is a process mapping shape, or element, used to show what starts or ends a process. Events help clarify not only when a process begins and finishes, but also why the process exists by identifying the trigger and the intended outcome.
In process mapping and process documentation, events are important because they define the boundary of the process. Many process problems come from unclear starts and ends—for example, when teams are unsure what triggers the work or what counts as a completed result. By defining events clearly, process maps become easier to understand, manage, and improve.
Events are often external to the process itself. A customer request, a scheduled date, an error, or a cancellation may trigger a process. In other cases, the start event is the output of a previous process in a larger end-to-end flow. Likewise, the end event shows the result that closes the process, such as a resolved complaint, delivered order, or approved request.
In many process mapping tools, events are shown as circles. A process map should typically include both a clear start event and a clear end event so teams can see the full scope of the process and avoid ambiguity.

For a broader overview of symbols, structure, and how events work together with activities, decisions, and swimlanes, read our guide to process mapping.
FAQ
An event is a tool used on a process map to establish what starts and ends a business process.
Its purpose is to show where the process originates from and why it exists.
Examples of events include a message, a timer, an error, or a compensation.