Straight into the service manual page
WrenchQuarry
More

4 fields to log for each safety standard a crew follows

WrenchQuarry Editorial Team · Published · 16 min read · How these guides are written

Every safety standard a crew cites needs four logged fields: the source and section number, the source's stated status, the amendment date with its year, and the effective or operative date. Together they answer four plain questions: what the standard is, what it claims to cover, which version is current, and when that version began to apply. The California railings regulation shows why both dates matter, because its amendment notes give a filing date and a separate operative or effective date for the same section.

The four fields

A job file works when every cited standard gets the same four fields, filled in the same way each time. Consistency matters more than polish. A crew member who opens the file months later should find the same information in the same place for every entry, whether the standard is a one-page guideline or a long regulation.

The first field is the source and section, named exactly as the source names it. Include the page title and any section number, so someone can locate the document again without guessing which page the crew meant.

The second field is the source's status: what the source says it covers and whether it claims to override anything else. This is the field most often filled in badly. A page title alone can make a reference look authoritative when it is only a general aid, so write the status from the source's own words rather than from the title.

The third field is the newest amendment date, written with its year. The fourth is the effective or operative date that applies to the version the crew uses. Record which word the source itself uses, because the two words are not interchangeable in the file.

The lead-acid battery page from CCOHS answers the status question in its own words: "NOTE: This OSH Answers document provides general guidance for lead-acid batteries used to operate vehicles and is not meant to replace the manufacturer's or legislation's requirements." (CCOHS: Garages - Lead-acid Batteries) That sentence sets the rule for the status field. A crew that cites this page is citing general guidance, so the entry should say so in those terms.

The same sentence also tells you what else the file needs. The manufacturer's requirements and the legislative requirements for the same batteries are separate sources, and each one gets its own entry beside the general guidance. When a reviewer later asks why a crew followed a particular practice, the file should show which document the practice came from and whether that document was meant to replace anything. Four consistent fields answer that question without anyone rebuilding it from memory.

Before filing, open each cited source, read its scope sentence, and copy the relevant words into the status field. It takes a few minutes for each standard and saves a great deal of confusion later.

Battery records need their own entries

Battery work does not all follow one source. The lead-acid page points readers elsewhere for other battery types, and it does so specifically: "Please see the OSH Answers Battery Safety - High-Voltage Batteries in Electric, Hybrid, or Plug-in Hybrid Vehicles for other battery systems." The pointer names the systems that fall outside the lead-acid guidance, and that is the boundary your log should follow.

For the job file, the practical rule is one entry for each document, not one entry for each shop or job. A crew that services lead-acid units and also works on high-voltage packs cites the two guidance pages plus the manufacturer's and legislative requirements, so the log needs a separate entry for each source. Merging them into one "battery safety" line hides which guidance applied to which vehicle. That gap causes trouble when a crew member assumes lead-acid practices carry over to a high-voltage system, which they may not.

When a work order says only "battery safety," ask one question before filing it: which battery system is involved? If the answer is a lead-acid battery in a vehicle, log the lead-acid entry. If it is a high-voltage pack, log the high-voltage entry under the title exactly as the pointer prints it. Each entry keeps its own four fields, and the status for the high-voltage document reflects its own scope, not the lead-acid work.

Side-by-side battery references

The two battery references can be compared on the same measures, which makes the logging decision easier. The lead-acid quote and the pointer quote back the first and second rows; the manufacturer row's coverage and the high-voltage row's scope are not quoted from those documents themselves.

ReferenceBattery system coveredStated statusEntry to make
Lead-acid battery pageVehicle lead-acid batteriesGeneral guidance, not meant to replace manufacturer or legislation requirementsOne entry for lead-acid battery practices
High-voltage battery pageHigh-voltage packs in vehicles, the systems the pointer namesNamed by the lead-acid page as the reference for other battery systemsA separate entry for high-voltage work
Manufacturer's requirementsBatteries covered by the manufacturer's documentNot replaced by the general guidance, as the lead-acid page's note statesOne entry for each manufacturer document

Reading across the rows shows the pattern. The first two rows differ in the battery system covered, so they cannot share an entry. The first and third rows may cover the same batteries, but their status differs. The general guidance says it is not meant to replace the manufacturer's or legislation's requirements, and logging the status for each row keeps that statement visible. A crew that cites the general guidance should be able to show from the file alone that the manufacturer's document was checked too. If you could not check a row, flag it in the file instead of leaving it looking complete.

Repeals and renumbering

Regulations change by subsection, and the history note at the end of a section records each change. The California railings regulation, Section 1620, has an entry filed 3-19-79 that does two things at once. Its history note reads: "Repealer of subsection (d) and renumbering of subsections (e)-(i) to subsections (d)-(h) filed 3-19-79; effective thirtieth day thereafter (Register 79, No." (California Code of Regulations, Title 8, Section 1620)

Read the entry carefully. Subsection (d) was removed. Subsections (e) through (i) moved down one letter, so (e) became (d), and (i) became (h). A crew note that cites "subsection (i)" from before the change now points to a different provision, and a note citing "subsection (d)" may point to something that no longer exists under that letter. The renumbering is the trap, not the repeal alone.

For the file, the entry should carry these fields. The source and section are Section 1620 under its page title as printed. The status records a history note for a repeal and renumbering. The amendment date is the filing date, 3-19-79. Enter the year from that printed date in the year field, and keep the printed form beside it.

The effective field records that the change took effect on the thirtieth day after filing, which is the wording the source uses. Do not substitute a calculated calendar date. The register reference is Register 79. In the same row, record both the old and new letters for each moved subsection, so any older note can be translated to the current lettering.

Amendments that keep the lettering

Not every change renumbers anything. The entry filed 1-14-86 for the same section amends a single subsection and leaves the letters alone. The note reads: "Amendment of subsection (c) filed 1-14-86; effective thirtieth day thereafter (Register 86, No."

Subsection (c) sits before the point where the 3-19-79 renumbering began. That renumbering started at subsection (e), so the letter (c) did not change. A crew note citing subsection (c) still points to the provision the 1-14-86 amendment changed. This is a useful check: when an amendment affects a subsection that was not renumbered, the letter in the entry stays the same, and only the amendment date and effective rule need updating.

For the log, the source and section stay as before. The status notes an amendment to subsection (c), not a repeal. The amendment date is the filing date, 1-14-86, and the year field takes its year from that printed date. The effective field records the thirtieth-day rule as printed, and the register reference is Register 86.

Each amendment gets its own dated row. A reviewer who sees only the newest text of subsection (c) cannot tell that its wording changed at the 1-14-86 filing. Keep this row even after a later change, so the history of the subsection stays readable to anyone who opens the file.

Adding a subsection

The history note also records additions. One entry adds a new subsection and uses different wording for when it applies: "New subsection (i) filed 6-1-92; operative 7-1-92 (Register 92, No."

This filing comes after the 1-14-86 and 3-19-79 entries, and before the 2007 entry below. The 3-19-79 renumbering moved the former (i) to (h), so the letter (i) was free to be used again. That renumbering moved the former (i) to (h), so the letter (i) was free to be used again, and this entry uses it for a new provision. A crew citing subsection (i) must confirm which version applies, which is why the date field matters.

The entry records two dates. The filing date is 6-1-92. The operative date is 7-1-92, and the source uses the word "operative" here, not "effective." Log that exact term, because the two words can carry different meanings in the file. The fields are the source and section, the status (a new subsection added), the amendment year taken from the 6-1-92 filing, the operative date of 7-1-92, and the register reference, Register 92.

Keep the new subsection's letter in the entry alongside both dates. A row that shows only the year of each event hides the month and day that separate the two, and the operative date is the one that tells the crew when the provision began to apply.

The 2007 amendment

The newest entry in the history note is the 2007 amendment, and it changes more than one part of the section. The note reads: "Amendment of article heading, section heading and section filed 4-20-2007; operative 5-20-2007 (Register 2007, No."

Three parts changed in one filing: the heading over the article, the heading over the section, and the section text itself. A file that records only "section amended" misses two of the three. Make one entry for the amendment and list each part the note names, so a reader can see that the heading a crew sees today changed in 2007, not just the body text.

The note gives two dates. The filing date is April 20, 2007, and the operative date is May 20, 2007. The note uses the word "operative," so log that word rather than "effective." The operative date is the one the crew relies on for work performed after it took hold.

For the four fields, the source is Section 1620 under its page title as printed. The status lists the changed parts. The year field reads 2007. The operative field reads May 20, 2007, and the register reference reads Register 2007. Because this is the latest entry in the excerpt, any crew note that quotes an older heading should be checked against this row before anyone repeats the old wording.

Cotton dust corrections

Minnesota's rules list corrections by item number and date, and a correction can point to a section other than the one a crew normally cites. One entry reads: "234, dated 12/5/78; "Corrections to 1910.1046; Occupational Exposure to Cotton Dust in Cotton Gins."" (Minnesota Legislature, Revisor of Statutes, Rule 5205.0010)

Read the entry as a record of a correction, not as the rule itself. It gives item 234, the date 12/5/78, and a subject: corrections to section 1910.1046, which the title identifies as occupational exposure to cotton dust in cotton gins. The corrected section is the number a crew would cite, so the correction belongs in the file next to that section.

The excerpt does not say what publication item 234 appears in, and the file should not fill that gap from memory. Log the number and date exactly as printed. If someone needs to trace the item to its original publication, record that trace as a separate step with its own source, so the Minnesota entry stays a faithful copy of what the page says.

A correction is also not always the same as the rule it corrects. Keep the correction and the underlying section as separate items in the file, with a note linking them, so a reader does not mistake the amended wording for the whole standard.

The date is printed with a two-digit year, "78." Take the full year from the printed date for the year field, and leave the printed date in the row so a reviewer can match the two. The same pattern applies to any standard a crew cites: an item number, a date, and the section the correction names.

Exposure limit corrections

The second correction covers a different section and date: "237, dated 12/8/78; "Corrections to Tables of Exposure Limits for Air Contaminants, 1910.1000."" It comes from the same Minnesota list, so it needs no second citation here.

The two corrections are three days apart, 12/5/78 and 12/8/78, and they name different sections: 1910.1046 for cotton dust and 1910.1000 for the exposure limit tables. Keep them as two rows. A reader who saw only one row might assume the tables and the cotton dust section were corrected together, and the separate dates show they were recorded as separate events.

The status field should say that the item corrects the tables, not name an individual limit. The excerpt lists no values from the tables, so do not record any in the file. Point the row to the full section for the numbers themselves.

Handle the year the same way as the cotton dust entry: take the full year from the printed date and leave the printed "78" in the row. Using one format for both corrections lets a reviewer scan the two rows without translating dates.

Comparing the amendment dates

The history note records four entries in this excerpt: the 3-19-79 repealer and renumbering plus three amendments, and this table covers only the three amendments. The table compares the filing date, the date the source gives for the change to apply, and the register reference for each amendment, with the 3-19-79 entry treated in the Repeals and renumbering section instead.

EntryPart changedFiling date (as printed)When it applies (as printed)Register
Amendment filed 1-14-86Subsection (c)1-14-86Effective on the thirtieth day thereafterRegister 86
New subsection (i) filed 6-1-92New subsection (i)6-1-92Operative 7-1-92Register 92
Amendment filed 4-20-2007Both headings and the section text4-20-2007Operative 5-20-2007Register 2007

The 1-14-86 entry gives a rule instead of a calendar date, so the file should show the rule as printed and not work out a date from it. The 6-1-92 and 4-20-2007 entries give calendar dates for the operative day. Each row copies the source's own word, effective or operative, so do not standardize the column.

Reading down the table, each row answers a different question. The 1-14-86 row shows which subsection changed and when the change was filed. The 6-1-92 row shows a letter coming into use again. The 4-20-2007 row shows several parts changed together. Keep all three rows, even though the newest text replaces the older ones, so anyone can trace how the section reached its present form.

Choosing your battery entries

The choice a team lead faces most often is how many entries a battery reference needs. Three options are possible, and the sources support only one of them for mixed work.

OptionEntries in the job fileWhat the sources support
1. Lead-acid page aloneJust the guidance row, which leaves the file incompleteCovers vehicle lead-acid batteries, and states it does not stand in for manufacturer or legislation requirements, so those rows are still missing
2. Lead-acid page plus high-voltage pageTwo entries, one for each battery systemThe lead-acid page points to the high-voltage page for other battery systems
3. Option 2 plus manufacturer and legislationSeparate entries for each sourceMatches the lead-acid page's note that its guidance does not replace those requirements

Pick option 3 when a crew works on lead-acid batteries and also on high-voltage packs. Option 1 leaves out the high-voltage reference that the lead-acid page names. Option 2 records both guidance pages but omits the manufacturer's and legislation's requirements, which the lead-acid note says the guidance does not replace. Option 3 is the only one that reflects both statements in the sources.

Choosing too few entries is the more common error. A team that picks option 1 for a shop that also handles high-voltage packs ends up with a file that looks complete but leaves out a reference the lead-acid page itself names, and that gap is hard to spot during a review. Give each source its own row, and copy the lead-acid page's scope statement into the status field as written.

Decisions that come up at the bench

A few decisions come up whenever a team fills in these rows, and the answers come from the same sources. For a general guidance page, copy its scope into the status field in the page's own terms. Use the full wording rather than a shorter version, because a shorter one drops the statement that the guidance does not replace other requirements.

One entry cannot cover both lead-acid and high-voltage work. The lead-acid page sends readers to a separate page for other battery systems, so each gets its own row.

When subsection letters have shifted, record both the old and new letters for each moved subsection. A note written before the 3-19-79 change that cites "(i)" may now point to a different provision, and the old and new letters let the team see that at a glance.

Log "effective" or "operative" as the source prints it. The 1-14-86 entry says "effective," while the 6-1-92 entry and the 2007 entry say "operative." Swapping one word for the other changes the record, even when the dates seem to line up.

Keep older amendment rows after a newer change. An older row shows what the text was at each point. Without the 1-14-86 row, a reviewer looking at the current subsection (c) could not tell that its text changed at that filing.

The Minnesota corrections carry two-digit years, 12/5/78 and 12/8/78. Enter the full year and leave the printed date in the row, so the row can be matched to the source.

The exposure table correction names only its subject and the section 1910.1000. The excerpt lists no values, so the file should not record any. The cotton dust correction works the same way: the excerpt gives the item number, date, and subject, and nothing more.

The 2007 amendment changed both headings and the section text together. One entry should list all three parts, with the filing date of 4-20-2007 and the operative date of 5-20-2007, using the word "operative" as the source does.

Finally, the two Minnesota corrections are separate events. Item 234, dated 12/5/78, corrects section 1910.1046 on cotton dust, and item 237, dated 12/8/78, corrects the tables under 1910.1000. The dates are three days apart but name different sections. Keep them as two rows so a reviewer can see each correction on its own, and trace item 234 to its publication separately if anyone asks where it came from.

Not legal or tax advice.

Related guides: Annual driver record review: 4 checks every 12 months · Apply 8 safety checks before dispatching for hot work · Battery charging safety: 7 checks before you start.

Sources

More field guides