Trigger: variance/reduction request, shared-use agreement, “do we have enough parking,” due diligence. Inputs: site plan w/ stall inventory, land-use program (sizes, units), jurisdiction code section, access locations.
- Understand project type & land uses (program table with SF/units/seats — the demand basis).
- Pull local parking code → a parking-code note (ratios, shared provision, reduction path).
- ITE Parking Generation rates if applicable (LU code, edition, setting; avg vs 85th — ask what agency accepts).
- ULI Shared Parking applicability (≥2 uses with offset peaks?) → plan the model.
- Define study area (site-only vs incl. on-street/nearby public — agency guideline governs).
- Inventory supply: total by type (standard/compact/ADA/EV/reserved/loading), on/off-street map.
- Collect occupancy: hourly circuits covering expected peak periods; ≥1 typical weekday + weekend day if retail/mixed; avoid holidays/events; log weather → the field-data sheet.
- Observed peak demand: accumulation curve; peak hour, peak occupancy %.
- ITE estimate: rate × units; show work.
- ULI shared model: ULI Shared Parking Calculation.
- Apply/justify every adjustment (hourly, monthly, weekday/weekend, modal, non-captive, captive) — each with a sourced basis line.
- Demand vs supply table (all four demand columns side by side).
- Demand vs code requirement; compute surplus/deficit vs code.
- Shared-parking opportunities (agreements, time-restricted stalls, valet, wayfinding).
- Operational issues observed (queuing at gates/drive-thru spillback, circulation conflicts, illegal parking) — photos.
- Exhibits: inventory map, occupancy heat map by hour, accumulation curve, ULI table.
- Findings & recommendations (numbers first, adjectives never — “peak demand 412 vs supply 460 (90%)” ).
- QA/QC: counts foot to raw sheets · ratios traced to code section text · ITE LU codes right edition · every ULI factor sourced · exhibit numbers = table numbers = text numbers · QAQC System Layer 1.
- Final memo/report → a close-out parking-study note archives assumptions + lessons.
Time it actually takes: small site ≈ field day + 2–3 analysis/writing days (calibrate your own). Practice question: observed peak is 55% of code requirement — list three explanations you must rule out before recommending a reduction. QA/QC reminder: the four-way demand comparison table appears, or the study isn’t done.