Teacher material · Page · Unpublished in Canvas

Facilitator Guide: Reliability Lab Day 4 — Compare Error Costs

Canvas state
Unpublished

TEACHER ONLY · LESSON GUIDE

Reliability Lab Day 4 — Compare Error Costs

Use this page to run the lesson. The student item directly below remains the independent and absence route.

Daily Learning Contract

Topic: Error consequences and labeling policy

Objective: Students will compare the consequences of false alarms and misses for an intended use and justify a repeatable labeling policy.

TEKS:
  • §126.19(c)(6) — The student uses digital tools to transform data, make inferences, and predictions. The student is expected to use digital tools in order to transform data, analyze trends, and predict possibilities and develop steps for the creation of an innovative process or product.
  • §126.19(c)(12)(A) — integrate use of appropriate technology terminology in scholarly inquiry and dialogue such as classroom discussion and written samples;

Demonstration of learning: Case File page 5 with an observable labeling rule, a false alarm, a miss, and a justified error-cost decision.

Before class

Time: One class period

Student route:
Day 4: Compare the Cost of Mistakes

Use what already exists: Completed Case File pages 2–4; current Day 4 scenario.

Lesson flow

  1. Launch: Use a low-stakes and a high-stakes error scenario.
  2. Model: Model the consequence of a false alarm and a missed case.
  3. Do: Teams apply an error-cost policy to their named use.
  4. Check + support: Ask which error costs more and for whom; use a consequence chart.
  5. Close + handoff: Collect the decision and prepare the model card.

Check before students leave

Ask each student or team to point to the specific evidence named above and explain one choice, test, or revision. Completion alone is not evidence of understanding.

Support + troubleshooting

Scaffold: Keep the visual task sequence visible, assign purposeful partner roles, and use the sentence stems on the student page before simplifying the task.

When stuck: Ask students to show the exact step where the system stopped, then check setup, inputs, and saved work before replacing the task.