Parker council delays vote on Buckingham Estates annexation after late paperwork, residents press for two‑acre minimum

A developer seeking to annex land known as Buckingham Estates into the City of Parker asked the council to approve a development agreement and annexation on Feb. 4, but council members postponed action after residents and councilors said the final agreement arrived too late for proper public review.

John Arnold, representing Scribe Company and the project team, told the council the proposal covers roughly 46.69–50 acres (transcript references vary) in Parker’s extraterritorial jurisdiction and would be developed as 39 single‑family lots of about one acre each. Arnold said minimum homes would be about 3,000 square feet, with pricing starting around $1.2 million; builders named for the project included Drees Homes, Highland Homes and Windsor Homes. He said an HOA would maintain common drainage features, that private lot drainage would be the homeowner’s responsibility, and that the developer planned to begin a drainage analysis immediately if the agreement moved forward.

Why it matters: council members said the submission timeline denied citizens and some council members adequate time to review the final development agreement before a vote. Several residents urged the council to require two‑acre minimum lots inside Parker; others said approving a one‑acre plan could be preferable to the owner platting the property in the county where the city would have no control.

Council discussion and public comment: multiple residents spoke during the meeting. Lucy Estabrook and Karen Pratt urged the council to hold to a two‑acre standard. Resident speakers and several council members repeatedly raised concerns over drainage, the proximity of a creek on the property, and whether any detention or creek cleanup would be required. Arnold said the developer planned a detention pond if the drainage study showed it was needed and that the landowner had agreed to work with the developer on creek improvements.

Several council members criticized the timing of the materials. Councilmember Pilgrim and others said the final agreement was delivered “yesterday” and that councilors and the public had not had at least 72 hours to review the documents per good practice; councilmember Pilgrim and Councilmember Noe called for more time for public review. Arnold said the developer faces contractual and financial deadlines with the landowner and that a delayed vote could jeopardize the developer’s ability to close the purchase on the current timeline.

Formal action: Councilmember Noe moved and Councilmember Fett seconded a motion to postpone consideration of Resolution No. 2025‑831 approving the development agreement and annexation. The council voted to postpone the item (vote recorded as 4‑0 with one abstention). The motion left the item pending and scheduled for a future meeting after the council and the public have had more time to review the final documents.

What remains unclear: the transcript contains inconsistent references to the property acreage (speakers referred to “about 50 acres,” “approximately 46.69 acres” and at one point “6.69 acres”); the final development agreement’s exact acreage was not settled in public remarks during the meeting. The developer told the council the final version was completed only shortly before the meeting and said the anticipated closing date on the land was the end of February, with construction targeted to begin late summer if approvals proceed.

Next steps: council postponed Resolution No. 2025‑831 to allow staff time to upload and distribute the final development agreement to the packet and to give residents and council members adequate time to review it before voting. The developer said it intended to return if the council is ready to consider the agreement at a later meeting.