Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Operational Constraints topic
No spam. Unsubscribe anytime.
Staff warns developer needs clear lottery rules; council asks for caps and flowchart
Summary
City staff told the council the developer/operator needs clear, pre-defined lottery priority rules because units must produce rent to cover debt service; staff proposed a capped priority with dynamic usage and asked council whether to set fixed partnership unit counts or allow priorities to float.
City staff told the council the developer and operating entity require clear, pre-established guidance on lottery priorities because the project's debt service and monthly operating budget depend on occupied units.
Chris Everson explained the mechanics: "All of the units are always part of the general lottery. All that we're providing an employer to, let's say, is a priority in that lottery." He said under the proposed approach there would be a cap on employer-priority units (staff used 40 as a working example) but priorities would be dynamically applied and would default to the general APHA-qualified pool if unused.
Council members said they wanted a flowchart showing how units move between partnership allocations and general lottery pools, and several recommended pilot terms (for example, a 5- or 10-year agreement) rather than permanent allocations. Members also emphasized employer protections that require partners to commit to rent obligations if a designated employee leaves.
Staff agreed to return with a clearer program map, proposed caps, and language to limit long-term expansion of partnership units.
