Why Eagle's cap-compliance pattern is the most reliable signal in the Treasure Valley.
A statistic-dense look at how Eagle's City Council has voted on residential rezones across an 11.5-year archive — what the data actually shows about cap-compliance, sub-area density ceilings, and the conditions you can expect from the current roster.
Cap-compliance is the dominant predictor of approval in Eagle. Across the searchable 11.5-year Eagle City Council archive, every low-density residential rezone that respected its binding sub-area density ceiling has approved — and every one that breached the ceiling has been denied. The pattern survives a roster turnover and a comprehensive-plan rewrite in April 2026. One specific hearing on May 12 will test whether it transfers cleanly to the current four-member council.
The setup
Eagle is structurally different from any other Treasure Valley city. Three review layers — Staff → Planning & Zoning Commission → Design Review Board → City Council. Nine codified architectural design styles. A five-working-day testimony deadline. The political environment is unusual too: Mayor Brad Pike, elected in January 2024 on a slow-growth platform, votes only to break ties, but with a four-member council, ties are real and his tie-breaker carries weight.
Inside all of that complexity, one signal cuts cleanly through the noise: does your project respect the binding sub-area density ceiling. Cap-compliant applications move through the system. Cap-breach applications, even ones that attempt a comprehensive-plan-amendment workaround, do not.
The headline pattern
Bailey's searchable Eagle CC archive spans 11.5 years — 372 of 375 meetings with full agenda-text and transcript coverage (99.2%). Across that period, twenty-two distinct low-density residential rezones were identified via a two-axis search: agenda-text grep for product-type and rezone terminology, cross-referenced against applications filtered to ≤2.5 dwelling units per acre. Every cap-compliant proposal in that set approved. Every cap-breach proposal denied.
In the most recent 24-month window, Bailey tracks 9 substantive Eagle CC residential rezone hearings — 8 cap-compliant approvals (rate: ), 2 cap-breach denials. The current dataset rests on Granicus video transcripts, signed Findings of Fact from Eagle Laserfiche, and the city's published Development Tracker.
The cap-breach denials
Two named precedents anchor the denial floor. Both are public record; both passed through the Whitehurst-era council that approved the 8 cap-compliant applications.
Tavira — a 2.55 du/ac proposal in Eagle's §6.6 Village sub-area. Denied 4-0 in 2025 on policy grounds. The breach was 0.55 du/ac over the binding ceiling, and the Council was prepared to deny on that alone. Council Member Kvamme reasoned during the denial deliberation that he "would only really support a maximum of R-2 in this." The vote was unanimous, fast, and explicitly cap-driven.
Evian — a comprehensive-plan-amendment path that attempted to clear a sub-area cap by changing the Future Land Use Map designation. The Planning & Zoning Commission negotiated the FLUM ask down from Neighborhood (2–4 du/ac) to Large Lot (≤1 du/ac) before forwarding the application. The City Council denied 4-0 in August 2025 on policy grounds. The CPA shortcut, in this Council's posture, is not a viable path to clear a cap.
Together these two denials bound the floor. Cap-compliance approves; cap-breach denies — even with a comprehensive-plan amendment offered as a backstop. The Council uses the binding ceiling as the controlling variable regardless of which procedural lever an applicant pulls.
The roster-continuity question
The Whitehurst-era Council that approved 8-of-8 cap-compliant rezones from 2024 through mid-2025 has turned over. Two members of the current roster served on that bench. Two new members took their seats in January 2026 following the November 2025 election. The pattern is established, but it has not yet been tested under the new four-vote configuration on a clean within-cap proposal.
This is the question every Park Lane–area applicant is asking right now: does the cap-compliance pattern transfer cleanly, or does the new roster bring a different read? Bailey's per-commissioner playbook covers the specific evidence and framing that have moved each current-roster member's vote — generalized below; the specifics ride with active project teams.
The course-correction mechanism
When Eagle CC is not ready to approve as-filed, the pattern is remand-and-revise, not denial. Two recent examples illustrate the mechanism.
Reining Horse went from 7 buildable lots to 4 after a remand for transitional-lot-sizing rework — a 43% reduction, approved 4-0 at the second round. The remand was a refining instrument, not a rejection signal.
Watermark Subdivision moved through a three-hearing chain in spring 2026: tabled February 24 with direction to cut density, administratively continued March 24, approved 3-0 on April 28 at 131 units (down from 147 — an 11% reduction). The deliberation contained zero references to the §6.5/§6.6/§6.7 sub-area caps because Watermark sits in Mixed-Use zoning, a regulatorily distinct frame from the Park Lane R-district pathway. Watermark confirms the current roster will approve attached housing at density when procedural posture is good — but it sets no R-district precedent.
The practical implication for any cap-compliant applicant: budget 2–4 hearings, not 1, and treat remand pressure as a refining mechanism, not a denial signal. Applicants who have built neighbor relationships and design quality have consistently moved through this pattern intact. Bailey runs the same intelligence pattern in Boise — the remand-and-revise mechanism appears across multiple Treasure Valley cities, with city-specific framings (see Civil Engineering in Boise for the Boise version of this pattern).
What this means for a Park Lane parcel right now
Two paths describe the realistic shape of a cap-compliant Park Lane rezone under current conditions. They diverge on procedural surface, on precedent base, and on live counsel questions — but they converge on the same unit count under the binding cap. The right choice depends on product type, market positioning, and which procedural risks the applicant is willing to absorb.
The May 12 pivot
The first observable test of the cap-compliance pattern under the current roster is on the Eagle City Council agenda for May 12, 2026 — the Mabury Subdivision hearing (RZDA-2025-07, 1010 N Park Ln). Mabury sits inside the Park Lane corridor, uses the same four-application procedural stack as a typical low-density rezone, and represents the only near-term observable signal on whether the 8-of-8 / 22-of-22 historical pattern transfers cleanly to the current four-member configuration.
For any applicant considering a Park Lane filing in the next six months, Mabury is the timing pivot. Filing decisions should be sequenced after the Mabury outcome lands — not because the outcome is in doubt for any well-prepared cap-compliant proposal, but because the post-hearing record will sharpen the per-commissioner read in ways no pre-hearing analysis can. Bailey publishes a follow-up read of the Mabury verdict after the public record settles, typically within 48 hours of the hearing.
How long does it actually take
The biggest variable is the applicant's pace and submittal completeness, not the city's. Eagle staff turn around questions within typical bounds; the Design Review Board adds a layer that other Treasure Valley cities do not have. The submittal-completeness checklist that pre-empts most second-round questions is shared on intelligence calls along with the specific time differentials Bailey tracks between first-pass and second-pass applications.
Why this window may not stay open
Cap-compliance has been the reliable signal for Eagle residential rezones for two years. Two forces will pressure the framework in the next 12–18 months.
The first is Idaho's 2026 state-preemption package — SB 1352 (Starter Home Subdivisions), SB 1354 (ADUs by Right), and HB 706 (Single-Stair Small Apartments) — all effective July 1, 2026, with a city compliance deadline of February 1, 2027. Eagle's framework will need to absorb these new state-level constraints alongside its existing sub-area cap regime. How that absorption happens in practice is a counsel-and-staff question that has not been resolved.
The second is the April 14, 2026 comprehensive-plan rewrite (CPA-2025-03), which removed the Neighborhood designation's density floor and restructured the citywide density framework into "up to" ceilings. The Park Lane and Floating Feather planning areas were not redrawn in that rewrite. How the new ceiling-not-range structure interacts with the sub-area cap layer that still governs Park Lane is the load-bearing question for any applicant whose math sits at the upper bound of the binding cap.
Bailey's recommendation: if you have a Park Lane–area parcel and the density math works within the binding cap, the next twelve months are likely to be the highest-yield window. The pattern is on your side. The Council is moving fast on well-prepared cap-compliant applications. The data — for now — is consistent.
- Named commissioners with verified voting history on cap-compliance (intelligence call)
- Specific approval-rate and time-to-vote numbers (intelligence call)
- Per-commissioner playbook: the framings that have moved each member's vote (intelligence call)
- Parcel-specific cap-compliance read for your site (parcel analysis)
Planning research, not legal advice — counsel required on application-specific reads.