BPMN basics

BPMN is a standard way to draw a business process: who does what, in which order, and what happens when things go wrong. You only need a handful of elements to read and draw most processes. Each one below comes with the Flowmark that draws it.

Events: where it starts, waits and endsCopy Anchor Link

An event is something that happens. It's drawn as a circle.

• A start event shows what starts the process. Every process has at least one.
• An end event shows how it finishes. Give each outcome its own end event.
• An intermediate event waits for something on the way, such as a day passing or a message arriving.

process Parcel delivery

start Parcel ordered
catch:timer(P1D) Next day reached
manual Deliver parcel
end Parcel delivered

Name events as a state: "Parcel ordered", "Invoice paid". Events can have a type, such as message or timer. See Events.

Tasks: the workCopy Anchor Link

A task is one piece of work, drawn as a rounded box. Name it as a verb and an object, such as "Approve invoice". The type says how the work is done: by a person in a system, by the system on its own, by hand, or by sending or receiving a message.

process Expense claim

start Expense incurred
user Submit expense claim
service Check spending limit
manual File paper receipt
end Claim submitted

See Steps for every task type.

Sequence flows: the orderCopy Anchor Link

A sequence flow is an arrow from one element to the next. It shows the order the work happens in. In Flowmark, lines that follow each other connect on their own, and -> lines draw arrows to anywhere else.

process Support request

start Request received
user Answer request
xor Customer happy?
  yes -> Request closed
  no -> Hand to specialist

end Request closed

user Hand to specialist
end Request escalated

Arrows out of a decision carry labels, such as "yes" and "no". See Flows and labels.

Gateways: decisions and parallel pathsCopy Anchor Link

A gateway splits the flow into branches, or merges branches back together. It's drawn as a diamond.

• An exclusive gateway (XOR) takes one path: a decision.
• A parallel gateway (AND) takes every path at once, and a second one waits for all of them.

process Office move

start Move approved
and #split
  -> Pack equipment
  -> Book movers

manual Pack equipment
and #done
end Move ready

user Book movers
  -> #done

See Gateways for all four kinds.

Lanes: who does itCopy Anchor Link

A lane is a horizontal band for one role or department. Each step sits in the lane of whoever does it, so the diagram shows hand-overs at a glance.

process Leave request
lanes Employee | Manager

lane Employee
start Leave needed
user Request leave
lane Manager
user Approve leave
end Leave approved

See Process and lanes.

Pools and messages: outside partiesCopy Anchor Link

The whole process sits in one pool. A party outside your organization, such as a customer or a supplier, gets a pool of its own. Messages, drawn as dashed lines, show what passes between you.

process Quote request
pool Customer

start:message Request received
  <= Customer: Quote request
user Prepare quote
send Send quote
  => Customer: Quote
end Quote sent

See Pools and messages.

Boundary events: when something interruptsCopy Anchor Link

A boundary event sits on the edge of a task. It catches something that happens while the task runs, such as a deadline passing or an error, and leads to what happens next.

process Contract signature

start Contract sent
receive Receive signed contract
  on:timer(P7D) No reply in a week -> Call customer
end Contract signed

user Call customer
end Customer called

See Boundary events.

NextCopy Anchor Link

Try the Quickstart to draw your first diagram, or see the common patterns these elements make up.