How a small group of neighbors got a protected crosswalk installed near an elementary school, and the exact playbook you can reuse for your block.
The quick version (TL;DR)
-
Problem: Cars were speeding past an unmarked crossing used by kids and seniors.
-
Goal: Install a high-visibility, ADA-compliant crosswalk with signage by Day 90.
-
Levers: Transportation department (TD) work order + small capital line in the city’s traffic-calming program.
-
Result: Crosswalk installed on Day 83; follow-up speed survey showed average speeds down 7% and yielding up 23%.
Why this works
Small, specific fixes (crosswalks, bus shelters, curb ramps, shade trees) live inside existing city programs. That means you don’t need to pass a law, you need to surface data, show support, and trigger an administrative decision tied to clear standards.
The 90-day playbook (steal this)
Weeks 1–2: Define the ask and collect receipts
-
Pick one location + one intervention. (e.g., “Install a high-visibility crosswalk across Maple Ave at 3rd.”)
-
Gather evidence:
-
10–15 geo-tagged photos/video at school arrival/dismissal and evening rush.
-
A quick neighbor survey (Google Form) capturing “how often you cross here,” “near misses,” and zip code.
-
Crash/safety context: prior police or 311 reports if you have them.
-
-
Draft a one-pager: problem, proposed fix, why it qualifies (school zone, senior center, bus stop), and a polite 150-word memo to the Transportation Department (TD).
Weeks 3–4: Build visible, local support
-
Petition: 150–300 signatures from immediate blocks + school community. Include a checkbox for “I can attend a meeting.”
-
Stakeholder calls: principal, crossing guard captain, ADA advisory council member, nearby small businesses.
-
Two quotes: one from a parent/caregiver, one from a senior or mobility-impaired neighbor.
Weeks 5–6: File the request and put it on a public agenda
-
Submit to TD via the official traffic-calming or “quick build” request portal (or email if no portal).
-
Ask for an item on the next Traffic & Parking Commission/Committee (TPC) agenda (or equivalent).
-
Confirm standards: cite the city’s crosswalk warrant policy or Vision Zero plan language if available.
Weeks 7–8: Do the hearing well
-
Prep speakers: 3–5 neighbors with 60–90 seconds each; no more.
-
Bring a one-page handout: map, photos, petition count, and the exact language you want adopted (“Direct TD to install…”).
-
Leave with a verb: aim for a motion directing TD to evaluate and, if it meets standards, install by a set date—or to bring back an implementation plan.
Weeks 9–10: Follow the paper and remove excuses
-
Inside baseball: ask the staffer which work order number will track the installation; note any procurement or weather holds.
-
Problem-solve fast: if the delay is paint availability, offer an alternate approved marking; if it’s a utility conflict, ask staff to adjust the placement 5–10 feet.
Weeks 11–12: Lock the date and show up
-
Confirm install week in writing.
-
Safety day: a small volunteer crew does “slow down” outreach with the school/center the morning after installation.
-
Document impact: repeat 15-minute yield counts and basic speed observations at the same times as baseline.
The artifacts (copy/paste)
1) Petition text (150 words)
We, the residents, parents, and neighbors near Maple Ave & 3rd, ask the City to install a high-visibility, ADA-compliant crosswalk with advance “Yield to Pedestrians” signage. This crossing serves [School/Center], a bus stop, and many seniors. Photo/video evidence (attached) shows frequent close calls and driver failure to yield. The City’s [Traffic Calming / Vision Zero] policy prioritizes school-area safety. We request staff evaluate per adopted standards and, if warranted, install by [DATE] as a Quick-Build measure. Sign to support; check the box if you can attend the hearing.
2) Email to Transportation Department (intro + attachments)
Subject: Request for high-visibility crosswalk at Maple & 3rd (School Zone)
Hello [Staffer Name],
On behalf of neighbors and [School], we’re requesting a high-visibility crosswalk at Maple & 3rd. Attached: a one-pager, 40 photos, a 2-minute compilation video, and 243 petition signatures. This meets [policy/standard] as a marked school-area crossing. Could you share the evaluation timeline and the work order number once created? We’re also requesting a Traffic & Parking agenda slot in [Month].
Thanks so much,
[Name], [Phone], [Address]
3) 60–90 second hearing script (pick one speaker per bullet)
-
Open with clarity (15s): “We’re asking for a high-visibility crosswalk at Maple & 3rd by [DATE].”
-
Evidence (30s): “Here are AM and PM videos showing kids stepping into traffic; yielding is under 50%.”
-
Policy match (20s): “Your adopted school-zone standard and Vision Zero plan prioritize this exact fix.”
-
Community voice (20s): “You have 243 local signatures; PTAs and [Senior Center] support.”
-
Close (10s): “Please move to direct staff to evaluate and, if warranted, install by [DATE], and report back if anything blocks the timeline.”
4) One-pager outline (front of handout)
-
Header: “Install a High-Visibility Crosswalk at Maple & 3rd by [DATE]”
-
Map + photo strip (AM/PM)
-
Why now: school zone, bus stop, prior 311s (bullets)
-
What we’re asking: crosswalk type, signs, curb paint; “Quick-Build eligible”
-
Support: petition count + logos (PTA, Senior Center, Business Assoc.)
-
Contact: lead organizer + TD staff email for updates
Measuring the win
-
Before/after yield rate: 20 random crossings each period; count driver behavior.
-
Average speed at free-flow: quick radar or “two-point timing” with a phone and a friend.
-
Near-miss log: ask the school/center to track for 30 days.
-
Satisfaction pulse: 3-question survey to the same list you used for the petition.
Common pitfalls (and fixes)
-
“Come back next year.” Ask which standard is unmet. If it’s volume, propose a pilot marking during school hours.
-
“No budget.” Ask to classify as maintenance or a quick-build (paint/posts) while capital is queued.
-
“We need a study.” Request a 30-day evaluation with a report-back date; offer volunteer counts to speed it up.
-
Diffuse asks. Keep it to one location, one treatment. Win it, then replicate.
Template timeline you can drop into your city
-
Day 1: Name the location + fix.
-
Day 7: Evidence packet complete.
-
Day 14: Petition hits 150; TD request submitted.
-
Day 28: TPC agenda confirmation.
-
Day 42: Hearing + motion adopted.
-
Day 60: Work order issued; install week penciled.
-
Day 83: Installation.
-
Day 90: Publish results; thank staff publicly; queue next site.
Make it public (so it scales)
-
Post the one-pager and evidence folder.
-
Share the work order number and install week—neighbors love following along.
-
After installation, publish your before/after counts and credit the city team by name.
Closing
Policy changes don’t always require a march. Sometimes they’re a memo, a motion, and a few mornings of patient counting. Pick one corner. Get organized. Win once. Then show your neighbors how to copy it. And if you want a low-key conversation starter at your next count shift, our “No Bans, Just Books” tote sits nicely on the table while you collect signatures.
0 comments