What a flowchart is and why you'd make one
A flowchart is a diagram that shows the steps in a process from start to finish, using boxes and arrows to show which step comes next. Each box holds one action or decision, and arrows point to what happens after. Flowcharts turn a messy list of instructions into something you can see all at once — which is why people use them to plan projects, document how software works, troubleshoot problems, or teach someone else a process.
You might create a flowchart to map out a work procedure, show how a customer moves through your business, plan the logic in a computer program, or figure out where a system is breaking down. The visual layout makes it much easier to spot missing steps, unnecessary loops, or places where the process could go wrong.
Key Takeaways
- A flowchart uses boxes for actions or decisions and arrows to show the order and direction of steps in a process.
- You can draw a flowchart on paper with a pencil, or use free online tools like Lucidchart, Draw.io, or Google Slides if you want to share or edit it later.
- Start by listing every step in the process in order, then decide which steps are actions, which are decisions, and where the process branches or loops back.
- Use standard shapes: rectangles for actions, diamonds for yes-or-no decisions, ovals for start and end points, and parallelograms for input or output.
- Test your flowchart by following it from start to finish to make sure every path leads somewhere and no steps are missing.
Gather the steps in your process
Before you draw anything, write down every single step that happens in the process you want to map. Do not worry about the order yet — just list what actually occurs. If you are documenting a process someone else does, watch them do it or ask them to walk you through it. If you are planning a new process, think through what needs to happen from the moment someone starts until the moment they finish.
Write each step as a short action: "Check email," "Send invoice," "Wait for approval," "Update database." Be specific enough that someone reading it would know what you mean, but not so detailed that you end up with fifty boxes. If a step has multiple parts, break it into separate steps. If a step is just a waiting period or a decision point, note that too — those are important to show.
Decide what tool to use
You can draw a flowchart by hand on paper with a pencil and ruler, and that is a perfectly valid way to start. If you want something you can edit, share, or print cleanly, a digital tool is faster. Draw.io is free, works in your web browser, and requires no account. Lucidchart offers a free tier with limited diagrams. Google Slides or Microsoft PowerPoint both have shape tools that work for straightforward flowcharts. Miro and Mural are collaborative tools if multiple people need to build the flowchart together.
For a first flowchart, Draw.io or Google Slides are the easiest entry points — both have flowchart shapes already built in, and you do not need to learn new software. If you are working alone and just need something to print or email, any of these will do. If your team needs to comment and revise together, Lucidchart or Miro handle that better.
Arrange your steps in order and identify decision points
Now take your list and put the steps in the order they actually happen. Look for places where the process branches — where the answer to a question determines what happens next. Mark those as decision points. For example, "Is the invoice correct?" is a decision point. If yes, the process continues one way. If no, it goes a different way.
Also look for loops — places where the process circles back. For instance, "If the form is incomplete, send it back to the applicant" creates a loop: the applicant fills it out again, and you check it again. Mark those too. Once you have the steps in order and you know where the branches and loops are, you are ready to draw.
Draw the flowchart using standard shapes
Use these shapes so anyone reading your flowchart will understand it:
- Oval or rounded rectangle: Start and end points. Label these "Start" and "End."
- Rectangle: An action or task. "Send email," "Update record," "Print report."
- Diamond: A decision or yes-or-no question. "Is the amount correct?" or "Does the customer have an account?"
- Parallelogram: Input or output. "Receive order," "Display result," "Print invoice."
- Arrow: The direction of flow. Always points to the next step.
Start with an oval at the top labeled "Start." Below it, add a rectangle for the first action. Draw an arrow from Start to that rectangle. Continue down, adding rectangles for each action step. When you reach a decision point, switch to a diamond. Label the question inside. Draw two arrows out of the diamond — one labeled "Yes" and one labeled "No" — each pointing to the next step that happens in that case.
If a path loops back to an earlier step, draw an arrow that curves back to that step. If a path ends, draw an arrow to an oval labeled "End." Keep the flowchart flowing downward and to the right when possible — it is easier to follow than a tangled mess of arrows going every direction.
Label every box and arrow clearly
Write a short, clear label inside each box. For rectangles, use a verb: "Verify payment," "Send confirmation." For diamonds, write the question: "Payment received?" For arrows coming out of diamonds, label them "Yes" or "No" so it is obvious which path to take. If an arrow loops back or jumps to a distant part of the flowchart, label it with what triggers that path: "Incomplete — return to step 2" or "Approved — continue."
Do not assume the person reading your flowchart knows what you mean. Someone who has never seen this process before should be able to follow your arrows and boxes and understand exactly what happens at each stage and why.
Test your flowchart by following it
Walk through your flowchart from start to finish as if you were actually doing the process. Follow every path — the happy path where everything goes right, and the paths where things go wrong or require a decision. Ask yourself: Does every box lead somewhere? Does every arrow point to a real next step? Are there any steps missing? Is there any place where someone could get stuck or confused?
If you find a gap, add a box. If you find a loop that does not make sense, redraw it. If someone else can read your flowchart and follow it without asking you questions, it is done. If they get confused or find a missing step, revise it. A flowchart is a tool to make a process clearer — if it is not doing that, it needs another pass.
Frequently Asked Questions
Can I use different shapes than the standard ones?
Yes, but standard shapes help anyone reading your flowchart understand it when ready. If you use a rectangle for a decision and a diamond for an action, someone familiar with flowcharts will misread it. Stick to the standard shapes unless you have a very good reason not to, and if you do use non-standard shapes, include a legend explaining what each one means.
What if my process has too many steps to fit on one page?
Break it into smaller flowcharts. Create one flowchart for the main process, and separate flowcharts for sub-processes. Use a box labeled "See flowchart: [name]" to point to the detailed version. This keeps each diagram readable and lets people understand the big picture before diving into details.
Should I include every tiny detail or keep it straightforward?
Keep it straightforward enough that someone can understand the overall flow in a few minutes. If you include every detail, the flowchart becomes too crowded to read. If the details matter for someone doing the work, create a separate detailed flowchart or a written procedure to go with the straightforward one.
How do I show that two paths come back together?
Use a small circle or a rectangle with one arrow coming in from each path and one arrow going out. This shows that both the "Yes" and "No" paths from a decision lead to the same next step. Without this, it looks like the paths are separate.
Can I make a flowchart for something that is not a work process?
Yes. Flowcharts work for any step-by-step process: troubleshooting a computer problem, deciding whether to buy something, planning a project, or teaching someone how to do a task. The shapes and logic are the same no matter what the process is.