What is a process flowchart?

What a process flowchart shows

Every process flowchart answers four questions: where the process starts, what happens at each step, where decisions split the flow, and where the process ends. The shapes carry the meaning: a rounded terminator marks the start and end, rectangles hold the actions, and diamonds hold the questions whose answers send the flow down different paths.

That's the whole grammar. Because the symbol set is small and standardized, a process flowchart made by one team reads correctly to another team, another department, or an auditor three years later, without a legend and without explanation.

The core flowchart symbols

Process flowcharts use a handful of standard symbols. You can build a complete, correct chart with just these four:

• Terminator (rounded rectangle or oval): the start and end points. Every flowchart has exactly one start; it may have several ends.
• Process (rectangle): a single action or task: "Review invoice", "Pack order", "Send confirmation".
• Decision (diamond): a question with two or more outcomes: "Approved?", "In stock?". Each outgoing arrow is labeled with an answer.
• Flow line (arrow): the connector that carries the sequence from one shape to the next.

When to use a process flowchart

Reach for a process flowchart whenever a sequence of steps needs to be understood by more than one person. The classic triggers: onboarding someone into a role, agreeing on how a cross-team workflow actually runs, finding the bottleneck in a slow process, or writing down a process before you change it.

Flowcharts beat written instructions for anything with branching. A checklist handles a straight line of steps; the moment the process contains "if yes, do this, if no, do that", prose becomes ambiguous and a diamond becomes the clearer tool.

Process flowchart vs. other diagrams

A process flowchart is one member of a family. A workflow flowchart is a process flowchart focused on recurring operational work moving between people and systems. A cross-functional flowchart adds lanes (one per role or department) so the chart also shows who performs each step and where handoffs happen. A process map is a flowchart scoped to a business process with owners and boundaries made explicit; our sister site ProcessMapping.app covers that spreadsheet-driven swimlane format in depth.

If you're choosing: start with a plain process flowchart. Add lanes when more than one role touches the process. You rarely need anything heavier.

• Process map vs. flowchart: when you need which (ProcessMapping.app)
• Swimlane process maps from a spreadsheet (ProcessMapping.app)

How to create a process flowchart without drawing

The traditional way to make a flowchart is a drawing canvas: drag shapes, connect them by hand, and nudge everything straight. It works, but layout maintenance eats most of the time: every inserted step means re-routing arrows and re-aligning boxes.

ProcessFlowchart.app takes the other approach: you type your steps one per row, mark the shape and what each step connects to, and the flowchart draws and lays itself out automatically. Inserting a step is one new row: the layout rebuilds itself.

For a step-by-step walkthrough with a worked example, QueryChart's guide builds a complete process flowchart from scratch, and its template library has a basic process flowchart to start from.

• How to create a process flowchart, step by step (QueryChart guide)
• Basic process flowchart template (QueryChart)

Frequently asked questions