The Rapid Response Roll.

Design v0.1 · Draft · 2026-08-30 · Not yet computing from live data

Every civic-tech tool leans adversarial and loses the internal champions inside city government. The Rapid Response Roll is the counterweight: a public, measured record of the municipal departments and crews that resolve reported hazards fastest. It exists because the DPW crew that filled the pothole in 48 hours deserves the same public visibility as the department that ignored one for 200 days.

1. Why this exists

Fault Line publishes an A–F Shame Index for municipal infrastructure performance because measurement drives accountability. But accountability is bidirectional. A pure-shame model produces three predictable failures:

• It loses public-servant allies. DPW crews and constituent-services staff who want to be effective get lumped with departments that don’t. Over time, they disengage from the platform — the exact opposite of what accountability data is supposed to accomplish.
• It flattens signal. Residents can’t tell the difference between a city that responded fast to their specific report and a city that has a low aggregate grade. Both look bad in the current design. That’s a data-quality failure.
• It gives cities no way to buy their way in. A municipal buyer looking at Fault Line has no visible path to being celebrated by it. That’s a sales-conversion failure that costs the pilot-cities program its most persuasive artifact.

The Rapid Response Roll addresses all three by making fast, verified resolution the same kind of publicly citable civic-performance data that slow response already is.

2. What qualifies as a rapid response

A response is eligible for the Roll when all of these are true:

• Report was community-verified. Only clusters that reached the verification threshold (3 independent reports) count. Random one-off reports don’t enter the calculation on either side of the ledger.
• Resolution is independently verified. Either (a) a repeat-photo verification from a nearby resident confirms the fix, (b) the authority’s own ticket system marked it resolved and a subsequent resident report did not reopen it within 30 days, or (c) both. Authority self-attestation alone is not sufficient.
• Response time was materially below the state statutory window. "Below the statutory window" is not the standard — that’s the legal minimum. The Roll uses fastest-quartile among comparable-severity reports in the peer municipal group. A city that fixes potholes in 20 days when peers take 45 gets a Roll listing; a city that fixes them in 40 days when peers take 45 does not.
• Severity was non-trivial. "Minor" hazard reports don’t count. This prevents a department from farming easy wins by cherry-picking low-severity clusters.

3. Minimum-data threshold

A crew or department appears on the Roll only when its measured performance clears the threshold:

• Volume: at least 10 qualifying resolutions in the trailing 90 days.
• Category breadth: resolutions span at least 3 distinct infrastructure categories — prevents a Roll listing based purely on one easy-to-fix category.
• Community-verification density: the underlying reports were verified by at least 15 distinct reporters across the qualifying resolutions — prevents a single high-volume reporter from tilting the calculation.
• No open counter-signals: the department has no more than 3 open reports past the statutory deadline in the same 90-day window. A fast-response record does not offset an ignored-hazard backlog.

4. Sample display (SAMPLE — not live data)

The Roll is not a fixed leaderboard — a department appears when it clears the threshold and drops off when it doesn’t, on a rolling 90-day window recomputed weekly. Rank ordering is by median days-to-resolution within each category tier, normalized to the peer group.

5. How the ranking works

6. What we deliberately do NOT do

1. Cities cannot pay for a Roll listing. The Roll is not sponsored. This is the same brand covenant as the Shame Index — if it can be bought, it stops being evidence.
2. Authorities cannot self-report resolutions as Roll qualifying. Independent verification (community re-photo or unopposed authority-ticket status + no reopen) is required. Self-attestation is data, but not on its own enough for a Roll listing.
3. The Roll does not cancel out the Shame Index. A city can appear on both. Fast response in one district does not offset systematic neglect in another; the Shame Index measures aggregate municipal performance and the Roll measures crew-level excellence, and they can be simultaneously true.
4. Individual names are not published without opt-in. Department and crew names are public (they’re public employees performing public functions). Individual crew-member names appear only if the department opts in through the pilot-city agreement — some crews will want to be named for morale reasons, others won’t.
5. We do not run negative-space campaigns. A department that drops off the Roll is not called out for dropping off. Absence isn’t evidence; only presence is.

7. How cities are notified when they earn a listing

When a department clears the §3 threshold for the first time, Fault Line sends:

1. A notification email to the authority contact of record: "Your department has earned a Rapid Response Roll listing. Here is the underlying data, the peer-normalized comparison, and a shareable link."
2. A press-ready one-page summary the department can circulate internally, share with the mayor’s office, or send to local media.
3. An embed snippet the city can put on its own website — the same infrastructure that surfaces the Shame Index grade also surfaces the Roll listing when it exists.

The point is to make being celebrated by Fault Line as effortless as being shamed by it is.

8. Guardrails against gaming

Any measurement system that touches performance creates incentives to game the measurement. Design responses:

• Cherry-picking easy categories: handled by §3’s category-breadth requirement (3+ categories).
• Marking-and-forgetting: handled by §5’s follow-up durability weight and by §2’s independent-verification requirement.
• Reporter-side gaming (a friendly reporter submitting many low-severity clusters that will be trivially resolved): handled by §3’s reporter-density requirement (15+ distinct reporters).
• Deprioritizing anything not on the Roll list (a real risk if Roll listings become municipally desirable): handled by §3’s counter-signal cap (no more than 3 open past-deadline reports in the window). If a department is speed-farming Roll qualifiers while ignoring hard hazards, the Roll listing disappears.
• Category boundary manipulation (marking a serious hazard as "minor" so it doesn’t need Roll-tier speed): the resident’s severity rating is the source of truth for eligibility, not the authority’s reclassification.

9. Relationship to the Shame Index

The Shame Index measures aggregate municipal-government performance across an entire jurisdiction. The Rapid Response Roll measures department- and crew-level excellence within a jurisdiction. They are complementary, not opposed:

• A city with an average Shame Index grade can have world-class Roll listings in specific departments — and those listings are the case study for peer cities.
• A city with a strong Shame Index grade may still have specific crews that stand out — and those crews deserve individual recognition, not just aggregate credit.
• A city that ignores everything appears nowhere on the Roll — and prominently on the Shame Index. That’s the design working correctly.

10. Data still needed before this ships

This page is a design commitment, not an operational feature. Before live Roll listings appear, three things must be true:

1. The escalation-log schema captures resolution events with (a) verified-by identifier, (b) resolution timestamp, (c) responsible department where identifiable, and (d) a follow-up-reopen flag on a 180-day timer.
2. Community re-photo verification is a shipped feature in the app (currently in the roadmap; see the changelog).
3. At least one pilot city has agreed to identify its own department/crew mappings for the Fault Line jurisdictional dataset.

Until those are in place, this page is the public commitment to the design principles. See DEFERRED.md #24 for the engineering scope of the underlying data model.

Not sponsored content. Not paid placement. Not a subjective rating. The Rapid Response Roll is computed from measured resolution data with published methodology — the same discipline that governs the Shame Index. Cities cannot buy their way onto or off of the Roll.