Covering a Role Nobody Else Understands

The preparation did not happen, or did not cover this. You are now running a role you do not understand, with whatever is on the person's desk.

For a resilience routine built around “Covering a Role Nobody Else Understands”, improvement depends on seeing whether backup work happens outside an emergency. Teams can use task time tracking to organise practice time and compare planned coverage with actual participation, but the record should prompt a handover conversation rather than become an automatic judgement about an employee.

For an independent benchmark, compare the local approach with O*NET occupational information; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

Start from obligations, not tasks

What has been promised to whom, by when?

Look at the calendar, the inbox, and any project tracker — in that order.

You are not trying to do their job. You are trying to meet commitments and prevent damage, which is a much smaller set.

Finding out what exists

Their calendar shows recurring commitments and external meetings.

Their sent mail shows who they deal with and what was recently promised.

Their filing shows the shape of the work.

Accessing a colleague's mail needs care: have a stated reason, do it with somebody else present, and record what you looked at. Employment and data protection rules apply and differ by jurisdiction.

Asking outward

Clients and suppliers know what they are waiting for.

A short message — "I am covering for a period, could you tell me what is outstanding between us" — produces an accurate list quickly and reads as competent rather than alarming.

People are generally helpful about this and it is the fastest route to the real picture.

Asking inward

Colleagues know fragments: who did what, what was mentioned in passing.

Ask everybody the same question — what did you know about their work — and assemble the fragments.

Somebody usually knows more than they realise.

What to do with the backlog

Triage as in the unplanned absence note: must happen, can slip, can stop.

Communicate the slippage rather than letting it be discovered.

Clients handle a clear "this will be two weeks later than planned" much better than silence followed by lateness.

Bringing somebody in

For a specialised role, a contractor who knows the domain can produce more in a week than an untrained colleague in a month.

Worth considering early, and most small organisations consider it late.

And a domain expert will also tell you what the role actually involves, which is information you need for the permanent answer.

Recording as you go

Everything you have to find out, write down.

This is the documentation that never existed, being produced under the only conditions that reliably generate it.

Do not lose it when the crisis ends, which is exactly what usually happens.

What to check

Would you be able to see a colleague's calendar and inbox, and under what rule?

Do you know who their external contacts are?

Is there any project tracker, or is everything in their head and their mail?

And is anybody writing down what is being discovered?

The point

Ask outward.

Clients and suppliers know what they are waiting for, and a short message produces an accurate list faster than any internal reconstruction.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.