DND Room Follow-Up Log

It is used to record rooms that stay on Do Not Disturb and require follow-up contact, a welfare check, or escalation. The log keeps the timeline clear: when the room was first flagged, who attempted contact, what was observed, and what action was taken. It is especially useful when staff need a single place to document duty-of-care decisions.

Review it during each shift handoff and any time a room remains inaccessible beyond your property’s policy threshold. Many hotels also review it after housekeeping rounds, before end-of-shift closeout, and whenever a guest requests privacy for an extended period. The key is to make the review cadence explicit so follow-up does not depend on memory.

It is usually owned by the front desk or housekeeping supervisor, with security or management added when escalation is needed. The DRI should be the person responsible for ensuring the next follow-up step happens, not just the person who first noticed the room. In smaller properties, one shift lead can own the log and assign tasks as blocking or non-blocking.

No. This log tracks the operational follow-up path, while a welfare-check record or incident report may be required if there is a safety concern, forced entry, or guest complaint. Use this template to capture the checklist items and handoff details, then link or reference the formal report when escalation occurs.

The most common mistake is writing vague notes like "guest not available" without recording the contact attempt, time, and verification step. Another pitfall is skipping escalation criteria, which makes it unclear when to involve management or security. A third issue is treating every case as critical instead of reserving critical priority for safety or compliance concerns.

Yes. You can adjust the recurrence, escalation thresholds, and required verification steps to match your property’s duty-of-care policy. Some hotels add language for VIP rooms, long-stay guests, medical privacy concerns, or local legal requirements. The template should stay specific to the actions staff can verify on each shift.

It works well alongside room-status boards, task assignment tools, and shift handoff notes. You can link the log to the room number, guest profile, incident record, or maintenance ticket so the next DRI has context without searching across systems. The main benefit is that the follow-up steps stay atomic and auditable even if the rest of the workflow lives elsewhere.

Escalate when the room remains unresponsive past policy, when there is a smell, noise, medical concern, or other welfare indicator, or when staff cannot complete a required verification step. Escalation should be blocking when guest safety or property policy is at risk, and non-blocking when it is only a documentation update. The template helps make that distinction visible.