CI/CD pipeline flowchart template

A pipeline works best as a decision flow, because the interesting part is what stops a commit rather than the sequence of jobs that runs it. We recommend following this process:

1. List every outcome a commit can reach: production, blocked merge, rollback.
2. Write down the gates that separate them, and mark which are automated and which need a person.
3. Turn each gate into a decision node with both exits drawn, including the failure paths.
4. Check that every path terminates. A pipeline diagram with a dangling branch is where a failed deploy goes unnoticed.
5. Draw it in the tool your audience already uses. A free template removes most of the layout work.

Continuous delivery means every passing build is ready to release, but a person decides when. Continuous deployment means every passing build goes to production automatically, with no human in the path.

The approval gate on this diagram is the entire difference. Remove it, and the same pipeline becomes continuous deployment. That is worth being deliberate about: teams often say deployment and run delivery, then discover the gap during an audit.

Continuous integration is everything up to the test gate, merging code frequently and proving it builds and passes automatically. Continuous delivery or deployment is everything after — getting that verified build into staging and then production.

On this diagram, CI ends at the tests-pass decision, and CD begins at deploy to staging. The split is not academic: they usually fail for different reasons and are often owned by different people.

Each one stops a commit for a different reason:

• Tests pass: automated, objective, and fast. A no notifies the author and blocks the merge.
• Approval gate: human, judgement-based, and slower. A no rolls back and halts rather than retrying.

Add a further gate for security scanning, performance budgets, or a change-advisory review; the branches stay attached as the diagram reflows.

Build and run tests uses the predefined process shape rather than a plain rectangle. In flowchart notation, that marks a step defined in detail somewhere else — in this case, the job configuration in your CI system.

It is a useful signal on a slide. It tells a reader that the box is a summary of a pipeline they can go and read, rather than a single action, without cluttering the diagram with every test stage.

The commit exits to notify and block the merge. Both halves matter: notifying without blocking means the failure is ignored, and blocking without notifying means the author finds out from someone else.

Drawing it as a terminal outcome rather than a loop back is deliberate. A failed build is not retried by the pipeline; it is returned to the person who wrote the code, which keeps the fix with the person who has the context.

It depends on what you are protecting against. A manual gate catches things automation cannot judge — a risky release before a holiday weekend, a change that needs a customer notified first, a compliance requirement for separation of duties. It also costs you speed and becomes a rubber stamp if nobody ever says no.

A reasonable test: if your approver has rejected nothing in six months, the gate is theatre and you should either automate it or add the criteria that would make a rejection possible.

Every gate should have a named owner, and they are rarely the same team:

• Developers: the commit and fixing anything the test gate blocks.
• Platform or DevOps: the build configuration, staging environment, and rollback mechanism.
• Release manager or tech lead: the approval decision itself.
• Security or compliance: the criteria the gate is checking against, where one applies.

If the same person writes the code and approves the release, the gate is not providing the separation it appears to.

PowerPoint can do it with SmartArt and the Shapes gallery, but the work is manual: you place each diamond yourself, label both exits, and reattach connectors every time something moves. For a pipeline with two gates and three terminal outcomes, this becomes the reason the diagram stops getting updated.

A faster route is the Lucen Flowchart tab, which snaps connectors to shape anchors and reflows the diagram with Auto Layout when you add a gate. Either way, the result stays a set of native PowerPoint objects on your slide.

The download is a free .pptx made of native PowerPoint shapes, so anyone can open, read, and edit it, and you can share it as you would any deck; recipients need nothing installed.

The smart connectors, Auto Layout, and Lucen AI come from the Lucen Flowchart add-in, which adds a Lucen Flowchart tab to the ribbon and runs on Windows with PowerPoint 2016 or later and with PowerPoint for Microsoft 365. PowerPoint for the web, Mac, and mobile are not supported. Setup and troubleshooting steps are in Lucen Support.