GLOGood Lookin’ Out

Tennessee regulations: details

Copied from the Tennessee Secretary of State’s posted chapter PDFs (https://sharetngov.tnsosfiles.com/sos/rules/), saved through a browser, on October 25 and 27, 2026. Check the official page before you rely on a rule.

What is here

  • Tennessee: GLO’s reading of the Tennessee Secretary of State’s posted chapter PDFs (https://sharetngov.tnsosfiles.com/sos/rules/) for every agency its rules pages link: Release 1, agencies 0420 (Department of Correction) and 1100 (Board of Parole), saved on 2026-10-25; Release 2, the other 115 agencies, saved on 2026-10-27; both through a browser (the site refuses scripts). The Secretary of State’s files are the publication; this text is not official. Nothing was checked against the Tennessee Administrative Register, so GLO does not say any rule is current, and pending and emergency rules are not included. Two of the Secretary of State’s pages refused the crawl (1360/1360-03/1360-03.htm and voting_systems/index.htm), so files linked only from them are not here. 11,801 of the 16,529 rules the files print are shown, 1,946 of them printed REPEALED and shown with only their Authority and history; 4,728 are held by name and not shown, each with its reasons. Held, by class (a rule can carry more than one): a rule printed by two posted files of one chapter (21 chapters), GLO not choosing which is current (TWO_FILES_ONE_CHAPTER 1,964); a word broken at a line end with a hyphen that GLO would not guess, including joins after a prefix and rarely printed spellings held rather than guessed (HYPHEN_JOIN_DOUBT 744); a paragraph label that may sit inside a sentence (LABEL_DOUBT 882); a file in which no rule heading was found (listed under its chapter, with no text) (NO_RULE_FOUND 321); a heading run over two lines into the text (HEADING_SPLIT 151); a heading GLO read cut inside the rule’s own number (HEADING_CUT 13); and a rule number printed more than once in the set (KEY_DUP 1,981); a file whose footers print more than one revision line (FOOTER_VARIES 258); a rule whose own pages print two different revision dates (FOOTER_DATES_IN_RULE 18); a superscript or subscript (SUPSUB 595); a number not in the chapter’s own table of contents (NOT_IN_LIST 545); the two readers disagree (READERS_DIFFER 486); a word left split at a line end (SPLIT_AT_KEPT_BREAK 298); a rule number printed wrong in its own heading (NUMBER_MISPRINT 212); a number the contents list but the file does not head (NOT_IN_BODY 201); text after the Authority paragraph (TEXT_AFTER_AUTHORITY 187); a footer run into the text (FOOTER_IN_TEXT 128); two Authority paragraphs (TWO_AUTHORITY 130); no Authority paragraph to end the rule (NO_AUTHORITY 99); a heading naming a range of numbers (RANGE_HEADING 87); pages whose text layer lost its hyphens (HYPHEN_LOSS 39); a page’s continued line run into the text (CARRYOVER_IN_TEXT 22); a REPEALED heading with text after it (REPEALED_WITH_TEXT 2); a table whose text across a page break does not read in the page’s line order (TABLE_CELL_ORDER 2); a linked file the host refused (1200-13-05.20150630.pdf) (NOT_SAVED 1). Release 1 was repaired on 2026-10-31 from a later reading of its twelve files: 0420-03-04-.03 and 0420-03-04-.04 are shown as the later readers read them on 2026-10-27 (read_at says so; the rest of Release 1 was read on 2026-10-25); 1100-01-01-.06 is held for a false paragraph label read on the page (a cross-reference set as a new paragraph), not corrected because GLO does not edit a paragraph split by hand; and 0420-02-01-.07, 0420-04-01-.01, 0420-04-01-.08 and 0420-04-01-.10, which the later readers flagged, were read against their pages by one reader, whose read found the labels real, and they stay shown. The shown rules were read by two readers that agree on every character, whitespace aside, and checked by hand on 60 drawn rules. On 2026-11-01, 15 Release 2 rules had their spacing after a hyphen repaired, by a reader rule from the files’ text and two samples read on the page, not read one by one on page images (statutes.section_tn_reg_r2d, carried unchanged into statutes.section_tn_reg_r3b, statutes.section_tn_reg_r4, statutes.section_tn_reg_r5 and statutes.section_tn_reg_r10). Release 3, built on 2026-11-03 from the same saved files: 150 rules of 18 Release 2 files, held until then only because each file’s pages print one revision month and year typed in more than one way, are shown; for them footer_revision is the form most of the file’s pages print, a tie going to the earliest page’s; each was checked against the text of its own pages, and 14 drawn were read by hand on the page images (statutes.section_tn_reg_r3b, carried unchanged into statutes.section_tn_reg_r4, statutes.section_tn_reg_r5 and statutes.section_tn_reg_r10). Release 4, built on 2026-11-03 from the same saved files: 205 rules of 33 Release 2 files, held until then only for their revision lines, are shown: 59 whose file prints the line misspelt, mistyped or cut on some pages (footer_revision is the readable form the file prints on the most pages, corrected by GLO), 129 whose file’s pages print different revision dates (footer_revision is the one the rule’s own pages print) and 17 whose revision line is the page’s last line, above GLO’s footer band; each was checked against the text of its own pages and 14 drawn were read by hand on the page images. 36 rules shown until then, each a table whose words GLO’s readers set out of the page’s order, were then held (TABLE_CELL_ORDER) (statutes.section_tn_reg_r4, its other rules carried unchanged into statutes.section_tn_reg_r5 and statutes.section_tn_reg_r10). Release 5, built on 2026-11-04 from the same saved files: 35 of the 37 table rules held for their order are shown, their text unchanged: read on the page’s lines (top to bottom, each left to right) it is in the page’s order; the earlier check had compared it with the PDF’s internal order, which runs a table column by column. Where a page sets one row’s label on several lines, the row’s figures sit on the line between, as printed (table_note). Each was checked on its own pages by a reader built on the characters’ positions and 14 drawn were read by hand on the page images; 2 stay held (TABLE_CELL_ORDER) (statutes.section_tn_reg_r5, carried unchanged into statutes.section_tn_reg_r10). Release 10, built on 2026-11-04 from the same saved files: 289 of the 368 rules held until then for a word broken at a line end with a hyphen or a page footer run into the text are shown. In them each such hyphen is kept or closed up as the rule’s own file prints that word in mid-line, kept where the file never breaks a word at a line end, and only where the file is silent as the corpus’s own spellings clearly settle it (hyphen_note); a page footer’s revision line is taken out of the text (footer_note). Each was checked on its own pages by a separate reader built on the characters’ positions, and 14 drawn were read by hand on the page images. 79 of the 368 stay held by name (a rule can carry more than one class): a paragraph that may run on past a page break into one the page sets apart (PARAGRAPH_JOIN_DOUBT, 59 of the 79); a hyphen neither the file nor the corpus settles (HYPHEN_JOIN_UNSETTLED, 17 of the 79); a new paragraph started in the middle of a sentence where the page may only leave a gap (PARAGRAPH_SPLIT_DOUBT, 5 of the 79); a text not found in the order its pages print it (PAGE_ORDER_CHECK, 2 of the 79); a label that may continue a citation (LABEL_SPLIT_DOUBT, 2 of the 79); 11 of them also for a footer in the text (statutes.section_tn_reg_r10). Releases 6 to 9 were built and failed their checks, and were never shown. The same tests, run over rules shown since earlier releases, flag places that may be faults of these kinds, and those rules stay shown as before until a later correction release reads them on their pages: a paragraph that may run on past a page break, outside an Authority paragraph (162 rules); a new paragraph started mid-sentence at a gap (16); a label set as a new paragraph that may continue a citation (10); a hyphen dropped where the file never breaks a word at a line end (3); and 1045-02-.05’s perioperative, which its page may print peri-operative. The tests over-hold, so not every flagged place is a fault. Release 11d, built on 2026-11-04 from the same saved files, read such places again: in 89 shown rules GLO corrected the text (text_corrected_by_glo): a paragraph break restored where the page ends a paragraph at a page break (78 rules), a running head the file prints atop its pages taken out of the text (7), a citation’s tail set as a paragraph label joined back (4); apart from a running head line taken out, every word and digit is as read before, and each was checked on its own pages by a separate reader. 91 rules shown until then are now held by name instead (PARAGRAPH_JOIN_DOUBT 59, PARAGRAPH_SPLIT_DOUBT 13, RUNNING_HEAD_IN_TEXT 6, HYPHEN_JOIN_UNSETTLED 4, NUMBER_SPLIT_AT_LABEL 4, PARAGRAPH_BREAK_UNPLACED 4, TAG_SPLIT_AS_PARAGRAPH 2; a rule can carry more than one class); with the rules held before, the held rules carrying these classes numbered at Release 11d: a paragraph that may run on past a page break into one the page sets apart (PARAGRAPH_JOIN_DOUBT, 118 at Release 11d); a hyphen neither the file nor the corpus settles (HYPHEN_JOIN_UNSETTLED, 21 at Release 11d); a new paragraph started in the middle of a sentence where the page may only leave a gap (PARAGRAPH_SPLIT_DOUBT, 18 at Release 11d); a running head left in the text (RUNNING_HEAD_IN_TEXT, 6 at Release 11d); a rule number wrapped at a line end and split as if its last part were a label (NUMBER_SPLIT_AT_LABEL, 4 at Release 11d); a page’s paragraph break GLO could not place exactly once (PARAGRAPH_BREAK_UNPLACED, 4 at Release 11d); a label that may continue a citation (LABEL_SPLIT_DOUBT, 2 at Release 11d); a text not found in the order its pages print it (PAGE_ORDER_CHECK, 2 at Release 11d); a short tag the file prints at a paragraph’s end set as its own paragraph (TAG_SPLIT_AS_PARAGRAPH, 2 at Release 11d). Two of these tests (the split rule number and the tag set as a paragraph) are patterns run over the text, not readings of the pages. 14 rules drawn from an earlier build of this release were read by hand on the page images; the one that did not match is held by name here. Release 12, built on 2026-11-04 from the same saved files, followed a census of running heads over all 11,748 shown rules: in 4 of them a running head or a page’s carryover line had stayed in the text, and GLO took it out (RUNNING_HEAD_STRIPPED, text_corrected_by_glo); every other word and digit is as read before, each was checked on its own pages, and all 4 were read by hand on the page images. The census finds a head only where it is the first text line of a page, so it does not prove that no other shown rule carries one, and other shown rules may still carry faults of these kinds (statutes.section_tn_reg_r12, every other shown rule carried unchanged). Release 13c, built on 2026-11-04 from the same saved files, read the held places on the page images: 53 rules held until then for where a paragraph starts or ends at a page break or a gap, or for a running head, number or tag set as its own line, are shown, each such place read on its page image by a model reader (not a person) and set as read, and each rule checked on its own pages by a separate reader (page_read_note; text_corrected_by_glo where the text changed, in 44 of them); and one shown rule, 1395-01-07-.06, gets back the list item (b) its page prints just above the running head, which GLO’s first reading had left out (DROPPED_LINE_SET, text_corrected_by_glo). Rules read the same way stay held by name where a check of the page’s line layout found lines the page sets on their own run together in GLO’s text, or where the page reading could not be placed or disagreed; with them, the held rules carrying these classes now number: a paragraph that may run on past a page break into one the page sets apart (PARAGRAPH_JOIN_DOUBT 81); a page that sets some lines on their own, such as a form’s labels, a table’s rows or an address, where GLO’s text runs them together (LAYOUT_RUN_TOGETHER 52); a hyphen neither the file nor the corpus settles (HYPHEN_JOIN_UNSETTLED 21); a page reading GLO could not place exactly once in its text (PAGE_READ_UNPLACED 14); a new paragraph started in the middle of a sentence where the page may only leave a gap (PARAGRAPH_SPLIT_DOUBT 11); a running head left in the text (RUNNING_HEAD_IN_TEXT 6); a text not found in the order its pages print it (PAGE_ORDER_CHECK 3); a page reading that disagrees with GLO’s text on where a paragraph ends (PAGE_READ_DISAGREES 3); a label that may continue a citation (LABEL_SPLIT_DOUBT 2); a page’s paragraph break GLO could not place exactly once (PARAGRAPH_BREAK_UNPLACED 1). No rule is now held for a rule number split at a label or a tag set as a paragraph. 12 rules drawn (11 of this release and the restored 1395-01-07-.06) were read by hand on their page images by model readers: 11 text match and 1 unsure about a printed gap inside a sentence, with no fault found. Release 13f, built on 2026-11-04 from the same saved files, sets a plus-minus sign (±) at the 4 places in 1200-03-31-.13 where the page prints a plus with a line drawn under it, the typed form of plus-minus (PLUS_MINUS_UNDERLINED, text_corrected_by_glo); a check of every shown rule’s pages found no other underlined plus, and the 2 plus signs that page prints plain stay plain. Release 13e, built on 2026-11-04 from the same saved files, ran a check of each page’s line layout over the rules shown in earlier releases and set a line break at 1,375 places in 239 shown rules where the page sets a line on its own, such as a form’s label, a table’s row or an address line, and GLO’s text ran the lines together (LAYOUT_LINE_SET, text_corrected_by_glo); each is taken only from the rule’s own lines on its page, and the words are unchanged. 16 rules whose flagged lines were another rule’s on a shared page, and 5 where a hyphen or dash stands at the place, are left as served; on the rules’ own lines 248 line pairs the check matched more than once (243 with every match joined, 5 mixed) and 29 it found nowhere could not be placed and stay as served. The check reads a line that wraps inside a narrow table cell as a line of its own, so some breaks show a cell’s wrap; table rows it never pairs and columns printed side by side stay as served. 12 rules drawn were read on their page images by three model readers (not people), with no fault on a break this release set (statutes.section_tn_reg_r13f, every other shown rule carried unchanged). In 14 shown rules the page prints 73 pictures inside the rule, such as a formula (0800-03-03-.10), a map, a form or a scanned appendix page, that GLO’s text does not carry, and in some of them that is most of the rule; each such answer names the pages to read on the page image (pictures_not_in_text, PICTURE_NOT_IN_TEXT). Nothing here says a rule is current or in force; check the Secretary of State’s rules before relying on one.
  • Releases 1 to 5, 10, 11d, 12, 13c, 13e and 13f: 11,801 of the 16,529 rules the files of 117 agencies print. Release 1 is the Department of Correction (0420) and the Board of Parole (1100), saved on October 25, 2026; Release 2 is every other agency the Secretary of State’s pages link, saved on October 27, 2026. Release 3 (November 3, 2026) shows 150 more rules from 18 of Release 2’s files, held until then only because their pages print one revision month and year typed in more than one way; for them GLO shows the form most pages print. Release 4 (November 3, 2026) shows 205 more from 33 of Release 2’s files, held until then only for their revision lines (a form misspelt or cut on some pages, pages printing different dates, or a line set low on the page), and held 36 rules shown until then whose tables GLO’s check found out of the page’s order. Release 5 (November 4, 2026) shows 35 of the 37 table rules held for their order again, their text unchanged: read on the page’s lines, it is in the page’s order (the earlier check had compared it with the PDF’s internal order, which runs a table column by column); where a page sets one row’s label on several lines, the row’s figures sit on the line between, as printed. 2 stay held. Release 10 (November 4, 2026) shows 289 of the 368 rules held until then for a word broken at a line end with a hyphen or a page footer run into the text: each such hyphen is kept or closed up as the rule’s own file prints that word, and the footer lines are taken out of the text; 79 stay held. Releases 6 to 9 were built and failed their checks, and were never shown. Release 11d (November 4, 2026) corrects the text of 89 shown rules where their paragraphs break at a page break, a running head ran into the text, or a citation’s tail was set as a paragraph label (each answer says so), and holds by name 91 rules shown until then whose text may carry faults of these kinds. Release 12 (November 4, 2026) corrects the text of 4 shown rules where a census of running heads over every shown rule found a running head or a page’s carryover line left in the text (each answer says so). Release 13c (November 4, 2026) shows 53 rules held until then for where a paragraph starts or ends at a page break or a gap, or for a running head, number or tag set as its own line: each such place was read on the page image by a model reader, not a person, and set as read (each answer says so), and 1395-01-07-.06 gets back a list item its page prints just above the running head that GLO’s first reading had left out. Rules read the same way whose page sets some lines on their own, such as a form’s labels or a table’s rows, while GLO’s text runs them together stay held by name (52 rules). Release 13e (November 4, 2026) sets a line break at 1,375 places in 239 shown rules of earlier releases where the page sets a line on its own, such as a form’s label, a table’s row or an address line, and GLO’s text ran the lines together: each was taken from the rule’s own lines on its page by a geometric check, and the words are unchanged (each answer says so). Release 13f (November 4, 2026) sets a plus-minus sign at the four places in 1200-03-31-.13 where the page prints a plus with a line drawn under it, and names the 14 shown rules whose pages print a picture GLO’s text does not carry. Of the 11,801 shown, 1,946 are printed as REPEALED and shown with only their Authority and Administrative History.
  • 4,728 rules are held and not shown, each with its reasons. The largest reasons: a rule number printed more than once (1,981); a rule printed by two posted files of one chapter, 21 chapters (1,964); a paragraph label that may sit inside a sentence (882); a word broken at a line end with a hyphen that GLO would not guess (744). A held rule comes back as held, with every file that prints it and its reasons, and no text. Held is not absent.
  • This is GLO’s reading of the Secretary of State’s PDFs, not an official text. Each rule is shown with the version date its file name carries, or none, and the revision line its own pages print. One file name, 0785-01.21010717.pdf, carries a date in 2101; GLO shows it as printed and marks it. Nothing was checked against the Tennessee Administrative Register, and pending and emergency rules are not included.
  • Each answer is a whole rule: its heading as printed (“REPEALED.” for a repealed one), its paragraphs, and its Authority and Administrative History (the rule’s own record of its filing, amendments and repeal) as the chapter prints them, with the agency, division and chapter lines where the file’s first page prints them.
  • Look a rule up as Tenn. Comp. R. & Regs. 0420-01-02-.04, Rule 1100-01-01-.14, 0020-01-.01 (a chapter numbered in two parts) or 0420-01-02-.04; the older form 0420-2-1-.03 works too. A subsection such as 1100-01-01-.14(2) returns the whole rule. Chapter 0420-01-02 or Chapter 0020-01 lists the rules of that chapter: shown and held.

How we checked it

  • For Release 13f, every shown rule was checked byte for byte against Release 13e but 1200-03-31-.13, which was checked to differ at exactly the four places, each plus to plus-minus; the six plus signs on its pages were clipped, shuffled and read by a model reader not told which were underlined, who named all six right.
  • For Release 13e, every shown rule it did not correct was checked byte for byte against Release 13c, and each of its 239 corrected rules was checked to differ only where a run of spaces became one line break at a listed place on the rule’s own lines, with its words unchanged and no flagged line pair left on its own lines. 12 corrected rules were read against images of their pages by three model readers not told GLO’s classes: none showed a fault on a line break this release set.
  • For Release 13c, each of its 53 rules was checked on its own pages by a separate reader (its text found in the page’s order, every break the page reading set at a page break or a gap the page shows), a check of the page’s line layout found none of its lines that the page sets on their own run together, and every other shown rule was checked byte for byte against Release 12 but 1395-01-07-.06, whose restored line was found on its page just above the running head. 12 rules, both restored lines among them, were read against images of their pages by three model readers not told GLO’s classes: 11 matched, 1 was unsure about a printed gap inside a sentence, and none showed a fault.
  • For Release 12, each of the 4 corrected rules was checked on its own pages by a separate reader (its text found in the page’s order, every line taken out the page’s running head or carryover line), every other shown rule was checked byte for byte against Release 11d, and all 4 were read by hand against images of their pages: 4 matched.
  • For Release 11d, each of the 89 corrected rules was checked on its own pages by a separate reader (every paragraph and break found there, every word and digit unchanged but a running head line taken out), every other shown rule was checked byte for byte against Release 10, and no shown rule matches the two pattern tests. 14 rules of an earlier build were read by hand against images of their pages: 13 matched, and the one that did not is held by name. Three earlier builds of this release (11, 11b and 11c) were never shown.
  • For Release 10, each of its 289 rules was checked on its own pages by a reader that rebuilds the page’s lines from each character’s position: every heading and paragraph had to be found in the page’s line order, every hyphen kept or closed up had to match the file’s own printing of that word, and no paragraph could start in the middle of a sentence or run on past a page break after a short last line. 14 of them were read by hand against images of their pages: all 14 matched, and the reader agreed with every one of the 15 hyphen corrections it checked. Four earlier builds of this release (Releases 6 to 9) each failed a check on a new kind of fault and were never shown; each of those kinds now holds its rules by name.
  • For Release 5, each of its 35 table rules was checked on its own pages by a reader that rebuilds the page’s lines from each character’s position: its heading and every paragraph had to be found in the page’s line order, one after another, as a run of the page’s words. 14 of them were read by hand against images of their pages, and every one read in the page’s order. 2 rules, 0180-16-.03 and 1720-01-09-.02, failed that check where their text runs across a page break, and stay held.
  • For Release 4, each of its 205 rules was checked against the text of its own pages, its revision line was read again from the PDF by the check’s own reader and found to be a form the file prints, and 14 of them were read by hand against images of their pages. Where a file prints its revision line misspelt or cut on some pages (59 rules), GLO shows the readable form the file prints most and says it corrected it; where a file’s pages print different dates (129 rules), the one the rule’s own pages print; where the line is the page’s last line (17 rules), that line. 18 rules whose own pages print two dates stay held.
  • For Release 3, each of its 150 rules was checked against the text of its own pages (every heading and paragraph, spaces and hyphens aside), its footer value is a form the file prints on at least as many pages as any other, and 14 of them were read by hand against images of their pages. One more rule of those files, 0400-45-01-.11, was held because a table cell printed on two lines seemed read out of the page’s order. The same check over the 11,088 rules Release 2 showed found 36 more, all in tables (fee schedules and columns), whose words are the page’s but not in the page’s order: 0080-03-02-.04, 0080-03-02-.07, 0080-05-04-.18, 0080-05-15-.03, 0160-01-.12, 0180-16-.03, 0400-15-01-.13, 0400-20-10-.27, 0400-48-01-.11, 0400-48-01-.21, 0460-01-.02, 0465-02-02-.05, 0620-05-01-.03, 0780-01-65-.15, 0780-01-71-.05, 0780-01-73-.06, 0800-01-03-.05, 0880-13-.06, 0950-01-02-.05, 1050-02-.02, 1150-02-.02, 1200-03-20-.06, 1200-06-03-.02, 1200-08-02-.13, 1200-12-01-.06, 1240-01-02-.02, 1240-02-01-.01, 1240-02-01-.02, 1240-02-01-.03, 1340-06-01-.07, 1540-01-06-.04, 1640-01-07-.05, 1660-01-08-.03, 1680-03-04-.12, 1710-01-02-.08 and 1720-01-09-.02. Release 4 held them (TABLE_CELL_ORDER). That check had compared each rule with the PDF’s internal order, which runs a table column by column; read on the page’s printed lines, 35 of the 37 are in the page’s order, and Release 5 shows them again; 0180-16-.03 and 1720-01-09-.02 stay held.
  • In Release 2d, GLO restored 14 marks in 4 rules (degree signs in 0400-40-03-.11 and em dashes in 0600-06-.01, .02 and .03) that its readers had kept as a symbol font’s codes. A mark this rule did not reach may still show as a blank or a box.
  • The Secretary of State’s site refuses scripts, so a desktop session that Jeff Trzaska ran saved the chapter PDFs in his browser, keeping each file only when its SHA-256 matched the one computed in the page; we read those saved files, and no script asked anything of the site.
  • Two separate readers, written with no shared code and using two different PDF libraries, read every chapter. A rule is shown only where both give the same characters in the same order (spaces aside).
  • A rule is held when its number is printed twice or by two files of one chapter, when a hyphen at a line end could be a real hyphen or a word split to fit the line, when a paragraph label may sit inside a sentence, when its heading runs into or is cut by the text, when it prints no Authority paragraph or two, when it prints a superscript, when its number is printed wrong or not in the chapter’s contents, or when the two readers disagree.
  • Before release, 60 shown rules drawn at random (20 in Release 1, 40 in Release 2 over 30 agencies) were read against images of their pages, every word and digit, and 30 hyphen joins were checked on the page. The one Release 2 rule that differed began a class GLO now holds (a heading cut inside the rule’s own number, 13 rules).
  • One AI system wrote the readers, ran every check and made every reading and ruling; the drawn rules were read by other instances of the same system, with no human reader.

What it can't tell you

  • Whether a rule is in force, valid or current, or is good law.
  • Any change after the version the Secretary of State posted for each chapter, and any pending or emergency rule.
  • What the held rules say.
  • Whether this text matches the PDF in some way the readers cannot see.

Known gaps

  • 4,728 rules are held, not shown, each with its reasons by name (coverage_note counts every class).
  • Release 13e’s check of each page’s line layout reads a line that wraps inside a narrow table cell as a line of its own, so some of its breaks show a cell’s wrap; table rows it never pairs, columns printed side by side, and 277 line pairs it could not place on the rules’ own lines stay as GLO first read them. In 14 shown rules the page prints a picture inside the rule (73 in all: a formula such as 0800-03-03-.10’s, a map, a form or a scanned appendix page) that GLO’s text does not carry, sometimes most of the rule; each such answer names the pages to read on the page image.
  • Release 11d’s hold tests for a rule number split at a label and a tag set as a paragraph are patterns over the text, not readings of the pages, and Release 12’s census of running heads finds a head only where it is the first text line of a page, so other shown rules may still carry faults of the kinds Releases 10 and 11d hold.
  • Release 10’s tests, run over rules shown since earlier releases, flag places that may be faults of the kinds Release 10 holds: a paragraph that may run on past a page break (162 rules), a new paragraph started mid-sentence at a gap (16), a label set as a new paragraph that may continue a citation (10), a hyphen dropped where the file never breaks a word at a line end (3), and 1045-02-.05’s perioperative, which its page may print peri-operative. Those rules stay shown as before until a later correction release reads them on their pages; the tests over-hold, so not every flagged place is a fault.
  • Two of the Secretary of State’s pages refused the crawl (1360/1360-03/1360-03.htm and voting_systems/index.htm), so files linked only from them are not here; one linked file, 1200-13-05.20150630.pdf, was refused by the host and is not saved.
  • Release 1 was repaired on October 31, 2026, from a later reading of its twelve files. 0420-03-04-.03 and 0420-03-04-.04 are shown as the later readers read them on October 27, 2026; the rest of Release 1 was read on October 25, 2026. 1100-01-01-.06 is held for a false paragraph label read on the page (a cross-reference set as a new paragraph), not corrected because GLO does not edit a paragraph split by hand. 0420-02-01-.07, 0420-04-01-.01, 0420-04-01-.08 and 0420-04-01-.10, which the later readers flagged, were read against their pages by one reader, whose read found the labels real, and they stay shown. Those seven rules had that one reader and no second.
  • For some files the first page prints no chapter line above its contents, so those rules carry no agency, division or chapter line.
  • The chapters’ tables of contents are not carried. Bold, italics and indents are not kept; a few short lines keep their own line.
  • Keyword search reads only the shown rules. Held rules have no text here and never match.

Notes you may see on an entry

  • A repealed rule: “The chapter prints this rule as REPEALED: it is shown with only its Authority and Administrative History, and it is not a rule in force.”
  • A held rule: “GLO holds this rule and does not show its text, because its readers or the release check did not clear it. Its reasons are listed by name, with the file that prints it.”
  • A subsection asked for: “The whole rule is shown, with a note; the subsection is inside it under its own number or letter.”
  • A rule or agency not here: “Not in this copy. That never means the rule does not exist: two of the Secretary of State’s pages refused the crawl, and a rule changed after its chapter’s posted version may differ or be absent.”

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

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