content

Accessible Guest Stay Preparation

A guest-specific procedure for coordinating requested accessible stays across reservations, front desk, housekeeping and guest services. Confirm exact room features, share only service-relevant details, and close open questions before arrival.

Request pricing See it in MangoApps

Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Hotels and resorts · Hospitality · Serviced apartments

9:41

Sites

Overview

Accessible Guest Stay Preparation is a procedure page for coordinating a guest's requested stay features across reservations, front desk, housekeeping or room-details staff, and guest services. Its Harborlight Hotel scenario is explicitly fictional and demonstrates how the same request can move from an open question to a verified, limited handoff. The page separates requests where a guest names a feature from those where they describe an outcome, so staff can ask useful questions without assuming that a room-type label or similar feature is equivalent.

Use the sequence when a guest raises an accessibility need: ask what would help, have the responsible team verify the exact feature for the relevant dates, record only the service details needed, hand off confirmed information to the teams that need it, and recheck unresolved items the day before arrival. The worked example clarifies team roles, while the FAQ covers unclear preferences, unconfirmed features, privacy concerns and policy or safety questions. A final checklist identifies the confirmed request, verification source, open-question owner, guest-update plan and limits on note content.

This is a coordination aid, not a room inventory, reservation workflow, legal assessment or substitute for a property's approved local procedures. Do not use it to promise availability, decide which alternative suits a guest, or improvise answers to safety or policy questions. Before adoption, replace the fictional examples with verified local details and identify the property's approved recording method, trained escalation role and correction owner. Hospitality Operations owns the sample page; review it when a local procedure or room feature changes.

Standards & compliance context

Use this page alongside the property's approved local procedures; it is not a legal assessment and does not determine whether a room or service meets applicable accessibility requirements.
For regulated, privacy-sensitive or safety-critical questions, follow the approved local procedure and involve the trained role it names rather than improvising an answer.
Limit guest notes to information needed to deliver the service and use the property's approved recording and sharing method.
Keep the intranet page accessible with clear headings, readable table content on mobile, and WCAG 2.1 AA-aware authoring; accessibility of the page does not certify the property's rooms or services.

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

What's inside this template

Prepare a requested accessible stay without assuming or over-promising

Sets the scope, audience, fictional example and page owner before teams coordinate a guest-specific request.

For reservations, front desk, housekeeping and guest services teams When a guest mentions an accessibility need, ask what would make the stay work for them, check the specific feature with the team that knows the room or space, and pass on only what is confirmed. This page uses a fictional property, Harborlight Hotel , to show how that coordination looks across departments. Scope: this page covers guest-specific stay preparation. It is separate from workplace accommodations for employees. Harborlight's examples are illustrative. For regulated, privacy-sensitive or safety-critical questions, follow your property's approved local procedure and involve the trained role it names. Questions about this page: Hospitality Operations owns it. Raise corrections with that team, and review the page whenever a local procedure or a room's features change.

Two common requests, two different follow-ups

Shows why a named feature and a described outcome call for different questions and verification.

Swipe sideways on a phone to read each row in full. Example from the guest "Does the room have a roll-in shower?" "I find it hard to step into a bathtub." What to ask "Is that feature needed for the whole stay, or just for one part of it?" "What would make the bathroom work best for you?" What to verify That the specific room type has that exact feature, with the team that holds room details Which available rooms or arrangements could meet the outcome the guest described What not to assume That a similar-sounding feature or a nearby room type is the same thing That you know which feature the guest wants, or that one solution suits everyone What the guest hears next What was confirmed, what is still being checked, and when you will update them The options that were confirmed, plus a follow-up on anything still open

The coordination sequence

Gives each participating team the ordered actions from the first conversation through the pre-arrival recheck.

Follow it in order, whichever team takes the first call or message. Ask what would help Use open wording such as "What would make your stay easier?" Let the guest describe it in their own terms. Do not ask for more detail than the service needs, and do not ask for medical information. Confirm the exact feature and its availability Ask the team responsible for the room or space to verify the specific feature for the dates requested. Do not rely on a room-type name or a past stay. Record only the relevant agreed details Use your property's approved local method. Write the confirmed request in practical terms, for example "bathroom with a shower seat confirmed for Room 412", not the reason behind it. Hand off the confirmed information Send the detail to each department that needs it to deliver the service. Name the person or role who owns any open question. Recheck unresolved items before arrival Review open questions the day before arrival. If something is still unconfirmed, contact the guest before they travel rather than at the desk.

Who does what: a worked example at Harborlight Hotel

Maps the fictional request across reservations, the room-details team, front desk and guest services.

A guest asks whether a room has a particular bathroom feature. Here is how each team contributes. Reservations: clarify the request The guest asks about a bathroom feature for a three-night stay. Reservations asks what the feature needs to do for them, notes the dates, and asks the responsible team to verify. Reservations does not promise a specific room yet. Housekeeping or the room-details owner: verify the room The responsible team checks the specific room for the requested feature and replies with what is and is not present. Anything unclear is reported as unconfirmed, not guessed. Front desk: receive only the confirmed detail The arrival note reads: "Room 412 confirmed with the requested bathroom feature. Guest asked for a ground-floor drop-off; bell team notified." It carries no reason or background. Guest services: close the loop Guest services contacts the guest once the room is confirmed and checks whether anything else would help on arrival. If anything is still open, they name who is checking and when the guest will hear back.

When it is not straightforward

Explains how to handle uncertainty, unclear preferences, privacy questions and policy or safety concerns.

Pause any assurance you cannot support, and use the trained role or approved local procedure. What if the feature cannot be confirmed? Tell the guest plainly what you could and could not confirm. Do not say "it should be fine". Ask the responsible team whether another room or arrangement would meet the same outcome, and share the options only once verified. What if the guest's preference is unclear? Ask again in different words, such as "What would a good arrival look like for you?" Offer the verified options you do have and let the guest choose. Do not pick for them. What if a request raises a privacy question? Share the detail only with teams that need it to deliver the service. If you are unsure who should see it, stop and ask the role your approved local procedure names. What if a request raises a policy or safety question? Do not improvise an answer or an exception. Pause, tell the guest you are checking, and take it to the trained role or approved local procedure. Give the guest a time for your update. Can I record the reason for the request? Record only what teams need to carry out the service, using your property's approved method. The reason behind a request is generally not needed for service delivery.

Handoff checklist before arrival

Summarizes the confirmed detail, verification source, open-item owner, guest update and data-minimization check needed for a useful handoff.

A handoff is ready when every item below can be answered in a sentence. Confirmed request: the specific feature or arrangement, the room or space, and the stay dates. Verification source: the team or role that confirmed it, and when. Open question and owner: anything still unconfirmed, and the named role checking it. Next guest update: who will contact the guest, by when, and about what. Limited content: the note holds only what is needed for service, with no reasons, diagnoses or unrelated personal detail. Example note: "Room 412, 14-17 May: bathroom feature confirmed by Housekeeping on 9 May. Ground-floor drop-off requested; bell team notified. Open: reserved parking near the entrance, owner Guest Services, update to guest by 12 May."

How to use this template

Replace the Harborlight examples with verified property details, the local room-feature owner, the approved information-sharing method and the property's escalation route.
Assign the role that will coordinate each request and track the owner and due time for every unresolved feature or guest update.
Ask the guest an open question about what would make the stay work, then have the responsible team verify the exact feature for the requested dates.
Record and share only confirmed, service-relevant details through the approved local method, clearly marking anything still unconfirmed.
Review open items the day before arrival, contact the guest with verified information or a clear update plan, and revise the page when local procedures or room features change.

Best practices

Ask what would make the stay easier and let the guest describe the outcome in their own terms instead of inferring a need from a diagnosis or label.
Verify the exact room or space feature for the requested dates with the team responsible for those details rather than relying on a room-type name or past stay.
Mark an item as unconfirmed whenever the responsible team cannot verify it, and avoid assurances such as “it should be fine.”
Record the practical service request and its verification source, not a medical reason or unrelated personal detail.
Send confirmed information only to teams that need it to deliver the service, using the property's approved local method.
Give every open question an owner and a guest-update deadline, then recheck unresolved items the day before arrival.
When a preference is unclear, ask a neutral follow-up and present only verified options for the guest to choose from.

What this template typically catches

Issues teams running this template most often surface in practice:

Staff treat a room-type name as proof that the exact requested feature is present.

A feature is assumed available because it was present during a previous stay, without checking the requested dates.

The guest's request is paraphrased as a medical reason instead of a practical service detail.

An unresolved item reaches the front desk without an owner or a promised time for the next guest update.

A similar-sounding room feature is offered as equivalent before the responsible team verifies it.

Teams pass a request to people who do not need it, or use an unapproved channel to record or share details.

A long local rewrite buries the ordered coordination steps or leaves the escalation route unclear.

Common use cases

Reservations clarifies a bathroom request

A guest asks whether a room has a particular bathroom feature for a three-night stay. Reservations asks what the feature needs to do for them, captures the dates and requests verification without promising a room.

Housekeeping verifies a room feature

The team responsible for room details checks the specific room or room option and reports what is present. Anything that cannot be checked is handed back as unconfirmed rather than inferred.

Front desk receives a limited arrival handoff

The arrival note contains the confirmed feature and any relevant agreed arrangement, but not the reason for the request. The front desk can see which items are settled and which role still owns an open question.

Guest services closes the loop before travel

Guest services contacts the guest once the feature is confirmed, checks whether anything else would help on arrival, and gives a clear update time for any remaining question.

Frequently asked questions

Who should use this accessible guest stay procedure?

It is written for reservations, front desk, housekeeping or the team responsible for room details, and guest services. The Harborlight Hotel examples show how each role can contribute to one guest request. Assign a clear owner for unresolved questions and the next guest update. The page covers guest stays, not workplace accommodations.

When should teams follow the coordination sequence?

Use it whenever a guest asks about a feature or describes an outcome that may affect their stay. Start when the request arrives, verify the exact feature for the requested dates, and hand off the confirmed service detail. Recheck unresolved items the day before arrival. If a local procedure sets a different timing or escalation path, follow that procedure.

What should staff do if the requested feature is unavailable or unconfirmed?

Tell the guest plainly what has and has not been confirmed; do not say it should be fine. Ask the responsible team whether a different room or arrangement could meet the guest's stated outcome. Share alternatives only after they are verified, and let the guest choose. Name who owns any open question and when the guest will hear back.

Does this template establish legal or accessibility compliance?

No. It is an operational coordination example, not a legal assessment or a substitute for local accessibility requirements. Its sample property and process are fictional, and it directs staff to the property's approved procedure for regulated, privacy-sensitive or safety-critical questions. Have the appropriate local role review the page before using it.

What information should staff record and hand off?

Record the confirmed feature or arrangement, the relevant room or space and dates, and the role or team that verified it. Include unresolved items, their owner and the promised guest-update timing. Do not record a diagnosis or the reason behind the request when it is not needed to deliver the service. Use the property's approved method for recording and sharing details.

How do we customize this page for our property?

Replace Harborlight Hotel and its illustrative room, date and team examples with clearly identified local examples. Add the actual role responsible for room-feature verification, the approved method for recording and handing off service details, and the local escalation route. Confirm that examples reflect features your property has verified. Keep the privacy and no-over-promising safeguards intact.

Does the template connect to reservation or housekeeping systems?

The page describes a coordination process but does not include a configured reservation, room-inventory or housekeeping integration. It does not create a booking, confirm availability or send a handoff automatically. If your intranet supports connected blocks or linked systems, configure those separately and explain their source and limits. Until then, staff should use the property's approved local method.

How can a property roll this procedure out?

Have Hospitality Operations or the equivalent local owner validate the workflow, approved recording method and escalation roles before publishing. Brief each participating team on how to ask open questions, verify features and communicate uncertainty. Use a fictional or approved sample to practice a handoff without exposing guest information. Review the page when local procedures or room features change.

Why use this page instead of an informal handoff?

An informal handoff can leave teams unsure what was verified, who owns an open question or when the guest will receive an update. This page gives teams a shared sequence and a checklist for those details. It also distinguishes a guest naming a feature from describing an outcome, helping staff avoid assumptions. It complements rather than replaces the property's authoritative operating procedures.

Related templates

Sites

Housekeeping Team Site

A three-page hotel housekeeping site with room-standard checks, a worked room-status handoff, and...

Sites

Hotel Room Out-of-Service Coordination

A hotel room out-of-service coordination page shows housekeeping, engineering, and front desk how...

Sites

Hotel Night Audit Handoff

The Hotel Night Audit Handoff page shows night auditors how to document reconciliation exceptions...

Sites

Hotel Guest Experience Site

A five-page hotel guest-experience intranet site with front-desk conversation patterns, service-r...

Sites

Banquet Event Order Brief

A sample banquet event order brief page for coordinating one function across banquet, kitchen, an...

Forms

Customer Feedback Survey

Capture post-interaction customer feedback on overall satisfaction, specific touchpoints, and ope...

Inspections

Food Safety HACCP Audit

Food Safety HACCP Audit template for checking receiving, storage, prep, cooking, holding, cooling...

Sop

Cash Drawer Open & Count

Cash Drawer Open & Count is the SOP for verifying a drawer, counting the starting bank, recording...

Go deeper on the topic

Related concepts

Digital Workplace vs Modern Intranet

A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...

Ready to use this template?

Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Accessible Guest Stay Preparation ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Prepare a requested accessible stay without assuming or over-promising For reservations, front desk, housekeeping and guest services teams When a guest mentions an accessibility need, ask what would make the stay work for them, check the specific feature with the team that knows the room or space, and pass on only what is confirmed. This page uses a fictional property, Harborlight Hotel , to show how that coordination looks across departments. Scope: this page covers guest-specific stay preparation. It is separate from workplace accommodations for employees. Harborlight's examples are illustrative. For regulated, privacy-sensitive or safety-critical questions, follow your property's approved local procedure and involve the trained role it names. Questions about this page: Hospitality Operations owns it. Raise corrections with that team, and review the page whenever a local procedure or a room's features change. Two common requests, two different follow-ups Swipe sideways on a phone to read each row in full. Example from the guest "Does the room have a roll-in shower?" "I find it hard to step into a bathtub." What to ask "Is that feature needed for the whole stay, or just for one part of it?" "What would make the bathroom work best for you?" What to verify That the specific room type has that exact feature, with the team that holds room details Which available rooms or arrangements could meet the outcome the guest described What not to assume That a similar-sounding feature or a nearby room type is the same thing That you know which feature the guest wants, or that one solution suits everyone What the guest hears next What was confirmed, what is still being checked, and when you will update them The options that were confirmed, plus a follow-up on anything still open The coordination sequence Follow it in order, whichever team takes the first call or message. Ask what would help Use open wording such as "What would make your stay easier?" Let the guest describe it in their own terms. Do not ask for more detail than the service needs, and do not ask for medical information. Confirm the exact feature and its availability Ask the team responsible for the room or space to verify the specific feature for the dates requested. Do not rely on a room-type name or a past stay. Record only the relevant agreed details Use your property's approved local method. Write the confirmed request in practical terms, for example "bathroom with a shower seat confirmed for Room 412", not the reason behind it. Hand off the confirmed information Send the detail to each department that needs it to deliver the service. Name the person or role who owns any open question. Recheck unresolved items before arrival Review open questions the day before arrival. If something is still unconfirmed, contact the guest before they travel rather than at the desk. Who does what: a worked example at Harborlight Hotel A guest asks whether a room has a particular bathroom feature. Here is how each team contributes. Reservations: clarify the request The guest asks about a bathroom feature for a three-night stay. Reservations asks what the feature needs to do for them, notes the dates, and asks the responsible team to verify. Reservations does not promise a specific room yet. Housekeeping or the room-details owner: verify the room The responsible team checks the specific room for the requested feature and replies with what is and is not present. Anything unclear is reported as unconfirmed, not guessed. Front desk: receive only the confirmed detail The arrival note reads: "Room 412 confirmed with the requested bathroom feature. Guest asked for a ground-floor drop-off; bell team notified." It carries no reason or background. Guest services: close the loop Guest services contacts the guest once the room is confirmed and checks whether anything else would help on arrival. If anything is still open, they name who is checking and when the guest will hear back. When it is not straightforward Pause any assurance you cannot support, and use the trained role or approved local procedure. What if the feature cannot be confirmed? Tell the guest plainly what you could and could not confirm. Do not say "it should be fine". Ask the responsible team whether another room or arrangement would meet the same outcome, and share the options only once verified. What if the guest's preference is unclear? Ask again in different words, such as "What would a good arrival look like for you?" Offer the verified options you do have and let the guest choose. Do not pick for them. What if a request raises a privacy question? Share the detail only with teams that need it to deliver the service. If you are unsure who should see it, stop and ask the role your approved local procedure names. What if a request raises a policy or safety question? Do not improvise an answer or an exception. Pause, tell the guest you are checking, and take it to the trained role or approved local procedure. Give the guest a time for your update. Can I record the reason for the request? Record only what teams need to carry out the service, using your property's approved method. The reason behind a request is generally not needed for service delivery. Handoff checklist before arrival A handoff is ready when every item below can be answered in a sentence. Confirmed request: the specific feature or arrangement, the room or space, and the stay dates. Verification source: the team or role that confirmed it, and when. Open question and owner: anything still unconfirmed, and the named role checking it. Next guest update: who will contact the guest, by when, and about what. Limited content: the note holds only what is needed for service, with no reasons, diagnoses or unrelated personal detail. Example note: "Room 412, 14-17 May: bathroom feature confirmed by Housekeeping on 9 May. Ground-floor drop-off requested; bell team notified. Open: reserved parking near the entrance, owner Guest Services, update to guest by 12 May."