Loading...
operations

DND Room Follow-Up Log

Track every Do Not Disturb room that needs follow-up contact, welfare checks, or escalation in one place. This log helps hotel teams document attempts, assign a DRI, and close the loop on duty-of-care issues.

Get Started

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Hotels · Hospitality · Resorts · Extended Stay Properties

Overview

The DND Room Follow-Up Log template is a task checklist for tracking rooms that remain on Do Not Disturb and require contact attempts, welfare checks, or escalation. It gives hotel teams a structured way to record what was done, who owns the next step, and whether the issue is still blocking room access or has been resolved.

Use this template when a guest has left a DND sign in place longer than expected, when housekeeping cannot complete service, or when staff need to document repeated contact attempts before entering a room. It is also useful when the situation may involve guest welfare and the property needs a clear record of timing, escalation, and handoff between housekeeping, front desk, security, and management.

Do not use this log as a substitute for an emergency response form, medical incident report, or security incident record. If the guest is unresponsive, distressed, or there is an immediate safety concern, follow the property’s emergency procedure first and document the escalation here only as part of the operational trail. The template works best when each checklist item is specific, independently verifiable, and tied to a DRI so the next action is never ambiguous.

Standards & compliance context

  • This template supports duty-of-care documentation by showing when staff attempted contact and when escalation occurred.
  • If a welfare concern is suspected, follow local emergency and guest-safety procedures before any routine housekeeping workflow.
  • The log should align with property SOPs, privacy rules, and any hotel brand requirements for room-entry authorization.
  • If your jurisdiction or brand requires incident reporting, use this template alongside the required report rather than instead of it.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

How to use this template

  1. Create one log entry per room and record the room number, date, shift, and DRI before any follow-up action begins.
  2. Add each contact attempt as a separate checklist item with the time, method used, and result so the record stays auditable.
  3. Mark whether the issue is blocking room access, a welfare concern, or a non-blocking guest preference so the team can prioritize correctly.
  4. Assign the next action to a named DRI and note the escalation path if the guest does not respond after the required attempts.
  5. Review the log at shift handoff, close completed rooms with a clear resolution note, and carry unresolved items forward with updated timing.

Best practices

  • Record each knock, call, or key-card check as a separate checklist item so the timeline is easy to verify.
  • Use normal priority for routine privacy follow-up and reserve critical only for safety or compliance concerns.
  • Document the exact outcome of each attempt, such as no answer, guest declined service, or contact made, instead of writing vague notes.
  • Assign one DRI per room so accountability does not drift between housekeeping, front desk, and security.
  • Escalate based on the property SOP and elapsed time, not on guesswork or shift pressure.
  • Keep welfare checks distinct from housekeeping service attempts so staff do not blur operational access with safety response.
  • Close the log only after the room is either serviced, the guest has responded, or the escalation path has been completed.

What this template typically catches

Issues teams running this template most often surface in practice:

Repeated DND status with no documented contact attempts.
Missing DRI after a room is handed from housekeeping to front desk or security.
Vague notes that do not show whether the guest responded or refused service.
Delayed escalation because staff waited until the end of shift to review the room.
Confusion between a privacy preference and a potential welfare issue.
Incomplete handoff when an unresolved room is passed to the next shift.
Overuse of critical priority for routine service delays.

Common use cases

Housekeeping Supervisor Follow-Up
A housekeeping supervisor uses the log to track rooms that stayed on DND past the service window, record each knock or call, and assign the next step before the shift ends.
Duty Manager Welfare Check
A duty manager reviews repeated no-response entries and uses the template to document a welfare check, escalation decision, and any handoff to security or emergency procedures.
Security Escalation Trail
Security staff use the log to confirm when they were contacted, what was observed at the door, and whether the situation required a higher-level response.
Shift Handoff for Unresolved Rooms
The outgoing team leaves a clear record of unresolved DND rooms so the incoming shift can continue follow-up without repeating work or missing timing requirements.

Frequently asked questions

What is a DND Room Follow-Up Log template used for?

It is used to record rooms that remain on Do Not Disturb and need follow-up contact, a welfare check, or escalation. The template keeps each attempt, outcome, and next action in one audit-friendly place. It is especially useful when staff need to show what was done before entering a room or escalating to management.

Who should run this log during a hotel shift?

Housekeeping supervisors, front office leads, security, or the duty manager usually own the log, depending on the property’s SOP. The DRI should be the person who can coordinate contact attempts and authorize escalation. If your hotel separates guest contact from room-entry decisions, assign those tasks clearly in the log.

How often should this log be checked or updated?

Update it every time a contact attempt, knock, call, or welfare check is made, rather than waiting until the end of shift. For active cases, review it at shift handoff and again before any escalation decision. If your property uses a timed escalation path, the recurrence should match that SOP.

Does this template replace a hotel safety or incident report?

No. This log supports operational follow-up, but it does not replace an incident report, security report, or medical response form when those are required. If a guest appears unwell, unresponsive, or at risk, the log should point to the separate emergency workflow and record that escalation happened. Keep the template focused on tracking actions and outcomes.

What are the most common mistakes when using a DND follow-up log?

Common mistakes include vague notes like "tried room" without a time, no DRI, and no clear next step. Another issue is treating every case as critical, which makes it harder to prioritize genuine welfare concerns. The log works best when each checklist item is independently verifiable and the outcome is unambiguous.

Can this template be customized for different hotel brands or property types?

Yes. You can adapt the escalation path, contact methods, and approval chain for boutique hotels, resorts, extended-stay properties, or multi-property groups. Some teams add fields for guest preference notes, language needs, or local security contacts. Keep the core sequence the same so the log stays easy to use across shifts.

How does this compare with handling DND rooms informally by phone or memory?

An ad-hoc approach is easy to miss during busy shifts, especially when multiple rooms need follow-up at once. A structured log creates a single source of truth for blocking issues, non-blocking reminders, and escalation timing. It also makes shift handoff cleaner because the next DRI can see exactly what has already been done.

Can this template connect to other hotel operations workflows?

Yes. It pairs well with housekeeping inspection logs, guest incident reports, security escalation runbooks, and shift handoff checklists. Many teams also link it to task management so unresolved rooms stay visible until the welfare check or contact attempt is closed. That makes it easier to manage priority and avoid duplicate work.

Go deeper on the topic

Related concepts
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
  • A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
Related guides

Ready to use this template?

Get started with MangoApps and use DND Room Follow-Up Log with your team — pricing built for small business.

Get Started