Learn how to make a flowchart from scratch: define the process, pick symbols, connect decisions, avoid common mistakes, and build free online with FreeFlowCharts.
Flowcharts are one of the most powerful tools for visualizing processes, decisions, and systems. Whether you're mapping out a software workflow, planning a business process, or just organizing your thoughts, this guide will teach you how to make a flowchart from scratch.
What is a flowchart?
A flowchart is a diagram that represents a process or workflow. It uses standardized symbols (shapes) connected by arrows to show the sequence of steps, decision points, and outcomes.
Flowcharts were invented in the 1920s by engineers Frank and Lillian Gilbreth and have been a standard tool in computing, engineering, and business ever since.
When to use a flowchart
Flowcharts are ideal for:
Software development: Mapping out algorithms, user flows, API request handlingBusiness processes: Employee onboarding, approval workflows, customer service proceduresDecision making: Troubleshooting guides, diagnostic trees, if-then logicEducation: Explaining concepts, study guides, research methodologyProject management: Task dependencies, milestone tracking, sprint planningStep 1: Define the process
Before opening any tool, answer these questions:
What process are you documenting?Where does it start and end?Who are the people or systems involved?What decisions need to be made along the way?What are the possible outcomes?Write these down as a simple list before you start drawing.
Step 2: Identify the steps
Break your process into individual steps. Each step should be a single action or decision. For example, an employee onboarding process might include:
New hire accepts offerHR sends welcome emailIT provisions laptop and accountsEmployee completes compliance trainingManager schedules 1:1 meetings30-day check-inStep 3: Choose your symbols
Flowcharts use standardized shapes (we'll cover these in detail below):
Oval/Rounded rectangle: Start and End pointsRectangle: Process steps (actions)Diamond: Decision points (yes/no questions)Parallelogram: Input/Output (data entry or display)Rectangle with double lines: Subprocess (a process within a process)Step 4: Connect the steps
Use arrows to show the flow from one step to the next. Key rules:
Flow generally goes top-to-bottom or left-to-rightDecision diamonds have two or more exits: (Yes/No, or multiple paths)Arrows should never cross: if possible — rearrange nodes to avoid thisEvery path must lead somewhere: — no dead ends except at End nodesStep 5: Add detail
Once the basic flow is in place, enhance it:
Add descriptions to each node explaining what happensColor-code nodes by category (e.g., blue for automated steps, green for manual)Add swimlanes to show which team or person handles each stepInclude decision criteria on the arrows leaving decision nodesStep 6: Review and refine
Walk through the flowchart with someone unfamiliar with the process. If they can't follow it, simplify. Good flowcharts are:
Clear: Anyone can understand the flow in under a minuteComplete: No missing steps or undefined pathsConcise: No unnecessary detail — link to docs for complex stepsCommon flowchart mistakes
Too much detail: Flowcharts should be overviews, not instruction manualsMissing decision branches: Every diamond must have all possible exitsNo start/end nodes: Always explicitly mark where the process begins and endsCrossing arrows: Rearrange nodes to eliminate arrow crossingsUsing non-standard symbols: Stick to the recognized shapes so anyone can read your chartWorked example: simple refund request
Use this mini case to practice the steps above.
Define: Customer requests refund → decision approved/denied → money returned or reason sent → end.Steps: Request received → verify order → within policy window? → approve or deny → process payment or send denial → notify customer → end.Symbols: Start oval, process rectangles, one decision diamond, two end ovals (approved path / denied path).Connect: Label diamond exits Yes (within window) and No (outside window).Detail: Sticky note with policy link; color deny path amber.Review: Ask support to walk a real ticket through the chart.Digital vs whiteboard
Whiteboards are perfect for workshops. Digital flowcharts win when you need:
Shareable URLs for remote teamsVersioned docs (export Mermaid into Git)Reuse as templates across teamsAccessibility and zoom on large processesMake your flowchart now
The fastest way to create a flowchart is with an online tool like FreeFlowCharts. Drag nodes, connect them, and export — all free, all in your browser. No signup required for guest mode.
If you want to go even faster, Pro users can try AI generate: describe your process in plain English and get a complete flowchart draft in seconds, then refine nodes manually.
Next reading
Flowchart symbols and meanings10 flowchart examples and templatesFlowchart vs mind map vs org chartTool overview: free flowchart maker