Elbert County working group seeks clearer land‑use packet rules after privacy, record concerns

Elbert County planning commissioners, Community Development Services staff and the county attorney on a working‑group call July 1 discussed tightening procedures for what documents are included in land‑use application packets, and agreed to convene a subcommittee to recommend a mandatory checklist and related regulatory changes.

The discussion focused on three linked problems: inconsistent packet contents, potential exposure of personally identifiable information (PII) after packets are posted, and uncertainty about what documents legally constitute the record for quasi‑judicial land‑use hearings. Lance (county legal counsel) said, "The record in legal terms is what was actually submitted to the planning commission in the form of written documents, verbal testimony, or otherwise." Jennifer (Community Development Services director) told the group that staff had begun removing some underlying documents from packets because of privacy and fraud concerns and that applicants had been targeted with "fraudulent emails" requesting payment "—typically pretty big numbers ... dollars 8,000," she said.

Why it matters: The packet contents determine what the planning commission and later the Board of County Commissioners (BOCC) can properly consider in a quasi‑judicial hearing. Participants emphasized that decision makers must base votes on the record; information obtained outside that record can create due‑process risks that invite legal challenge.

The working group reviewed the zoning regulations and differing interpretations about whose responsibility it is to declare an application complete. Diana Edstrom (planning commission member) noted the zoning rules state the planning commission is appointed by the BOCC "to review land use applications before submission" and that the zoning code lists documents that are part of an application. Jennifer and other CDS staff said completeness is a staff‑level determination made early in the process, while the planning commission's role is to judge whether the materials presented meet the approval criteria.

Participants had a lengthy exchange about which documents are necessary for review. Several planning commissioners said some listed materials (for example, deeds or entire multi‑round comment histories) rarely change their decision and can contain extraneous PII. Kyle Denardo said the narrative required by Elbert County typically contains the information needed to evaluate approval criteria and that some supporting forms "do not change our decision." Jennifer proposed packaging a concise cover sheet (the items decision makers need) while keeping full supporting materials available in CDS offices if needed for deeper review.

Legal counsel, Lance, warned against decision makers conducting independent investigations outside the record. He told the group that if a commissioner develops information independently, it must be disclosed on the record to protect the county from challenge. He said site visits and other ways to see properties are possible, but any material relied on for the decision should be in the record assembled by staff and the applicant.

The group also discussed how referral agency comments and response histories should appear in packets. Several members preferred a final referral comment and the applicant's final response (rather than every earlier round) so reviewers see resolved issues rather than a confusing, multi‑round history. Jennifer suggested compiling final agency responses and putting earlier iterations in an appendix so the record shows both the final, resolved items and the development history.

On meeting minutes and transmission of planning commission recommendations to the BOCC, legal counsel noted minutes are summaries of action and that audio/transcripts can supplement minutes for anyone needing more detail. Several planning commissioners said they would like clearer ways for the planning commission to communicate the reasons behind split or minority recommendations when the item advances to the BOCC.

Outcomes and next steps: Participants agreed to start a subcommittee to draft a recommended packet checklist and any regulatory language changes and to give discretion to the chairs of the planning commission and the BOCC to convene that group. Staff cautioned that an ad hoc subcommittee with three or more members will be subject to Colorado open‑meetings requirements and must be noticed at least 24 hours in advance.

Members asked CDS to work with legal to return recommended language and procedures that (1) protect PII in posted packets, (2) clearly identify the minimum items required in the public packet and (3) describe where and how supplemental documents (referral histories, large multi‑round files) will be stored and made available. No regulatory changes were adopted at the meeting; participants agreed to continue work through the subcommittee and return recommendations to the full bodies for formal action.

Ending: The working group called the session productive and planned follow‑up meetings through the chairs and CDS staff. The group did not take formal votes on regulatory changes at this meeting and deferred any final decisions to subsequent, noticed meetings.