When Enforcement Becomes a Financial Shock: The Case Against Automated Ticketing

Last Saturday evening, my car was towed. Not because it was blocking a fire hydrant. Not because it posed an immediate safety risk. But because the city was preparing for a snow day.

As D.C. mobilized tow trucks en masse — clearing routes, staging for weather, doing what cities do in anticipation of disruption — my vehicle was flagged because I have unpaid tickets. Tickets that, candidly, I haven't stayed on top of. Not out of indifference, but because my current financial situation has made even relatively "small" obligations harder to manage than they once were.

The tow itself was the kind of experience that compresses time and perspective: the scramble to locate the car, the realization of compounding fees, the immediate logistical disruption, the sense that something administrative had quietly turned punitive. And it got me thinking — less about my own situation than about automated ticketing as a city policy, and whether we've ever really asked citizens if this is how we want traffic safety enforced.

From Personal Inconvenience to Public Policy

D.C.'s automated traffic enforcement regime didn't arrive all at once. It accreted over time. Red-light cameras were introduced in the late 1990s. Speed cameras followed in the early 2000s. Stop-sign enforcement came later. Bus lane and other automated enforcement tools expanded as technology matured and as the city's ambitions for Vision Zero took shape in the mid-2010s.

From a legal standpoint, this was orderly. The Council acted. Agencies implemented. Vendors were procured. The system scaled. From a democratic standpoint, something else happened: a qualitatively new enforcement regime became permanent without ever being put directly to voters. That matters because automated enforcement is not simply "more tickets." It is infrastructure. It is always-on. It is automated. It is financially consequential. And once installed, it becomes difficult to unwind.

Was Unsafe Driving a Real Problem in D.C.?

Yes. And it's important to acknowledge that plainly. In the 1990s and early 2000s, traffic fatalities in D.C. were materially higher than they are today. Unsafe and aggressive driving was a persistent concern in public discourse. Over time, that concern crystallized into Vision Zero — a formal commitment to eliminate traffic deaths and serious injuries.

Automated enforcement grew alongside that evolution. It was presented, credibly, as one tool among many: alongside road design, signal timing, public awareness, and later, data-driven safety strategies. So the question is not whether safety concerns were real. They were. The question is different: even if safety concerns motivated adoption, does that justify an intrusive, automated, financially punitive system that citizens never explicitly approved? That's a legitimacy question — not a safety question.

Why This Feels Different to Citizens

Automated enforcement changes the citizen experience in three fundamental ways. It removes discretion — no warnings, no human judgment, no context, just detection and penalty. It imposes real financial risk — a $100–$500 citation is not symbolic for low- and middle-income households, especially when tickets escalate, double, or move toward collections. And it introduces tail risk — repeat violations can trigger booting, towing, impoundment, and cascading costs that far exceed the original offense.

This is not how people experience traditional traffic enforcement. And it's why the policy feels intrusive even to residents who support safer streets.

The Referendum Question We Never Asked

Other jurisdictions have put automated enforcement to voters. D.C. has not. That doesn't mean D.C. acted improperly. But it does mean we skipped the most honest version of the policy test: given the full set of costs and benefits, would residents choose this system if asked directly? That is a referendum question.

And if we're unwilling to run an actual referendum, the least we can do is model one seriously.

Modeling a Referendum: A Citizen-Level Economic Framework

A referendum is not decided by averages. It's decided by how individual voters perceive their own welfare. A referendum-grade analysis therefore asks: for a given resident, does this policy raise or lower expected utility? Formally, each voter is implicitly evaluating something like:

Where ΔUᵢ is the net change in well-being for one person. E[ΔBᵢ] is the value of the benefits they realistically expect — slightly safer roads, lower crash risk, smoother traffic, or better public services if ticket revenue is actually used that way. E[ΔCᵢ] is the value of the costs they expect to bear — tickets, escalating fines, time and hassle, and the low-probability but high-impact risk of towing or losing access to their car. Φᵢ captures everything that doesn't show up neatly in dollars but still matters to voters: feeling constantly monitored, punished without discretion, or treated unfairly by an opaque system.

A serious model adds three features that are usually missing from public debate: heterogeneity (there is no "average citizen" — you model distributions across non-drivers vs. daily drivers, low-income vs. high-income households), tail-risk weighting (citizens don't evaluate policies on expected value alone — they overweight downside risk), and a voting rule that translates welfare estimates into predicted votes.

Why the Economics Likely Point the Same Way as a Referendum

Run honestly, this model produces an uncomfortable prediction. Even if automated enforcement produces real safety gains, a majority of voters — especially low- to middle-income drivers — are likely to vote against the current regime as structured. Three dynamics drive that result: marginal safety gains are what matter (if road design, vehicle safety, and navigation technology are already reducing risk, the incremental benefit attributable to cameras shrinks); financial pain is immediate (households heavily discount probabilistic safety benefits relative to certain, near-term cash losses); and escalation dominates psychology (the existence of compounding penalties and towing risk shapes behavior and voting more than average outcomes do).

In short: a policy can be defensible in aggregate and still fail a democratic welfare test.

Why Referendum-Grade Accountability Is Appropriate

If the city is confident in automated enforcement as currently designed, it should welcome one of two things: a real referendum asking residents to affirm or reject the system, or a referendum-grade evaluation with independent economic modeling, distributional analysis by income and geography, transparent accounting of where revenue actually goes, and sunset provisions requiring reauthorization.

This is exactly the kind of work a neutral firm like House Strategies Group could perform: not advocacy, not opposition, but rigorous modeling of how the policy actually lands on citizens. If the model predicts voters would reject it, that's not an argument to ignore the model — it's an argument to redesign the policy.

Ending Where This Began

My car will get out of impound. I'll deal with the consequences. That's not the point. The point is that policy clarity often emerges from lived experience. And mine reminded me that automated enforcement isn't just a safety tool — it's a financial system layered on top of daily life.

If we believe in it, we should be willing to ask voters directly. If we're unsure, we should model the vote honestly. Either way, the decision should belong to the people who bear the cost.