Vice Chair asks staff to review Smart Plan corridor assumptions, high‑density definition before CDMP changes
Sep 14, 2026
Vice Chair Thomas asked staff to return with options to retain, phase, modify, or remove CDMP provisions tied to Smart Plan transit corridors and to clarify the "or more" application in the high‑density residential land‑use category; staff agreed to report back prior to the next meeting.
The full story
Vice Chair Thomas asked staff to analyze whether the CDMP's Smart Plan corridor assumptions, development standards and implementation schedules still align with present funding and transit delivery expectations, and requested options to retain, modify, phase, or remove provisions where assumptions have materially changed.
Thomas said the Smart Plan remains in the CDMP and code but noted reported funding shortfalls for implementation, citing a mayoral memo: "we were $7,600,000,000 short over the next 20 years for that plan," he said. Thomas asked staff to provide information about current funding status, reasonably projected implementation timelines for each corridor, and how development standards should apply if transit delivery is delayed.
Staff described the prior application that sought to refine the high‑density residential category (60–125 du/acre and 'or more') and explained that the applicant's text was bifurcated at the BCC and transmitted to state and regional reviewers. Staff noted comments from state reviewers mentioning Senate Bill 180 concerns about adopting overly restrictive local criteria. Garrett Rowe said staff will follow up with the PAB and committed to returning before the next board meeting with the information requested.
Board members discussed phasing approaches and milestone triggers (e.g., ridership or funding thresholds) to avoid creating development allowances that outpace transit delivery. Staff committed to a follow‑up presentation to help the PAB make an informed recommendation when relevant CDMP changes arrive for review.
Written with AI from the event video and transcript. Check it against the source ↓
