Definition
A page of written instructions can hide a missing step. Draw the same instructions as boxes and arrows, and the gap jumps out at you.
A flowchart is a diagram that shows the steps of an algorithm as shapes joined by arrows. Each shape has a meaning: ovals for start and end, rectangles for actions, parallelograms for input and output, and diamonds for decisions. Arrows show the order in which the steps happen.
In simple words
A flowchart is like a board game path. You start at the start, follow the arrows, do what each square says, and at a fork you choose a path depending on the answer to a question, until you reach the finish.
Why it matters
Flowcharts make algorithms visible. They help you plan before building anything, explain a process to others, and spot missing steps or dead ends. Engineers, doctors, banks and governments all use them to describe procedures.
Key terms
- Flowchart
- A diagram of an algorithm using standard shapes and arrows.
- Terminator
- The oval shape that marks the start or end.
- Process box
- A rectangle containing one action, such as "boil water".
- Input/output box
- A parallelogram for information coming in or going out, such as "enter your age" or "show the result".
- Decision box
- A diamond containing a yes-or-no question, with two arrows leaving it.
- Flow line
- An arrow showing which step comes next.
Explained in detail
The standard shapes
| Shape | Meaning | Example |
|---|---|---|
| Oval | Start or end | Start / Stop |
| Parallelogram | Input or output | Read the temperature; display the message |
| Rectangle | An action or calculation | Add the marks together |
| Diamond | A decision with yes and no | Is the temperature above 38? |
| Arrow | The direction of flow | From one step to the next |
Using standard shapes means anyone who knows them can read your flowchart, in any language or country. That is why the same symbols appear in textbooks, factory manuals and hospital procedures around the world.
A simple example: checking for fever
- Start (oval).
- Input: read the thermometer (parallelogram).
- Decision: is the temperature above 38 °C? (diamond).
- If yes: output "You have a fever. Rest and tell an adult." (parallelogram).
- If no: output "No fever." (parallelogram).
- Both paths join and reach Stop (oval).
Rules for clear flowcharts
- There is exactly one start, and every path reaches an end.
- Each box holds one step, written in a few clear words.
- Every diamond has exactly two labelled exits: yes and no.
- Arrows flow top to bottom and left to right where possible, and do not cross.
- Test it by tracing a real example along the arrows with your finger.
Why draw before building
Drawing a flowchart is cheap; fixing a mistake after a system is built is expensive. A bank designing a loan-approval process, or a hospital designing a triage process for emergencies, will draw and review the flowchart with many people first. Someone will spot the path that leads nowhere, or the question that has no answer for a certain kind of patient. The same habit helps you plan school projects, recipes and AI projects.
Flowcharts also have limits. A very large process can produce a flowchart that spreads across many pages and becomes hard to follow. Designers handle this with abstraction: one box on the main chart, such as "check the patient's history", can stand for a whole smaller flowchart drawn on a separate page. Others prefer writing numbered steps in plain language, or using swimlane charts that show which person or department does each step. The best choice is whichever makes the process clearest for the people who must follow it.
How it works
- Write the steps of your algorithm in words first.
- Start with an oval labelled Start.
- Draw each step in the right shape, joined by arrows.
- For each question, draw a diamond with yes and no arrows.
- End every path at a Stop oval, then trace an example to test it.
Try it yourself
The flowchart that found a missing step
A canteen team writes the steps for serving lunch, then draws them as a flowchart.
Match the shape to its job
What does each flowchart shape mean?
- Oval
- Rectangle
- Diamond
- Parallelogram
Common mistakes
- Leaving a decision arrow that leads nowhere.
- Putting several actions in one box.
- Using random shapes instead of the standard ones.
Check yourself
Summary
- A flowchart shows an algorithm with standard shapes and arrows.
- Ovals start and end, rectangles act, parallelograms input and output, diamonds decide.
- Every path must reach an end; trace examples to test.
Finished reading?
Sources: BBC Bitesize: Introduction to computational thinking · CS Unplugged