Parking Occupancy and Turnover Analysis Builder

Analyze parking occupancy and turnover using sensor, meter, permit, citation, or manual count data to improve pricing, enforcement, signage, and curb access.

Prompt Template

You are a transportation and operations analyst. Build a parking occupancy and turnover analysis plan.

Parking context: [downtown district, campus, hospital, retail center, airport, event venue, residential permits]
Parking assets: [on-street spaces, garage, lots, loading zones, accessible spaces, EV charging, permits]
Business question: [pricing, enforcement, signage, allocation, employee parking, peak demand, curb access]
Data sources: [sensors, meter payments, license plate recognition, permits, citations, manual counts, gate counts]
Time window: [days, weeks, season, event dates, before/after change]
Granularity: [space-level, block face, lot, garage level, zone, hourly, daily]
Known constraints: [missing sensors, unpaid parking, privacy rules, special events, construction, holidays]
Metrics needed: [occupancy, turnover, dwell time, violation rate, revenue, availability, search time proxy]
Segments: [permit type, public vs staff, zone, daypart, weekday/weekend, event/non-event]
Tools: [SQL, spreadsheet, Python, GIS, BI dashboard]
Decision audience: [city staff, property manager, university, hospital operations, retail landlord]
Policy or privacy concerns: [plate data, permit data, accessibility, equity, enforcement rules]

Create:
1. Data inventory and validation checklist.
2. Metric definitions for occupancy, effective occupancy, turnover, dwell time, availability, revenue per space, and violation rate.
3. Cleaning rules for missing sensors, repeated reads, event days, outlier dwell times, and permit exceptions.
4. Analysis design by zone, daypart, weekday/weekend, and special events.
5. Dashboard specification with maps, heatmaps, time series, and exception tables.
6. Interpretation framework for underused, saturated, high-turnover, and long-stay zones.
7. Recommendations menu for pricing, time limits, permits, enforcement, signage, loading zones, and employee parking.
8. Privacy and governance cautions for plate, permit, and citation data.
9. Before/after test plan for any policy or pricing change.
10. Executive summary template with assumptions and limitations.

Do not overclaim precision when data sources miss unpaid, illegal, or sensor-failed occupancy.

Example Output

Parking Analysis Plan

Core Metrics

| Metric | Definition | Use |

|---|---|---|

| Occupancy | occupied spaces / available spaces by hour | Identify saturation |

| Turnover | unique vehicles or sessions per space per day | Spot short-stay vs long-stay use |

| Dwell time | minutes per vehicle or paid session | Set time-limit policy |

| Effective availability | share of blocks with at least 1-2 open spaces | Driver experience proxy |

Initial Finding Template

Zone B averages 94% occupancy from 11:00-14:00 with low turnover, suggesting employee or long-stay use is crowding out lunch visitors. Zone D averages 42% occupancy with poor wayfinding and may absorb demand before pricing changes.

Dashboard Views

Hourly occupancy heatmap, map by block face, dwell-time distribution, violation rate by zone, event-day comparison, and before/after policy change chart.

Tips for Best Results

  • 💡State the data source clearly because meter payments, sensors, and manual counts each miss different behavior.
  • 💡Analyze by daypart; daily averages can hide lunch, shift-change, or event peaks.
  • 💡Add privacy constraints when license plate, permit, or citation data is involved.
  • 💡Pair pricing recommendations with availability and turnover metrics, not revenue alone.