Plan the Road Trip

Overview

A summer road trip becomes a map of towns (nodes) and roads (edges). Students pick a start and a destination, find a good route, and add up the miles to prove it. Then the real lesson: the “best” route depends on what you’re trying to save — fewest miles, least time, or cheapest gas — and those can be different routes. They’ve met graphs and shortest-path reasoning, the everyday math behind every navigation app. Point the trip at whatever you teach.

A base integrated lesson — pathfinding and trade-off thinking that any single-subject teacher can run as-is, with a callout for your subject. Unplugged core plus a plugged twin.

Pre / Post assessment

• Pre: “If two roads both get you to the lake, how would you decide which to take?”
• Post: “Your route had the fewest miles. When might a longer route still be the better choice?”

Objectives

Students will (1) model a set of places and routes as a graph with weighted edges, (2) find and verify a shortest route between two points, and (3) explain how the “best” route changes when the goal changes.

CONTEXTUALIZE — why it matters

Every map app, delivery network, and emergency-routing system answers one question millions of times a second: what’s the best way from here to there? The “best” hides a choice — fewest miles, least time, least fuel, avoid the highway — and that choice has real consequences for real communities (a route optimized only for speed can pour traffic down one neighborhood’s street). The students who learn to model connections and ask “best for whom?” are the ones equipped to design the systems that move people, packages, power, and help — and to make those systems serve the people who depend on them.

REFRAME — surface the wrong model, install the right one

Students think the best route is “the straight line” or “the one I know.” Reframe: the map is a network of connections, and the best route is the one with the smallest total for the cost you care about — which often isn’t the straightest line, and changes the moment you change the goal.

ASSEMBLE — I do / we do / you do

• I do: On the map, total the miles for one route from start to finish; state it as the route to beat.
• We do: Find a second route between the same two towns; compare totals; keep the smaller.
• You do: Teams find the shortest route for their trip, then find the fastest route (using road speeds) and notice whether it’s the same.

FORTIFY — Check the Machine

The verification is the lesson: a route isn’t “shortest” until you’ve checked an alternative. (1) Add up the roads on the chosen route. (2) Find at least one different path between the same two towns and total it. (3) If the alternative is shorter, the first answer was wrong — fix it; if not, you’ve earned the claim. Then the “errors are features” twist: hand teams a map where the route with the fewest stops is longer in miles than a route with more stops. The check reveals that “fewest steps” and “shortest distance” are different goals — a correct method for one can lose for the other. Choose what “best” means before you trust the answer.

TRANSFER — forward + plugged twin

• Forward: “Where else is something finding a ‘best path’ for you?” (a package crossing the country, water through pipes, a message across the internet). Name the bigger arc: the students reasoning about these routes now are the future engineers who decide how a community gets where it needs to go — and who the route should serve.
• Plugged twin (+15 min): open a map app, route the same trip, and switch between fastest/shortest/avoid-highways — watch the route change with the goal. Or build a tiny mileage table in a spreadsheet and sum candidate routes.

What to listen for

Use the Post prompt — “Your route had the fewest miles. When might a longer route still be the better choice?” — as your read on mastery.

• Proficient: names a real trade-off beyond distance. “A longer highway route is faster and skips the closed bridge — fewest miles isn’t always best.”
• Getting there: finds the shortest but treats distance as the only goal. Nudge: “What else could matter — time, tolls, safety?”
• Not yet: assumes shortest miles is best, unchecked. Reframe: ‘shortest’ isn’t earned until you’ve compared an alternative.

Proficient when a team totals the chosen route, compares at least one alternative between the same towns, and names a trade-off where a longer route could win.

Differentiation

• K-2 adaptation: use 4–5 towns and whole-number “blocks” instead of mileage; the route is “count the blocks.”
• 3-5: 8 towns, two-digit mileages, find the shortest route.
• 6-8 extension: add road speeds to compute time; compare shortest vs. fastest; introduce the idea that more connections make the problem harder.
• 9-12 bridge: name the algorithm (always extend the cheapest-known frontier) and connect to the subject-tier Road Trip Router drop.

3-2-1 Review

3 roads on your route · 2 totals you compared · 1 trip where “best” means something other than shortest.

Family / community connection

“Plan a real local trip with a grown-up — to the store, a relative’s, a park. Find two ways there and decide which is ‘best,’ and say what ‘best’ meant to you.”