A practical way to find single-person dependencies is to ask what stops, slows down or becomes unsafe when one colleague is unavailable. In a hotel, the answer may sit in a system permission, supplier relationship, night routine or piece of local knowledge. To connect dependency planning with the operating model, review Feathers Hospitality’s management approach, explore the hotel management platform, or contact the team about your property.
Map work, access, knowledge and tested backup so critical hotel routines do not rely on one person.
At a glance
- Clarify the outcome and risk the process must control.
- Name who decides, acts, covers and follows up.
- Test the arrangement and update it using operational evidence.
Start with work that must continue
List guest-facing and back-of-house activities that cannot simply wait: access control, room readiness, urgent maintenance, payment reconciliation, safety checks and key communications. Rank them by consequence and acceptable delay. The priority is continuity of service and safe operation, not replacing every specialist with a second person.
Ask who can actually complete each task
For each activity, record the trained primary person, a capable backup, required system access, approvals and reference material. A name on a rota is not proof of competence. Check whether the backup has practised the task under realistic conditions and can reach necessary information during the relevant shift.
Prioritise dependencies that combine high impact with a long recovery time. A rare monthly close may matter more than a frequent low-impact task if no one else can reconstruct its inputs.
Trace knowledge and access dependencies
Look for passwords, undocumented exceptions, supplier contacts, manual workarounds and recurring decisions held in one person’s memory. Keep credentials in approved access controls; do not put passwords in a continuity document. Separate knowledge transfer from privileged access, which should remain individually controlled.
Document the recovery route beside the work procedure, including who can restore access and how completion is confirmed. Review the material after each real absence or failed handover.
Measure the consequence of absence
Estimate what would happen after an hour, one shift or several days without the primary person. Consider guest impact, safety, financial exposure, regulatory duties and workload transferred to others. Use a simple impact scale with explicit examples, rather than false precision that disguises uncertainty.
Build a proportionate backup
Depending on the risk, options include cross-training, paired shifts, documented steps, a central support contact or an external provider. Define the boundary: a backup may perform routine steps but must escalate exceptions. Check training time and capacity so the plan does not create an unmanageable second job.
Test handover and recovery
Run a tabletop exercise or supervised practice. Give the backup a realistic scenario and observe whether they can find instructions, decide within authority and contact the right person. Afterward, fix gaps in documents, permissions and escalation. A test should reveal design weaknesses, not become a blame exercise.
Ask the primary person to walk a colleague through a normal case and an exception. The questions raised during practice often expose missing context that a polished procedure alone will not reveal.
Keep the plan safe and current
Assign an owner, review date and change trigger such as staff departure, system change or supplier transition. Limit sensitive operational and personal data to authorised readers. If a task involves regulated qualifications or safety controls, confirm the permitted coverage with appropriate professional advice.
Avoid creating shared accounts as a shortcut for backup. Use approved individual access, least privilege and a documented route for urgent provisioning when the usual administrator is absent.
Use dependency findings in planning
Group similar gaps across departments and decide where training or process redesign will reduce exposure most. Track whether backups remain available and whether critical knowledge is recoverable. The map supports decisions about resilience; it is not a guarantee that disruption will never affect service.
Frequently asked questions
Does every task need two fully trained people?
No. Match redundancy to impact and recovery time. Some specialist tasks may need external cover or a safe pause rather than duplicate in-house expertise.
Should the dependency map include personal details?
Only operational information needed for continuity. Keep staff contact and HR data in approved systems with appropriate access controls.