Day 4: Robots for Crayons Evidence and Action Plan

Daily Learning Contract

• Topic: Manufacturing Troubleshooting
• Objective: Students will identify Manufacturing career opportunities and explain how workers use case evidence to plan a response to two production problems.
• TEKS: d(1)(C)
• Demonstration of Learning: A completed two-problem Robots for Crayons plan with two case clues, a testable solution, ordered steps, tools or adjustments, a time estimate, production effect, and next check for each problem.

Teacher presentation: PowerPoint file (IISD sign-in) · Make a Google Slides copy (IISD sign-in)

Lesson Overview

Warm-Up (5 min)

WARM-UP: A factory machine starts failing right after one part is replaced. What should the team check first, and what evidence would help them decide?

Students complete a 60-second Stop and Jot, then compare one answer with a partner. Listen for a first check that uses the timing of the failure rather than immediately replacing unrelated parts.

Activity 1: Read the Factory Brief and Machine Reference (10 min)

Source: (FYF pp. 200-201: "Robots for Crayons," Steps 1-2)

Teams read the two production problems:

• Color Confusion: boxes have repeated or missing colors, especially Sky Blue and Violet.
• Slowpoke Robot: the arm moves too slowly or misses crayons, creating falls, piles, jams, and stopped production.

Chunk the machine reference into three systems: color sensors, robotic arms, and production lines. After each chunk, ask students to name one possible cause the source actually supports. Record possibilities without choosing a final answer yet.

Activity 2: Read the Shift Evidence by Role (10 min)

Source: (FYF pp. 201-202: "Robots for Crayons," Step 3)

Assign each student one lens: Shift Supervisor, Quality Control Specialist, Maintenance Technician, or Packaging Supervisor. Students mark two clues for each problem and record what their role would check first.

Active Monitoring: Make two laps. Lap 1 target: every student has marked evidence from the shift notes rather than a general guess. Lap 2 target: each team can explain why the replacement color sensor matters to Color Confusion and why the replaced arm belt matters to Slowpoke Robot. If several teams use the software update as proof, pause and distinguish a possible cause from a confirmed cause.

Teacher key:

• Color Confusion: the problem began after the color sensor was replaced; cleaning, lighting adjustment, and recalibration did not solve it. The software update is a possible factor, not proof. A defensible first plan checks compatibility, installation, and controlled testing of the replacement sensor before unrelated repairs.
• Slowpoke Robot: the problem began after the rubber belt was changed; mismatched speeds and belt tension are named causes in the reference. A defensible first plan checks belt size/tension and then retests the arm and conveyor together.
• Accept a different plan when students cite the source, use a safe test, and name what result would lead to the next check.

Activity 3: Brainstorm and Build Both Action Plans (20 min)

Source: (FYF pp. 202-203: "Robots for Crayons," Steps 4-5)

Teams generate ideas for both problems on sticky notes. The workbook suggests at least 15 ideas; protect the quality of the final plan if a group needs to stop below that count. Students then complete the expanded action-plan packet. The packet gives each reasoning job its own writing space instead of forcing steps, tools, time, and production effect into narrow workbook table cells.

Each problem needs:

1. two clues from the source;
2. one selected solution;
3. how the solution works;
4. three ordered steps;
5. tools or adjustments;
6. an estimated time and production effect; and
7. a prevention step or next evidence-based check.

Use a 10-minute checkpoint: students should have both evidence sections and one selected solution. Use a 16-minute checkpoint: students should be writing the second set of ordered steps. If a team cannot name a tool, test, or time, the plan is still an idea and needs another pass.

Exit Ticket (5 min)

Choose one Manufacturing role that would take part in the response. In two or three sentences, explain what that worker would do first and cite one clue from the case.

Collect the action-plan packet. The workbook's Step 6 peer presentation may be used as an early-finisher or next-day feedback routine, but it is not required evidence this week because Day 5 protects the required Xello Matchmaker block.

Differentiation

• Support: Read the shift notes aloud, provide the two-problem packet, and allow students to dictate a plan to a partner or use speech-to-text. Pre-teach evidence, sensor, calibration, belt tension, downtime, and production.
• Extension: Students add a short test-result table showing what the team would do if the first test passes and what it would do if the first test fails.
• ELL: Use bilingual labels: evidence = evidencia, sensor = sensor, belt = correa, adjustment = ajuste, downtime = tiempo de inactividad. Frame: "The clue _ matters because . We will test __ by _____."
• Absence route: Use the embedded workbook images and action-plan packet in Canvas. Complete both plans independently; no robot, group, or presentation is required.