Key points
- Record the observation without inferring an intention.
- Separate declined, postponed and inaccessible service.
- Give each open exception an owner and a next action.
Use statuses that describe what happened
DND means a non-disturbance signal was observed at the time of the visit. “Declined” records the guest’s explicit decision about a particular service. “Postponed” means another time has been requested or accepted. “Not completed” describes an outcome but does not explain its cause. Keeping these distinctions prevents a single label from obscuring several different decisions.
Maintaining a DND list appears in a public Marriott job description. The log below is a proposed method for adaptation to the property; it does not describe that brand’s room-entry policy. The supervisor agrees the labels with the front desk so that the same event has the same meaning across shifts and departments.
Follow a short decision table
| Observed situation | Proposed action | Record |
|---|---|---|
| DND at the visit | Do not begin service; follow the local contact or recheck rule | Observed DND and assigned follow-up |
| Explicit decline | Confirm the scope declined under the property process | Relevant service declined |
| Different time requested | Check feasibility and confirm the window | Accepted postponement or alternative needed |
| Conflicting information | Refer to the supervisor or front desk | Awaiting clarification |
| Concerning situation | Alert the designated manager under the local protocol | Handled through the appropriate response process |
A safety concern moves outside ordinary housekeeping exception tracking. The attendant reports observed facts rather than improvising an entry or technical investigation. The local procedure identifies escalation routes, authorized people and the actions appropriate to the circumstances. The decision table is a coordination aid, not an emergency-response protocol.
Keep the log focused on operational facts
Record room, date, observation time, planned service, observed condition, authorized action and follow-up owner. Add an operational deadline when one has been agreed. Avoid assumptions about the reason for declining service or personal comments about the guest. Useful evidence comes from a consistent chain of observation, decision and result rather than a detailed personal narrative.
The front desk checks requests already received before making another contact. This helps prevent several colleagues from approaching the same room independently. It adds a specific exception record to broader front desk and housekeeping communication, rather than creating another general discussion about messaging channels.
Example: an observation followed by an agreed visit
Fictional example: at 10 a.m., a room attendant observes DND on a stayover room. The front desk already holds a request for service at 2 p.m. The supervisor checks available capacity and confirms that window. The original observation remains in the record, while the next action becomes “service at 2 p.m.” with an assigned owner and no unnecessary intermediate attempts.
At 2 p.m., the guest requests towels only. The attendant records the delivery and the service not performed; the supervisor applies the closure rule for that request. The history shows what happened without turning the original DND observation into an all-day decline. These times are fictional and establish no mandatory waiting period or right to enter.
Reflect exceptions in the remaining workload
The supervisor tracks completed services, closed declines and accepted postponements separately. A declined room is not a cleaned room; an accepted postponement remains potential work until its outcome is known. Use the categories to reassign resources and explain changes without ranking attendants by situations outside their control. A daily completion figure should retain those distinctions.
At shift end, open exceptions go to a named colleague with the latest confirmed fact. Close the record after completed service, a confirmed decline or a documented decision by the appropriate manager. The absence of further information is not a closure event. Review the procedure if the same conflicts repeatedly arise between guest requests and room assignment sheets.
Frequently asked questions
Should every DND room automatically be contacted again?
The property should define that rule according to its policy and the circumstances. Before any authorized contact, check existing requests so several colleagues do not repeatedly approach the same room.
Does declining cleaning also mean declining deliveries?
Not necessarily. Clarify which service was declined and any supplies the guest still wants. A towel delivery and a complete room clean should not be hidden behind one ambiguous outcome.
