Parking Reduction on a Transit-Adjacent Infill Site
A developer proposes 68 apartments on a 1.9-acre (82,764 sf) infill parcel two blocks from a light-rail station, with 20% of units deed-restricted affordable. Zoning requires 1.5 parking spaces per unit, or 102 spaces; the developer requests a reduction to 0.9 per unit, or 61 spaces, and points to reduced parking minimums adopted elsewhere in the region. At 350 sf per stall including drive aisle, 102 spaces would consume about 35,700 sf, or 43% of the site; 61 spaces would consume about 21,350 sf. The site fronts a collector street with a bus stop, has an alley at the rear, and sits in a combined-sewer area where the utility requires on-site retention of the 1.2-in rainfall over new impervious area. The proposed building footprint is 15,300 sf, four stories. The fire department has not yet reviewed the site plan, and the developer wants to submit in six weeks.
1. Advise the developer on whether to pursue the parking reduction. What evidence and conditions would make the request defensible?
Read the worked answer
The math favors asking, but only if the request is built on evidence rather than on the site constraint alone. Removing 41 stalls frees about 14,350 sf - roughly a third of an acre - which is the difference between a buildable stormwater strategy and a variance request. That is a legitimate planning argument, and the transit proximity supports it.
What makes the case defensible is a parking demand study grounded in this site: census tract vehicle ownership, the share of affordable units (which typically have lower car ownership), station-area ridership, existing on-street occupancy counts on weekday nights and weekends, and a documented plan for what happens if demand exceeds supply. Offer conditions that reduce the risk to the city: unbundle parking from rent so spaces are leased separately, price spaces, provide a car-share space and secure bicycle parking at a ratio the code can accept, and design the site so that a future parking structure or additional surface stalls could be added without demolition.
Also test the downside honestly. If the reduced count fails after occupancy and residents park on the collector street, the bus stop and adjacent neighbors absorb the cost. Recommend a monitoring commitment - occupancy counts at 6 and 18 months - and state a contingency such as a shared-parking agreement with a nearby use. Do not present the reduction as purely a construction-cost saving; that framing invites denial.
2. Identify the conflicts the fire department review will create and how you resolve them without losing the stormwater area.
Read the worked answer
Expect three conflicts to surface. First, apparatus access: the alley is likely too narrow, so the design will need an internal fire lane meeting the locally adopted fire code - commonly around 20 ft of unobstructed width, 13 ft 6 in of vertical clearance, adequate turning radius, and a surface capable of carrying apparatus loads. Verify against the adopted code before drawing, because the numbers vary by jurisdiction. Second, the lane must reach within a required distance of every building face, which usually pushes it against the landscape strip you were counting on for bioretention. Third, a fire-department connection and hydrant placement will want space near the frontage.
Resolution strategy: make the fire lane and the stormwater facility the same piece of ground. A paved lane can drain to adjacent bioretention cells in the landscape strip; the cells occupy the 10–20 ft band the lane cannot use anyway. Confirm with the fire department that an approved alternative surface or a reinforced-pavement section over a storage bed is acceptable - some jurisdictions allow permeable pavers or a plastic arch system under the lane, which converts the fire lane into subsurface storage and roughly doubles your available volume on the same footprint.
Get the fire department in for a concept review during the six-week window rather than after submittal. One pre-application meeting here is worth more than a redesign later.
3. Size the stormwater approach on the reduced-parking scheme and state what data you still need.
Read the worked answer
Run the numbers on the scheme you are actually proposing. With 61 spaces instead of 102, impervious cover drops by about 14,350 sf. Assume roughly 45,000 sf of new impervious area across roof, drive aisles, and sidewalk; the 1.2-in rainfall depth is 0.1 ft, so the retention volume is on the order of 4,500 cu ft.
Check whether that fits. Bioretention with 12–18 in of ponding depth above the media needs about 3,000–4,500 sf of ponding surface, plus side slopes and pretreatment. Against 14,350 sf of newly available landscape, that is feasible if the cells are distributed along the fire lane and the alley edge rather than consolidated in one basin. If the site instead has to retain the volume in subsurface storage under the fire lane, expect arch chambers at roughly 1 cu ft per unit of storage plus cover, which also fits but costs more.
Data still needed before committing: the actual curve number or impervious coverage from the site plan, the local design storm definition and whether attenuation (not just volume) is required, the seasonal high water table and infiltration rate from a test pit, the combined-sewer discharge rule that governs the overflow path, and the basement or slab elevation relative to the bioretention ponding elevation. Without the infiltration rate and the seasonal high water table, choosing infiltration-based practice over a lined, underdrained practice is guesswork - and the wrong choice can fail at permit review or, worse, at the first high-water season.