Event-driven Process Chain (EPC): Map Events and Functions in Order
A simple way to draw a process as a chain of events and the tasks they trigger.
In short
An Event-driven Process Chain (EPC) is a simple way to draw a process as a chain of events and the tasks they trigger, joined by AND, OR and XOR connectors.
4 min readFree
What You Will Learn
This lesson shows you how to read and draw an Event-driven Process Chain, called an EPC. An EPC is a picture of a process. It shows what starts the work, which tasks follow, and what state the process ends in. You will learn the building blocks, the connector symbols, a few drawing rules, and a short Python check.
Key words
- Process
- A set of steps that turns a start into a result, such as taking a customer order.
- Event
- A state or moment, such as 'Order received'. An event does not do work by itself.
- Function
- An active task that changes something from one state to another, such as 'Check stock'.
- Connector
- A logic symbol, labelled AND, OR, or XOR, that decides how a flow splits or joins.
- Control flow
- The arrows that show the order in which events and functions happen.
- Modeling language
- A set of symbols and rules for drawing a system or process the same way each time.
What is an EPC?
The event-driven process chain, or EPC, is a graphical modeling language. It was built in 1992 at Saarland University as part of a research project with SAP. Many companies now use it to map, study, and improve their workflows.
The core pattern repeats. An event starts a function. The function finishes and leads to a new event. A complete EPC begins and ends with events. Its supporters say the notation is simple to read, and that is one reason it spread.
What are the three building blocks?
Event
An event describes a state, such as 'Stock checked'. In diagrams, events are drawn as hexagons.
Function
A function is an action, such as 'Ship order'. In diagrams, functions are drawn as rounded rectangles.
Connector
A connector shows where the flow chooses a path, runs paths together, or brings them back into one line.
Arrows called control flow link these pieces in chronological order, and they are drawn as dashed arrows.
What are the connectors AND, OR and XOR?
XOR means exactly one path is chosen. For example, the stock is either on hand or it is not. AND means all paths run at the same time. OR means one or more paths run. Every split must be joined again by a connector of the same kind that opened it.
How do you draw one?
- 1
Start with a trigger
Begin the chain with an event, because an EPC must start with an event.
- 2
Add the first task
Attach a function that does the work. Name it as an action.
- 3
Record the result
Add the event that states what is true after the function ends.
- 4
Add connectors
Use AND, OR, or XOR wherever the flow splits, chooses, or merges.
- 5
End on an event
Finish the chain with an event that shows the final state.
Which drawing rules should you check?
Events and functions take turns, so a function links to events rather than to another function. Only functions make decisions, so an event should not sit directly before a choice. Some modelers warn that these rules create long diagrams full of small events, so they suggest leaving out trivial ones.
Tip
Name events as states, like 'Requirement captured'. Name functions as actions, like 'Place order'. Mixed names make a chain hard to read.
A Small Python Check
This program stores a chain as a list. It checks that events and functions alternate. It uses only the standard library, so it prints the same result every time.
chain = [
"event: Order received",
"function: Check stock",
"event: Stock checked",
"function: Ship order",
"event: Order shipped",
]
for number, item in enumerate(chain, start=1):
kind = item.split(":")[0]
expected = "event" if number % 2 == 1 else "function"
status = "OK" if kind == expected else "WRONG"
print(number, kind, status)
Output
1 event OK 2 function OK 3 event OK 4 function OK 5 event OK
Using EPC as a Designer
EPC was made for business processes, such as handling an order inside a company. Screens are different, but the habit still helps. Before you draw a user flow, name the event that starts it, the tasks the user performs, and the state the user reaches. Creately says EPCs can help teams examine dependencies, responsibilities, information needs and handoffs.
Check Yourself
Quick check
Which shape does an EPC use for an event?
Sources
- Event-driven process chain, Wikipedia
- Event-Driven Process Chain (EPC), ARIS Community
- Create an Event-driven Process Chain (EPC) diagram, Microsoft Support
- Create Event-Driven Process Chains, M-Files Process Maps
- Rules of EPC Modelling, Paschinger
- EPC Diagram: Definition, Symbols, Free Templates, and Applications, Creately
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.