Show two simple instruction lists for making a sandwich or drawing a shape, with the steps in different orders. Ask which one works best and why. Connect the idea to code: computers follow instructions exactly as given.

Think-pair-share which sequence works and explain how changing the order changes the result.

Define sequencing and model a short code example step by step. Think aloud while tracing each instruction and predicting the output before revealing it.

Listen, annotate notes, and predict what the program will do at each step.

Display 2–3 short code snippets with one sequencing mistake each. Model the first one, then ask students to identify what happens when steps are out of order.

Work with a partner to trace each snippet and mark where the sequence breaks.

Give students a scrambled set of instructions for a simple task, such as drawing a square, moving a character, or greeting a user. Ask them to arrange the steps in the correct order and justify their choice.

Individually or in pairs, reorder the steps, test the logic mentally, and explain why their sequence works.

Ask a few quick oral questions to check understanding: What happens if one step is moved? How do you know the order is correct? What is one strategy for debugging sequence errors?

Respond verbally and compare answers with a partner.

Summarize that sequencing is about order, accuracy, and predicting results before coding. Highlight that strong coders trace instructions carefully and fix order problems first.

Write one sentence in notebooks: 'Sequencing matters in coding because...'