GLOGood Lookin’ Out

Michigan regulations: details

Copied from the rule-set PDF files the Michigan Office of Administrative Hearings and Rules posts on its Administrative Rules System site on October 20, 2026. Check the official page before you rely on a rule.

What is here

  • Michigan: rules of the Michigan Administrative Code as the rule-set PDF files that the Michigan Office of Administrative Hearings and Rules (MOAHR) posts on its Administrative Rules System site print them, fetched by GLO on 2026-10-20 and read by machine: GLO's reading of the publisher's files, not the publisher's own presentation. 19,610 rules are served as text, 5,647 of them rescinded rules shown as the file prints them ("Rescinded" and the History line, no text); 2,552 rules are held, each by number with its reasons, mainly rules on pages that carry a table (919), rules the two readers read differently (498), rules whose catchline runs onto a second line (409); 88 are held because a page they span prints a line through text (words struck through, or a fraction bar), which GLO's reading does not mark (Release 1b, 2026-10-21, holds 68 of them that Release 1 served as text until then, 28 with struck words in their text); 1 of the publisher's 770 files could not be fetched (R 285.641.1 to R 285.641.18, Agriculture and Rural Development: Regulation No. 641. Commercial Fertilizer Bulk Storage), so its rules are not here. Release 2 (2026-10-21) holds 51 more rules that Release 1b served as text until then: 14 whose text runs on past their own History line into a next rule whose head was printed in a form GLO's readers missed, and 37 whose text ends on a cut word; the other 18,510 are served with the same text, nothing mended or split. These tests catch a run-on only where a History line comes before the missed head, and a cut end only on a word a sentence cannot end on; others are not caught. Release 3 (2026-10-24) holds 152 more rules that Release 2 served as text until then: a page of theirs prints a word with one character struck through (a comma, a period or a letter under a short stroke), which the earlier test, counting a stroke only when it crosses half a word or more, did not see; the other 18,358 are served with the same text, nothing mended. The test is page-wide and also holds some rules whose mark is not a strike; a strike shorter than 1 point, or made some other way than a drawn line, is still not seen. Release 4 (2026-11-01) shows 12 more rules, of the Department of Corrections' General Rules, held until then because their catchlines ran onto a second line. Their words are the file's own text, with the catchline's second line moved back to the catchline. They were compared with a separate AI model's reading of the page images, and their heads were read by hand; no person read their whole text, and the readers and the model can share a fault. Release 5 (2026-11-01) shows 948 more rules, held until then because their catchlines ran onto a further line. Their words are the file's own text, with the catchline's later lines moved back and checked against the file's bold type. An AI model compared a sample with the page images; no person read them, and the readers and the model can share a fault. Release 6 (2026-11-02) shows 217 more rules, held until then because their catchlines ran onto a further line and the file's two text readers also differed in spacing. A third program found the first reader's words, the catchline's later lines moved back and checked against the file's bold type. An AI model compared a sample with the page images; no person read them. Release 6 also removes page numbers GLO's readers had read into the text of 9 rules (R 460.702, 460.722, 460.724, 460.732, 460.741, 460.744, 460.746, 168.359 and 168.361). In R 460.746 the number had made a figure read "6 or 10 more"; the rule now reads as the file prints it. Release 7 (2026-11-02) restores 5,462 line breaks in 783 rules where the file starts a numbered or lettered item on its own line, and changes no word. An AI model compared a sample with the page images; no person read them. Release 8 (2026-11-02) shows 75 more rules, held until then because their catchlines ran onto a further line and the file's `Rule` line prints a number that does not end like the rule's number; both numbers are shown as the file prints them. It also restores 784 line breaks in 302 rules where the file starts a new line after a line ending a sentence, and changes no word; some of these may be only where a line of the page wraps, not a new paragraph. An AI model compared a sample of each with the page images; no person read them. Other breaks, including breaks that cross a page, may still be lost, so a closing sentence or a list may still run on from the line before; check the file. Release 9 (2026-11-02) takes back 7 line breaks in 7 rules that Release 7 had put where the page runs on as one sentence, most of them inside a cross-reference such as R 338.619(1) and (2); no word changes. An AI model compared each of the 10 places of that shape with its page image and kept the 3 the page sets out as separate items; no person read them. Other wrong or lost breaks may remain; check the file. Rules the two readers read differently beyond spacing stay held. 409 rules with a wrapped catchline stay held. Each rule shows its History line as its file prints it and the date its file was made; neither is a finding that the rule is in force. The served rules were checked by hand against the publisher's own rendering on 60 drawn rules, so a fault rarer than about 1 in 20 rules could remain unseen. Nothing here says a rule is current or still in force; check the publisher's file before relying on it.
  • Release 9: 19,610 rules from 763 of the publisher’s 770 rule-set files, copied on October 20, 2026. 5,647 of them are rules the file prints as rescinded: we show the word “Rescinded” and the History line, and no text.
  • Of the 22,162 rules our readers found, 2,552 are held and not shown, each with its reasons: mainly rules on pages that carry a table (919), rules the two readers read differently (498), rules whose catchline runs onto a second line (409). A held rule comes back as held, with its reasons and no text. Held is not absent.
  • 1 file could not be fetched (R 285.641.1 to R 285.641.18, Agriculture and Rural Development: Regulation No. 641. Commercial Fertilizer Bulk Storage); the site answered with its own error page. Its rules are not in this copy; the file is listed by name.
  • Each rule shows its catchline, its part heading, its History line and any Editor’s Note as the file prints them, the department and bureau the publisher’s index names, and the date the PDF file was made. That date is not an effective date.
  • Look a rule up by its number, as in R 791.701. A long rule comes back in pages, and nothing is cut. R 791 lists the rule sets under that number, and each rule set lists its rules: shown and held.

How we checked it

  • Two separate readers, written with no shared code, read every file, each with a different PDF library. A rule is shown only where both agree on every word of its number, catchline, text, History line, part heading and Editor’s Note.
  • Where the two differed only in spaces, a third, separate program read the file, and the rule is shown only if that program found the first reader’s words in the same order, spaces and hyphens set aside (3,029 rules).
  • A rule is held when its page carries a table, an image or a line through text (even through one character of a word), when the readers differ, when its catchline runs onto a second line, when the next part’s heading runs into it, when its number is printed twice or falls outside its file’s range, or when a page footer stands in its text.
  • A rule is also held when its text goes on after its own History line (the next rule’s head was printed in a form our readers missed), or ends on a word a sentence cannot end on, with another rule after it.
  • Before release, we drew 60 shown rules at random, in three draws of 20, and read each one word for word against the publisher’s own web rendering of its file. The first two draws found faults of three kinds (a heading run into a History line, a catchline’s second line read as text, part headings run together); every rule showing one of those kinds was then held. The third draw matched in full.
  • 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.
  • When a rule took effect. The file’s date is when the PDF was made; the History line is the publisher’s own record.
  • What the held rules say, or what the file that could not be fetched holds.
  • Whether anything changed after the files were copied.

Known gaps

  • 2,552 rules are held, not shown; the largest group is rules on pages that carry a table (919); next are rules the two readers read differently (498).
  • Release 6, on November 2, 2026, shows 217 more rules, held until then because their catchlines ran onto a further line and the file’s two text readers also differed in spacing. A third program found the first reader’s words, the catchline’s later lines moved back and checked against the file’s bold type. An AI model compared a sample with the page images; no person read them. Release 6 also removes page numbers GLO’s readers had read into the text of 9 rules (R 460.702, 460.722, 460.724, 460.732, 460.741, 460.744, 460.746, 168.359 and 168.361). In R 460.746 the number had made a figure read “6 or 10 more”; the rule now reads as the file prints it. Release 7 (2026-11-02) restores 5,462 line breaks in 783 rules where the file starts a numbered or lettered item on its own line, and changes no word. An AI model compared a sample with the page images; no person read them. Release 8 (2026-11-02) shows 75 more rules, held until then because their catchlines ran onto a further line and the file's `Rule` line prints a number that does not end like the rule's number; both numbers are shown as the file prints them. It also restores 784 line breaks in 302 rules where the file starts a new line after a line ending a sentence, and changes no word; some of these may be only where a line of the page wraps, not a new paragraph. An AI model compared a sample of each with the page images; no person read them. Other breaks, including breaks that cross a page, may still be lost, so a closing sentence or a list may still run on from the line before; check the file. Release 9 (2026-11-02) takes back 7 line breaks in 7 rules that Release 7 had put where the page runs on as one sentence, most of them inside a cross-reference such as R 338.619(1) and (2); no word changes. An AI model compared each of the 10 places of that shape with its page image and kept the 3 the page sets out as separate items; no person read them. Other wrong or lost breaks may remain; check the file.
  • Release 5, on November 1, 2026, added 948 rules whose catchlines ran onto a further line. Their words are the file’s own text, the catchline’s later lines checked against the file’s bold type; an AI model compared a sample with the page images, and no person read them.
  • Release 4, also on November 1, 2026, added 12 rules of the Department of Corrections’ General Rules whose catchlines ran onto a second line. Their words are the file’s own text; they were compared with a separate AI model’s reading of the page images and their heads were read by hand. No person read their whole text, and the readers and the model can share a fault.
  • Release 2, served on October 21, 2026 until Release 3 replaced it on October 24, showed 152 rules on pages that print a word with one character struck through (a comma, a period or a letter under a short stroke), so their text kept a character the agency struck. Release 3 holds them by name. The test is page-wide, so some held rules carry a mark that is not a strike; a strike shorter than 1 point, or made some other way than a drawn line, is still not seen.
  • Release 1b, served on October 21, 2026 until Release 2 replaced it the same day, showed 51 rules whose text ran on past their own History line into the next rule or ended cut short. Release 2 holds them by name; a run-on with no History line before the missed head, or a cut end on another word, is not caught.
  • The rules were read by machine and checked by hand on 60 drawn rules, so a fault rarer than about 1 in 20 rules could remain unseen.
  • Long part headings keep the PDF’s line breaks.
  • Keyword search reads only the shown rules. Held rules have no text here and never match.

Notes you may see on an entry

  • A held rule: “GLO holds this rule and does not show its text, because its two readers or the release check did not clear it. Its reasons are listed by name.”
  • A rescinded rule: “The file prints this rule as rescinded. We show the word and its History line, and no text.”
  • A file not fetched: “The publisher’s site did not return this file. It is listed by name; its rules are not in this copy.”
  • A rule not in this copy: “Not in this copy of Michigan’s regulations, 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 Michigan result (source=mi).

Michigan regulations in GLO: what is here and how it was checked