An Administrator Without a Successor Is a Liability

The indispensable administrator is often praised as loyal and efficient. The institution has mistaken personal capability for resilience.

They know the domains, keys, provider contacts, fragile systems and undocumented exceptions. If they leave, become hostile or fall ill, ownership does not create operational control.

Inventory authority, not tasks

Identify what only this person can approve, recover, explain or change. Include provider relationships and personal devices, not only administrator roles.

Value object — The Administrator Succession Pack

- Critical environments and access route.

- Named secondary administrator.

- Keys and recovery held institutionally.

- Undocumented dependencies.

- Provider recognition and escalation.

- Latest independent exercise.

Prove the successor can act

Have the secondary perform a controlled recovery and change without the primary’s account. Document gaps and rotate secrets exposed during handover.

Respect expertise by making it transferable. The administrator should be valuable for judgment, not irreplaceable through withheld control.

Where this breaks

Documentation projects often record configuration while leaving judgment with the primary administrator. The successor can follow instructions until something differs, then the institution is dependent again.

The operating move

Transfer decisions as well as passwords. Record why fragile exceptions exist, which changes are unsafe and how providers recognise institutional authority.

Shadow a real change.

Perform an independent restore.

Rotate personal credentials.

Interview the secondary without the primary present.

The test

Give the successor an unfamiliar but bounded failure. If they can diagnose, decide and recover, succession has transferred capability rather than files.