This guide answers a practical hotel management question and connects it to how a property operates. Explore our management approach, see the operating platform and speak with Feathers Hospitality to learn about Feathers Hospitality’s approach.
Use the framework alongside the property’s own agreements, procedures and operating data. Technical, legal, safety, employment and privacy matters should be checked with the qualified professional responsible for that area.
- Define what needs an on-call response and who can authorize it.
- Publish primary and backup coverage with sustainable limits.
- Test contacts, handovers and escalation before peak season.
Set the boundary for on-call support
List the incidents that justify calling the on-call person and those that remain within normal shift responsibilities. A leaking pipe affecting guest rooms, a loss of access control or a service outage may need a different response from a routine request. Define the trigger in practical terms and give staff a simple first action while they wait for support.
A rota should not create a promise that someone can resolve every incident remotely. State what the contact can authorize, what requires a specialist and what emergency services or property procedures take priority. For a coastal property, consider alerts and access disruptions that could affect arrival, staffing or suppliers, while relying on the property’s own risk plan for specific hazards.
Choose primary, backup and escalation coverage
Publish who is primary, who is backup and how they can be reached. Define what happens if a person does not respond within the agreed interval. Check that contact details are current and that the backup has enough authority and context to act. Avoid a rota where only one person knows the plant room, supplier contacts or emergency shutoff process.
Share information on a need-to-know basis and store it in an approved channel. Do not put sensitive guest records in a personal messaging group. The rota should identify the role and property, not expose personal information beyond what staff need to make contact.
Build a rota people can sustain
Estimate the likely call volume, seasonal peaks and recovery time after an incident. Share coverage fairly and ask staff about availability before publishing. Employment terms, rest periods and any applicable collective agreements must be checked by the employer and qualified local advisers; this article is not a schedule of Portuguese labour-law requirements.
Keep coverage reliable during leave, illness and shift handovers. Make a swap process and approval owner explicit. If the rota depends on people remaining informally available outside their agreed working arrangement, redesign it rather than treating goodwill as permanent capacity.
Prepare the person taking the call
Provide a short operating pack: property location, current manager, approved suppliers, escalation contacts, key systems, incident log and authority limits. Store current plans where the on-call person can access them securely. Test whether a colleague unfamiliar with the document can find the essential steps without calling the author.
After a call, record time, issue, decision, owner and follow-up. The next shift needs enough context to continue work. Separate urgent containment from permanent repair and ensure a qualified person checks technical decisions when needed. Close the incident only after the property confirms the service is stable.
Test the rota before the busy period
Run a short exercise before a high-demand season and after changes to staff, suppliers or systems. Test contact order, information access, decision authority and handover. Include a realistic scenario such as a late guest arrival combined with a building fault, but do not simulate actions that could endanger guests or interrupt live systems.
Review missed calls, unnecessary escalations, response time and the burden on the team. If too many routine issues reach the on-call person, improve shift guidance. If incidents cannot be resolved because authority is unclear, update the policy. A rota is useful only when the people using it understand both its reach and its limits.
Frequently asked questions
What should trigger an on-call call?
Only events defined as urgent or time-sensitive in the property’s escalation procedure. Routine issues should remain in the normal workflow.
How many people should be on the rota?
Enough to cover the agreed response and backup needs while keeping workload sustainable. The right number depends on property scale and risk.
Can an on-call person approve any emergency spend?
Only within written authority. Define limits and a route for costs or decisions beyond them.