Back to playbooks

Module: Transportation (Captivity + Fair Terms + Reliability)

Purpose: lower the monthly squeeze by making transportation less of a money trap and less of a daily gamble.

This module is designed to be runnable by normal people in small weekly sprints.

What is happening (1-2 sentences)

Transportation squeezes households through vehicle costs, insurance, repairs, and unreliable non-car alternatives.

The trap gets worse when people cannot realistically opt out.

Why it is happening (mechanism, plain language)

Transportation often mixes two different systems:

A) household traps in vehicle pricing, financing, insurance, and repair
B) reliability failures in transit, walking access, and work access

Both matter, but they do not move through the same targets.

That is why the practical rule is: pick your battlefield before you pick your ask.

What good looks like (principle)

A healthier transportation system has:

• clear all-in prices before anyone signs anything
• add-ons that are actually optional
• insurance rules people can understand
• repair choices that are real, not fake
• reliable routes and last-mile connections
• fewer choke points where one missed connection wrecks the day

Choose your battlefield

Battlefield A: Household traps

Run this when the main harm is vehicle pricing, financing, insurance spikes, or repair lock-in.

Battlefield B: Reliability and non-car access

Run this when the main harm is route unreliability, winter access, missing sidewalks, or weak work access.

Default plays (recommended)

Default Play A: All-in pricing and add-on cleanup

Run this when people are getting trapped at the point of sale.

One Ask (template): Require all-in vehicle pricing, clear opt-in for add-ons, and quarterly complaint reporting on financing and add-on abuses.

Minimum components:

• all-in price at offer
• add-ons separately approved
• complaint channel
• quarterly reporting

Why it wins: It is concrete, consumer-facing, and easier to explain than a giant transportation theory.

Default Play B: Reliability on one corridor

Run this when the main pain is getting to work, school, or care reliably.

One Ask (template): Publish monthly reliability on one key route or corridor and improve it by 15% within 6 months, with one named owner and one choke-point fix plan.

Minimum components:

• route or corridor selected
• monthly reliability metric
• top choke points identified
• winter maintenance or last-mile gap note if relevant

Why it wins: It forces the system to measure the daily reality people actually experience.

Definition of Done (every module sprint)

At the end of any Transportation sprint, you should have:

1. One ask
2. One target map
3. One 1-page ask memo (250-400 words)
4. One 90-second testimony script
5. One scoreboard stub (3-5 metrics + data source)
6. One follow-up date
7. One public-record step if ignored

Target map (who can say yes)

Household-trap targets

• state attorney general or consumer protection office
• state insurance regulator
• dealer licensing or motor-vehicle regulator
• city or county consumer-protection office where relevant

Reliability targets

• transit GM or operations lead
• city public works or transportation department
• county transportation lead
• employer or institutional mobility coordinator for corridor pilots

Civil society and amplifiers

• commuter groups
• legal aid or consumer advocates
• disability and accessibility advocates

Receipts stubs (what to gather before you argue)

You only need a few items to build shared reality.

Household traps:

• sample dealership listings and fee breakdowns
• complaint stats if available
• insurance renewal notices with large spikes
• repair estimates for common fixes

Reliability and access:

• route reliability dashboard or PDF
• public works maintenance reports
• sidewalk or stop access gaps
• winter response or clearance timing

If the data is not published, asking for the dashboard may be the first win.

Escalation ladder (what to do when ignored)

Level 1 - direct ask

• email staff owner + elected sponsor with one-page memo

Level 2 - office hours

• ask who owns the reporting, complaint tracking, or corridor fix plan

Level 3 - public record

• testimony at council, board, or agency hearing

Level 4 - accountability move

• records request, complaint data ask, or performance dashboard request

Level 5 - budget or rule change

• add reporting requirement, corridor funding, or consumer-protection rule

Scoreboard (choose 3-5 metrics)

Pick a small set that matches your play.

If running Play A (household traps)

• share of offers with clear all-in pricing
• add-on complaint rate
• yo-yo financing complaints
• insurance renewal spikes above threshold
• repair-cost spread for common fixes

If running Play B (reliability)

• on-time performance or headway reliability
• average trip-time reliability
• top choke-point delay
• last-mile access gap count
• winter response time on priority corridors

60-minute Transportation Sprint (minimum viable)

If you only have an hour:

1. 10 min: pick household traps or reliability
2. 10 min: build your target map
3. 20 min: write the one-page ask memo + scoreboard stub
4. 10 min: send two emails
5. 10 min: schedule follow-up + log

Done. Repeat next week.

One Ask examples (ready to use)

• “Require all-in vehicle pricing and clear opt-in for add-ons, with public complaint tracking by quarter.”
• “Publish insurance renewal spike data and hold automatic review above a clear threshold.”
• “Adopt a fair diagnostics rule for independent repair shops and track repair-cost differences.”
• “Publish route reliability monthly and improve Corridor X by 15% within 6 months.”

Bridge language (calm, non-tribal)

• “Transportation is a money problem and a time problem.”
• “If people cannot realistically opt out, the rules need to be cleaner.”
• “Reliability is affordability.”
• “Let us fix the traps we can name and measure.”

Weekly cadence (how to keep it small and real)

• Week 1: pick the battlefield + send the ask
• Week 2: office hours or staff follow-up
• Week 3: public record step
• Week 4: follow-up for inclusion and reporting

Then repeat or pivot based on what moved.

Back to playbooks