**By Matt Feagins and Rob McConnell ยท Edited for Parking Practice by Andrew Sachs, PTMP*
The entrance is where the public street's problems become the facility's, and the design principle that governs it is deliberately asymmetrical: favor the entering traffic, even at the expense of complicating the exit. A queue inside the facility inconveniences customers; a queue backing onto the public roadway endangers them, angers the city, and can close the project's approvals the next time it needs one. Everything in entrance design serves the rapid movement of vehicles off the street, and the exit inherits whatever complexity that priority creates.
Read the street pattern first. Entrances belong on major streets inbound to the destination area, with the most direct access; exits belong on low-volume streets where departing vehicles meet the least conflict. Right turns in from a two-way street, or entry from a one-way street, beat left turns across peak opposing traffic, which are both slow and dangerous. Larger facilities take more than one entrance and exit, dispersing flow and keeping the facility reachable through street repairs, equipment failures, and emergencies. And carry one contingency consciously: one-way street patterns change, and when the city reverses the street, the facility reverses every access direction with it. A design that survives that reversal is worth the drawing time.
Buy queuing space with geometry. On high-volume or fast streets, a deceleration lane ahead of the entrance prevents rear-end collisions and protects street flow. Entry control equipment sits far enough inside that a vehicle behind the one at the dispenser clears the sidewalk; where no deceleration lane fits, put the equipment three to four vehicle lengths into the facility. Test the geometry with a large van or SUV in driving-simulation software, because the design vehicle for queuing and turning at control equipment is the big one, not the average one. Single entry lanes run 13 to 16 feet at the street, tapering to 10 feet at the equipment; double lanes take 24 feet minimum; and any ramp beginning at an entrance gets a short level segment beyond the controlled area before the slope starts.
Count lanes from volume and behavior, not floor area. One inbound lane serves a facility of 300 to 500 vehicles with average behavior; larger facilities, or smaller ones with hot turnover, need more entries or entries on additional streets. The exit side scales with how the facility empties: a steady-trickle office garage and an all-at-once event garage of identical size need very different exit counts, and the gated-lane planning table in the source (one entry and one to two exits at 200 spaces, scaling to four entries by 2,000) is the starting grid a traffic study then refines. Gateless operation changes the arithmetic entirely: one entry and one exit lane per street access point generally suffices, which is part of that technology's site-planning appeal. Two lane-allocation refinements pay for themselves: a dedicated credentialed lane where monthly parkers otherwise queue behind fumbling transients, and reversible lanes (equipped to run either direction) where event or shift peaks slam the facility one way at a time.
Design the exit to meter itself. A turn in the drive aisle approaching the exit slows vehicles and controls the release rate into the street. The exit equipment sits far enough from the sidewalk that at least one paid vehicle can wait inside the facility, taking gaps in street traffic on its own schedule. Keep exits 75 to 100 feet from corner intersections, so facility traffic and signal queues do not interlock. Event facilities get their own rules: a proper traffic study to position egress, maximum lane throughput, pay-on-entry to make departure a free flow, and external traffic control by police or attendants, because no internal geometry can manage a stadium's simultaneous exit alone.
Match the payment system to the pedestrian plan. Pay-on-foot economics depend on pedestrians actually passing the pay stations, which means pedestrian access is channeled, not open. And every POF facility needs pay-in-lane machines at the exits for the customer who forgot, because the alternative is a driver backing out of an equipment lane against traffic, which is the exact conflict the whole design exists to prevent. Cameras built into the entrance equipment, coupled to the intercom, put management's eyes and voice in the lane without a booth.
favor entry over exit everywhere the two compete, and prove the entrance with the large-vehicle simulation before pouring it. Locate entries on inbound majors and exits on quiet streets 75-plus feet from corners, size lanes from turnover behavior rather than space count, give the monthly parkers their own lane where volume justifies it, and design the exit approach to meter vehicles into street gaps rather than launch them at the intersection.
From the shelf
- Module 13: site selectionthe access test applied before purchase
- Module 51: gates and PARCS geometry · link pending platform buildthe queue math at the gate itself
Source crosswalk -- where each section came from in the manuscript
| Module section | Source: Chapter 8, "Functional Design" |
|---|---|
| Street pattern | "Street Traffic, Entrances, & Exits" (inbound/outbound, one-way reversal, left-turn caution, multiple access) |
| Queuing geometry | Same section (deceleration lane, 3-4 lengths, Autoturn/large vehicle, lane widths, level segment) |
| Lane counts | Same section (300-500 rule); "Operation & Revenues Systems" (gated-lane table, gateless 1+1, monthly lane, reversible lanes) |
| Exit metering | "Street Traffic..." (turn before exit, one-vehicle reservoir, 75-100 ft, event control) |
| Payment/pedestrian | "Operation & Revenues Systems" (POF access control, pay-in-lane, pay-on-entry planning and its mixed-user caution); camera/intercom passage |
| Not carried forward | Facility types and safety framework (in #17); space/module design (in #23-24) |