DND Room Follow-Up Log

It is used to record rooms where a Do Not Disturb sign or repeated non-response requires follow-up contact, a welfare check, or escalation. The template keeps each checklist item atomic so staff can verify what was done, when it was done, and who owns the next step. It also creates a clear audit trail for guest safety and hotel policy compliance.

Housekeeping, front desk, security, or a supervisor can run it depending on the property’s policy and the situation. The DRI should be the person authorized to make contact decisions and escalate if the room remains unresponsive. For larger properties, the log often works best when one role owns the task and others add notes or verification steps.

Use the recurrence and timing rules from your hotel policy rather than a fixed universal cadence. Some properties require same-shift follow-up after a missed service attempt, while others escalate after a second attempt or a set number of hours. The key is to define the recurrence_config clearly so staff know when the next contact attempt is due.

Include only independently verifiable actions such as verify the DND status, attempt guest contact, document the response, notify the supervisor, and complete a welfare check if required. Avoid compound items that mix multiple actions into one line, because that makes it hard to confirm what actually happened. Each checklist item should support a yes, no, or N/A answer.

Yes, it supports documented follow-up for guest safety and internal escalation procedures. It is not a legal policy by itself, but it helps teams show that they followed a consistent runbook and recorded each verification step. If your property has specific local rules or brand standards, customize the escalation path and approval steps to match them.

The most common mistake is treating the log like a freeform note instead of a checklist with clear ownership and closure criteria. Another issue is inflating every item to critical priority, which makes it harder to separate routine follow-up from true safety escalation. Teams also sometimes skip the verification step, leaving the room marked as handled without confirming the outcome.

Yes, it should be customized to match your property’s guest-contact rules, escalation thresholds, and staffing model. You can adjust the checklist items, priority levels, and recurrence to fit limited-service hotels, resorts, extended-stay properties, or multi-property operations. Keep the task type simple or checklist based on how much detail your team needs at handoff.

Ad hoc notes are easy to miss, hard to assign, and difficult to audit later. A structured log makes the next action obvious, reduces ambiguity about blocking versus non-blocking issues, and helps the team close the loop before the end of shift. It is especially useful when multiple departments may touch the same room.