Flowchart Templates: 4 Types, the Symbols You Need, and How to Build One With Your Team

A flowchart template is a pre-drawn set of standard shapes (start, step, decision, end) joined by arrows, laid out so you replace the placeholder text with your own process instead of drawing the structure from scratch. Four template types cover most work: a basic flowchart for a single path, a swimlane chart when several people or teams share the process, a decision flowchart for branching rules, and a data flow diagram for how information moves between systems.

This guide is written for an operations lead or team manager who needs to document a process, such as customer onboarding or an approval chain, and wants the whole team to agree on it before it is written into a handbook. It covers the four types, the symbols, a worked example, and a way to build the chart together on an online whiteboard instead of one person drawing it alone.

What is a flowchart and where does it come from?

A flowchart is a diagram that shows the steps of a process as shapes connected by arrows in the order they happen. The idea is older than software: Frank and Lillian Gilbreth presented their “flow process chart” to the American Society of Mechanical Engineers in 1921, as a way to record each operation, move, inspection and delay in a factory process. The symbols most people use today are standardised in ISO 5807, the international standard for documentation symbols and flowchart conventions.

The reason the form has lasted is that it forces a process to be explicit. A step that “everyone knows” has to be drawn as a box, and a rule that “depends” has to be drawn as a diamond with named exits. The first time a team draws its own process, the disagreements that surface are usually the most valuable output.

What evidence is there that mapping a process helps?

Most of the rigorous evidence comes from healthcare, where process mapping is a standard quality improvement tool. Marriott’s review for Dayton Children’s Hospital describes process maps as a key quality improvement tool for visualising the step-by-step flow, timing and handoffs of a process, and argues that mapping should be a foundational element of both process design and quality improvement.

A larger review looked at how well the technique is actually applied. Antonacci and colleagues at Imperial College London carried out a systematic review of process mapping in healthcare, proposing quality criteria for how a map is built, evaluated and reported, and then assessing published cases against them. Two lessons carry over to any team: the map is only as useful as the people who helped build it, and a map that nobody revisits stops matching the process.

The four flowchart template types

1. Basic flowchart template

A basic flowchart is a single path from start to end with occasional decisions. It is the right template when one person or one team owns the whole process and the aim is to write it down: an expense claim, a content publishing checklist, a weekly report.

Keep it to 15 steps or fewer. Beyond that the chart stops fitting on one screen, and the better move is to split it into a high-level chart and one detailed chart per stage.

2. Swimlane flowchart template

A swimlane flowchart divides the chart into horizontal or vertical lanes, one per person, role or team, so each step sits in the lane of whoever does it. The arrows crossing between lanes are the handoffs.

This is the template to choose when a process fails in the gaps between people. Handoffs are where requests wait, get lost or get done twice, and a swimlane makes every handoff a visible line. Marriott lists handoffs among the things a process map is meant to make visible, and a swimlane is the layout that shows them most directly.

3. Decision flowchart template

A decision flowchart is built around diamonds. Each diamond asks a yes/no (or multiple-choice) question and each exit leads to a different step. It suits support triage, eligibility rules, escalation policies and troubleshooting guides.

Write every diamond as a question that can only be answered one way at that moment (“Is the order a repeat order?”) and label every exit. An unlabelled exit is the most common error in decision charts, and it is the one that a reader cannot resolve without asking the author.

4. Data flow diagram template

A data flow diagram shows how information moves between people, systems and stores, rather than the order of tasks. It uses its own shapes: processes, data stores and external entities.

It suits a team documenting how a sign-up form reaches a CRM and then a billing system, or a school mapping how attendance data travels. If your question is “where does this information go?”, use a data flow diagram. If it is “what happens next?”, use one of the first three.

Which flowchart symbols do you actually need?

You need five symbols for nearly every flowchart, and learning them takes a few minutes. The table lists them with the plain meaning of each.

Symbol	Shape	Meaning	Example label
Terminator	Rounded rectangle or oval	Start or end of the process	”Request received”
Process	Rectangle	An action or step	”Check stock level”
Decision	Diamond	A question with two or more exits	”In stock?”
Input/output	Parallelogram	Data entering or leaving the process	”Customer enters address”
Connector/arrow	Line with arrowhead	Direction of flow	Labelled “Yes” or “No”

Two conventions keep charts readable. Flow runs left to right or top to bottom, never both on the same chart. And every shape holds a verb phrase for actions (“Approve invoice”) and a question for decisions (“Approved?”), which makes the chart readable aloud.

A worked example: customer onboarding as a swimlane flowchart

To show the template in use, take a seven-step onboarding process for a small software business with three lanes: Customer, Sales and Support.

Step	Lane	Shape	Text
1	Customer	Terminator	Signs up
2	Sales	Process	Confirm plan and contact details
3	Sales	Decision	Needs custom setup?
4a	Support	Process	Schedule setup call (if yes)
4b	Sales	Process	Send welcome pack (if no)
5	Support	Process	Run first-session walkthrough
6	Customer	Terminator	First task completed

The chart has one decision, three lanes and two handoffs from Sales to Support. Drawn this way, the question a manager asks is immediate: who owns the gap between step 3 and step 4a? If nobody does, that is the finding. This example is an illustration we constructed for this guide; it is not data from a real company.

The Three-Pass method for building a flowchart as a team

The Three-Pass method is a framework we use to get a team-agreed flowchart in one sitting instead of three meetings. It separates what happens from who does it from what goes wrong.

1. Pass one, the happy path. Everyone lists the steps for a case where nothing goes wrong, as plain sticky-note-sized boxes in order. No diamonds yet. Ten minutes is usually enough.
2. Pass two, owners and handoffs. Convert to a swimlane by moving each box into the lane of the person who does it. Any box that two people claim, or that nobody claims, is circled for discussion.
3. Pass three, exceptions. Now add the diamonds: for each step ask “what happens if this fails or is declined?” and draw the exit. Stop at the exceptions that happen often; a flowchart that tries to cover every rare case becomes unreadable.

The order matters. Teams that start with exceptions never finish the happy path, and teams that skip pass two produce charts that nobody can act on because no step has an owner.

How do you build a flowchart template online with others?

Open a flowchart or swimlane template, share the board, and run the three passes with everyone adding boxes at once while on a call. The live features page for HuddleIQ lists real-time collaboration, in which cursors move and changes appear instantly, plus built-in video conferencing, so the discussion and the chart sit in one place (checked on the live site on 25 October 2026). It also lists polls and voting, which settle questions such as “do we keep this step?” faster than debate.

Run the build in five steps, with everyone on the board and on the call together.

1. Pick the template type from the four above and put the process name and its start and end events in the first two shapes.
2. Run pass one in silence for five minutes with everyone adding steps, then read them aloud together.
3. Run pass two on the call, moving boxes into lanes as the team speaks.
4. Run pass three, adding diamonds and labelled exits, and use a vote to cut anything the team agrees is too rare to chart.
5. Present the finished chart from the board in the same meeting to confirm it, so the version everyone agreed to is the version that exists.

HuddleIQ’s features page describes 100+ templates across brainstorming, meetings, planning and education that can be customised, and teams can create their own. Once a team has a swimlane layout with its lanes named, saving it as a template means the next process map starts with the lanes in place. For a broader look at the diagram family this belongs to, see what diagramming is and how it helps and the diagramming page.

How do you keep a flowchart accurate after you build it?

A flowchart goes stale when the process changes and the chart does not. Three habits keep it honest. Put the date and an owner in a corner of the chart. Review it whenever a step is added or removed, rather than on a calendar schedule. And link it from wherever people actually look for the process, such as the onboarding handbook, instead of leaving it in a folder.

If a chart has not been touched in a year and the process has changed, redraw it with the three passes; it takes less time than correcting the old one, and the conversation is as useful as the result.

Common flowchart mistakes

The most common mistake is a diamond with one exit. If a decision has only one outcome, it is a step and should be a rectangle. The second is mixing levels of detail, with a box reading “Handle customer” next to a box reading “Click the blue Save button”. Choose a level and hold to it across the chart.

The third mistake is arrows that cross. Crossing arrows usually mean the layout has not been tidied or that the process contains a loop; move boxes until the crossings disappear, and if a loop is genuine, label it (“Repeat until approved”).

The fourth is drawing alone. A chart drawn by one person records that person’s view of the process, and the gaps surface later, when someone follows the chart and it does not match what they do. The shared build is what turns a flowchart from a document into an agreement.

Next step

Choose the type from the list at the top, and block 45 minutes with the people who actually do the work. Start with the happy path. If you want a brainstorming stage before the chart, begin with a mind map template to collect the steps, then convert them into a flowchart.