Excel swimlane flowchart template with lanes and phases
A two-axis swimlane flowchart template: five phases across the top, four owner lanes down the side, worked through event delivery with a six-week venue cut-off and a four-week registration checkpoint.
What the excel swimlane flowchart template with lanes and phases process is
A swimlane flowchart answers who does a step. A two-axis swimlane also answers when. Lanes run one way for the owner, phases run the other way for the stage of work, and every box lands in a cell defined by both. That grid is what a table of process steps actually produces once it has an owner column and a phase column: two categorical fields, two axes, one position per row. Most swimlane templates give you the owner axis and nothing else, so the phase axis gets bolted on later as three labels dividing the page into thirds: beginning, middle, end. That version is decoration. A second axis is only worth its width when it carries something the reader cannot already get by reading the boxes in order.
Where it breaks is in the phase labels. Named after the work rather than the calendar (planning, execution, review) they repeat what the boxes already say, and the axis costs a third of the page for nothing. Meanwhile the dates that actually govern the process sit in prose underneath the diagram, or in one organiser's head, or in a project plan nobody opens. So the chart shows a tidy left-to-right flow and hides the fact that one column ends in a hard deadline and the next in a soft one. The test is simple. If you cannot say what changes when a step crosses from one phase into the next, the phase axis is labelling the page rather than describing the process, and lanes alone would read better.
The chart below is an event planning and delivery process, chosen because its phases have dates attached to them. Five phases run across the top (Brief, Budget, Promote, Deliver and Wrap-up) and four lanes down the side: Organiser, Marketing, Finance, and Venue and operations. Two of the phase boundaries are real deadlines. The venue contract has to be countersigned six weeks out, and registrations are counted against target four weeks out. Both are drawn as decisions with a route for the failing side, and the shape of the result is worth looking at on its own: every way this process ends badly is decided in the Budget column, and once the flow reaches Promote there is no exit but delivery.
What this flowchart covers
In this template
- Two axes on one chart: five phases across the top, from Brief through Budget, Promote and Deliver to Wrap-up, and four owner lanes down the side, including a single "Venue and operations" lane for the people who hold both the room and the day itself.
- A budget gate that is two decisions rather than one: "Budget approved by Finance?" hands a refusal across to "Reduced-scope option viable?" in the Organiser lane, which either loops back to rebuild the numbers or ends the process at "Event cancelled".
- A dated phase boundary instead of a decorative one, at "Venue contract signed by the six-week cut-off?" in the Venue and operations lane. An unsigned contract is what stops the Promote phase from starting, so the boundary is enforced by the chart rather than described beside it.
- A recovery route for a lost date: "Alternative venue free on the target date?" either sends the process backwards across the phase axis to shortlist venues again, or terminates at "Event postponed to a new date": the only two honest outcomes once a held date is gone.
- A counting loop that stays inside one column: "Registrations on target at the four-week checkpoint?" sends a shortfall to extra promotion and direct outreach, which returns to the same checkpoint for a recount at two weeks without disturbing any other phase.
- Deliver and Wrap-up as a straight line: confirm final numbers, catering and the running order, run the day, then follow up and collect feedback before the process closes in the Organiser lane at "Event delivered and reviewed".
When to use this template
- Your steps are already in a spreadsheet that records who does each one and which stage it belongs to, and neither of those two columns is currently doing anything except sorting the list.
- You have a swimlane diagram that shows who does what, and the argument you keep having is about when: which step was late, and whether it was late enough to matter.
- Two or three deadlines in your process are hard and the rest are soft, and nobody outside the core team can tell which is which from the documentation as it stands.
- You run the same process repeatedly (events, launches, campaigns, intakes) and want one map a new owner can follow without first being told the unwritten cut-offs.
- You used the Visio Data Visualizer add-in for Excel to turn a table with function and phase columns into this shape, and you are looking for where that shape lives now.
How it works
Decide what your phase axis measures
Rename Brief, Budget, Promote, Deliver and Wrap-up to your own stages, but keep the axis only if each boundary means something a reader cannot infer from the boxes. Here Budget ends at a countersigned contract and Promote ends at a confirmed head count. If your candidate phases amount to early, middle and late, delete the phase axis and keep the lanes.
Put your own figures into the two dated decisions
The template is set to a six-week venue cut-off and a four-week registration checkpoint. Replace both: the notice your venues genuinely need before a held date is released, and the point at which extra promotion can still change the head count. Keep the number in the decision label rather than in a comment, because the label is what people read off the diagram.
Split or merge the lanes to match who signs
Venue and operations is one lane because the same people hold the room and run the day. Split it if AV or catering is separately accountable, and merge Finance into Organiser if one person owns both the brief and the budget. The test for keeping a lane is whether anything in the chart waits on it: a lane nothing waits on is a strip of width carrying no information.
Decide which of the two bad endings you actually use
Both non-delivery terminators sit in the Budget phase: one cancels the event, the other postpones it to a new date. Name who has the authority to declare each, and delete the branch you never use. A process that offers both exits and names an owner for neither postpones by default, usually several weeks later than it should have.
Delete the rescope loop if you cannot rescope
"Reduced-scope option viable?" loops back to rebuild the budget from the venue and per-head quotes. That loop is honest only where a smaller version of the event is genuinely available. A fixed-format conference or a contractual sponsor commitment has no reduced scope, and leaving the branch in invites a negotiation round that cannot succeed.
Give every new row a phase before you give it a position
In Visio a phase is a Separator shape you drop onto the lanes, so the phase axis is a set of objects sitting over the diagram rather than a property of it. Here the phase is a field on the row, so adding a step means adding a row with a lane and a phase in it. Use that: decide the phase first, because a step whose phase you cannot name is usually two steps in different phases.
Frequently asked questions
What are the phases of an event planning and delivery process?
Five, and each one ends at something specific rather than at a date in a plan. Brief ends when the target date, the audience and the attendee target are agreed and venues have been asked for a written hold. Budget ends when finance has released the money and the venue contract is countersigned. Promote ends when registrations have been judged against target and final numbers can be confirmed. Deliver is the event itself. Wrap-up is the follow-up and the feedback that lets you say whether the event produced the outcome the brief asked for.
What is the difference between a swimlane and a phase in a cross-functional flowchart?
A lane is a party and it persists: every step inside it is owned by the same team, and the lane exists whether or not that team is busy right now. A phase is a stage of the work and it is sequential: everybody crosses it, in order, and a phase boundary marks a change in what is committed. So a lane answers who is holding this step, and a phase answers how far along the process is when they hold it. The two axes are independent, which is why one step can sit in Finance during Budget and another in Finance during Wrap-up.
Who owns an event planning process end to end?
The organiser owns the outcome and the calendar; nobody else has sight of every lane. Finance owns the approval gate and the release of money, marketing owns registrations and the campaign, and venue and operations own the room, the contract and the day itself. Each of those three can execute perfectly while the event still fails, because the failures are almost always at the boundaries: a hold that expired, a head count nobody confirmed. Give the organiser explicit authority to declare a postponement, or the decision gets made by the calendar instead.
How do I get both lanes and phases out of a spreadsheet?
Both axes come from two extra columns on the table of steps. The Data Visualizer templates in the Visio desktop app read a function column and a phase column from an Excel table and fill the swimlanes and the timeline from them; Microsoft documents those templates as available with Visio Plan 2, and a diagram connected to Excel that way cannot be edited in Visio for the web. QueryChart works from the same two fields without the round trip: the lane and the phase are values on the row, sitting beside the step's own label, so the grid above is generated from the table rather than assembled shape by shape — and editing the table is the only way to edit it.