Telling a Real Requirement From a Retold One
A four-hour method for separating rota rules that genuinely bind from rules that have been retold until they sound like requirements.
Six rules quoted as requirements at one site, checked against their documents
One of the six was what everybody believed it was. Four hours of document-reading reclassified five of them, and two of those had been costing cover every week. This is one employer's own check, not a statement of what any rule requires.
Most rota rules described as requirements are retellings. The retelling is honest, the rule is usually sensible, and the distance between the document and the practice is where a rota loses most of its flexibility.
The constraint in “Telling a Real Requirement From a Retold One” becomes useful only when its source, cost and effect on coverage are visible. A team considering see the available controls directly for team productivity metrics can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
Checking is not an audit and does not need a project. It is four hours with a list of rules and whatever documents exist, and it reliably moves about half the list.
The assumptions behind “Telling a Real Requirement From a Retold One” can also be checked against Joint Commission safety resources. Record what applies locally and what requires qualified advice.
What retelling does to a rule
It broadens it. A requirement attached to a process becomes attached to a room; a requirement attached to a room becomes attached to a shift; a requirement for a trained person to be available becomes a requirement for one to be present.
Each step is a small, reasonable act of caution. Four of them turn a narrow requirement into a constraint that determines the whole pattern.
The method
- List every rule currently treated as a requirement, in one sentence each.
- For each, write the document it comes from. Leave it blank if nobody can say.
- Read the clause, not the summary, for each one that has a document.
- Write what the clause actually covers: which activity, which place, which people, which hours.
- Mark the gap between the clause and the practice.
Step five is the output. Everything before it is clerical, and most of it can be done by somebody who does not build rotas.
What the blanks mean
A rule with no document is not thereby wrong. It is unsourced, which puts it in a different queue: somebody has to decide whether to keep it, rather than somebody having to comply with it.
In most organisations the blanks are about a third of the list, and two or three of them are expensive.
The documents worth reading first
Contracts and variation letters for the people on the rota. Risk assessments and method statements. Insurer and customer requirements. Any internal policy with "staffing", "cover" or "supervision" in the title. Scheduling system configuration.
The last one is a document in every sense that matters: it enforces rules, and somebody typed them in.
The phrase that does the most damage
"Health and safety" used as a reason without a document behind it. It is usually offered in good faith and it terminates the conversation, which is why it survives.
The response is not scepticism about safety; it is a specific question. Which assessment, which hazard, which control. Where the answer exists the constraint is now precise and usually narrower. Where it does not, something else is going on and it is worth knowing what.
What to do with a gap
Nothing automatic. A gap between document and practice is information, not an instruction to revert to the document. Practice is sometimes stricter for good reasons that were never written down.
The decision belongs to whoever owns the risk, taken knowingly, with the document in front of them. That is a different thing from a rota built on a rule nobody has read.
Who should do the reading
Not the person who most wants the constraint relaxed. The exercise produces results that will be argued with, and its credibility depends on the reader having no stake in the outcome.
The most useful pairing is somebody from the area and somebody from outside it, reading together, with an agreement that they record the clause rather than their interpretation of it.
What usually changes afterwards
Two or three constraints narrow, one disappears, and the rest are confirmed with a document reference next to them.
The confirmed ones are not a wasted afternoon. A constraint that has survived a check can be quoted with its source for the next three years, and nobody has to rediscover it the next time the rota is short.
The second pass, a year later
Rules drift back. A narrowed constraint gets retold within a couple of years, because the retelling is safer for whoever is repeating it and nobody is penalised for being too careful.
Running the same four hours annually, against the same list, is enough to hold the line. The second pass takes half as long as the first, because the documents have already been found and the only question is whether anything has changed.
The habit worth keeping
Whenever somebody says a rule is a requirement, ask which document, once, without edge. Over a year that single habit does most of what the formal exercise does.
It also changes what gets said. People stop describing preferences as requirements when the next question is predictable, and the rota conversation gets considerably more honest.