Week 9 — Two Honest Options, and the Third One to Avoid

This week: the honest framing of the trade-off.

There are two coherent ways to manage curb space. Either one can work well.

Option A — Differentiated rules with on-curb information. Set time limits and rates calibrated to each block’s role and demand pattern: restaurant blocks need longer dwell windows in the evening; retail blocks need higher turnover at lunch; loading zones need protected windows in the morning. This produces the highest economic value from a fixed inventory. It comes at a cost: signage and information systems must be designed to communicate complex rules to drivers in motion. On-curb hardware that signals legality and discloses the rule at the space is essential.

Option B — Uniform rules with trivial signage. One citywide rate, no time limits. Signage becomes simple because there’s nothing complex to communicate. You give up active demand management at the block level, but the information environment becomes coherent. Drivers always know what to expect. Compliance is easy. Turnover is determined by price alone, which is a blunter instrument than time limits, but at least it’s an instrument that works.

Both options are defensible. Cities have run each successfully. The choice depends on how dense the commercial activity is, how variable the demand patterns are, and how much investment the city is willing to make in on-curb information for Option A.

The problem isn’t either of these. The problem is the third option that many American cities have drifted into without choosing it: differentiated rules with the rule disclosure pulled away from the curb.

In this configuration, the rules are complex (Option A’s complexity) but the disclosure is at the corner, in an app, or on a kiosk (Option B’s signage minimalism). The rules exist. They’re enforced. But the driver has no realistic way to access them at the moment of decision. This is the worst of both worlds: operationally complex, communicatively opaque, and corrosive to public trust.

A surprising number of cities have arrived at this third option as a side effect of removing curbside hardware in “asset-light” or “no-hardware” deployments. The hardware was performing the disclosure function — it just wasn’t named that way in the procurement spec — so when the hardware was removed, the disclosure went with it, while the underlying rule complexity stayed. The result: drivers can’t read the rules, but they’re still expected to follow them.

The fix is to choose, deliberately, between Option A and Option B. Either invest in the disclosure (on-curb hardware, information designed for in-motion reading), or simplify the rules to the point that no disclosure is needed beyond a single citywide sign. What doesn’t work is the in-between.

The honest question for any city manager looking at their existing system is: which option are we actually running? If the answer is “we have differentiated rules and we mostly post them at corners,” the city is running the third option. The fix is upstream of any individual procurement decision.

Next week: the four-step framework that makes Option A work — set policy, communicate, comply, enforce.