A useful hotel backup contact plan identifies who can take over a particular decision, what they are authorised to do, which information they can access and where they should escalate an exception. A second phone number is not enough if that person has not agreed to the role or cannot open the working records.
Before the owner becomes unavailable
Separate receiving a request, carrying out work and approving a change.
Confirm the backup person's actual availability and authority.
Test access and handover using an explicitly labelled exercise.
Keep private contact details and system credentials out of public documents.
This article concerns continuity of ordinary business coordination. It does not replace a property's emergency procedures. Safety-related incidents should follow the property's established emergency route rather than wait for the business approval chain described here.
Start with decisions that stall when one person is missing
Review occasions when the team had to wait for the owner: a delivery without a confirmed recipient, a guest-information change that needed verification, or a request for work beyond an approved scope. These situations do not require the same authority.
Create one row for each decision type. “Call the manager for everything” hides a distinction: the manager may be able to receive a request but may not be authorised to change a commercial commitment. The backup needs to know both what can proceed and what must remain on hold.
Include how to communicate an unresolved matter without promising an outcome. Acknowledging a request is useful; describing it as approved when it is not creates another problem for the next person.
Build a decision-specific contact table
| Decision | Primary role | Backup role | Permitted action | Exception route |
|---|---|---|---|---|
| Delivery against an approved order | Purchasing coordinator | Agreed shift supervisor | Check documents and receive through the agreed process | Record discrepancies and refer to the approver |
| Confirmed guest arrival information | Guest-information owner | Communication cover | Use the current verified information | Escalate conflicting facts rather than guess |
| Work outside the agreed scope | Work owner | Backup coordinator | Gather the proposal and its operational impact | Seek the designated approval before committing |
These are suggested roles, not actual Kines staffing assignments. Add the people responsible for your property and confirm their agreement before relying on the table. The complete internal contact directory does not need to be distributed to every guest.
Confirm that the backup can do the work
Ask the backup to find the necessary record using their own account: the approved delivery list, supplier contact or unresolved task. Check that they can see what they need, understand which version is current and know where to record the outcome.
Do not solve access gaps by placing a shared password in a group chat. Use the access method supported by the relevant system and review it when responsibilities change. Until access works, describe the arrangement as not ready instead of treating a name on a spreadsheet as completed preparation.
Availability also needs a real agreement. Someone who can provide cover during one period may be unavailable during another. Record the agreed coverage period and a review date. A person's presence in a contact list should not imply an unlimited obligation to respond at all times.
Worked example: a delivery while the owner is travelling
Consider a hypothetical property with an approved equipment order. The main coordinator cannot be reached. The backup can open the order and check the quantities and models through the receiving procedure. Several items, however, are substitute models without recorded approval.
Authority to receive a delivery does not automatically include authority to accept a substitution. The backup records the difference, tells the supplier that it is being checked and refers it to the named approver. The order is not marked fully received and accepted while that question remains unresolved.
The handover records what has been checked, what is pending and who owns the next decision. This allows part of the work to continue without granting unlimited authority by implication. It is an operational example, not advice on purchase-contract rights or a report of a real property's performance.
Decide what happens when neither contact is available
A plan should offer more than repeated calls to the same two people. Identify the next coordination role, the place to log the issue and the status message that accurately describes the situation. Specify which work must retain its current state until approval is obtained.
Set response arrangements according to the decision and the actual service agreement. There is no single suitable response period for every task. Keep emergency routes separate from ordinary business requests.
Once a decision is made, update the people who received the request earlier. Otherwise, several people may act independently on different versions of the same problem. The final decision should be visible in the working record rather than exist only in a private call.
Test the route without creating a fake guest problem
Run an exercise clearly labelled as a handover test. Participants should know it is a test; messages must not lead guests or suppliers to believe a real incident has occurred. Check whether the team reaches the correct role, opens the correct information, recognises its authority limits and records the next action.
Fix specific failures such as an outdated number, expired permission or duplicate document. A successful exercise shows that the tested route worked under those conditions. It does not prove readiness for every situation. Review affected entries when staff, suppliers or systems change.
Questions owners often ask
Must the owner be the last backup for everything?
That depends on the decision and agreed authority. Some matters can be delegated to another role. Simply adding the owner's name to every final column preserves the same dependency rather than resolving it.
Can a supplier be a backup contact?
A supplier may provide operational support, but that is different from approving a decision on the property's behalf. Verify the actual service scope and availability. A saved number is not an agreement to provide after-hours support.
Is this still needed with a management company?
Check who receives requests, who approves exceptions and which decisions remain with the owner. Use the overview of what a hotel management company does to frame the conversation, then agree the property-specific handovers.
Next step: Message LINE OA @kines about the types of decisions that currently wait for you. Ask about a suitable coordination scope without sending guest personal details or passwords in the initial message.
Prepared by: Kines editorial team. Basis: Kines' role, contact and issue-record framework. The table and hypothetical example are editorial planning tools, not a confirmed service agreement or certified emergency plan.


