An exception should be documented when it changes a decision, creates risk or keeps returning. Explore Feathers Hospitality’s management approach and operational platform, or speak with the team about a process that relies on memory.
Recording an exception is useful when it helps a colleague understand what happened, what temporary action was taken and who must review it. A one-off note is different from a permanent rule. Look for recurrence, consequence and the reason the normal process could not be followed before changing a checklist or procedure.
- Capture context, impact, decision owner, workaround and review point.
- Separate a genuine one-off from a repeated pattern or a control gap.
- Change the underlying procedure only after checking the cause and the people who use it.
Which exceptions deserve a record?
Record a deviation when the normal process could not be followed, when a decision required authority outside the usual role, or when the outcome affects a guest, asset, safety control or financial commitment. A delayed supplier delivery may be routine if it has no impact; the same delay may be material if it leaves a room unavailable or compromises a promised service. The record should help another person understand the situation without reconstructing it from several conversations. The useful question is whether someone will need this context to complete work, explain a decision or prevent recurrence. A short record in the approved operating system is generally more useful than a personal message that disappears when a shift ends.
What belongs in a practical exception record?
Write the date and time, location or process, expected step, actual condition, immediate impact and temporary response. Identify who made or approved the decision, which follow-up remains and when it should be reviewed. Use plain descriptions rather than labels such as “careless” or “always late”; separate what was observed from what is assumed. Keep guest and staff data to the minimum required for the operational purpose. Include the normal reference or procedure so the reader can see what differed. If the exception involved a supplier, equipment or booking condition, add a reference number rather than copying unnecessary personal or commercial information. The HSE shift-handover guidance supports structured, two-way transfer and checking; apply it as general human-factors guidance, not as a hotel-specific legal standard.
When is recurrence evidence of a process problem?
Look for the same task, trigger, role or workaround appearing more than once. A repeated exception may mean that the written step is unclear, a threshold is unrealistic, the system does not show the right information, or the assigned role lacks time or authority. The pattern matters more than an arbitrary count. Two similar failures with serious consequences may justify immediate review; several low-impact variations may simply reflect normal operating judgement. Compare records across shifts and departments, then ask the people doing the work what makes the standard process difficult. Avoid interpreting a high exception count as poor performance before checking whether the process itself is workable.
How should the hotel respond to a pattern?
First decide whether the temporary workaround is safe and authorized. Then test likely causes with the relevant team: unclear ownership, missing supplies, a dependency that arrives late, conflicting instructions or a system field that is difficult to use. Choose a targeted response, such as changing the trigger, clarifying the hand-off, adding a supplier contingency or providing training. Name an owner and a review date. The HSE guidance on procedures emphasizes that instructions should fit the work and its context. That is a useful design principle, but it does not determine Portuguese compliance requirements or the right staffing model for a particular property. Confirm operational and statutory requirements with the appropriate local advisers.
How can a change avoid becoming another checkbox?
Test the revised step during a representative shift. Ask a colleague who did not design it to follow the instruction and explain how they would handle the same exception. Check that the action is possible with the tools, access and authority available at that time. If the change needs a new record, remove duplicate reporting elsewhere or explain which record is authoritative. After rollout, review whether the same exception continues and whether the new step creates delays or workarounds of its own. If the exception was genuinely unusual and the process worked, close the note rather than embedding an unnecessary permanent rule.
Frequently asked questions
Should every exception trigger a procedure update?
No. Update a procedure when the evidence shows the standard is unclear, unsafe or poorly matched to the work. A legitimate one-off can be documented and closed without becoming a new step.
Who should review a recurring exception?
The process owner and the people affected by the work should review it together. Bring in safety, technical, financial or privacy expertise when the issue crosses those responsibilities.