Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Parking Policy topic
No spam. Unsubscribe anytime.
Council debates draft developer parking agreement policy, stops short of adoption
Summary
Council members discussed a draft policy to standardize downtown developer parking agreements and set a 50–60% cap on contracted spaces, but raised questions about fees, grandfathering of existing agreements and whether the item should be labeled a policy or guideline.
City parking staff presented a draft developer parking agreement policy on Aug. 11 intended to standardize terms for developers that request long‑term access to city ramp spaces. Nolan Shield, city parking system administrator, told the council staff wants uniform terms for duration, remuneration and how many spaces can be committed so the parking enterprise retains availability for transient users and downtown visitors.
Key elements presented included an initial contract term of seven years with one optional three‑year extension (a potential 10‑year initial commitment), a systemwide guideline to keep contracted spaces between roughly 50% and 60% of ramp capacity, and an example fee methodology based on estimated per‑space capital cost (staff used $40,000 per structured parking stall as an illustrative cost). Shield said current contracted spaces are about 1,800 of 3,500 ramp spaces (roughly 51%); staff said the policy aims to preserve a similar balance.
Council members raised several points during the discussion: - Equity and grandfathering: Several council members asked how existing long‑term agreements would be treated; staff said current agreements would be grandfathered until they expire and the policy would apply to new agreements only. Council Member Doring emphasized a desire for staff to produce a list showing each existing agreement and its term so council can see the timeline for when grandfathered arrangements expire. - Remuneration and enterprise goals: Some council members urged that the parking enterprise operate like a business and avoid cross‑subsidies. Staff provided an example showing the current developer rate often falls below a cost‑recovery estimate and invited council to set a policy direction for whether developer agreements should be priced closer to true capital and operating costs. - Policy versus guideline: Members debated whether the draft should be an enforceable policy or a set of guidelines. Several favored a policy for clarity; others preferred “guidelines” to preserve flexibility for unique projects and lender concerns. - Monitoring and limits: Council requested that every proposed agreement show the current system contracted percentage so the council can see implications before approving new commitments. Staff agreed that every time an agreement comes forward, staff will document the system percentage and impacts to availabilty.
Council direction Council generally supported moving forward with a standard set of terms but asked staff to bring back a refined document that: clarifies whether it is a policy or guideline, lists the 15 current agreements and their durations, documents the expected process for monitoring system contracted percentage, and outlines options for remuneration rates (including a cost‑recovery approach and a discounted developer rate). No final vote was taken.
Why it matters Downtown parking supply and pricing influence where developers choose to build and how downtown businesses and visitors access services. The policy’s balance between long‑term contracted spaces and transient availability affects downtown economic vitality and the parking enterprise’s financial health.
Provenance: staff presentation and council Q&A during the reports and recommendations section of the Aug. 11 meeting.
