6-8 · 55 min · Math · Science · Social Studies · CS/Technology
The plugged companion to Decision Paths: students build a simple spreadsheet model of a real classroom or school question — supplies, lunch lines, a fundraiser — change the inputs, and check the model against reality, meeting modeling and 'what a model leaves out.'
Materials last updated Jun 23, 2026.
55 min in class~15 min prepDevices required
The hookContextualize6m
Fix the misconceptionReframe5m
Do the activityAssemble24m
Check the machineFortify12m
Wrap up + connect forwardTransfer + review8m
Before class~15 min
On devices, open a spreadsheet and build a blank inputs → formula → output model — or use the printed Model sheet (model-sheet.pdf).
Pick a real, measurable question with collectable data (supplies needed, lunch-line wait, a fundraiser total).
Arrange to collect one real value during class (count the supplies, time the line) so teams can check the model against reality.
Teaching one subject? Also print its page: Math proportion-model, Science model-vs-data, Social Studies budget-tradeoff, or CS variables-abstraction.
Model the Question
Make it yours
One lesson, woven into your subject
No co-teacher needed. Open your subject for a single card with the core
content you teach and the specifics for weaving this lesson into
your room — nothing to look up elsewhere.
Topic refresher
New to a concept? Tap a topic for a printable cheat sheet — plain-language definitions and classroom examples.
Teacher cheat sheet · refresher
Model the Question
6-8 · 55 min · Math · Science · Social Studies · CS/Technology
Woven together — one idea, every subject
One idea runs through every subject here: a model turns a real question into inputs → a formula → an output you can act on — and because a model is a deliberate simplification, its confident number is a prediction to be checked, not a fact. Proportional reasoning, scientific models, civic trade-offs, and abstraction are all that same move.
Math — Write output = rate × input; check it scales proportionally.
Science — Run the model, then check its prediction against data.
Social Studies — Change a budget input; watch who gains and who loses.
CS/Technology — Name the variables; state what the model ignores on purpose.
Concepts in this lesson
Abstraction & modeling
Abstraction means hiding detail to focus on what matters; a model is a deliberately simplified stand-in for something real that you can study, run, or predict with.
ExampleA subway map (an abstraction that drops real geography) or a paper "model" of a population you step forward round by round to predict what happens.
Key wordsmodel · simplify · abstraction · predict
Watch forEvery model leaves things out. The useful question is not "is it true?" but "what did we ignore, and does that break the prediction?"
Variables
A variable is a named container that holds a value which can change — like a labeled box or a scoreboard whose number you can update.
ExampleA "score" you raise and lower during a game, or a "name" slot a greeting fills in — the label stays the same while the contents change.
Key wordsvalue · name/label · update · store
Watch forStudents confuse the variable's name with its current value. The label is fixed; the value inside is what changes.
Validation & data integrity
Validation is checking that data is reasonable and complete before you trust it; data integrity is keeping that data accurate and uncorrupted as it's stored or passed along.
ExampleCatching an "age" of 200 or a blank required field on a class survey before it pollutes the results.
Watch for"It looks fine" is not validation. Decide the rules for acceptable data first, then check every entry against them.
Run it in your subject — core content + how it weaves in
Math
Write output = rate × input; check it scales proportionally.
Core content6.RP.A and 7.RP.A.2 are proportional reasoning: a ratio or unit rate relates two quantities, and in a proportional relationship doubling one quantity doubles the other (a straight line through the origin). MP.4 — 'model with mathematics' — is writing the equation that links them. In plain terms: find the rate, write output = rate × input, and confirm the output scales the way a true proportion should.
Standards6.RP.A · 7.RP.A.2 · MP.4
Weave it inThis is proportional reasoning made operational, serving 6.RP.A and 7.RP.A.2 (rates, ratios, proportional relationships) and MP.4 (model with mathematics). Run it as: (1) build the formula linking inputs to output (students × sheets-each = paper needed; people ÷ rate = wait time); (2) change one input and predict the new output before recomputing; (3) confirm the relationship is proportional by checking that doubling an input doubles the output. Watch the misconception that every relationship is additive or linear — have students test whether the output scales proportionally. Quick assessment: students predict an output for a changed input, then verify it against the recomputed cell and explain any difference.
Science
Run the model, then check its prediction against data.
Core contentThe MS science-and-engineering practice of developing, using, and evaluating models means building a representation of a phenomenon, using it to predict, and judging it against real measurements. In plain terms: a model is a stand-in for the real thing — you run it to see what it predicts, then compare to data, and a gap can be a genuine error OR a simplification you chose on purpose.
StandardsMS SEP: models
Weave it inThis frames the spreadsheet as a scientific model validated against data, serving MS SEP (developing, using, and evaluating models). Run it as: (1) model a measurable phenomenon (plant growth, cooling, distance over time); (2) run 'what if' changes to predict behavior; (3) collect real measurements and compare them to the model's prediction. Watch the misconception that a mismatch automatically means the model is 'wrong' — distinguish a genuine error from a simplification the model made on purpose. Quick deliverable: a model prediction, the measured value, and a one-sentence explanation of the gap.
Social Studies
Change a budget input; watch who gains and who loses.
Core contentC3 D2.Eco covers scarcity and allocation: resources are limited, so every choice about who gets what forces a trade-off. Decision analysis lays out options and their consequences. In plain terms: a budget line, a vote tally, or a price is an input you can change, and changing it shifts who is better and worse off — the math shows the result, but the values question is who it should favor.
StandardsC3 D2.Eco · decision analysis
Weave it inThis models civic and economic trade-offs, serving C3 D2.Eco (scarcity, allocation) and decision analysis. Run it as: (1) model a budget, a vote tally, or a resource allocation with inputs and a formula; (2) change an input (a price, a turnout rate, a split) and observe who gains or loses; (3) identify the trade-off each scenario forces and who is affected. Watch the misconception that the model's numeric output is automatically the 'fair' answer — separate what the math says from what the values question asks. Quick deliverable: two 'what if' allocations compared, naming who is better and worse off under each.
CS/Technology
Name the variables; state what the model ignores on purpose.
Core contentCSTA 2-DA-09 and 2-AP-16 cover models/simulations and using variables and abstraction in programs. In plain terms: a variable is a named value the model uses, abstraction means keeping only the details that matter for the question and dropping the rest, and validation means testing the output against a real value to decide whether a gap is a bug or an intended simplification.
StandardsCSTA 2-DA-09 · CSTA 2-AP-16
Weave it inThis makes abstraction and validation concrete, serving CSTA 2-DA-09 and 2-AP-16 (models, variables, abstraction). Run it as: (1) name each variable and the formula relating them; (2) state explicitly what the model includes versus deliberately ignores and why; (3) test the model against a real value and decide whether a gap is a bug or an intended abstraction. Watch the misconception that a more detailed model is always better — discuss how a good abstraction keeps only what matters for the question. Quick deliverable: a labeled inputs-formula-output model plus a short list of what it abstracts away on purpose.
Loom & Lesson — printable teacher refresher · Model the Question
Overview
The screen-side twin of Decision Paths. Students turn a real
classroom/school question into a small spreadsheet model: inputs feed a
formula that produces an output. They change inputs to ask “what if,” then check
the model against a real measured value — meeting modeling, variables, and the
crucial idea that a model is a deliberate simplification. Aim the question at
whatever you teach.
A base integrated lesson (plugged) — math and science modeling students can
steer toward whatever they teach — run it in your room as-is.
Pre / Post assessment
Pre: “How could a spreadsheet help you answer ‘how many supplies do we need?’ before buying any?”
Post: “Your model predicted X; reality was Y. Is the model wrong, or did it leave something out on purpose?”
Objectives
Students will (1) build an inputs→formula→output model, (2) run “what if”
scenarios by changing inputs, and (3) validate the model against real data.
CONTEXTUALIZE — why it matters
Engineers, scientists, and planners build a model before they pour concrete,
plant a field, or launch a program — modeling is how people turn a question into
a prediction they can act on. The tools your community will lean on tomorrow —
in hospitals, on farms, in city budgets, in the software that runs them — are
built by people who can name the inputs, write the formula, and stay clear
about what the model leaves out. A spreadsheet is just one instrument here, and
the student who learns to interrogate a prediction is the one who gets to decide
what gets built and whether to trust it.
REFRAME — surface the wrong model, install the right one
Students think a model must capture everything. Reframe: a model is a chosen
abstraction — keep the inputs that matter, drop the rest — and its output is
a prediction to be checked, not a fact.
ASSEMBLE — I do / we do / you do
I do: Build a 2-input model (e.g., students × sheets each = paper needed); change an input.
We do: Add a third variable and a clear output cell together; predict before recomputing.
You do: Teams model their assigned question and run three “what if” scenarios.
FORTIFY — Check the Machine
Collect a real value for the thing modeled (count the actual supplies used,
measure the actual line). Compare to the model’s prediction and explain the gap:
a missing variable, an oversimplified rate, real-world messiness. Students
distinguish “the model is buggy” from “the model abstracts that away on
purpose.” A prediction earns trust only when checked against reality.
TRANSFER — forward
Tie back to Decision Paths: a model can inform a branch in the decision tree.
Forward: weather, traffic, infrastructure, and budget tools are bigger versions of this — built by engineers and scientists whose communities depend on them. The student who can build and question a model is on the path to being one of the people who decides what those tools should account for.
What to listen for
Use the Post prompt — “Your model predicted X; reality was Y. Is the model wrong, or did it leave something out on purpose?” — as your read on mastery.
Proficient: distinguishes a bug from an on-purpose simplification. “Model said 240 sheets; we used 210. Not wrong — it assumed everyone was present. Add an attendance input.”
Getting there: sees the gap but calls the model “wrong.” Nudge: “Is it a mistake, or did it leave something out on purpose — and which?”
Not yet: trusts the output because the cell looks tidy. Reframe: the number is a prediction to check, not a fact.
Proficient when a team builds an inputs → formula → output model, predicts the effect of changing an input before recomputing, and explains a gap as either a bug or a deliberate abstraction.
Differentiation
6-8 support: provide the spreadsheet skeleton; students fill inputs and one formula.
Extension: add a chart of output vs. an input, or a simple random element to simulate variation.
3-2-1 Review
3 inputs in your model · 2 “what if” runs · 1 thing your model
leaves out on purpose.
Family / community connection
“Model a household question in a spreadsheet (grocery cost, road-trip time),
then check it against what actually happens.”
The national computer-science learning standards from the Computer Science Teachers Association.
2-DA-09+
Data & Analysis strand, grades 6–8
CS/Technology:CSTA 2-DA-09 and 2-AP-16 cover models/simulations and using variables and abstraction in programs. In plain terms: a variable is a named value the model uses, abstraction means keeping only the details that matter for the question and dropping the rest, and validation means testing the output against a real value to decide whether a gap is a bug or an intended simplification.
2-AP-16+
Algorithms & Programming strand, grades 6–8
CS/Technology:CSTA 2-DA-09 and 2-AP-16 cover models/simulations and using variables and abstraction in programs. In plain terms: a variable is a named value the model uses, abstraction means keeping only the details that matter for the question and dropping the rest, and validation means testing the output against a real value to decide whether a gap is a bug or an intended simplification.
Standards for how students use technology to learn, from the International Society for Technology in Education.
ISTE-5b+
Computational Thinker (Standard 5)
ISTE-5c+
Computational Thinker (Standard 5)
Common Core State Standards — Mathematicsreference ↗
The Common Core math standards used by most U.S. states.
6.RP.A+
Ratios & Proportional Relationships, grade 6
Math:6.RP.A and 7.RP.A.2 are proportional reasoning: a ratio or unit rate relates two quantities, and in a proportional relationship doubling one quantity doubles the other (a straight line through the origin). MP.4 — 'model with mathematics' — is writing the equation that links them. In plain terms: find the rate, write output = rate × input, and confirm the output scales the way a true proportion should.
Math:6.RP.A and 7.RP.A.2 are proportional reasoning: a ratio or unit rate relates two quantities, and in a proportional relationship doubling one quantity doubles the other (a straight line through the origin). MP.4 — 'model with mathematics' — is writing the equation that links them. In plain terms: find the rate, write output = rate × input, and confirm the output scales the way a true proportion should.
You just read a free Math lesson. There are 30 more, going deeper.
The Educator plan ($9/mo) unlocks the standards-aligned Math library
for your grade band — extended lessons, slides, answer keys, and standards maps. Advanced adds PD contact-hour certificates for license renewal.