Safety rule history: 3 checks before crew handoff

• Name the version label exactly as the page shows it.
• Read the dated history notes and annotations next to the rule, and check the full entry for anything cut off.
• Match every number, date and deadline to the version you are reading.

When a dispatcher passes a rule to a crew, or an owner tells a foreman what a rule says, the instruction carries whatever version of the text the speaker happened to read. Rules get amended, replaced and republished, and an older copy can look just as official as a newer one. A page that loads cleanly is not proof that it is the text the crew has to follow.

This post gives three history checks to run before you rely on a rule text. They are working habits, not legal advice. Each check draws on the official examples in this post, and each example holds only where it applies. The two UK sources quoted here come from UK legislation. The California source is California's own rule. Neither one is a general rule for other places, other agencies or other kinds of work. If you are unsure which text governs your job, ask the person who owns the rule before the crew acts on it.

After those, we cover a worked example, how to pass a checked rule on, and a short checklist.

Name the version label on the page you are reading, because the same rule can appear in more than one form. The UK legislation website makes this visible. On its page for regulation 10 of the Construction (Design and Management) Regulations 2015, the site says: "At the current time any known changes or effects made by subsequent legislation have been applied to the text of the legislation you are viewing by the editorial team."

That sentence has two parts to read carefully. The first is that the text you see may already include later changes. The second is that the editorial team has applied the changes it knows about. The sentence says "any known changes," so it describes changes the site has applied. It does not say anything about changes that have not been applied. For a dispatcher, the point is that the copy you read today may differ from the text as it was first made, and the version label is what tells you which one you have.

The same page explains that the versions it offers depend on the item being viewed. It says: "Dependent on the legislation item being viewed this may include:" Two of the labels that follow matter for this check. The first is "Original (As Enacted or Made): The original version of the legislation as it stood when it was enacted or made." The second is "Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team."

Put plainly, the Original label points to the text as it stood when it was made, while the Latest Available (revised) label points to the text with later changes applied. If one person reads one label and another person reads the other, they may be working from two different instructions without knowing it. That gap is what this check is meant to catch.

Paper copies and screenshots can cause trouble here. A printed page or a picture on a phone may not show the version label, so before you rely on a copy, go back to the page it came from and read the label there. If the label is missing from the copy, treat the copy as unconfirmed.

Here is what to do with this check:

• Write the label beside the rule, using the wording on the page. Keep "Original (As Enacted or Made)" or "Latest Available (revised)" as written, instead of a shorter phrase you made up.
• Avoid describing a copy as "the current rule" or "the official version" unless the page itself uses that wording. Those are your words, not the page's words.
• If you cannot find a version label, do not fill the gap by guessing. Say the version is unconfirmed and ask the owner before the crew acts on it.

The quoted sentences do not say which label applies to a particular job. That decision belongs to the person who owns the rule. Do not make it yourself because one label reads more clearly to you.

Yes, a text can change after you first read it, so check the dated history notes before you rely on it. Two official examples show what such notes can look like, and they are formatted differently from each other. Read the format of each source you use before you go looking for a date.

The first example is from California. The California Code of Regulations, Title 8, Section 1510, titled "Safety Instructions for Employees," carries history notes that record filings. Under California's section, one entry reads: "Amendment filed 5-21-75; effective thirtieth day thereafter (Register 75, No." The quoted text stops at "No.", so the register number is not shown here. Read plainly, the entry says the amendment was filed on 5-21-75 and became effective on the thirtieth day after filing.

Another entry on the same page reads: "Repealer and new section filed -27-85; effective thirtieth day thereafter (Register 85, No." In the quoted text, the filing date appears only as "-27-85", with the part before the hyphen missing. Rather than guess the missing part, read the full entry on the page before you give a date to a crew. The two entries describe two separate filings, and each one carries its own effective-date wording. A date you copy from a summary can drop part of an entry, so go back to the entry itself. Treat a history note as a pointer to the entries and dates you need to read in full, not as a summary of them.

The second example is from the UK. Schedule 3 of the Construction (Design and Management) Regulations 2015 has an entry about work with ionizing radiation that requires the designation of controlled or supervised areas under regulation 17 of the Ionising Radiations Regulations 2017. The page also carries an annotation that reads: "3 substituted (1.1.2018) by The Ionising Radiations Regulations 2017 (S.I." The quoted annotation stops partway through the citation, so the rest of it is not shown here. What the quoted part does show is a substitution dated 1.1.2018, made by The Ionising Radiations Regulations 2017.

For a dispatcher, the lesson is to read the date on any annotation before you treat the wording as settled. If the notes show a change, compare the date of that change with the version you are reading. A copy that predates the change may not show it.

They must, and you should confirm it rather than assume it. Each number, date and deadline has to come from the same version as the rule's wording, because a figure is only as current as the version it came from. The examples in Check 2 show why dates matter. The California notes carry filing dates and effective-date wording. The UK annotation carries a substitution date of 1.1.2018. A date taken from one version and placed in the wording of another can mislead a crew, even when both pages look official.

When you relay a number, copy it from the page rather than from memory. Do not round it, shorten it or convert it to a different unit unless the owner tells you to. Keep the number's exact wording next to the version label and the date you checked. That way anyone who reads the message can compare it with the source without asking you.

If the same number appears in two versions with different values, treat that as a version question, not as a typing mistake, until you have checked both pages. Writing the two values side by side is faster than arguing about which one is right.

Read the whole sentence around a number, too, not only the figure. A number can change what a sentence requires, such as whether it sets a minimum or a maximum. When you pass a number on, copy the full sentence so the crew can see the scope of the number.

Suppose a dispatcher receives an unlabelled copy with an illustrative deadline of 10 days. This is a made-up figure, not a safety requirement.

First, the dispatcher asks the owner for the page the copy came from and checks its version label. Second, the dispatcher reads the dated notes and finds an annotation later than the message. Third, the dispatcher compares the deadline: the page says 50 days, also an illustrative figure.

Instead of choosing one, the dispatcher sends the owner both versions, each with its label, its date and its link. Last, the dispatcher records the checks and the owner's answer.

It does not tell you which version governs any particular job. Whether a version applies to your work depends on facts about that work, and those facts belong with the person who owns the rule. This post is a set of habits for reading and passing on a text, not a substitute for the owner's decision or for advice from a qualified professional.

Do not choose between them yourself; send the question to the person who owns the rule. That is the safest first step, and the rest of this section explains how to make the question easy to answer.

Start by naming both versions with their labels and the page each came from. Then write down what each one says about the point in question, in plain words and with the exact numbers and dates. Next, say which version you are reading and which one the crew might see, for example on a shared link or a printed copy. Finally, ask the owner which version governs the work, and record the answer with the owner's name and the date.

Until the owner answers, do not present the rule to the crew as settled. Pass on the open question together with the rule, so the crew knows the point is unresolved. This keeps the decision with the person who can make it and gives the crew an accurate picture of what is known.

Send the rule with its version label, the date you checked it and a link to the page, all in the same message. A message in that form lets the crew and the owner see the same source without relying on memory, and it lets anyone check your copy against the page.

For the wider job handoff, use the dispatch handoff checklist. Before sending the message, review the stop words to check before a customer text.

Keep the format short. A short message is easier to check than a long one, and the label stands out when it sits on its own line. If the version is still unresolved, name the owner who needs to confirm it.

Ask which version a message came from, because the crew acts on the words it receives, not on the version you meant to send. An owner who hears a rule second-hand can ask for the label and the date in the first reply. The owner can also ask the dispatcher to confirm the link before anything is written into a job plan.

Owners can keep a simple record of which version was used for each job. The record does not need to be complicated. Keep the record with the job file so it is easy to find when it matters. An owner who keeps this record also has a clear answer if a crew later asks which text it was given. That answer comes from the record, not from memory of the conversation.

Use the label the page gives, and describe the date the page shows or the date you checked it. The Latest Available (revised) label, for example, describes a version that incorporates changes made by subsequent legislation and applied by the editorial team. That is a narrower statement than "the current law," so describe it in the narrower way.

Keep words about scope exact as well. If a rule applies to one kind of work, say so. If a rule comes from one jurisdiction, name the jurisdiction in the same sentence as the rule. A rule from the UK legislation pages and a rule from California's code each hold only in their own jurisdiction, and a message that blends them without naming the source is hard to check.

Today, take one rule already in a job file and compare its copy with the linked page. Record the version label, the check date and any difference that needs the owner's answer before you pass it on.

Is a screenshot enough to confirm the version?

No, a screenshot without a version label leaves the version unconfirmed. Return to the page it came from to check the label.

Does a history date decide which version governs the job?

No, a history date identifies a recorded change; it does not decide which version governs your work. Take unresolved questions to the person who owns the rule.