When Voters Take Matters into Their Own Hands
How one controversial annexation proposal in Castle Pines, Colorado, led residents to rewrite the rules for future development.
An 800-acre annexation proposal near Parker, Colorado, never made it across the finish line. But the fight it started has changed how Castle Pines will handle large annexations for years to come. On November 3, Castle Pines voters approved two ballot measures that give residents the final say on certain annexations. Question 300 passed with more than 71% of the vote. Question 301 received about 64%. For developers, the bigger story isn’t the election result. It’s how a single controversial proposal turned into a permanent change to the city’s approval process.
The Project Disappeared. The Opposition Didn’t.
The dispute began with Crowsnest, a plan to bring roughly 800 acres near Parker into Castle Pines using a narrow connection along Crowfoot Valley Road. That approach, often called a “flagpole annexation,” drew pushback from neighbors who questioned the proposal and the process behind it.
Crowsnest was eventually withdrawn. The city paused new annexation requests in March and adopted its first annexation policy in August. By then, residents were already organizing. Roughly 1,600 people signed petitions to put annexation decisions to a public vote. The City Council opposed the ballot measure. Residents passed it anyway. That distinction matters. The immediate project was off the table, but the concerns it raised hadn’t gone away. Voters weren’t just responding to Crowsnest. They were deciding who should have the final word when the next large proposal comes along.
A City Policy Wasn’t Enough
Castle Pines didn’t ignore the controversy. Its new annexation policy called for proposals to advance long-term community goals, provide public benefits, encourage substantial public engagement, preserve at least 30% open space, and undergo independent fiscal review. It also favored land next to existing city limits.
Those are meaningful standards. But there’s a difference between a policy adopted by elected officials and a rule written into the city charter.
A future City Council can change its own policy. A charter provision is much harder to undo. That’s the protection voters chose.
Under Question 300, annexations involving more than 20 acres under common ownership, control, or a shared development plan require voter approval. Related or successive annexations count together, so dividing a larger proposal into smaller pieces doesn’t sidestep the threshold. Question 301 adds a separate, shorter-term check. It requires voters to ratify certain parcels larger than 20 acres annexed during the first 180 days after the new provision takes effect. If no qualifying annexation occurs during that window, the Council may repeal Question 301’s provision by ordinance.
Council Can Negotiate. Voters Can Say No.
The city still has a substantial role. Council members can evaluate proposals, negotiate conditions, and weigh impacts on roads, infrastructure, finances, and nearby neighborhoods. For annexations covered by Question 300, however, council approval is no longer the last step. Mayor Tracy Engerman and other opponents of the measure warned that a yes-or-no public vote could make it harder for the city to negotiate the best possible deal. They also questioned whether 20 acres was too low a threshold.
There’s a real tension here. Elected officials can bargain over the details of a development agreement. Voters generally get a simpler choice: approve the annexation or reject it. A developer might decide that navigating another election is more trouble than it’s worth and look at a neighboring jurisdiction instead.
And the rule applies regardless of what is being proposed. A housing development, a commercial project, a public facility, or an open-space annexation can all face the same voter-approval requirement once they cross the threshold. That doesn’t mean Castle Pines has shut its doors to growth. It does mean the political campaign may now be just as important as the land use application.

One Bad Fight Can Follow the Next Developer
Here’s the part that should get the attention of project sponsors well beyond Colorado: the next applicant could do everything differently and still face rules born out of the Crowsnest dispute. A new developer might bring a better site plan, more transparent financial information, stronger community benefits, and a serious outreach effort. None of that eliminates the election requirement.
When a project loses public trust, the consequences don’t necessarily end when the application is withdrawn. Residents can organize against one proposal, or they can organize to change the approval process for everybody. Castle Pines shows what happens when they choose the second route.
For cities, there’s a parallel lesson. Passing a thoughtful policy after a dispute may be a good response, but it may not restore the public’s confidence. Once people believe they’ve been left out of a major land use decision, they may want a permanent seat at the table rather than another promise of public engagement.
Don’t Wait for the Petition
Political due diligence should start before the entitlement application, not after neighborhood opposition appears.
Find out how residents feel about growth and annexation. Understand the city’s charter and its initiative process, not just its zoning code. Identify who has organized around previous projects. And make sure the public can understand why the proposed land belongs in the city and what the community stands to gain.
That also means getting the facts out early. Traffic, infrastructure costs, fiscal impacts, open space and public benefits shouldn’t be details unveiled for the first time at a contentious hearing. If a proposal could end up on the ballot, the team should be thinking about public support, credible messengers and a potential campaign from day one.
Cities have work to do, too. Explain the tradeoffs openly. Show residents the fiscal and infrastructure analysis. Make clear what the city can secure through negotiation and what might be lost if those negotiations fail.
The next thing to watch in Castle Pines is how the city applies the new rules once they take effect, how its annexation policy evolves and whether nearby landowners begin looking at other jurisdictions. Those answers will show whether the measures change the volume or location of development, or simply the way projects seek approval.
The Bigger Warning From Castle Pines
Whether Castle Pines made the right policy choice is for its residents to decide. But the path to this vote should sound familiar to anyone who works on controversial land use projects.
A proposal sparks concern. The city responds. Residents decide the response isn’t enough. Before long, what started as a fight over one site becomes a fight over who controls the process. That’s a much bigger problem than one difficult hearing or one withdrawn application.
At Land Use Strategies, we help developers and public agencies identify these political risks early, engage communities, and build support before opposition hardens into a ballot campaign. Once voters decide to rewrite the rules, the next project has to live with them.
Recent Posts









