Checkout | What Must Be Checked Before We Build Further?

Quick Read

After locating the learner’s Arrival State, the next question is not automatically “What should we teach next?” It is “What must already work for the next step to make sense?”

Checkout is the disciplined check of the capabilities, representations and conditions that the next learning move depends on.

One-Sentence Answer

A Tutorial Checkout verifies the smallest set of prerequisites that must be available before new teaching, harder practice or reduced support is justified.

Why Checkout Exists

Learning becomes expensive when a new idea is placed on top of a weak dependency. The learner then has to manage the new content and compensate for the earlier weakness at the same time.

This often looks like carelessness or low confidence from the outside. In reality, working memory may be carrying too many unresolved pieces.

The Historical Anchor

In launch preparation, checkout procedures exist because individual systems must work before larger integration can be trusted. The educational translation is modest: before adding load, verify the small capability that the next step requires.

This analogy does not turn a child into a machine. It reminds the adult not to confuse scheduled progression with justified progression.

A Dependency Is Not the Same as an Earlier Chapter

A prerequisite is whatever the current task actually needs. Sometimes it comes from years earlier. Sometimes it was taught last week. Sometimes the learner knows it conceptually but cannot retrieve it under load.

• Algebra may depend on fraction and signed-number control.
• Percentage may depend on multiplicative comparison.
• Trigonometry may depend on diagram interpretation and algebraic rearrangement.
• Calculus may depend on function meaning and algebraic fluency.
• A word problem may depend on language and representation rather than a new formula.

The Minimum Checkout

Checkout should be economical. Test only what could change the next decision.

1. Identify the next mathematical move.
2. Name the one or two capabilities it depends on most.
3. Ask a short independent question that isolates each dependency.
4. Observe whether support is still required.
5. Proceed, repair or reconfigure based on the result.

A Mathematics Example

A Secondary 3 learner repeatedly fails quadratic equations. Before reteaching the whole chapter, Checkout asks whether the learner can factorise simple expressions and preserve equality while rearranging equations.

If factorisation is unstable, that is a useful repair target. If both prerequisites are secure, the Tutorial can look instead at recognising which quadratic route applies.

The purpose of Checkout is to eliminate avoidable ambiguity before spending a whole lesson on the wrong cause.

Common Checkout Errors

• Checking too much: the learner spends the lesson proving everything they already know.
• Checking only answers: the Tutor misses dependence on prompts or representations.
• Using age as proof: a learner is assumed to own a prerequisite because it was taught in an earlier year.
• Repairing too broadly: the learner is sent backwards through whole chapters rather than one active weak link.
• Never returning forward: remedial work becomes a permanent lower-level curriculum.

Repair Should Be Narrow and Reconnected

If Checkout finds a weak dependency, repair it only as far as the current mission requires. Then return to the original task quickly.

This matters psychologically as well as mathematically. The learner can see why the earlier skill matters and experience the repair as restored access rather than as being sent backwards.

Checkout Can Also Reveal Over-Support

Sometimes the dependency is secure but hidden by adult habit. The Tutor keeps naming the method, supplying the diagram or reminding the formula even though the learner no longer needs it.

Checkout should therefore ask not only “Can the learner do this?” but “Can the learner do this with less help?”

From Checkout to Assembly

Once the required pieces are visible, the Tutorial can configure the next learning event properly. Secure dependencies can be left in the background. Fragile ones can be supported. Missing ones can be repaired. Unnecessary supports can begin to fade.

Parent Decision Guide

• Does tuition identify the prerequisite instead of simply assigning more topical worksheets?
• Is repair narrow and connected back to the current syllabus?
• Can the Tutor explain why an earlier skill matters now?
• Are supports tested for removal as well as added?
• Does my child return to the original problem with greater control?

Frequently Asked Questions

Does every new topic need a prerequisite test?

No. Checkout can be embedded naturally in the first independent task. Formal testing is only needed when uncertainty is consequential.

What if the prerequisite is weak but exams are near?

That makes precision more important, not less. Repair the smallest high-value dependency and return to examination application rather than restarting the whole curriculum.

Can a learner pass Checkout with a calculator or formula sheet?

Only if those supports will also be available for the target task and are not hiding the capability being inspected.

The Long Arc

Early learners depend on adults to identify what must come first. Mature learners increasingly perform Checkout themselves: before tackling a difficult problem, they ask what they need to know, which part is actually missing and whether they need a tool, a refresher or specialist help.

The mature learner does not fear prerequisites. They know how to locate and restore them without losing sight of the real mission.