SwimlaneCross-team processComplex

Reimbursement approval swimlane

PlantUML swimlane covering a request for reimbursement that branches by amount, escalates to the department head, and returns to finance.

Reimbursement approval swimlane preview

What this diagram shows

Step 01
Branch by amount

Small claims stop at the direct manager; larger claims escalate up the chain.

Step 02
Rejection has its own path

If the department head rejects, the requester is notified and the flow ends — no silent dead-ends.

Step 03
Finance closes the loop

Approved claims always end at the finance lane disbursing payment, then back to the requester.

About swimlane diagrams

Swimlane diagrams split a process into vertical columns — one per team, system, or role — so handoffs between owners are visible at a glance. They are the natural fit for PRD user flows, approval chains, order fulfilment, and incident response runbooks where who-does-what matters as much as what-happens-next.

This template is written in PlantUML — plain text you can edit, version in git, and regenerate the image from any time.

View PlantUML sourcePlain-text diagram syntax — copy or edit directly.
diagram.mmd
1@startuml
2|#E6E6FA|Requester|
3start
4:Submit reimbursement;
5|#ADD8E6|Direct Manager|
6if (Amount < 50k?) then (yes)
7 :Manager approve;
8else (no)
9 :Forward upward;
10 |#FFFACD|Department Head|
11 :Head review;
12 if (Approved?) then (yes)
13 :Release;
14 else (no)
15 |Requester|
16 :Receive rejection;
17 stop
18 endif
19endif
20|#FFDAB9|Finance|
21:Disburse payment;
22|Requester|
23:Funds received;
24stop
25@enduml