How to create a cross-functional flowchart in Visio
Which Visio you need for a cross-functional flowchart, how to open the template on the desktop and in the browser, and the three web-only restrictions: fixed orientation, immovable separators, unrotatable labels.
In Visio for Windows a cross-functional flowchart is a template in the Flowchart category; it exists in Visio for the web too, but only for Visio Plan 1 and Plan 2 subscribers, and with three restrictions the desktop app does not have.
The short version
- Use lanes when the failures live in the handoffs; a single-team sequence is better off as a basic flowchart.
- Desktop: start Visio, click Flowchart in the Categories list, click the template, select Create. Visio Standard is enough.
- In Visio for the web the template needs Plan 1 or Plan 2: Microsoft states it is not available in Visio in Microsoft 365.
- Three web-only restrictions: orientation cannot be converted after you start, a Separator cannot be moved, and label text cannot be rotated.
- Lanes are functions; phases are separate "Separator" shapes, and deleting a lane deletes every shape inside it.
Lanes earn their keep when the failures live in the handoffs
A cross-functional flowchart is a flowchart divided into lanes, one per function, so that every step sits in the row belonging to whoever performs it. In the Visio desktop app it is a template: start Visio, click Flowchart in the Categories list, click the template and select Create. You get the same stencil the basic flowchart uses, with some swimlanes already placed on the page for you to start with, and the orientation is chosen at that moment: if prompted, select Horizontal or Vertical and click OK. Cross-functional flowcharts work in Visio for the web as well, but only on a paid Visio subscription, and the browser version carries three documented restrictions the desktop one does not.
Before any of that, decide whether you want lanes at all. They earn their keep when the failures live in the handoffs: work sitting in a queue between two teams, two people each assuming the other is checking something, nobody able to say who is allowed to refuse. Lanes make that argument visible in a way a plain flowchart cannot, because the arrow that crosses a lane boundary is the moment the process changes hands. If your process is one team doing eight things in order, lanes add a column of headings and nothing else, and a basic flowchart is the better diagram; /guides/how-to-create-a-flowchart-in-visio covers that route. The test is not how large the process is, it is whether the boundaries are where it goes wrong.
The tiering is what people discover too late. Desktop cross-functional flowcharts are a Standard-edition feature (Microsoft's Applies-To list runs from Visio Standard 2016 through 2024), so Professional is not required to draw one. Among the subscriptions, though, Plan 2 is the only tier that includes the desktop app at all; Plan 1 is web and Teams only. In the browser Microsoft's wording is flat: "In Visio for the web, cross-functional flowcharts are only available for Visio Plan 2 and Visio Plan 1 subscribers. They are not available in Visio in Microsoft 365." So the free lightweight web app bundled with Microsoft 365 commercial plans does not carry this template, and Microsoft 365 Personal and Family do not include Visio at all.
If you are going to work in the browser, three restrictions apply before you commit. Orientation cannot be converted once you have started (Microsoft's words are "Once you start, you can't automatically convert from one orientation to another"), so a vertical chart means deleting the default diagram and rebuilding it from the "Swimlane (vertical)" and "Separator (vertical)" shapes. A Separator, which is the shape that marks a phase change, cannot be moved at all on the web; it can only be deleted and re-added. And the lane label text cannot be rotated. Generating the chart from a table is a third route again, and a Visio Plan 2 desktop one: the "Cross-Functional Flowchart - Data Visualizer" template. The worked example below is this same shape of process (content review and publishing across four functions and five phases) built up in four stages, so you can watch where the lane crossings land.
A cross-functional flowchart built in four stages
Content review and publishing across four functions and five phases. Watch each stage add a lane crossing rather than a step.
One function, then the first handoff
"Draft the content against the agreed brief" and "Attach sources, images and alt text" both sit with the Author in the Draft phase, and nothing about them needs lanes. The chart starts earning them at "Sub-edit for accuracy and house style", which crosses into the Editor lane and the Review phase at the same time, and lands on the first decision, "Editor approves the draft?".
A loop that changes lane but not phase
The No branch goes to "Revise the draft against the editor's notes", which sits back in the Author lane while staying inside the Review phase: the clearest illustration that the two axes are independent, and the reason phases in Visio are Separator shapes rather than a second set of lanes. Row 6 then asks whether the content makes regulated or comparative claims, which decides whether a third function is involved at all.
The third lane, and a branch with three exits
Only the Yes branch enters Legal and compliance, where "Legal clears the claims as written?" has three labelled exits rather than two: cleared, amendments required, or cannot be substantiated. The amendments route records the required wording and hands back to the author, so the loop crosses two lane boundaries. Sign-off then returns to the Editor lane inside the Approval phase.
Publishing, and a review date that reopens the loop
The Web team lane takes over for staging, the pre-publish checks bounce failures back to the web team rather than to the author, and the last decision asks whether the page is meeting its goal at the review date. Needing an update sends the work all the way back to "Revise the draft against the editor's notes", which is what a real editorial process does. Two routes terminate: published and measured, or spiked.
How it works
Open the template on the platform you can actually finish on
Desktop: start Visio, click Flowchart in the Categories list, click the cross-functional flowchart template, then Create. Web: open the Gallery, scroll down to the Cross Functional Flowchart row and select Create, which needs a Visio Plan 1 or Plan 2 subscription. The web version opens with two functions and one phase already in place, and offers "Credit Approval Process" and "Event Planning Process" as starters if you would rather adapt something than start empty.
Choose the orientation before you draw a single shape
If Visio prompts for the swimlane orientation, select Horizontal or Vertical and click OK. On the desktop you can change your mind afterwards from the Cross-functional Flowchart tab on the ribbon. In Visio for the web you cannot: Microsoft says you cannot automatically convert from one orientation to another once you have started, and a vertical chart means deleting the default diagram and building it out of the "Swimlane (vertical)" and "Separator (vertical)" shapes instead.
Name the lanes after functions, not after people
The label bar on each lane reads "Function" by default; double-click the bar to change it. Name lanes for the role that owns the work (Editor, Legal and compliance, Web team), because a chart labelled with names goes stale the first time somebody changes job. Adding, reordering and deleting lanes has enough detail of its own that /guides/how-to-create-a-swimlane-diagram-in-visio covers it properly; the short version on the desktop is to right-click a lane header and choose Insert 'Swimlane' Before or After.
Mark the phases with Separator shapes
Phases are not lanes. They are "Separator" shapes from the Cross-Functional Flowchart Shapes stencil, dropped onto the swimlanes to mark a phase change, and they run across every lane at once. Use them for the stages a reader thinks in (draft, review, approval, publish) and keep the lanes for ownership. On the web, place them deliberately: a Separator cannot be moved once it is down, only deleted and re-added.
Drop the flowchart shapes into the owning lane and connect them
The cross-functional template uses the same stencil as the basic flowchart, so the shapes and the connecting behaviour are familiar: hold the pointer over the first shape and select the small arrow pointing towards the shape you want to connect to, or use the Connector tool from the Home tab, Tools group (Ctrl+3). Drop each shape into the lane whose function performs it, and check for the green highlight on the lane, which confirms the shape is genuinely contained rather than merely sitting on top.
Validate the diagram, then fix the page size before printing
On Visio Professional and Plan 2, Process tab > Diagram Validation > Check Diagram opens an Issues window; the flowchart templates default to the Flowchart Rule Set, and a Cross Functional Flowchart rule set is also available. Findings you disagree with are suppressed with Ignore This Issue or Ignore Rule. A chart that spills across printed pages is a page-size problem rather than a lane problem: Design > Page Setup dialog launcher > Print Setup tab, and under "Fit to" type 1 into both boxes.
Mistakes to avoid
Starting in the browser and then wanting vertical lanes
On the web, orientation is settled the moment the diagram opens. Changing your mind means deleting the default diagram and rebuilding with the "Swimlane (vertical)" and "Separator (vertical)" shapes, and re-placing every step. Decide the orientation first, or start on the desktop app, where the Cross-functional Flowchart ribbon tab can convert it.
Expecting the bundled Visio to have the template
Visio in Microsoft 365 (the free lightweight web app included with Microsoft 365 commercial plans) does not offer cross-functional flowcharts; Microsoft restricts them on the web to Plan 1 and Plan 2. Microsoft 365 Personal and Family include no Visio at all. Check which of the three you are signed in to before you plan the work.
Reaching the end of the draft with a lane you no longer want
Deleting it takes its contents with it (Microsoft's wording is that all the shapes contained in the swimlane are also deleted), so the tidying-up pass at the end of a build is the riskiest moment on this template. Move the shapes out before you delete anything, and read /guides/how-to-create-a-swimlane-diagram-in-visio before you start rearranging lanes at all, because the same is true of every operation that changes the lane set.
Assuming the Excel-driven route comes with your licence
Generating a cross-functional flowchart from a table means the "Cross-Functional Flowchart - Data Visualizer" template, and Microsoft documents the Data Visualizer templates as Visio Plan 2 only, in the desktop app. Data-connected diagrams also cannot be edited in Visio for the web, so that route is Windows desktop in practice. /guides/how-to-turn-excel-data-into-visio-flowchart covers the table it expects.
Open the content review as a live chart
Open the content review example as your own chart, rename the four lanes to your own functions, and edit the rows.
Related guides
Frequently asked questions
Can you create a cross-functional flowchart in Visio for the web?
Yes, on a paid subscription. Microsoft's wording is "In Visio for the web, cross-functional flowcharts are only available for Visio Plan 2 and Visio Plan 1 subscribers. They are not available in Visio in Microsoft 365." Open the Gallery, scroll to the Cross Functional Flowchart row and select Create; the diagram starts with two functions and one phase, and "Credit Approval Process" and "Event Planning Process" are offered as starters. Three limits apply that the desktop app does not have: orientation cannot be converted after you start, a Separator cannot be moved once placed, and the lane label text cannot be rotated.
Do I need Visio Professional or Plan 2 for a cross-functional flowchart?
Not to draw one. Microsoft lists the desktop cross-functional flowchart article as applying to Visio Standard 2016 through 2024, so it is a Standard-edition feature. Two things around it are tiered, though. Diagram validation with Check Diagram is documented for Visio Professional and Plan 2, and the "Cross-Functional Flowchart - Data Visualizer" template that builds the chart from an Excel table is Plan 2 only. Among subscriptions, Plan 2 is also the only one that includes the desktop app: list prices at the time of writing are US$5.00 per user per month for Plan 1 and US$15.00 for Plan 2, paid yearly.
Is it a "cross-functional flowchart" or a "cross functional flowchart" in Visio?
Both, which is why searching for it is confusing. Microsoft's own spelling is inconsistent across its documentation: the desktop how-to calls the template "Cross Functional Flowchart" with no hyphen, the ribbon tab is "Cross-functional Flowchart", the stencil is "Cross-Functional Flowchart Shapes", and the Gallery article writes "Cross-functional flowchart". Try it both ways rather than assuming one spelling is canonical. Related point: there is no documented "legacy" versus "modern" cross-functional flowchart in Visio. The API models exactly two orientations, horizontal and vertical, and nothing else, so ignore any guide that claims a variant switch.
How do I keep a cross-functional flowchart accurate once the process changes?
That is the part no template solves, and it is where the handoffs bite: a lane boundary moves and the diagram nobody owns quietly stops matching the work. Visio gives you one real tool for it, and it is a good one: on Professional or Plan 2, Check Diagram will tell you the chart is now structurally wrong, which most alternatives cannot do at all. Visio files stored in OneDrive or SharePoint use file version history; retention depends on the account and library settings. Check those settings and any separate approval workflow before relying on them for controlled documents. QueryChart takes the other approach: the chart is a table of rows with lane columns, so reassigning a step is editing a cell, and revisions are checkpointed with an author and a timestamp behind a native approval workflow. The example above is that same chart.
