Presentations

Process slide templates

A process slide in this library is not a row of arrows drawn as text. Seventeen layouts carry it, and the required block on the purpose is a real flowchart, which is why a decision with two outcomes fits on one and a roadmap of quarters does not.

Create a presentation with OneCraftSeventeen process layouts, the flow block behind them, and when to use a timeline instead

Seventeen layouts, one required block

Seventeen templates carry the process purpose and one more lists it as a secondary role. What they share is the flowchart block, which is required by the vocabulary rather than optional: a process slide is expected to draw an actual flow with nodes and connectors. That is the difference between this and a slide of numbered boxes, and it is why a process slide can show a step that splits into two outcomes without you drawing anything by hand.

Branching is the point, not the exception

The purpose is described as branching flowcharts, decision gates and approval flows. Most slide libraries treat branching as the hard case and give you a row of chevrons; here it is the default case. If your process really is a straight line with no decisions, the same layouts still work through the flow steps list, where each step carries a label, a sublabel and its index.

What each step can carry

The slide title runs to forty characters and the optional description to a hundred and sixty. Steps in the flow steps list carry a label and a sublabel each. Some layouts add a centre badge, an icon with a title of twenty two characters and a caption of forty, for the thing the whole process revolves around, and a footer with a headline of forty eight characters and a caption of sixty four for the outcome. Grouped layouts hold up to four detail items under each stage.

Process against timeline

The test is whether the thing that orders your steps is a decision or a date. A process is ordered by what has to finish before the next thing starts. A timeline is ordered by the calendar, and eighteen separate layouts exist for it, with a period carrying a number, an icon, a label, a date and a body. Putting quarters into a process slide loses the dates; putting an approval flow into a timeline invents dates you do not have.

Pillars are not a process

Three or four things that are all true at once, in no particular order, belong on a pillars slide, and thirty three layouts carry that purpose. The giveaway is whether swapping two of your boxes changes the meaning. If it does not, they are pillars, and drawing arrows between them tells the reader something untrue about how the work happens.

How it works, in three steps

  1. Step 1

    Add the slide from the library

    From Library, filtered to the process purpose. Seventeen layouts come back, grouped by how much detail each stage carries.

  2. Step 2

    Lay out the flow

    Add the nodes and connect them. A decision node with two outgoing paths is the case these layouts are built for.

  3. Step 3

    Label each step in a few words

    A label and a sublabel per step. If a stage needs a paragraph, it is a section of its own rather than a node.

  4. Step 4

    Say what it produces

    Use the footer headline and caption for the outcome, so the slide ends on the result rather than the last box.

The full walkthrough with screenshots is in the guide Add, reorder and restructure slides.

Limits worth knowing

Questions people ask

Is there a separate flowchart slide type?

No, and this is the thing worth knowing before you go looking for one. The process purpose is the flowchart purpose: its own description names branching flowcharts, decision gates and approval flows, and the flow block is required rather than optional. Search the library for a flowchart role and you will find nothing, because these seventeen layouts are it.

What if my process is a straight line?

It still fits. The flow steps list holds a label, a sublabel and an index per step, so a five step linear process lays out as five nodes in a row with no decisions. You are using a branching capable slide for a simple case, which costs nothing.

When should I use a timeline instead?

When dates are what order the steps. A timeline period carries a date field alongside its label and body, and eighteen layouts are built around that. If somebody would ask when for each of your steps, and you can answer, it is a timeline. If the honest answer is after the previous one finishes, it is a process.

How many steps fit on one slide?

Enough that the labels stay readable from the back of a room, which in practice is about five or six nodes with a decision or two. A fifteen node flow is a document rather than a slide. Split it at a natural handover, or show the shape here and put the detail in an appendix.

Can I swap a process layout for a timeline layout?

Not directly. The layout picker filters by purpose, so a swap moves you between the seventeen process layouts, keeping your content. Moving to a timeline means a new slide, because the fields are different: a period has a date, a flow step does not.

Can the AI draw the flow for me?

The first generation fills the slide from your brief, flow included, so describing the approval path in the prompt gets you nodes and connectors rather than a blank block. After that the AI chat is text only, so it can reword a node's label but not add a step or move a connector; that is builder work.

Make your own presentation

The button opens the generator with this use case already described. Change the wording to match yours, generate, then edit anything you like.

Create a presentation with OneCraft

Related pages

More finished work of this kind is on the presentation examples hub.

Written and checked by the OneCraft team. Last checked .