Golden rule
The toolbox is national; the rules are local. Each agency’s program dictates eligible streets (functional class, volume caps, transit/EMS routes), petition/scoring process, and allowed devices — see agency notes, and log criteria in each agency note.
Device table
| Device | Targets | Typical context | Watch-outs |
|---|---|---|---|
| Speed hump/cushion | speed | local streets | EMS objections → cushions; drainage |
| Speed table / raised crosswalk | speed + ped crossing | locals/collectors | ADA at crossings; signing/marking per MUTCD |
| Mini-circle / traffic circle | speed + angle crashes at minor ints | local-local | left-turn behavior; truck paths |
| Curb extension/bulb-out | crossing distance, speed at turns | wherever parking exists | drainage inlets; sweepers; bike lane pinch |
| Chicane | speed | low-volume locals | parking loss; delivery access |
| Median island / refuge | crossing, cut-throughs | collectors+ | driveway blocking; width for refuge (verify min) |
| Lane narrowing / road diet | speed / crash types | 4→3 candidates per FHWA guidance | capacity screening first; agency politics |
Free companions
FHWA/ITE Traffic Calming ePrimer — the per-measure authority behind this table: 8 free modules covering 22 measures with design/installation specifics, speed effects, EMS and transit impacts, and program case studies. Cite it when a resident (or reviewer) asks “says who?”
Spawn one treatment note per device as you use it, with CMFs and local examples (Workflow - Comparable Sites Research).
Practice question
Resident petition on a 3,500 ADT collector bus route wants humps — what do you check first, in what order?
QA/QC reminder
Device eligibility verified against THIS agency’s program doc, dated.