Resolution No. 2026-133 · Resolution · 2026 · Town of Castle Rock

Resolution Approving a Site Development Plan for Residential Development Within the Crystal Valley Ranch Planned Development (Lot 1, Block 2, Crystal Valley Ranch Filing 14 and Part of Tract P, Crystal Valley Ranch Filing 1) [Located north of Crystal Valley Parkway, east of Rhyolite Park and west of Snow Goose Road]

Official status: Adopted

Prime sponsors

Sponsor information is on the official bill page (linked below).

Progress (from the official record)

Official summary

Official text — shown in English exactly as published by the official source. The official text controls.

The official page for this measure does not publish a summary. Its full text is linked below.

Plain-language explainer

Plain-language explainer — not the bill text

Written by AI from the official bill text · 2026-11-20 · Human review pending

This resolution approves a site development plan for residential development within the Crystal Valley Ranch Planned Development, on Lot 1, Block 2 of Crystal Valley Ranch Filing 14 and part of Tract P of Filing 1. The plan by CVR PA3A LLC covers 112 single-family detached homes on about 21 acres, including 4.58 acres of dedicated open space and public land, northwest of Crystal Valley Parkway and Snow Goose Road. The record lists its status as Adopted.

Status timeline

Every recorded action on Resolution No. 2026-133, oldest first
DateLocationAction
11/17/2026Town CouncilListed on the Town Council agenda — Passed
11/17/2026Town CouncilMoved by Councilmember Brooks, seconded by Councilmember Davis, to Approve Quasi-Judicial Resolution RES 2026-133 as presented. The motion passed by a vote of: (moved by Max Brooks, seconded by Mark Davis)

Full text

Full text — side-by-side reader

Showing the latest official version: Attachment B: Resolution version (official PDF),

Official text — shown in English exactly as published by the official source. The official text controls.

RESOLUTION NO. 2026-133

A RESOLUTION APPROVING A SITE DEVELOPMENT PLAN FOR RESIDENTIAL DEVELOPMENT WITHIN THE CRYSTAL VALLEY RANCH PLANNED DEVELOPMENT

(Lot 1, Block 2, Crystal Valley Ranch Filing 14 and Part of Tract P, Crystal Valley Ranch Filing 1)

WHEREAS, CVR PA3A LLC (the “Developer”) has requested approval of a site development plan (the “Site Development Plan”) for 112 single-family detached homes within the Crystal Valley Planned Development (the “Project”); and

WHEREAS, the Project is located on approximately 21 acres of property, including 4.58 acres of dedicated open space and public land, located northwest of the intersection of Crystal Valley Parkway and Snow Goose Road; and

WHEREAS, the uses associated with the Project are uses permitted by right pursuant to the Crystal Valley Planned Development Plan and Zoning Regulations, Amendment No. 7, approved on January 20, 2026, pursuant to Town Council Ordinance No. 2026-001; and

WHEREAS, according to Section 17.38.030 of the Castle Rock Municipal Code (“CRMC”), the Town Council has the requisite authority to approve the Site Development Plan, following a review and recommendation by the Planning Commission; and

WHEREAS, on October 8, 2026, a public hearing was held before the Planning Commission, which voted to recommend approval of the Site Development Plan to the Town Council; and

WHEREAS, based upon the evidence presented at a public hearing held at tonight’s meeting, the Town Council finds that the Site Development Plan is in substantial compliance with:

(i) The goals and objectives of the Town of Castle Rock’s Vision 2030 and the 2030 Comprehensive Master Plan;

(ii) The development standards set forth in the Crystal Valley Planned Development Plan and Zoning Regulations, Amendment No. 7;

(iii) The site development plan review and approval criteria set forth in CRMC Section 17.38.040;

(iv) The Town of Castle Rock Technical Criteria; and

(v)The terms and conditions of that certain Memorandum of Understanding between the Town and Developer dated October 21, 2025, and approved by Town Council Resolution No. 2025-139.

NOW, THEREFORE, BE IT RESOLVED BY THE TOWN COUNCIL OF THE TOWN OF CASTLE ROCK, COLORADO AS FOLLOWS:

Section 1. Approval. The Site Development Plan for the Project is hereby approved in the form presented at tonight’s meeting.

PASSED, APPROVED AND ADOPTED on first and final reading this 17th day of November, 2026, by the Town Council of the Town of Castle Rock by a vote of ____ for and ____ against.

ATTEST: TOWN OF CASTLE ROCK

Lisa Anderson, Town Clerk Jason Gray, Mayor

Approved as to form: Approved as to content:

Michael J. Hyman, Town Attorney Tara Vargish, Director of Development Services

Change history

Official record

Town of Castle Rock — Town Council agendas and packets, Legistar (castlerock-co.legistar.com)

Source: Town of Castle Rock — Town Council agendas and packets, Legistar (castlerock-co.legistar.com) · Data as of

Verify this record

This record carries a fingerprint of its official content, computed by our data pipeline with the SHA-256 algorithm — a real computation over the record itself, not a badge we award ourselves. Anyone can recompute it from the official source and compare.

SHA-256 fingerprint

df83c23f0b3d7cc4695551505aaf06ba9612c9100ad9ba27c70999d9664081ab

What it covers: the record exactly as the official source publishes it — its identifiers (bill number, session, jurisdiction), its official title and long title, its official summary, its status, its sponsors in published order, every recorded action, every recorded vote, and the link to each official text version — assembled in a fixed canonical form described on the How this data works page.

Computed 2026-11-21 · Algorithm: SHA-256 · Canonical form: rogata-canonical-v1

Source: Town of Castle Rock — Town Council agendas and packets, Legistar (castlerock-co.legistar.com) · Data as of

The fingerprint does not cover our retrieval date (the “Data as of” stamp in the source line): re-fetching unchanged official content produces the same fingerprint, while any change to the official content changes it.

If you recompute the fingerprint from the official source and get a different value, one of us is out of date — please report it through the corrections log.