When a procedure changes, who needs retraining?

A procedure gets revised. Somebody rewrites a section of the safety management system after a near miss, the new version is approved, and it replaces the old one in the document library. The change is handled properly at every step, and it still leaves a problem nobody raised in the meeting: several hundred crew have a training completion on file against the version that no longer exists.

Are they trained or not? The honest answer is that the record cannot say, because it was never designed to.

A completion is a claim about content

Most training records store a person, a course, and a date. That is enough to answer "has this crew member done the fire drill module", which is the question people expect. It is not enough to answer "has this crew member done the current fire drill module", which is the question that actually matters after a revision — and the two only look alike while the material is standing still.

Attaching a version to the completion changes what the record can tell you. It stops being a tick against a course name and becomes a statement that a named person completed a specific revision of specific material on a date. That is a much smaller claim, and a much more useful one, because it can be compared against what the material says today.

"A training record that does not know which version was taught is not a record of training. It is a record that training was mentioned."

Not everyone needs retraining

The reflex after a revision is to reassign the whole course to everyone who ever took it. It is defensible, and it is expensive in the one currency a vessel cannot print, which is crew time. It also erodes the thing it is trying to protect: a workforce that has been made to re-sit unchanged material three times stops treating an assignment as a signal that something changed.

The alternative needs the version history to be legible. If the system knows what changed between revisions, and knows which revision each person completed, then the population needing action is a calculation rather than a guess — and it is usually much smaller than everyone. Some revisions are typographical and touch nobody. Some change one procedure that only affects deck crew on two vessels. Scoping the reassignment to those people is only possible if the record was granular enough to support the question.

This is a different problem from getting the training delivered, which is its own constraint at sea and is covered in delivering training onboard. It is also different from watching a certificate run out, which is the expiry problem. Here nothing has expired and nobody has left; the material moved.

What this looks like when someone checks

The value shows up under scrutiny. An inspector or an internal auditor asking about a revised procedure is not really asking whether training exists — they are asking whether the organisation noticed the change and did something proportionate about it. A system that can show the revision, the date it took effect, who had completed the prior version, who was reassigned, and when they finished is answering the actual question. One that produces a list of course completions with no version against them is answering a different, easier one, and the gap is visible.

That is the same underlying discipline as audit readiness: the work is done continuously in the record, or it is done frantically in the week before somebody arrives. How training sits alongside crew records and scheduling is on the modules page, and if you want to see the retraining path against one of your own revised procedures, that is a good thing to bring to a walkthrough.