Counting Demand: Occupancy, Turnover, and Utilization Fieldwork

Every parking recommendation stands on counts, and the counting discipline is where studies earn or forfeit their credibility. The manuscript's methodological through-line is short and strict: measure what actually happens, for long enough to mean something, and interview the humans, because the numbers alone are never enough.

The three measurements. Inventory comes first: every space in the study area counted, located, and classified by facility type, because utilization percentages are meaningless against an uncounted denominator. Occupancy is the state measurement: how many spaces are filled, where, at what times, captured across the daily and weekly cycle so the peaks and the valleys both appear. Turnover is the flow measurement: how many distinct vehicles use a space across the day, the number that separates a full-but-productive facility from a full-and-stagnant one, and the number shared parking strategies exist to raise. Utilization analysis binds the three into the finding that matters: not whether the district "has enough parking" in aggregate, but where and when the supply and the demand miss each other.

The duration rule. The manuscript's most quotable fieldwork discipline: determining parking demand should not be limited to a duration of 5 to 7 days. A week of counts captures a week's weather, one school calendar, zero seasonal effects, and whatever anomaly happened to visit. The standard is as much data as can be obtained (one full month to multiple years where records exist), and the modern facility helps: PARCS transaction logs, guidance-system occupancy feeds, and revenue records are continuous counts already collected, waiting to be analyzed. The corollary discipline is baseline honesty about existing comparable facilities: office garages historically fill at 75 to 85 percent of capacity, and a demand basis drawn from a similar use's actual performance beats a ratio drawn from a table.

Interviews are data. The operational analysis's survey work (stakeholders, attendants, managers, customers) is not a courtesy lap; it is a second dataset. Tenants who believe a development will strand them, operators who know which levels never fill, and the employees who watch the queue every morning hold information no tube counter collects, and shared-parking arrangements in particular live or die on stakeholder willingness that only interviews reveal: some parties simply will not share coordination, capital cost, or maintenance responsibility, and finding that out before the calculation beats finding out after the agreement.

Forecasting on the counts. The demand analysis projects the measured base forward through expected land-use change, population growth, and auto-use trends across the project's lifetime, and the current era adds its complication: with workforce schedules no longer the Monday-to-Friday, eight-to-five constant the discipline was calibrated on, the consultant must analyze recent data for trend rather than assume the historical pattern, and design the management plan (equipment, controls, allocation flexibility) to accommodate parkers whose days and hours vary. The adjustments that move the forecast (transit, TNCs, remote work, events, seasons) are the next modules' subject; this module's claim is prior: no adjustment methodology rescues a thin count.

Source crosswalk -- Module 2