## Reapplication, approvals, communication and transition review — October 9 addendum

Proposed checklist safeguards; these are not confirmed provisions of Brighton's pending ordinance.

- Reapplication: obtain the accepted withdrawal, affected case numbers and remaining approvals. For a resubmission, identify the controlling rules on its filing date, any lawful waiting period, new fees and completeness requirements. Require updated studies and renewed notice when applicable; do not assume an old application or study remains valid.
- Approvals: publish a stage-by-stage matrix naming the decision maker, controlling criteria, required studies, public hearing or administrative procedure, permit dependencies, conditions, expiration and appeal deadlines. A preapplication meeting is not approval.
- Community communication: maintain one dated public project page with applications, study versions, hearing notices, staff reports, decisions, conditions and approved minutes. Label draft minutes and distinguish DCAP notes from the City's official record. Proposed physical notices must remain stationary, unobstructed and readable.
- Transition and claimed vested rights: require a dated municipal-attorney determination identifying the adopted ordinance's actual effective date, pending-case rules, exemptions and documentary basis for any vested rights. Neither withdrawal nor first reading establishes permanent cancellation or grandfathering.
- Changes after approval: review increases in power, floor area, generators, water demand or operating intensity against the controlling modification rules. Identify when amended approvals and renewed notice are required. Transfers must address successor responsibility, financial assurances and ongoing conditions.


## Gate 0 — Community notification and participation at intake

DCAP proposed policy, version 1.1 | October 9, 2026. This is proposed ordinance and administrative language, not adopted law. The affected community is a primary public stakeholder from the beginning of review.

### Proposed policy clause

The municipality shall include affected residents and other community stakeholders in its initial project-notification and review process. Upon receipt of the first site-specific data-center inquiry, concept, preapplication, rezoning request, application, or request for municipal infrastructure or economic-development assistance, staff shall open a public project record and initiate community notification at intake, before the first substantive municipal coordination or negotiated project commitment. Notification shall not be deferred until an application is complete, a hearing is scheduled, or a preferred project has been negotiated.

Staff shall acknowledge and publish the intake record immediately upon receipt, with a proposed outside deadline of one business day. The record shall identify the receipt date, site/parcels, requesting party, proposed use, current and requested zoning, known campus scope, unknown inputs, preliminary review route, municipal contact, and how to submit questions. Preliminary inquiries shall be labeled as preliminary; receipt is not approval.

The municipality shall initiate direct notice to the mapped affected community alongside its initial substantive notifications to project stakeholders and agencies. Affected residents include owners and renters and communities across municipal or county boundaries. Notice shall also reach relevant schools, hospitals, farms and animal facilities, community organizations and neighboring governments. Staff shall justify the notification area using foreseeable noise, air, water, traffic and infrastructure impacts; an adopted minimum mailing radius is a floor for this proposed supplemental outreach, not proof that effects stop at that boundary.

Use a permanent public project page, direct notice, an optional subscription channel and stationary readable site notices where authorized. Provide accessible formats, language access and a noninternet contact route. Do not rely solely on an HOA, social media, a newspaper, or residents discovering the case themselves. Preserve required hearing notices as separate obligations.

Hold an early community scoping meeting before a formal application is deemed complete and before study scopes and siting alternatives are finalized. Publish preliminary plans, assumptions and study questions first. Provide a proposed minimum 30-calendar-day written input period following initial notice; the municipality shall use comments to refine study scopes, alternatives and mitigation. Staff may gather information during this period, but may not use that work to bypass the participation gate.

Maintain a public issue-and-response register linking community questions to applicant responses, study tasks and municipal findings. Explain unresolved concerns, rejected recommendations and the evidence supporting each decision. Attendance or silence shall not be recorded as community consent. Participation does not guarantee a particular outcome or create an automatic public veto.

Where a statute requires withholding particular information, municipal counsel shall document the legal basis, scope and duration and release the nonexempt project information and a redaction log to the extent lawful. A private confidentiality agreement shall not itself determine public-record disclosure duties.

### Gate 0 checklist

- [ ] Earliest site-specific contact logged, including the originating department and receipt date.
- [ ] Public intake page published promptly; time of publication recorded.
- [ ] Existing zoning, requested changes, preliminary campus scope and unknowns disclosed.
- [ ] Owners, renters, affected cross-boundary communities and sensitive uses mapped.
- [ ] Initial direct community notice initiated; delivery methods, dates and reach documented.
- [ ] Accessible, language and noninternet participation routes provided.
- [ ] Early scoping meeting held and proposed input period completed.
- [ ] Community issues connected to study scopes, alternatives and a public response register.
- [ ] Any withholding justified under applicable law; nonexempt information released.
- [ ] Clerk and planning officer sign the participation record; municipal counsel identifies authority and adoption requirements.

Status: PASS / FAIL / HOLD / N/A. Record authority, evidence links, reviewer/date, outstanding correction and deadline. Under an adopted version of this proposal, missing notice or participation documentation is a HOLD before completeness acceptance or discretionary advancement. Cure the defect through lawful notice and a renewed meaningful input opportunity; document whether any affected step must be repeated.

### Reapplication and continuing communication

Refresh initial notification for resubmissions and material changes, including changes in zoning, campus scope, operator, power, water, generation or siting that affect the public assessment. Explain what changed and which studies need updating. Publish later hearing notices, decisions, conditions and monitoring results on the same record.

### Existing law and unresolved history

Brighton's published Article 2, section 2.01(D), requires neighborhood meetings before formal applications where Table 2-1 or other specified provisions require them; the Director may require them for other complex or impactful projects and may waive certain routine meetings under stated criteria. This proposal establishes an earlier, broader notification gate for data centers and requires lawful adoption before enforcement.

The organizer reports late discovery of Project Silo. No exact period of community exclusion or finding of unlawful notice is established here. Obtain the earliest project contacts, neighborhood-meeting notices and minutes, waiver determinations, distribution records and dated public postings to reconstruct the timeline.

Early engagement supplements required hearings and ordinance readings. It does not eliminate a legally required second reading or transfer the municipality's decision authority.

Source: https://www.brightonco.gov/DocumentCenter/View/21239
