A STEM lesson plan should connect the problem, constraints, prototype, test and next design decision. Building something is one stage; explaining why to change it is another.
An original tabletop bridge challenge
Illustrative lesson, not a performed test or structural-engineering specification. The imaginary teacher supplies the following classroom challenge and confirms the actual materials and setup before teaching.
Success criterion: Span a 10 cm gap between fixed supports and hold three teacher-selected identical lightweight tokens for at least 20 seconds under the supplied test procedure.
Constraints: One supplied paper sheet per prototype; no adhesive; fixed supports and gap; the same three tokens, placement and timing procedure for both designs. Sheet size and token specification must be supplied for the real lesson.
| Design proposal | Original sketch description | Question to test |
|---|---|---|
| A: flat | One flat sheet extends between the two fixed supports. | Does it meet the stated load/duration criterion? |
| B: channel fold | The same permitted sheet has its two long edges folded upward, forming a channel between the supports. | Does this construction meet the same criterion? |
Neither proposal has a result yet. Keep the sketches labeled proposed and actual test fields blank. The folded drawing is not evidence of a winning design.
Separate criteria from constraints
The 20-second requirement describes success. The one-sheet/no-adhesive rule limits what can be used. A design that holds the tokens but uses unapproved extra material would not satisfy the declared challenge, while a permitted design that falls at eight seconds would not meet the duration criterion.
That eight-second result is a hypothetical feedback example, not an observation from the class. It supports “did not meet 20 seconds in that trial,” not a claim about the design's maximum load or what its next version will achieve.
A proposed 45-minute design sequence
- Problem, 5 minutes: Establish what needs to be spanned and what the prototype must hold.
- Criteria and constraints, 5 minutes: Read the success rule and allowed materials; identify missing setup inputs.
- Sketch, 8 minutes: Draw the proposed construction and name the feature to compare.
- Build, 10 minutes: Make the teacher-authorized prototypes within the supplied constraints.
- Test and revise, 8 minutes: Use the same conditions, record the result, and propose one change from the evidence. Retest if the actual allocation permits it.
- Share, 5 minutes: Explain the observed result and reason for the revision.
- Cleanup, 4 minutes: Follow the teacher's material-return routine.
The blocks add to 45 minutes. If the real building or testing needs more time, adjust the lesson allocation rather than inventing a completed retest.
Make the revision record useful
Use fields for prototype ID, gap, sheet specification, token set and placement, observation time, result, feature changed, and reason. A learner might propose changing the fold height after a trial; keep it a proposal until built and tested.
If both the fold and token placement change, the comparison no longer isolates that construction change under the same test. Record the changed conditions and avoid attributing the result solely to the fold. Keep the original test alongside the revised one so the explanation remains traceable.
Ask “What did you observe that supports this next change?” rather than “Which design should win?” Actual response fields remain blank before the lesson.
Copy an evidence-led design brief
Create one complete, self-contained US-English HTML companion for “Paper bridge studio • plan and evidence”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Check 20-second criterion; Review supplied trials; Clear trial records; Prepare text; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Draft an original STEM engineering-design lesson in US English.
Class context and duration: [enter or TO CONFIRM]
Design problem and success criterion: [paste]
Authorized materials/time/setup constraints: [paste]
Prototype descriptions and one feature to compare: [paste]
Fixed test gap/load/placement/timing procedure: [paste]
Teacher-supplied participation and cleanup arrangements: [paste]
Plan problem, criteria/constraints, sketch, build, test/revise, share and cleanup;
times must sum to the lesson length. Separate success criteria from constraints. Keep test conditions explicit and identical for the intended comparison. Leave
actual results blank. Label hypothetical evidence separately and judge only
the stated criterion. Connect a proposed revision to the recorded evidence;
do not invent a winner, strength rating, retest, approvals or learning gain.
Return the plan, original sketch descriptions, test fields and revision record. If requested, offer an HTML colleague-review copy comparing the rule, proposals
and blank evidence record. Do not present an animation as a performed test,
claim engineering certification, or collect student results.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# STEM Lesson Plan Template: Give the Design a Criterion and a Fair Test
Two paper bridges look different, but calling the folded one “stronger” before testing it would give the lesson a predetermined answer. State what each design must do, keep the test conditions the same, and ask learners to justify one revision from the evidence they actually record.
A STEM lesson plan should connect the problem, constraints, prototype, test and next design decision. Building something is one stage; explaining why to change it is another.
## An original tabletop bridge challenge
**Illustrative lesson, not a performed test or structural-engineering specification.** The imaginary teacher supplies the following classroom challenge and confirms the actual materials and setup before teaching.
**Success criterion:** Span a 10 cm gap between fixed supports and hold three teacher-selected identical lightweight tokens for at least 20 seconds under the supplied test procedure.
**Constraints:** One supplied paper sheet per prototype; no adhesive; fixed supports and gap; the same three tokens, placement and timing procedure for both designs. Sheet size and token specification must be supplied for the real lesson.
| Design proposal | Original sketch description | Question to test |
| --- | --- | --- |
| A: flat | One flat sheet extends between the two fixed supports. | Does it meet the stated load/duration criterion? |
| B: channel fold | The same permitted sheet has its two long edges folded upward, forming a channel between the supports. | Does this construction meet the same criterion? |
Neither proposal has a result yet. Keep the sketches labeled **proposed** and actual test fields blank. The folded drawing is not evidence of a winning design.
## Separate criteria from constraints
The 20-second requirement describes success. The one-sheet/no-adhesive rule limits what can be used. A design that holds the tokens but uses unapproved extra material would not satisfy the declared challenge, while a permitted design that falls at eight seconds would not meet the duration criterion.
That eight-second result is a **hypothetical feedback example**, not an observation from the class. It supports “did not meet 20 seconds in that trial,” not a claim about the design's maximum load or what its next version will achieve.
## A proposed 45-minute design sequence
- **Problem, 5 minutes:** Establish what needs to be spanned and what the prototype must hold.
- **Criteria and constraints, 5 minutes:** Read the success rule and allowed materials; identify missing setup inputs.
- **Sketch, 8 minutes:** Draw the proposed construction and name the feature to compare.
- **Build, 10 minutes:** Make the teacher-authorized prototypes within the supplied constraints.
- **Test and revise, 8 minutes:** Use the same conditions, record the result, and propose one change from the evidence. Retest if the actual allocation permits it.
- **Share, 5 minutes:** Explain the observed result and reason for the revision.
- **Cleanup, 4 minutes:** Follow the teacher's material-return routine.
The blocks add to 45 minutes. If the real building or testing needs more time, adjust the lesson allocation rather than inventing a completed retest.
## Make the revision record useful
Use fields for prototype ID, gap, sheet specification, token set and placement, observation time, result, feature changed, and reason. A learner might propose changing the fold height after a trial; keep it a proposal until built and tested.
If both the fold and token placement change, the comparison no longer isolates that construction change under the same test. Record the changed conditions and avoid attributing the result solely to the fold. Keep the original test alongside the revised one so the explanation remains traceable.
Ask “What did you observe that supports this next change?” rather than “Which design should win?” Actual response fields remain blank before the lesson.
## Copy an evidence-led design brief
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Check the criterion and test conditions with a teaching colleague before class. Keep both designs unproven until tested, then use the recorded trial to choose and explain the next construction change.