A flowchart turns a process you can only describe in paragraphs into a picture anyone can follow at a glance. Whether you are documenting how a support ticket gets resolved, mapping the logic of a small program, or explaining a sign-up flow to a teammate, a flowchart makes the sequence — and every decision along the way — impossible to misread. The good news is that you do not need specialized software to build one. This tutorial walks through making a flowchart from scratch on a free online whiteboard, from understanding the standard symbols to exporting a clean, shareable file.
What a Flowchart Is
A flowchart is a diagram that shows the steps of a process in the order they happen, connected by arrows that trace the path from start to finish. Each step is drawn as a shape, and the shape you choose carries meaning: a reader who knows the conventions can tell an action from a decision without reading a single word. That shared visual language is what makes flowcharts so useful across teams — an engineer, a manager, and a new hire can all look at the same chart and understand the same thing.
The purpose is clarity, not decoration. A flowchart should answer three questions instantly: where does the process begin, what happens at each step, and what changes when a decision goes one way versus another. Everything in this guide serves those three questions.
The Standard Flowchart Symbols
Flowcharts use a small, well-established set of shapes. You only need five to build the vast majority of charts, and learning them takes a minute:
- Terminator (oval or rounded "stadium" shape) — marks the start and the end of the process. Every flowchart begins with one terminator labeled something like "Start" and ends with one or more labeled "End". Think of them as the bookends of the whole diagram.
- Process (rectangle) — a single action or step: "Send confirmation email", "Calculate total", "Package the order". If something happens in your process, it is a rectangle. Most of the boxes in a typical chart are processes.
- Decision (diamond) — a point where the path splits based on a yes/no or either/or question: "Payment approved?", "Stock available?". A diamond always has one arrow coming in and two (or more) going out, each labeled with the answer that leads down it.
- Input/Output (parallelogram) — data entering or leaving the process: "Enter email address", "Print receipt", "Display results". Use it when the step is about information moving in or out rather than an internal action.
- Arrows (flow lines) — the connectors that show direction. Arrows are the backbone of the chart; they tell the reader which step follows which, and they are what make a flowchart flow rather than sit as a loose pile of boxes.
There are more specialized symbols — cylinders for databases, documents with a wavy bottom edge, connectors for jumping across pages — but you can build clear, professional flowcharts with just the five above. Resist the urge to over-symbolize; a chart that mixes in exotic shapes only slows readers down.
Plan Your Steps Before You Draw
The single biggest mistake people make is opening a canvas and immediately placing shapes. A flowchart is only as clear as the thinking behind it, so spend a few minutes planning before you draw a single box. This is easier than it sounds and saves a lot of rearranging later.
Start by writing the process out as a plain list, in order, one step per line. Don't worry about shapes yet — just capture the sequence: "customer submits form, system checks the email, if the email is invalid ask again, otherwise create the account, send a welcome message, done." Once the list exists, go back through it and mark each line with its shape: the first and last are terminators, the plain actions are rectangles, and any line containing "if", "check", or a question is a decision diamond. You now have the entire skeleton of the chart on paper, and drawing it becomes a matter of translation rather than invention.
While you plan, watch for two things. First, make sure every decision has a clear answer for each branch — a diamond that says "Valid?" needs to define what happens for both "Yes" and "No", with no dangling path. Second, confirm the process actually ends; a flow that loops forever with no exit is almost always a sign of a missing decision or terminator.
Building the Flowchart, Step by Step
With your planned list in hand, open the online whiteboard and build the chart. Here is the sequence that keeps things tidy:
- Place the start terminator. Drop an oval (or rounded rectangle) near the top of the canvas and label it "Start". Working top-to-bottom matches how most people read a flowchart, so give yourself plenty of vertical room below it.
- Add each step as a shape. Going down your list, place a rectangle for every action and a parallelogram for every input or output. Leave generous space between shapes — you will need room for arrows and labels, and a crowded chart is far harder to fix than a roomy one.
- Label every shape with text. Type a short, verb-first phrase inside each box: "Validate email", "Create account", "Send welcome message". Keep labels to a few words; the shape carries the category, so the text only needs to say what specifically happens.
- Insert decision diamonds where the path splits. At each decision point, place a diamond and phrase its label as a question ending in a question mark: "Email valid?". A question makes the two exits obvious.
- Connect the shapes with arrows. Draw an arrow from each shape to the next. Attach the arrow's ends to the shapes themselves rather than to empty canvas, so the connection is bound: when you later drag a box to a new position, its arrows follow and stay attached instead of leaving a broken, dangling line. This is the biggest advantage of building a flowchart on a real editor rather than sketching it by hand.
- Label the branches leaving each diamond. Add a small text label — "Yes" / "No", or "Approved" / "Declined" — next to each arrow coming out of a decision, so no reader has to guess which branch means what.
- Align and snap for tidiness. Nudge shapes so they line up on a shared vertical spine, keep the spacing between steps even, and straighten the arrows. Many editors snap shapes to a grid or to each other as you drag, which does most of this work for you. A chart where boxes are aligned and arrows run straight looks intentional and is markedly easier to follow.
- Use color to distinguish branches. Give the "happy path" one color and error or exception branches another, or tint all decision diamonds a single accent color. Color is a fast, pre-verbal cue that helps a reader trace the main route through a busy chart without reading every label.
- Add the end terminator(s). Finish each path with an oval labeled "End". A chart can have several end points — a rejected payment and a completed order might both terminate — and that is perfectly correct.
Work through the list once to lay everything down, then make a second pass purely to clean up: this two-phase rhythm — build, then polish — keeps you from fussing over alignment while ideas are still landing.
Common Mistakes to Avoid
A few recurring errors separate a confusing flowchart from a clear one. Watching for them as you build will save rework:
- Unlabeled decision branches. A diamond with two unlabeled arrows forces the reader to guess. Always mark which exit is "Yes" and which is "No".
- Arrows without direction. A plain line does not tell the reader which way the process moves. Use arrows, not lines, so flow is unambiguous — this is the whole point of the chart.
- Wrong shape for the job. Drawing a decision as a rectangle, or an action as a diamond, breaks the visual language and confuses anyone who knows the conventions. Match the shape to the step's role.
- Crossing and tangled arrows. When lines cross repeatedly, the chart becomes a knot. Rearrange boxes so arrows mostly flow in one direction (top-to-bottom or left-to-right) and cross as little as possible.
- Steps that are too big. If a single rectangle hides five sub-steps, the chart is not actually explaining the process. Break large steps into smaller ones, or link out to a separate detailed chart.
- No clear start or end. Every flowchart needs exactly one starting terminator and at least one ending terminator. A chart that just trails off leaves the reader wondering whether they have seen the whole thing.
If you find yourself sketching loosely before committing to structure, that is fine — many people brainstorm the rough shape first. For more on moving from a loose sketch to a structured diagram, see our guide to visual thinking with diagrams and sketches, and if you want a broader tour of the canvas before diving in, the walkthrough on using an online whiteboard for brainstorming and annotation covers the toolbar in depth.
Exporting and Sharing the Finished Chart
A flowchart only earns its keep when other people can see it, so the last step is getting a clean file out of the editor. Which format you choose depends on where the chart is going:
- PNG is the everyday pick — a flat image you can paste into a chat, a document, or a ticket. Export at a larger size if the chart will be projected or printed, so the labels stay crisp.
- SVG keeps every box, arrow and label as a true vector, so the chart scales to poster size without blurring and can be reopened and edited later in a vector program. Choose SVG for documentation you expect to revise.
- PDF gives you a single printable page, ideal for a handout or an email attachment that should look the same on every device.
- The editable scene file (typically JSON) saves the chart itself, with every shape still movable and every arrow still bound. Keep this so a future edit is a five-minute tweak rather than a rebuild.
A reliable habit is to export two files whenever a chart matters: a PNG to share right now, and the editable scene so the diagram is never a dead end. For a fuller rundown of the trade-offs between raster and vector output, our guide on exporting a whiteboard to PNG, SVG and PDF walks through each format and when to reach for it.
Start Your First Flowchart
The fastest way to learn is to map a process you already know. Open the online whiteboard, list the steps of something simple — how you make coffee, how a form gets submitted, how a refund is approved — and translate that list into ovals, rectangles, diamonds and arrows. Bind the arrows, align the boxes, color the branches, and export a PNG when it reads cleanly. Because the whole tool runs in your browser, nothing you draw ever leaves your device, which makes it just as safe for an internal process map as for a quick sketch you share in seconds.