GLOGood Lookin’ Out

Colorado regulations: details

Copied from the Word files of the Colorado Secretary of State’s Code of Colorado Regulations site on October 19, 2026. Check the official page before you rely on a rule.

What is here

Release 2: 514 of the 843 current documents of the Code of Colorado Regulations, about six in ten, read by us from the Word file of each document’s current version on the Colorado Secretary of State’s site: 89 from the newer .docx files, as Release 1 showed them, and 425 from old binary Word files. We copied the files on October 19, 2026. Each document comes back whole, its head first and its Editor’s Notes last, as its Word file prints them. A document changed after we copied it is not reflected here.
329 current documents are held and not shown, each by name with its reasons: mainly documents whose two readers do not read the same words (123) and documents whose list line says they were repealed, recodified, moved, superseded or transferred (105); others carry pictures, drawings or equations (76), text printed through fields or symbols (47), a current version the site lists with no date (41), or struck-through text (2). A held document comes back as held, with its reasons and no text. Held is not absent.
256 documents the agencies’ lists mark repealed come back as repealed, with the list’s own words and no text.
It is not the official print: the authenticated PDF on the Secretary of State’s site is. The site says its publications “may be outdated or inaccurate and may be revised from time to time without notice”. Its terms forbid robots and data mining and claim copyright in some of its publications; those are the State’s words, not ours. We show the rule text as law.
Look a document up by its number, as in 1 CCR 101-9, 1 Colo. Code Regs. 101-9 or 6 CCR 1007-3 Part 100. A long document comes back in pages, and nothing is cut. An agency number such as 1 CCR 101 lists its documents: shown, held and listed repealed.

How we checked it

Two separate readers, written with no shared code, read every Word file. For the .docx files one uses an XML parser and one its own tag scanner; for the old binary Word files one is antiword, a long-standing open-source reader, and the other our own reading of the file format. A document is shown only where both agree on every word, paragraph by paragraph and table row by table row.
Where the two binary readers differ only in capital letters, we show the letters the file stores: Word can display a heading in capitals without storing capitals, so a heading the PDF prints in capitals may show here in mixed case, the same letters.
A document is held when it carries a picture, drawing, text box or equation, footnotes, struck-through text, or text printed through fields or symbols, when its two readers disagree, when its file prints its number differently from the site’s list, when the site sent an error page instead of the file or lists its current version with no date, when its list line says it was repealed, recodified, moved, superseded or transferred, when its notes record the entire rule repealed, when it is a placeholder titled Reserved, or when its current version prints only its head and notes.
A check run on the whole release confirmed that every document of the site’s lists is shown, held or listed repealed, that every repealed flag matches the saved list pages, and that every held document has a reason.
Before each release we read 20 shown documents drawn at random against the site’s authenticated PDF: the head, one inner passage and the last line of the Editor’s Notes. In Release 1, 19 matched word for word; the 20th printed only its head and notes ending “Entire rule repealed” although its list did not mark it repealed, and that kind of document is now held. In Release 2, 19 matched word for word, with no struck-through text on their pages; the 20th was a placeholder titled “Reserved for Future Use” whose notes end “Entire rule repealed”, and that kind of document is now held too.
A separate test of every old binary Word file looked for struck-through text in its formatting; it found 2 such documents, which are held, and the same struck words were found drawn through on their PDFs.
One AI system wrote the readers, ran every check and made every reading and ruling, with no second reader.

What it can't tell you

Whether a rule is in force, valid or current, or is good law.
Whether anything changed after we copied the files on October 19, 2026.
Whether the Word text agrees with the authenticated PDF beyond the 40 documents we compared.
What the held documents say.

Known gaps

329 of the 843 current documents are held and not shown, each by name with its reasons.
Word’s all-caps display is not carried: a heading the PDF prints in capitals may show here in mixed case, the same letters.
Headers, footers and footnotes of the Word files are not shown; pictures, drawings and equations are not carried, and a document that has them is held.
Bold, underline, italic type, indentation and page layout are not shown; a table comes back one row a line, its cells separated by a tab.
Keyword search reads only the shown documents. Held documents have no text here and never match, so part of the Code is outside search.

Notes you may see on an entry

A held document: “GLO holds this document and does not show its text yet, because its two readers or the release check did not clear it. Its reasons are listed by name.”
A document listed as repealed: “The agency’s list on the Secretary of State’s site marks this document repealed. GLO lists it with the list’s own words and shows no text.”
A document not in this copy: “Not in this copy of the Code of Colorado Regulations, neither shown, held nor listed repealed. That never means the rule does not exist.”

Nothing here is legal advice or a judgment that a rule is in force. Full counts for software: the defect_floor field on every Colorado result (source=co).