Today we check our builds with numbers. How will we know a change made a build stronger: because it looks tougher, or because it holds more?
Keep this as a short curiosity hook — no loading yet. Point at one finished build from earlier in this project (do not load it yet). Ask for hands: look tougher, or holds more? Steer the class to the number held.
Link to the project: groups already have a full-size load-bearing build and success criteria from earlier sessions (for example hold four library books, hold a tablet without tipping, take wet coats). Keep those criteria on the wall or IWB in one line per group if useful.
Key question: Engineers show an improvement with a measurement, not an opinion. What number will we write down today?
The big idea today is the load test. You add the real load carefully and write the number held.
Will one change make that number go up?
Board stays short: one big idea (load test = write the number held) and the question. Bring in one change as the label when groups fix, and evidence when they compare before and after numbers. Use the full table below yourself; do not project it.
| Concept | Why it matters | Example |
|---|---|---|
| Load test — adding the real load (or the same weights) slowly until the build fails or hits the target, then recording the number held | Without a number, nobody can tell if a later change helped | A tablet stand holds the tablet plus two books before it tips: the number held is 3 items |
| One change — a single fix to the weakest shape or join so the test stays fair | If you change three things at once, you cannot say which fix earned the gain | Only add a triangular brace under a sagging beam; do not also swap the tape and thicken the legs |
| Evidence of improvement — the after number is higher than the before number | Engineers show a fix worked with a measurement, not by saying it looks stronger | Held 4 coats before a gusset was added and 8 after: the gain is 4 |
Worked model (keep inside five minutes): Pre-load the demo scrap span once before the lesson (or in the first 30 seconds) and write before: 6 on the board so the class does not wait through two full load-to-failure runs. Live, think aloud only the change and the re-test:
Misconception to head off: children may say the build is better because it looks neater. Keep asking what do the numbers say?
Ideas they may use for the one change (from earlier in this unit): triangle brace; arch or rolled tube for a weak middle or beam; taped triangular gusset instead of plain tape; stop a pivot join that should not move.
Load your build the way your job needs: books, a tablet, coats, or the same weights every time.
Before you start: choose one loader, one counter, one safety spotter. Agree what counts as failure (sag, tip, peel, or collapse).
Add the load slowly. Keep it low, near the desk or floor. Stop when it fails or you hit your target.
Write the number held as your before result on your PrototypeEval journal page (the load-test sheet with the before and after rows).
Fallback if a full prototype is missing or damaged: that group uses their half-size test piece from earlier in the project, or a quick scrap span like the teacher demo, still with an agreed load and a clear failure rule. A low before number is still useful data.
Groups collect the build they made earlier in this project, their Design Brief success criteria, and the real load or agreed weights. Clear floor space so nobody stands under a failing build.
What good looks like: a clear before number and a named weak point (for example middle of flat beam, tape peel at a join, tip at the front feet).
If a build fails immediately: record held = 0 or 1, name the fail point, and move to peer advice. The low number is still useful data.
Label in talk: this is the load test and the before number.
Differentiation: less confident groups use large easy-to-count loads (books). Confident groups may use smaller units (coins in a tub) for a finer number, still one agreed unit.
Builds stay where they are. Visit another group's station and look for the weakest shape or join. Tell them one idea that could strengthen it: a triangle, a stronger middle or beam shape (like an arch or rolled tube), or a stronger join. Listen to their advice for your build. Choose one change only.
In-place peer visit (do not move full-size builds): prototypes stay on their desks or floor spots. Pair neighbouring groups. About 3 minutes looking at the host build, 2 minutes giving advice, then reverse so each group hosts and visits (about 7 minutes total including the reverse). Keep advice tied to ideas from earlier in this unit (triangles hold shape; arches and braced middles or beams; gussets and firm joins versus pivot joins).
Sentence stems to post: The weakest part we see is… One idea that might help is… because…
Your job while circulating: stop groups from listing five fixes. They may hear several ideas but must pick one change to make next. Write that one change on the PrototypeEval or ResultsAndConclusion page before they touch materials. Block any attempt to drag a coat rail or shelf across the room.
Fold the class in: after one pair of groups shares aloud, ask the room Do you agree that is the weak point? Which idea matches: triangle, stronger middle shape, or stronger join?
1. Make only your one change. When the teacher calls stop, put tools down even if the fix is simple.
2. Load the same way as before — same load, same place, same slow method. Keep the load low, near the desk or floor.
3. Write the after number on the after row of your PrototypeEval page (the load-test sheet).
4. On your ResultsAndConclusion page (the results sheet) write: before number · one change · after number · gain.
5. Gain = after minus before (after take away before). If it went up, write the gain. If it stayed the same or went down, write stayed the same or went down / no gain.
Timing (protect the re-test — say the stop aloud and keep it on the board): hard mid-step stop after about 6–7 minutes of fixing. Call a 2-minute warning, then every group re-loads even if the fix is simple. Roughly 6–7 minutes to make the change, 5–6 minutes to re-load and record. Journal order after the re-test: after row on PrototypeEval first, then before / one change / after / gain on ResultsAndConclusion. Pre-cut triangle and gusset scraps sit on the central tray so groups are not cutting from scratch. Tape-only fallback: a single taped triangle or taped overlap is enough for a valid after number.
Journal (both pages): PrototypeEval completes the after row (number held and where it failed or sagged). ResultsAndConclusion holds before number, the one change in plain words, after number, gain (after take away before, or stayed the same / went down), and a one-line conclusion (The change worked because… or The number did not rise, so next time we would try…). Label the rise (or flat or lower result) as evidence.
Unexpected results are data: if the number falls, that is still science. Ask what the change may have weakened. Pupils write went down / no gain, not a blank.
Safety: same as the first load. Adult help for difficult cuts. Spare tape, pre-cut card strips, split pins and gusset scraps on a central tray so groups are not hunting the cupboard.
You're previewing this lesson. Get full access to this lesson and hundreds more — each one ready to teach, with interactive activities, printable resources and pupil progress tracking built in.