Did you know? In a control-system question, “feedback” does not mean advice from a person. It is information about the system’s result that returns to influence what happens next. G2 Design and Technology tuition can help by teaching the child to follow the flow of information and action, instead of memorising four labels in isolation.

Try this next: ask your child to draw arrows for a hot-water dispenser. What senses the water temperature? What compares it with the target? What changes the water? What new information returns? If the arrows cannot be explained aloud, the confusion is structural and can be repaired before more circuit symbols are added.

A student’s Posting Group does not automatically fix every subject level. Under Full Subject-Based Banding, the child may take G2 D&T while taking other subjects at G1, G2 or G3. Always confirm the school’s actual subject offering and the correct examination-year syllabus.

Find the exact misconception

Students often know the words but attach them to the wrong things. They may call a push button the “process” because it starts the device, call a motor the “feedback” because it moves, or list a sensor without saying what quantity it detects. A quick diagnostic uses one familiar product and asks four role questions:

• Input: What information or command enters the system?
• Process: What rule, comparison or decision is applied?
• Output: What action or change does the system produce?
• Feedback: What information about the result returns and affects further control?

The child should answer with verbs as well as nouns. “Temperature sensor” is incomplete; “the sensor measures the water temperature and sends that value to the controller” exposes the relationship. The goal is to make the hidden movement visible.

Back to contents

Build a four-part map from the desired result

Start at the end: what is the product trying to keep, change or communicate? For a hot-water dispenser, the useful result is water near a selected temperature. From there, work backwards and then trace forwards.

1. State the target: the selected temperature.
2. Name the input information: the measured water temperature and the user’s setting.
3. Describe the process: compare measured temperature with the setting.
4. Name the output action: switch or regulate the heater.
5. Close the loop: the new water temperature is measured again.

This map prevents a common mistake: treating the physical component as if its role never changes. A switch can be a user input in one design. A sensor provides input data. A controller performs the processing rule. An actuator or display produces an output. Feedback is not a special-looking component; it is the returned information path.

Drawing arrows is not decoration. Each arrow should answer “what travels here?”—a button state, a measured value, a control signal or a changed physical condition.

Back to contents

Contrast an open loop with a closed loop

Example 1: a simple table lamp

A person presses a switch, the electrical path changes, and the lamp produces light. The lamp does not necessarily measure the room brightness and correct itself. In this simple example, the user command is an input, the switching/control action is the process and light is the output. There is no automatic returned measurement controlling the next action, so the system can be described as open loop.

Example 2: a temperature-controlled dispenser

A temperature sensor measures the water, the controller compares that value with a setting, and the heater changes the temperature. The result is sensed again. This returned measurement lets the system reduce, stop or resume heating, so the loop contains feedback.

The comparison matters more than the definitions. If the sensor is removed, what becomes impossible? If the controller ignores the returned measurement, does the loop still regulate temperature? “What breaks?” questions force the student to reason about function.

Back to contents

Use questions that reveal understanding

A tutor can vary one feature at a time. Replace the temperature sensor with a timer. Move the light sensor so the lamp shines directly on it. Ask whether the behaviour is still useful. The student must predict the consequence before choosing labels.

• What quantity is sensed?
• What is the target or rule?
• Which component acts on the physical world?
• Does the output change the next input?
• Is that returned information intended, useful or destabilising?
• What would the user notice if one component failed?

These prompts turn a block diagram into a testable model. They also connect electronics with the design brief: a technically correct loop can still be awkward, unsafe or inappropriate for the user.

Back to contents

Respect the 2027 syllabus and the project boundary

The 2027 SEAB G2 directory lists Design and Technology as syllabus K234. The 2027 G2 D&T K234 syllabus asks candidates to explain open- and closed-loop applications, consider input, process, output and feedback, and adapt available electronic kits involving sensing of light, moisture and temperature. The written paper is design-centric, with technology questions on mechanisms and electronics.

Paper 2 is an individual 20-week Design Project under school supervision. Tuition may use unrelated practice circuits, neutral product diagrams and oral diagnosis. It must not choose or build the candidate’s assessed electronics, write the Design Journal or replace school safety instruction. The student’s design decisions and evidence must remain their own.

The syllabus also expects safe working habits. Practical construction and powered testing belong within appropriate facilities, equipment rules and competent supervision; a diagram lesson is not permission for unsupervised workshop or mains-electricity work.

Back to contents

How a small group can practise without copying

If a provider actually offers G2 D&T tuition, a conditional three-student activity can be useful. Give each learner a different product—such as a plant-watering alert, a temperature warning and a light-activated indicator. Each student maps the system, then the others ask one “what travels here?” question and one “what happens if it fails?” question.

The answers should stay different because the systems are different. The tutor listens for role confusion, redraws only the broken link and then asks the learner to explain the complete loop independently. This is closer to design thinking than copying a single perfect diagram.

Back to contents

Look for transfer, not label recall

Progress is visible when the child can meet four checks on a fresh system:

• assign roles by function rather than by the component’s appearance;
• state what information or action crosses every arrow;
• distinguish a user command from automatic feedback;
• predict how the system behaves when a sensor, controller or output fails; and
• connect the technical loop to user interface and functionality.

A strong independent check is to ask the child to invent a plausible wrong diagram and explain why it fails. If they can diagnose their own deliberate error, the structure is probably understood rather than memorised.

Back to contents

Continue the series

Read Why Does My Child Have D&T Ideas but Struggle to Explain Design Decisions? for the broader design-reasoning problem. Use the series directory to check other G2, G3 and G1 subjects without confusing Posting Group with subject level.

For tonight, use one product and ask: “What comes back into the system after the output changes?” If nothing returns automatically, your child may be looking at an open loop—not missing a definition.