Pre-production planning
A flow chart is a pre-production document that breaks a problem or process down into separate stages. Each stage is shown as a step, and the decisions taken by organisations, people or programs are included so you can see which route the process takes.
A flow chart is mainly used where a process needs to be shown, rather than to plan a media product directly. It suits any process where the order of steps and the choices along the way matter.
| Type of process | Why a flow chart suits it |
|---|---|
| Organisational process | Shows the stages for sorting lost property and the decision about whether an owner is named. |
| Instructions for a process | Guides someone through using a self-service kiosk, including a check for whether the book has been scanned. |
| Website algorithm or process | Shows the checks a website makes before confirming a click-and-collect order is ready. |
| Computer game character algorithm or process | Shows how a game character decides whether to offer the player a side quest, including a check for whether the player has already completed it. |
| Work process | Shows the order for opening a café, including a decision about whether the till has been counted. |
A flow chart is less useful for directly planning a media product such as a poster or magazine cover. Those products depend on layout, colour, images and typography, and a flow chart cannot show where elements sit on the page or what the visual style looks like. A storyboard or visualisation diagram is a better fit for those decisions. A flow chart can still help plan a process around a media product, such as how a poster design is approved, but it does not plan the product itself.
A flow chart is a diagram that breaks a process into steps and decisions. Every shape comes from a standard set of symbols, so a flow chart drawn by one person can be read the same way by anyone else, whatever they know about the process.
| Symbol | Shape | What it shows |
|---|---|---|
| Terminator | Rounded rectangle or oval | The start or the end of the flow chart |
| Process | Rectangle | A step where something is done |
| Decision | Diamond | A question or comparison with more than one possible route |
| Input/output | Parallelogram | Data entering the process or leaving it |
| Arrow | Line with an arrowhead | The direction the flow travels in |
A decision box holds a question or comparison, and two arrows leave it, one labelled Yes and one labelled No. The labels matter because the shape alone does not say which route is taken when the answer is true and which when it is false. Each arrow then leads to a different part of the flow chart, so the reader can see both outcomes.
Imagine a school canteen till. The flow chart opens with a start terminator, then an input parallelogram reading “Enter money”. What the user types is stored in a variable so it can be used later. The next shape is a decision diamond asking money >= 2.50? — the comparison belongs in the diamond, not in the input box. The Yes arrow leads to a process rectangle, “Serve hot meal”, while the No arrow leads to an output parallelogram, “Display ‘not enough money’”. Both routes finish at an end terminator, so the process has one clear beginning and one clear finish.
Many job roles may need to understand a flow chart, and which role depends on the process it shows. The user is anyone who needs to understand the flow chart to carry out, check or build that process.
| Job role | Flow chart they may need to understand |
|---|---|
| Website designers and web developers | A flow chart for a website algorithm or process, such as the steps a customer follows to book a bike in for a repair. The web team uses it to build and check the pages in the right order. |
| Production managers, directors or editors, camera operators, audio technicians and on-screen talent | A flow chart for an organisational process, such as the steps for a filming day on location: arriving, safety briefing, setting up, filming and packing away. Each person can see their part and when to act. |
| Programmers and animators | A flow chart for a computer game character's algorithm or process. The programmer uses it to program the character's behaviour, and the animator uses it so the character's actions match the same decisions. |
| Campaign managers | A flow chart for a promotional process, such as approving a short video advert for a leisure centre open day. It shows who checks the advert and when it can be posted online. |
The flow chart should match the role that carries out or checks the process. A website booking flow chart is used by the web team, while a game character flow chart is used by programmers and animators. When the flow chart fits the role, the right person can follow it and make the right decisions.
An effective flow chart can be followed by someone who has never seen the process before. It uses the correct standard symbols throughout and starts and ends with a terminator, so the reader knows exactly where the process begins and stops. Every decision has both arrows labelled Yes and No. Input/output and process boxes are complete: they say what data is entered or displayed and what action is carried out, rather than using a vague label such as 'details'. The chart contains enough detail to represent each stage and decision that actually occurs, leaving nothing out.
Improving a draft means changing its content so it matches the real process, not just making it neater. A useful check is to walk through the process from memory and compare each stage with the draft.
| Draft problem | Specific improvement |
|---|---|
| A decision has only one arrow labelled. | Label both routes from the decision Yes and No so every path is clear. |
| An input says 'Enter days borrowed', but the decision just asks 'Overdue?'. | Use the variable name in the input, such as days_borrowed, and put the comparison in the decision: days_borrowed > 14? |
| A step is missing. | Add the missing process box, such as 'Print due-date slip'. |
| An output box just says 'book'. | Complete it so the data leaving the process is clear, such as 'Display book title and due date'. |
| The start or end symbol is missing. | Add the missing terminator. |
| The draft skips a check that really happens. | Add the missing step or decision, such as 'Book already on loan?' before the book is issued, so the flow chart reflects the real process. |
If a draft is too simple, add the missing detail until it represents the process fully. Improvements should be specific to the process shown. A vague 'make it clearer' is much less useful than 'label the Book already on loan? decision Yes and No'.