Cross-functional flowchart template (content review and publishing)
A cross-functional flowchart template built on a content review and publishing process: four lanes for author, editor, legal and compliance and web team, across five phases from the brief to a post-publication review.
What the cross-functional flowchart template (content review and publishing) process is
A cross-functional flowchart is an ordinary process map cut into lanes, one lane per owner, so that every step says both what happens and who is holding it. The lanes are not decoration and they are not free. They roughly double the space the diagram needs, and they force you to name an owner for the steps where ownership is genuinely disputed. The test for whether you need them is simple. Draw the process as a plain sequence first, then ask what has actually gone wrong on the last ten runs. If the steps themselves are what went wrong, keep the plain flowchart. If what went wrong is the handoffs, the lanes are the whole point of the diagram.
Content review and publishing is the process used here because its entire difficulty is the crossings. A claim about a competitor or a savings figure has to be cleared by somebody who does not write copy. A page is built and staged by the web team but signed off by an editor who cannot deploy it. A piece that comes back from legal needs the author again, not the reviewer who found the problem. The failures are reliably the same three: nobody knows a piece is waiting on them, the legal check is skipped because the author judged it unnecessary, and the pre-publish checks get run against the document instead of the staged page. Every one of those is a handoff.
The chart below runs from a brief to either a published page with a review date or a piece spiked and never published. It has four lanes, author, editor, legal and compliance and web team, across five phases, and the crossings are drawn rather than described. The revision step sits in the author's lane inside the review phase. Legal writes the required wording into a register and hands the piece back to the author rather than to the editor who raised it. The pre-publish decision belongs to the editor while the remedial work returns to the web team. Readers who reached this shape through Visio's Cross Functional Flowchart template will recognise the structure, edited here as rows rather than drawn.
What this flowchart covers
In this template
- Four lanes, Author, Editor, Legal and compliance, and Web team, across five phases: Draft, Review, Approval, Publish and After publishing.
- The editorial loop at "Editor approves the draft?", whose No branch goes to "Revise the draft against the editor's notes" and back into the sub-edit, with the revision step sitting in the author's lane while the piece stays in the review phase.
- A claims trigger owned by the editor rather than the author, at "Does the content make regulated or comparative claims?", which is what sends a piece across into the legal lane instead of leaving that call to whoever is on deadline.
- A three-way legal decision at "Legal clears the claims as written?": cleared goes on to sign-off, amendments required writes the wording into "Record the required wording in the claims register" and returns the piece to the author, and a claim that cannot be substantiated ends the process at "Content spiked and not published".
- A staging gate at "Page passes the pre-publish checks?" that lives in the editor's lane while the remedial work goes back to "Build the page and stage it for preview" in the web team's lane, so a failed check never lands on the author by default.
- Life after publishing: "Check indexing, redirects and page errors", then "Is the page meeting the content goal at the review date?", whose update branch re-enters the same revision step so amended claims are cleared again rather than slipped in.
When to use this template
- Pieces sit for days and nobody can say whether they are waiting on the editor, on legal or on a deployment slot.
- A claim about a competitor, a price or a performance figure reached a live page without anyone outside the content team reading it.
- The web team is being asked to fix copy problems at staging because the sign-off happened on a document rather than on the built page.
- Two people each believed the other had approved the piece, and it went out with a placeholder or a broken link.
- You are writing the editorial workflow down for the first time, and want one picture rather than four team checklists that disagree at the edges.
How it works
Decide whether the lanes are earning their place
Before you adapt anything, check that your failures live in the handoffs. If your problem is that drafts are weak, a lane diagram will not help and a plain sequence is easier to read. Give a lane only to a team that makes a decision or holds work while it waits, never one per person: lanes named after individuals stop describing the process the first time somebody changes job.
Rename the lanes to the functions you actually have
Replace Author, Editor, Legal and compliance and Web team with your own. If you have no in-house legal reviewer, do not delete the check along with the lane: move "Check each claim against its evidence" into the editor's lane and name the external counsel or compliance owner who signs it off. Merge the author and editor lanes only if one person genuinely does both, which is the point at which the chart stops being cross-functional.
Write the claims trigger list down
"Does the content make regulated or comparative claims?" is only as good as the list behind it. Record yours on the step: named competitors, pricing or savings figures, performance or safety claims, customer names and logos, medical, financial or legal advice, and any regulated term. Keep the decision in the editor's lane. Authors under a deadline route around a check they own themselves, which is the failure this crossing exists to prevent.
Set legal's turnaround and name one reviewer
The template assumes a stated turnaround, three working days being a common one, and a single named reviewer per piece. Put your real figure on the step. Keep the third branch at "Legal clears the claims as written?": a claim with no dated evidence behind it is not an amendment case, and collapsing it into the amendment branch is how unsupportable claims get reworded rather than dropped.
Make the pre-publish checks yours, and run them on the staged page
List your checks on the decision step: approved copy in place, title and meta description, headings and alt text, working links, mobile layout, consent behaviour on any embedded media. Two things matter more than the list. They run against the staged page rather than the document, and a failure returns to the web team, so leave that branch pointing at "Build the page and stage it for preview".
Set the review date at sign-off, not later
"Sign off the copy and set the publication date" is also where the review date belongs, typically 30 or 90 days out, judged against the goal named in the brief rather than against traffic alone. Leave the update branch feeding back into the revision step: an amended claim needs clearing again. If your team genuinely never revisits published pages, delete the last phase rather than leaving a step nobody performs.
Frequently asked questions
When do you need a cross-functional flowchart rather than a plain flowchart?
When the failures live in the handoffs. Draw the process as a plain sequence and look at what has actually gone wrong recently. If the steps are being done badly, lanes add width and tell you nothing new. If work stalls because nobody knows it has arrived, or gets done twice because two teams each assumed it was theirs, then the ownership is the information you are missing and lanes are the way to show it. The publishing process here qualifies on that test: a claim needing legal clearance and a page the web team stages but the editor signs off are both crossings, and both are where pieces are lost.
What are the stages of a content review and publishing process?
Five, and they map to the phases in this chart. Draft: write against a brief that names the audience, the goal, the destination URL and the target date, then attach sources, images and alt text. Review: sub-edit for accuracy and house style, then an editor decision with a revision loop. Approval: decide whether the piece makes regulated or comparative claims, clear those claims against their evidence, then sign off the copy and set the publication date. Publish: build and stage the page, run the pre-publish checks on it, publish and request indexing. After publishing: check indexing, redirects and errors, then judge the page against its goal on a set review date.
Who owns a content review and publishing process?
The editor owns the flow; nobody else is in a position to. The author owns the draft and the revisions, legal and compliance owns whether a claim can stand as written, and the web team owns the built page and the deployment. But the editor is the only role that appears in four of the five phases, which is why the claims trigger, the copy sign-off, the pre-publish decision and the post-publication review all sit in that lane. If your process keeps stalling, look first at whether that end-to-end owner exists at all, or whether each team is simply doing its own part and hoping.
How does this compare with a cross-functional flowchart in Visio?
Visio's desktop template is called Cross Functional Flowchart, and Microsoft's own hyphenation of the name varies across its documentation, so do not read a difference into it. Two things there surprise people. Phases are not a lane property but separate Separator shapes dropped onto the lanes, and deleting a swimlane deletes every shape inside it, with Microsoft's documented workaround being to move those shapes completely outside the diagram first. On the web, cross-functional flowcharts need Visio Plan 1 or Plan 2; they are not available in the bundled Visio in Microsoft 365 tier. Here the lane is a value on the step itself, so reassigning a step is an edit to that row.