Week 4 — Type II: The Zoned Curb
Catch-up — CPS = 5 levels × 6 dimensions; level = min. (Full Week 1 →) | Previously: Type 0 (W2 — un-managed) and Type I (W3 — industrial baseline, where most US cities sit).
This week: the level where cities first differentiate the curb intelligently — and the level where many sophisticated cities have stopped, often without realizing it.
Type II at a glance
| Dimension | What Type II looks like |
|---|---|
| Policy | Block-zoned rates. Time-of-day differentiation. |
| Data availability | Quarterly occupancy studies. Per-meter transaction telemetry. |
| Wayfinding | Static city map of metered zones; rates posted online. |
| Decision Point Info | Static signs at corners with zone + time-band. Digital meter showing rate. |
| Transaction ease | Coin + card meter at the space. |
| Enforcement | Officer + handheld. LPR-equipped vehicles on some routes. |
Type II in practice — and why even the exemplars sit here overall
Type II is the zoned curb. Premium retail blocks priced higher than peripheral commercial blocks. Some time-of-day differentiation — peak rates from 10 a.m. to 4 p.m., off-peak after that. Possibly some basic loading-zone time-share. Meters at the spaces. Static signs at corners that can communicate the zone and time-band. Enforcement still mostly officer-driven, but typically with some help from license-plate-recognition vehicles or handhelds that speed up patrol.
Type II is a real operational improvement over Type I. The user mix at prime blocks shifts toward higher-spend segments — long-stay parkers self-select to the cheaper peripheral curb. Commerce per block on the prime corridors rises. Cruising loss falls because the rate-and-occupancy match is closer.
Many cities consider Type II the destination. Most “we have a parking program” cities operate at Type II on their flagship downtown corridors and slip back to Type I or Type 0 elsewhere. Even the cities held up as exemplars — SFpark, LA Express Park, Seattle, Pittsburgh — operate at Type II overall. They have reached Type III on the Policy dimension with demand-responsive pricing on flagship corridors. But the other five dimensions trail. The honest grade looks like this:
The exemplar reality — Type III Policy on a Type II foundation
| Dimension | SFpark / LAEP grade |
|---|---|
| Policy | Type III — demand-responsive pricing |
| Data availability | Type II — per-space sensors decommissioned; transaction-derived occupancy |
| Wayfinding | Type II — rate/zone info online; limited live data exposure |
| Decision Point Info | Type II — smart meter shows rate; no per-space dynamic indicators |
| Transaction ease | Type II–III — multi-channel at the meter |
| Enforcement | Type II — officer + handheld; some LPR; not exception-based dispatch |
| OVERALL (min) | Type II |
The ceiling of Type II is set by the same constraint that capped Type I: the legibility of static signage. A static sign at the corner can clearly communicate one zone, one rate, and one time-band per block. It cannot communicate three rates per block, or rates that vary continuously by demand, or rules that depend on which space within the block.
There is a third option many cities mistakenly drift into when trying to reach beyond Type II without solving the signage problem. Differentiated rules — by block, by time, by space — but with the rule disclosure pulled away from the curb into a kiosk or a phone app. The rules exist. They are enforced. But they aren’t visible at the moment of decision. This is the worst of both worlds: complex policy with informationally austere driver experience.
The honest Type II: color codes, simplified zones, and the deliberate ceiling
Some cities don’t trail at Type II by accident — they choose it. Two strategies, both legitimate.
Color-coded curbs. Red, yellow, green, white, and blue paint conventions communicate the species of curb regulation visually, in the 1.5-second decision window. They do something static text cannot — they’re parseable from 80 feet at 20 mph, in poor light, by drivers in motion. A driver sees red and knows “no parking” before they’ve registered any words. Color codes lift Decision Point Info above the bare-meter baseline because they encode categorical legality at distance.
What color cannot do is encode temporal variation. A yellow curb tells you “loading zone.” It cannot tell you “loading 7–10 a.m., parking after.” A white curb says “passenger loading.” It says nothing about Tuesday 8–10 a.m. streetsweeping that turns the same curb into a tow zone. Color is one bit of information per channel; temporal rules need many bits. Add color blindness (about 8% of men have red-green confusion), paint fade, snow and salt damage, and inter-city variance, and color codes are a strong Type-I-and-II tool with a hard Type II ceiling. They reach their limit precisely where temporal differentiation begins.
Simplified zone policies — the Copenhagen approach. A small fixed set of categories — 1-hour, 2-hour, 4-hour, residents-only — applied citywide, with rates and durations stable enough that static signage carries the entire rule. Drivers learn the city’s parking grammar once and use it everywhere. Compliance runs high because the rules are unambiguous. Communications cost is low. Politically defensible: simple, equal, predictable.
The trade-off is real. Curb supply doesn’t actually match curb demand evenly. Restaurant blocks need longer evening dwell, retail blocks need lunchtime turnover, loading zones need protected morning windows. Flat zone policy wastes capacity on both ends — peripheral curb under-used because the rate doesn’t reward circulation, prime curb over-used because the rate doesn’t reflect scarcity. Cruising loss runs higher than under demand-responsive pricing. The v1 model puts the foregone commerce uplift at $50–$90 million a year for a mid-size downtown. For a city that calculates the gap and decides the simplification is worth it, this is a defensible choice — particularly for dense walkable cities with strong transit and bike modal share, where on-street parking turnover isn’t the dominant commerce driver.
Three coherent stances, only two of them honest
| Stance | Policy | Decision-point comms | Outcome |
|---|---|---|---|
| Deliberate Type II | Simple, uniform, color-coded | Static signs + color paint | Low capex; predictable; foregoes ~$50–90M/yr commerce uplift |
| The third-option trap | Differentiated, dynamic | Static — corner signs + apps only | Operational complexity; manufactured violations; foregone commerce plus enforcement and trust costs |
| Full Type III | Differentiated, dynamic | Dynamic at-space signage + per-space indicators | $5–$15M capex; recovers $50–$90M/yr commerce; sustainable |
The error to avoid is sliding from Deliberate Type II into the third-option trap. A city that starts with simple zones and color codes and then adds differentiated policy elements — an event-pricing pilot here, a corridor-specific rate there — without upgrading the decision-point layer has accidentally moved from a coherent strategy into an incoherent one. This is how a lot of US cities ended up where they are. The strategic question is not “are you Type II?” — it’s “are you a deliberate Type II, an accidental third-option-trap Type II, or are you graduating to Type III?”
Color codes don’t go away in a Type III deployment. They get supplemented. Color = “this is the species of regulated curb.” Dynamic display = “here are the current rules for this species right now.” The two together are stronger than either alone.
What Type II costs — and what graduating to Type III requires
The gap from Type II to Type III is the largest, most strategically important, and most under-recognized jump on the entire scale. Our v1 modeling suggests $50–$90 million a year in additional commerce on a 1,500-space mid-size downtown — substantially larger than the Type I→II gap, and almost entirely a function of unlocking the five trailing dimensions to match the policy ambition.
What graduating to Type III requires. The technology preconditions are dynamic signage at the space, per-space occupancy sensing, app integration that places the answer to “what does this space cost me right now?” in the driver’s pocket and on the meter at the same time, multi-channel transaction at the space, and LPR-driven exception-based enforcement. The capital required is real: $5–$15M for a mid-size downtown. But the recovery period is short. Most Type II→III investments pay back in commerce uplift inside 18 months.
The Type II→III jump is the one CivicSmart was built to enable.
Next week: Type III — the Responsive Curb. Where the curb finally answers the driver in real time.
Continue the series
8 parts · ~48–56 min total
There is a Bortle scale for night skies, a Saffir-Simpson scale for hurricanes, and a Kardashev scale for civilizations. Each describes a phenomenon as a small set of clearly-defined…
Read week 1 →Type 0 is the un-managed curb. The curb is treated as overflow public space — first-come-first-served. In its purest form, Type 0 is a residential side-street where everyone parks for free…
Read week 2 →Type I is the curb run on industrial-age tools. Single citywide rate. Hard time limits posted on static signs at corners. Mechanical or low-end digital meters at the spaces. Enforcement by…
Read week 3 →Type II is the zoned curb. Premium retail blocks priced higher than peripheral commercial blocks. Some time-of-day differentiation — peak rates from 10 a.m. to 4 p.m., off-peak after that…
Type III is the responsive curb. The defining feature: the rules can change continuously, and the driver knows what they are at the moment they need to know.
Read week 5 →Type IV is the adaptive curb. The defining feature: the curb is integrated with the rest of the urban transportation system, and the integration is bidirectional. The curb knows what’s…
Read week 6 →Most US downtowns sit at Type II overall. The investment to graduate each dimension to Type III is concrete and quantifiable.
Read week 7 →This week — the final week of the series: how the level-up actually gets done. Six investments in sequence; the final four delivered by the SpaceMaster stack — with CivicSmart support…
Read week 8 →