Rules Whose Author Has Left
What happens to a rota rule when the person who made it goes, why the rule hardens rather than fading, and the handover question that prevents the whole category.
A rule made by a manager who then leaves does not fade. It hardens, because the one person who could have explained or relaxed it is gone, and everybody else inherits it as a fact about the world.
The constraint in “Rules Whose Author Has Left” becomes useful only when its source, cost and effect on coverage are visible. A team considering review the current attendance guidance for employee monitoring for performance reviews can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
That is the mechanism behind most of the constraints in this section. Not neglect, not bureaucracy — turnover, applied to undocumented decisions.
For an outside reference relevant to “Rules Whose Author Has Left”, consult NIOSH work-hours training. Compare the general material with the organisation’s jurisdiction, sector and written agreements.
Why it hardens rather than lapsing
Because a rule with no author cannot be questioned by anybody in particular. There is nobody to ask, so the safe course is to continue, and continuing is also the path of least effort.
Over two or three handovers the rule acquires the status of policy, and by then somebody new will defend it on the assumption that it was properly decided.
What the successor actually inherits
A pattern and a set of practices, with no distinction between the parts that are required and the parts that are preference. Almost no management handover separates the two.
The successor then spends a year discovering which is which, usually by breaching something, and the rules that are never breached are never examined at all.
The handover question
One question, asked of every departing manager who owns a rota: which rules in this pattern did you decide, as opposed to inherit or have imposed on you?
Which rules in this pattern did you decide, as opposed to inherit or have imposed on you?
Most will answer accurately in ten minutes. That ten minutes converts an entire category of future constraint into a dated list with a name on it, and it is almost never asked.
The second handover question
Which of them would you do differently now? Departing managers are unusually candid, and the answers frequently identify the one or two rules that everybody has been quietly working around.
Nothing has to be done with the answer immediately. It belongs on the register, marked as such, for whoever next has reason to look.
Reconstructing it afterwards
Where the departure has already happened, the sources are the longest-serving team members, the correspondence from the period, and any pattern change that was formally consulted on.
That is slower and it works. Two hours of asking usually attributes most of the unexplained rules well enough to decide whether to keep them.
The successor's own position
A new manager who changes an inherited rule in their first month will be read as changing things for the sake of it, and a new manager who never changes anything inherits the whole set permanently.
The way through is the register: write down what you have inherited, mark which are sourced, and say that the unsourced ones will be reviewed over the year. That is a position anybody can defend and it does not depend on knowing the answers yet.
Rules attached to a person who is still here
The easier version, and it is worth doing first. Where the author is present, a single conversation settles the rule, and the conversation is usually welcome: people rarely enjoy having an old decision quoted at them as a law.
Do these before the person leaves, which is the only window that exists and which nobody treats as urgent.
What this does to the next departure
An organisation that holds a constraint register with authors on it loses far less when somebody goes. The pattern is documented, the decisions are attributed, and the successor inherits a list rather than a folklore.
That is the main reason to keep the author column, and the benefit only appears at the moment nobody plans for.
The folder nobody opens
Departing managers often leave a folder, and it usually contains the pattern, some correspondence and a spreadsheet nobody can interpret.
It is worth an hour on the first week of a new post. Not to adopt anything, but to find the two or three documents that explain why the pattern looks the way it does, which are frequently in there and which nobody has opened since.
What to do in the first month
Nothing structural, and one thing clerical: write down every rule you are following and mark the ones you cannot source.
That list is worth more at month one than at month twelve, because a new arrival can still see which rules are strange. After a year the same person will have stopped noticing them, which is how the next set gets inherited.
The fields that sort the register
For each rule: the author if known, whether they are still in the organisation, the date of the last confirmation, and whether it has been reviewed since the author left.
The last field sorts the register into exactly the right order for anybody arriving new into the role, which is the moment this document earns its existence.