Cross-Cover That Exists Only on Paper
Why documented cross-cover arrangements fail at the moment they are needed, how to tell a real one from a nominal one, and the single test that distinguishes them.
Cross-cover arrangements are written down far more often than they are used. Two teams agree to cover each other, the arrangement goes in a document, and the first time it is needed it turns out that nobody on either side has done the other's work for three years.
The constraint in “Cross-Cover That Exists Only on Paper” becomes useful only when its source, cost and effect on coverage are visible. A team considering using managing freelance project time in workforce forecasts for managing freelance project time can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
The arrangement was real when it was written. It decayed quietly, because nothing exercises it and nothing reports on it.
As a separate benchmark for “Cross-Cover That Exists Only on Paper”, see Lean Enterprise Institute guidance. Keep the source rule, operational interpretation and scheduling decision distinct.
Why it decays
Cross-cover depends on familiarity, and familiarity depends on use. A capability that is never used degrades in months: systems change, passwords lapse, processes move, and the person who was trained has moved on.
Nothing in the arrangement notices any of that. The document still says the two teams cover each other, and the rota is built on the strength of it.
The test that distinguishes real from nominal
When was it last used, by whom, and did it work? Three questions, one answer each.
- When was this arrangement last used in anger?
- Who exactly did the covering, by name?
- Did it work, and what had to be chased to make it work?
An arrangement used in the last quarter is real. One used eighteen months ago is probably nominal. One that has never been used is a piece of paper, and the rota should be built as though it does not exist — because it does not.
What a real arrangement requires
Three things: named people rather than named teams, a cadence of actual use, and access that is kept live. A capability somebody cannot log in to perform is not a capability.
The first is the one most often missing. "Team B covers Team A" names nobody, which means the obligation falls on whoever happens to answer, which means nobody has prepared.
The cadence that keeps it alive
A shift or two a quarter, planned, with the covering person actually doing the work rather than shadowing. Planned use is cheap: it happens on a normal day, with support available, when nothing is on fire.
Unplanned use is what the arrangement exists for, and it only works if the planned use has happened. Organisations that skip the planned version get one chance at the unplanned one.
Access, which fails first
Logins, keys, codes, badge permissions and system roles all expire or get removed during tidy-ups, and none of that reaches the cross-cover document.
An access check once a quarter — can these named people actually get into what they would need — takes ten minutes and finds something roughly every other time.
Reciprocity, which is usually asymmetric
Most cross-cover arrangements are used far more in one direction than the other, and the imbalance builds resentment that surfaces exactly when the arrangement is needed.
Counting the uses by direction, once a year, makes the asymmetry visible and allows it to be acknowledged or corrected. An unacknowledged imbalance is the most common reason a cross-cover arrangement quietly stops being honoured.
What to tell the rota
Only the real arrangements. A constraint register that lists nominal cover alongside genuine cover is worse than one that omits both, because it produces plans with phantom capacity in them.
The entry should carry the date of last actual use, and anything older than a stated period should be marked as unverified rather than available.
The arrangement between sites
Cross-cover between sites adds travel, which is usually the thing that makes it impractical when it is actually needed. The document says one hour of work; the day costs three hours.
Where travel is part of it, write the travel time into the arrangement. Half of the cross-cover that looks available on paper turns out to be unavailable at short notice for this reason alone.
The version that works without a document
Some of the most effective cross-cover is informal: two managers who know each other, two teams who have worked together, a habit of answering the phone.
That is worth protecting and worth writing down lightly — the names, not a procedure. Informal arrangements survive on relationships, and the relationships move. A line in the register naming who currently has the habit costs nothing and keeps the arrangement alive through one departure, which is usually what kills it.
The short list to plan with
A short list of named people, each with a capability and a date of last use, reviewed quarterly, with access checked at the same time.
That list is usually much shorter than the document it replaces, and it is the only version anybody should plan with. A rota built on the short list is harder to build and does not fail at seven in the morning.