Engineering Token System

Overview

Today students will set up and practice a token economy designed to promote behaviors that support engineering learning: teamwork, problem-solving, safety procedures, and effort. Students will connect their actions to measurable class expectations and use a tracking process to guide improvement.

Learning intentions

• Students will be able to describe class expectations for productive engineering behavior.
• Students will be able to explain how tokens can be earned and what actions “count” as evidence of those expectations.
• Students will be able to identify how tokens are redeemed and how feedback will help them improve.
• Students will be able to use a rational-number mindset to compare and justify progress scores (earned vs. goal).

Success criteria

• I can name 3–4 engineering behaviors that earn tokens and give a specific example.
• I can follow the safety and teamwork rules during a short engineering task.
• I can track my tokens and calculate whether I met a progress goal using rational-number reasoning (earned/goal or difference).
• I can reflect on one behavior I will improve and one strategy I will try next time.

Curriculum links

• Number System — applying and extending addition and subtraction to add/subtract rational numbers represented on a number line.
• Number System — apply and extend multiplication and division of rational numbers.
• Number System — use rational approximations of irrational numbers to compare and locate approximations on a number line (future skill bridge; optional classroom reference).
• Engineering task work is supported by clear expectations and evidence-based feedback; students use rational-number tools to quantify progress.

Lesson structure (60 minutes)

1. 0–5 min · Hook (Behavior as Design). Teacher displays the engineering challenge directions and asks: “What behaviors make engineering work smoother?” Students quick-write 2 behaviors and 1 safety rule they think matters.

2. 5–12 min · Introduce the token economy. Teacher shows the token board/trackers and explains: tokens represent real evidence of target behaviors; feedback will be timely. Students listen, then turn-and-talk to list which target behaviors match their written ideas.

3. 12–22 min · Co-create token categories (what earns tokens). Teacher posts 4 categories: Teamwork, Problem-solving, Safety, Effort. Teacher models one “yes” and one “not yet” example per category (e.g., listening during partner work vs. interrupting). Students in groups suggest one specific action for each category and vote on the final wording for the class.

4. 22–30 min · Practice run: micro-scenarios. Teacher reads short scenarios (e.g., “Your prototype breaks—what do you do next?”). For each scenario, students hold up a response card: earns token, doesn’t earn, or earns partial. Teacher confirms and explains the evidence students should look for.

5. 30–45 min · Token-earning engineering task (hands-on). Students work in pairs on a timed build using a simple, safe constraint (e.g., create a freestanding structure with limited materials). Teacher observes and awards tokens immediately for: safety compliance, shared roles, asking/trying strategies, and persistence. Students track tokens on their personal sheet during the task.

6. 45–52 min · Redeem and quantify progress (rational thinking). Teacher explains redemption: at the end of the week, tokens can be exchanged for choices (extra lab time, leading a safety demo, preferred partner for one session, class job pass). Then students calculate a progress check:

• Example: “Goal = 12 tokens. I earned 9.” Compute difference (12 − 9) and an earned fraction (9/12 simplified). Students complete their progress line using a number line or fraction bar model.

7. 52–58 min · Behavior reflection and class feedback loop. Teacher prompts: “What behavior will you intentionally practice tomorrow?” Students write one goal tied to a category and one strategy (e.g., “I will ask a question before giving up” or “I will share materials first”). Teacher selects 2–3 students to share one improvement plan.

8. 58–60 min · Exit ticket. Students submit:

• One sentence naming their next behavior focus
• A quick math check: “If you earn 3 more tokens out of a 12-token goal, what is your new earned/goal ratio?” (students answer as a fraction and/or simplified fraction)

Resources

• Token board visible to the class
• Individual token trackers (paper or digital)
• Category posters: Teamwork, Problem-solving, Safety, Effort
• Scenario cards for micro-scenarios
• Safe engineering materials for a short build (e.g., paper/cardboard, tape, straws, connectors)
• Timer
• Student response cards (Earns / Partial / Not yet)
• Redemption menu sheet (choices and conditions)
• Progress-check worksheet with number line or fraction bar
• Exit ticket slips

Assessment

• Formative observation: teacher awards tokens using a simple rubric aligned to the four categories during the task.
• Scenario check: students’ response cards show understanding of what evidence earns tokens.
• Progress math check: exit ticket confirms students can compute rational progress (difference and fraction/ratio).
• Reflection: teacher reviews one written goal to ensure it is behavior-specific and actionable.

Differentiation

• Support: provide sentence starters for token categories and reflection goals (e.g., “I earned a token because I…” “Tomorrow I will…”).
• Support: offer a partially completed progress worksheet (guided fraction/ratio prompts).
• Structured roles: assign partner roles (Materials Manager, Safety Checker, Builder, Recorder) and rotate during the task.
• EAL support: include visual icons for each category and model the “yes/no” examples with gestures.
• SEN support: reduce language load in scenarios by highlighting key words; allow extra processing time before response cards.
• Extension: for students ready for more rigor, ask them to compare two classmates’ progress scores using a ratio and justify which is greater with number-line reasoning.