Medical Office on a Sloped Site: Parking Math, Detention, and a Hostile Audience
A developer proposes a 52,000 sf, two-story medical office building on a 6.8-acre suburban parcel. Zoning allows 40 percent maximum lot coverage, a 35 ft front setback, 15 ft side and rear setbacks, and requires parking at 1 space per 250 sf of gross floor area. The site falls 14 ft from northwest (elevation 612) to southeast (598). The seasonal high water table is at elevation 600, and a 0.6-acre forested wetland lies along the southeast corner. A local stormwater ordinance, adopted after repeated neighborhood flooding, requires that post-development peak runoff for the 2-year storm not exceed pre-development peaks, with no exemption for site size. Neighbors have told the planning commission they expect the project to worsen flooding on their side of the property line. The developer wants a site plan in three weeks and has not commissioned a wetland delineation, geotechnical borings, or a traffic study.
1. Run the zoning and parking math and describe the site-planning logic created by the 14 ft grade change.
Read the worked answer
Parking: 52,000 / 250 = 208 spaces. At roughly 330 to 350 sf per stall including aisles for a surface lot, that is about 70,000 sf, or 1.6 acres of pavement. The building footprint is 26,000 sf, about 0.6 acre. Add drives and walks and impervious area lands near 2.4 to 2.5 acres, roughly 36 to 37 percent of the 6.8-acre site. That is under the 40 percent coverage limit but close enough that wider aisles or a drive-through would break it.
Setbacks: 35 ft front and 15 ft sides leave an envelope the 26,000 sf footprint can meet, but the parking lot must also hold setbacks, and on this site the lot usually controls layout more than the building does.
Accessible parking: at 208 stalls the code table calls for about seven accessible stalls, at least one van-accessible; confirm against the adopted code and any local amendment.
Grade logic: put the building on the high northwest ground with the main entry at the front setback and a grade-level entry; terrace the lot in two or three benches with retaining walls rather than one long 5 percent slope; keep the wetland buffer as open space and drainage, never parking. If the client will fund a shared-parking or transit study, the stall count may drop enough to pull pavement out of the buffer and reduce detention volume, but do not promise that before the zoning administrator agrees.
2. How do you satisfy the no-net-increase stormwater standard given a high water table and a wetland buffer?
Read the worked answer
The no-net-increase standard controls the design, and infiltration may not be available because the seasonal high water table sits at elevation 600 while the low corner is 598.
Approach:
- Cut impervious area first, because every square foot of pavement is detention volume you must buy. Narrow aisles to the minimum the fire code allows, use landscaped islands, consider pervious pavement in overflow rows, and share the drive with the adjacent parcel if an access easement exists.
- Compute pre- and post-development hydrology for the 2-year storm and size extended detention with an outlet control structure that attenuates post-development peaks to pre-development peaks. Check the 10- and 100-year storms and the local water-quality volume, often the first inch of runoff.
- Siting: the low southeast corner is hydrologically logical but sits at or inside the 50 ft buffer. Use the existing swale as a vegetated channel and keep the basin outside the buffer, or pursue a buffer variance with mitigation. Do not fill the swale.
- Do not assume infiltration. If infiltration testing fails because of the water table, design a lined basin.
Commission the geotechnical borings and infiltration tests immediately; they take weeks and the basin size depends on the results. Submitting a plan before those results exist invites a denial.
3. Neighbors are expected at the planning commission meeting. What do you present, what do you avoid, and what studies must precede submittal?
Read the worked answer
At a neighborhood meeting you are a guest, not the decision-maker, and it is not the place to design or to concede.
Before the meeting, have the civil engineer run an existing-conditions drainage analysis. The neighbors' flooding may predate the project and may originate from an undersized downstream culvert, which changes the conversation entirely. Bring a large site plan, a zoning compliance table, and the engineer.
At the meeting, state facts rather than assurances. 'The hydrology study is not complete and will be submitted with the site plan' is stronger than 'it will be fine.' Explain what the ordinance requires, that post-development peak runoff cannot exceed pre-development, and how you intend to meet it. Record every concern with names and addresses and route them to the engineer.
Avoid promising a specific basin or wall, arguing with residents about whether their basements flood, discussing property values, or accepting responsibility on the owner's behalf. Refer legal and property questions to the owner and its counsel.
Before submittal, the missing studies are not optional: wetland delineation and a permitting strategy, geotechnical borings and infiltration testing, a traffic study for the access permit, and the hydrology report. Submitting without them invites a denial that is far harder to undo than a two-week delay.