# Colorado Compliance Index — October 2026

Publisher: EnergyzedWorld / Chris Mbori. Methodology 1.1.
Canonical article: https://energyzedworld.com/bps/colorado-compliance-index
Edition: 2026-10. Status inputs retrieved October 1, 2026, approximately 02:03–02:05 MDT (08:03–08:05 UTC). Each status record carries its source's retrieval timestamp. These are observation dates, not the authorities' last-update dates. Rules pages were also reviewed October 1.

## Metric and status semantics

Report acceptance = accepted / (listed - explicit exemptions, waivers and non-covered records) × 100, rounded to one decimal. Unknown statuses stay in the denominator. This is an annual-reporting observation, not legal or energy-performance compliance. Do not rank programs with different calendars and coverage or sum overlapping jurisdiction counts.

`accepted`: source label In Compliance (case-insensitive).
`revision`: Pending revisions, Pending revisions: Error, Pending revisions: Warning, or Received but not in compliance.
`excluded`: Exempt, Approved for waiver, or Non-covered.
`not_submitted`: explicit Not submitted or Submission not received label.
`unknown`: no published or joined status. Other, newly observed labels stop the build for review.

For Denver, Boulder and Fort Collins, `filed_at_least` = accepted + revision; `not_filed_count` = explicit not-submitted labels. These are public-label measures, not a complete private-portal submission ledger. For Colorado, receipt is not established by the pending-error label: both measures are null. Colorado's underlying `not_submitted: 0` means zero occurrences of those specific labels, not zero non-filers. Aspen has no current status evidence, so accepted, revision, not_submitted, excluded, denominator and rate are null. Its 189 unknown records reflect address-list coverage only. Lakewood's counts are all null: no public inventory/status dataset was obtained.

## Source universes

### Colorado

Public list: https://co.beam-portal.org/cbl/2/properties/?cycle_id=8
Cycle 8 is explicitly labeled "2026 Reporting Period (2025 Calendar Year Energy Data)".
Identity API: https://co.beam-portal.org/cbl/properties/filter/?organization_id=2&include_related=false&cycle=8&per_page=1000&page=1 (all 11 pages).
Status API: https://co.beam-portal.org/map/inventory_locations/properties/?organization_id=2&cycle=8

The universe is 10,363 unique list IDs. Join identity property_view_id to status id; decode labels from the page's cbl-data status_payload. Seven identities have no status-map match and four matched rows have null status. Status-map rows outside this identity list do not expand the denominator. All identities are retained, including 463 missing gross floor areas and 226 below 50,000 sq ft. Those are data-quality flags, not independent eligibility judgments.

### Denver

Map: https://map.energizedenver.org/
API: https://app.touchstoneiq.com/api/region/map?hash=ee666b4105180a50229c83a2b8292b4f&year=2026&valid_id=1&parent_property=1&only_compliant=1&required_to_report=1

3,104 unique building IDs. Required-to-report parent-property query, unchanged from September. The API parameter `only_compliant=1` is retained because the map itself uses it; it does NOT mean we select only accepted statuses. The response includes accepted, revisions, not submitted and exempt records. Older ArcGIS exports are excluded.

### Boulder

Coverage workbook: https://bouldercolorado.gov/media/4225/download?inline
Map: https://maps.touchstoneiq.com/boulder/ (the older touchstonebenchmarking.com URL redirects here).
API: https://app.touchstoneiq.com/api/region/map?hash=efed58b997d2c6d503ba03fb9c0bfe59&year=2026&valid_id=1&parent_property=1&only_compliant=1&required_to_report=1&voluntarily_reported=1

The workbook, identical to September by SHA-256, defines 478 IDs: 427 private and 51 city-owned. Reviewed ranges: `2026 Affected Buildings List!A6:F432` and `City-Owned Buildings!A6:D56`. All 476 map IDs join to that universe. EB427 and EB251 remain unknown. Older workbook status values are not used. Both required and voluntary API flags are deliberately retained from the baseline to join the workbook universe, although the map's default UI selects required records. No map-only rows are added.

### Aspen

2026 covered list: https://www.aspen.gov/DocumentCenter/View/15687
Historical report, background only: https://www.aspen.gov/DocumentCenter/View/15566

The covered PDF is byte-identical to September. A section-aware parser and visual page review identify 190 address occurrences: 121 commercial, 46 multifamily and 23 city. Exact uppercase-address deduplication gives 189 strings; 155 LONE PINE RD appears twice. Addresses such as `540, 550 E Main Street` and `50-400 HARMONY PL` are retained, not split. Similar but nonidentical addresses are not merged. This is not a certified count of physical buildings or independently benchmarked properties. No current filing labels are published in this input. Synthetic address-row IDs are edition-local, not stable identifiers for longitudinal building comparisons.

### Fort Collins

Map: https://maps.touchstoneiq.com/fortcollins/
API: https://app.touchstoneiq.com/api/region/map?hash=8ymNl9ucL5kwynzTt7pkwO6VBEwJOQgy&year=2026&valid_id=1&parent_property=1&only_compliant=1&required_to_report=1

1,362 unique IDs. Required-to-report only, as in September. The UI defaults to including voluntary records, but those are not added to this series. The observed map population is not a certified full inventory.

### Lakewood

Official program: https://www.lakewoodtogether.org/benchmarking-and-building-performance
First 2025-energy report due December 31, 2026. No current public coverage/status inventory obtained from the official pages reviewed. Unavailable is not zero. State records bearing a Lakewood city name are not substituted for the local 10,000+ sq ft universe.

## Conservative Denver–state match

Select state city field DENVER (uppercase, trim), require the same numeric state jurisdiction_property_id_101 and Denver building_id, then require equal, nonblank normalized addresses. Normalization: uppercase, remove punctuation, collapse whitespace, and map STREET/ST, AVENUE/AVE, BOULEVARD/BLVD, ROAD/RD, DRIVE/DR, COURT/CT, PLACE/PL, NORTH/N, SOUTH/S, EAST/E, WEST/W, PARKWAY/PKWY, CIRCLE/CIR and LANE/LN. No fuzzy matching or manual joins.

1,893 shared IDs yield 1,488 ID-and-address matches; 405 address mismatches are excluded. Among 1,363 Denver-accepted matches, 730 have state Pending revisions: Error and 633 have state In Compliance. 730/1,363 = 53.6%. This selected subset is not representative. Different deadlines, source-refresh timing or record boundaries can produce different labels; the observations do not establish a violation or its cause.

## Comparing with September

Both snapshots use the same reporting cycle, source filters, rate formula and deterministic match rules. Compare source universes and explicit exclusions before rates:

- Colorado: list 10,390 → 10,363; 28 entered IDs and 55 exited; exclusions 14 → 22; denominator 10,376 → 10,341; unknowns 85 → 11.
- Denver: one ID exited, no entrants; exclusions 68 → 69; denominator 3,037 → 3,035.
- Boulder and Fort Collins: unchanged ID sets and denominators.
- Aspen: unchanged coverage document and count; no status trend. Lakewood: no measurable status trend.

`monthly-change.json` reports common IDs, entrants/exits, status-group transitions and accepted-count attribution. Colorado's 10,335 common IDs show 412 revision-to-accepted and 52 unknown-to-accepted changes, offset by six accepted-to-other changes. One new ID is accepted: net +459. Unknown-to-accepted changes include previously unavailable information, not necessarily new submissions. IDs can survive changes to source identity fields, so a common-ID comparison is a reporting-record cohort, not verified longitudinal physical-building tracking.

Percentage-point changes use unrounded accepted/denominator fractions and are then rounded to one decimal. Subtracting rounded displayed rates can differ by 0.1 point (Denver: +0.7 points from raw fractions, despite displayed 88.2% → 89.0%).

Cross-match populations: 1,489 → 1,488, with 1,484 shared matched IDs, four entrants and five exits. Within the shared matches, split labels move 799 → 728. Of the September split-status records in that shared set, 83 now show acceptance in both systems; other transitions offset part of that change. Do not interpret the headline 804 → 730 as exactly 74 resolved cases.

## Methodology version 1.1 and preservation

The formula and coverage definitions are unchanged. Version 1.1 makes Aspen's unavailable metrics null instead of underlying zero label occurrences, adds a nullable `not_filed_count`, assigns per-source retrieval timestamps, explicitly rejects blank-address matches/new status vocabulary, and adds monthly cohort reconciliation. The Aspen extractor now skips headings and repeated footer text and retains comma/range addresses. Its verified 190-occurrence/189-distinct count is unchanged from the published baseline. These are parsing, validation and representation changes, not new compliance outcomes.

The September 2026 dataset, methodology, article source and original hero remain byte-for-byte unchanged. The current October article source is archived alongside this dataset. Full raw public responses stay local; published records contain minimal IDs/status labels without owner contact information or property addresses. `source-manifest.json` supplies hashes, sizes and retrieval timestamps, including background evidence that is not a calculation input. `source-review.md` identifies official rule checks and map endpoints.

## Other limits and citation

Reported city names are postal/source fields, not verified municipal boundaries. Campus/property structures can differ by program. Public maps can lag owner portals; confirm final status directly. Never add overlapping jurisdiction totals or infer legal/energy-performance compliance from report acceptance.

Citation: Mbori, Chris / EnergyzedWorld. Colorado Compliance Index, October 2026. Observed October 1, 2026 MDT. Methodology v1.1. Cite the stable article and dated dataset. Corrections: chris.mbori@aimdynamics.com with program, record ID, period and official evidence. Independent analysis; not a government index.