GLOGood Lookin’ Out

Utah regulations: details

Copied from the rule files on eRules, the Utah Office of Administrative Rules’ site on October 12, 2026. Check the official page before you rely on a rule.

What is here

Release 3, the last: 18,351 sections of the Utah Administrative Code, from 2,229 of the 2,324 current rules, read by us from the rule files on the Utah Office of Administrative Rules’ eRules site. Release 3 adds 1,994 sections from 110 rules to Release 2’s 16,357: in rules with a table drawn as page layout, the sections with no table in them, and in rules with a paragraph that looks like a section heading, the sections without one. Release 2 added 560: in rules whose file heading differs from the publisher’s rule list only in capital letters, in rules whose files draw lines or shading but no table, and in the two rules the publisher’s list gives twice, read from the file each rule’s own record names. We copied the files on October 12, 2026 (those two rules on October 13, 2026). A rule changed after that is not reflected here.
It is not the official code. The Office calls its code Utah’s official repository of administrative rules; read the rule there. The eRules site prints the notice “Utah Secretary of State ... All Rights Reserved”. That notice is the publisher’s, not ours. We show the rule text as law, under the rule that the text of the law belongs to the public (Georgia v. Public.Resource.Org, Inc., 140 S. Ct. 1498 (2020)). That is our reading, not legal advice.
eRules announced that it relaunches on October 16, 2026. Its addresses may change, so a link here may stop working after that.
We found 19,677 sections in the 2,324 rules. 1,376 units in 282 rules are held and not shown, each by name with its reasons: mainly rules whose closing lines are missing, repeated or followed by more text, places where our two readers disagree, sections that hold a table drawn as page layout, section numbers out of order, and section headings in a shape our readers do not take (49 such headings are listed by their own number, so asking for one says it is held). A held unit comes back as held, with its reasons and no text. Held is not absent.
One rule, R414-303, has an emergency amendment in effect. Its text is not shown here, and every section of that rule says so.
Each section comes back with its rule’s name and agency, the effective date the publisher’s rule list prints, and the closing lines the rule file prints once at the end of the rule (KEY, Date of Last Change, Notice of Continuation and the authorizing law).
Utah shipped in three releases, and Release 3 is the last for this copy. The held units stay held, each by name with its reasons; nothing held is shown.
Look a section up by its number, as in R13-1-1, Utah Admin. Code R13-1-1 or U.A.C. R13-1-1. A long section comes back in pages, and nothing is cut. A rule number such as R13-1 lists its sections: shown and held.

How we checked it

Two separate readers, written with no shared code, read every rule file: one in the file’s own order, one by where each line sits on the page. A section is shown only where both agree on its number, its caption and every word of its text.
A whole rule is held when its file prints rotated text or a picture, has a section number out of order, or its closing lines are missing or repeated. A table drawn as page layout holds only the section it sits in (lines or shading with no text in them hold nothing), and so does a paragraph that begins with the rule’s own number the way a heading would.
A check run on the whole release confirmed that the shown and held units add up to every unit found, that every rule listed was fetched and read, that every held unit has a reason and no shown one has one, and that every shown section has a number, a caption and text.
Before release, a person compared 20 shown sections drawn at random with the rule’s PDF from the same site. All 20 matched word for word. The rule’s closing lines were checked against the PDF text for all 20 rules. Before Release 2, a person compared 20 of the added sections, drawn at random, with the rule’s PDF in the same way. All 20 matched word for word. Before Release 3, a person did the same for 20 of the sections it added, looking for table text or a heading the section had lost. All 20 matched word for word.
Every comparison, read and ruling was made by one person, with no second reader.

What it can't tell you

Whether a rule is in force or valid.
Whether anything changed after we copied the files on October 12, 2026 (two rules on October 13, 2026).
Whether it agrees with the official code.
The text of emergency and proposed rules.
A section heading the file leaves out entirely: its text would be shown under the section before it.

Known gaps

1,376 units in 282 rules are held and not shown. The most common reasons: the rule’s closing lines missing, repeated or followed by more text (358), our two readers disagreeing (356), and a table drawn as page layout (322).
Bold or italic type, underlining, indentation and strike-through are not shown; the words are.
Keyword search reads only the shown sections. Held units have no text here and never match.

Notes you may see on an entry

A held unit: “GLO holds this unit and does not show its text, because its readers did not clear it. Its reasons are listed by name.”
A section of R414-303: “An emergency amendment to this rule took effect 8/13/2026 and, by the publisher's list, ends 12/11/2026. Its text is not served here; read it on the publisher's site.”
A section not in this copy: “Not in this copy of the Utah Administrative Code, neither shown nor held. 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 Utah result (source=ut).