Students read, interpret and compose procedural and instructional texts such as workplace procedures, recipes, safety instructions and how-to guides for authentic purposes

What this dot point is asking

Work and training run on instructions. A safety notice, a recipe, a machine manual, a set of steps for opening a shop in the morning: all of these are procedural texts. This dot point asks you to do two things. Read instructions accurately so you can act on them, and write your own instructions so clearly that another person can follow them without you in the room. The audience is a real worker or learner, and the purpose is to get a task done safely and correctly.

The answer

A procedure is a text that tells someone how to do something in order. Its whole value depends on clarity. If a step is vague or out of order, the task fails or someone gets hurt. So the language of procedure is plain, direct, and ordered.

Reading instructions accurately

Reading a procedure is an active job, not a quick skim. Read all the steps before you start, so you know what is coming. Notice warnings and the word order inside a step. "Turn off the power before opening the panel" means something very different if you read only half of it. Watch for signal words: first, then, next, before, after, until. These words carry the order, and missing one changes the meaning.

When a procedure includes a diagram or a list of materials, treat those as part of the text. The instruction and the picture work together, and skipping the picture is skipping information.

Features of a clear procedure

Strong procedures share a recognisable shape.

• A clear goal stated up front: what this procedure achieves.
• A list of what you need: materials, tools, or information.
• Numbered steps in the exact order they happen.
• One action per step, written as a command (an imperative verb): turn, press, check, record.
• Warnings placed before the step they apply to, not after.

The grammar is deliberately simple. Procedures use imperative verbs and short sentences because the reader is acting, not analysing.

Writing your own procedure

To write a procedure, do the task yourself or picture it exactly, then write down every step a beginner would need, including the ones an expert forgets. The most common failure is leaving out an obvious step because you already know it. Test your draft by giving it to someone who has never done the task and watching where they get stuck. Each point of confusion is a step you need to rewrite.

Examples in context

Compare two versions of one step in a procedure for closing a cafe. The weak version reads "clean up and lock". This bundles many actions and assumes knowledge. The strong version separates the actions and orders them.

Switch off the coffee machine at the wall. Wipe the bench with the blue cloth. Take the till float to the safe and record the amount in the logbook. Set the alarm, then lock the front door.

The strong version uses one imperative per step, names the specific cloth and book, and puts the alarm before the lock so the worker does not lock themselves in an unarmed shop. The improvement is not fancier English. It is clarity matched to a real task, which is what the module rewards.

Common mistakes

Try this

• Write a procedure for a simple task you know well, such as making a sandwich, then give it to someone and watch where they hesitate.
• Take a bundled instruction like "set up the room" and split it into single imperative steps.
• Find a real safety notice and underline every signal word that carries order or warning.