Accessible-stay requests and confirmation accuracy research visual

Accessibility Intake

Published

Accessible-stay requests and confirmation accuracy

A measurement protocol for accessible-stay requests, with task-based intake, measured routes, verified feature claims, and a record of what the property could actually deliver.

The useful measure is the share of accessible-stay requests whose confirmed features matched the property at arrival, and the share of guests who received the access plan before the booking was final.

Methodology

  1. The unit of analysis is one stay with an access-related request, whether the guest uses a mobility device, needs a step-free route, or requires a bathroom feature. A case enters the population when the guest mentions an access need before or at booking. A general question about parking is excluded unless it is tied to a mobility or access requirement. Each case carries the property, the unit, the requested feature, and the coordinator who handled it.
  2. The observation window opens at the first access question and closes at the end of the stay or at cancellation. A case still open at the cutoff is reported as open rather than counted as a success. The reviewer does not extend the window to capture a later complaint that arrived after the reporting date. This keeps the measure tied to the confirmation the guest received.
  3. Intake is coded by whether the coordinator asked about tasks rather than diagnoses. A task-based question names the activity, such as entering without stairs, showering, or sleeping on the main floor. A diagnosis-based question asks for a medical label that the property does not need. The reviewer records the first question and whether the guest had to repeat the need in a later message.
  4. Each confirmed feature is coded against a property record: entrance steps, door width, bathroom entry, grab bars, bed height, and the level of the sleeping area. A feature is confirmed only when the coordinator has a measurement or a photo from the actual unit. A listing description alone is treated as unverified. The reviewer notes the date the evidence was captured.
  5. The route is coded from the parking area to the unit door, including curbs, gravel, thresholds, and the distance the guest must travel. A step-free door with a steep or broken path is marked partial. The reviewer records whether the route was walked in person or checked from photos. Photos taken at night or from a street view are marked as weaker evidence.
  6. The building record is coded separately from the unit. Elevator size, lobby thresholds, door pressure, and the distance to the nearest accessible parking are recorded when available. A building that cannot be entered without help is a limitation even when the unit itself is level. The reviewer notes whether the guest was told about the building limit before paying. A guest who cannot enter the building never sees the unit.
  7. The promise is coded as confirmed, conditional, or declined. A confirmed promise lists the features the property has verified. A conditional promise names a vendor installation or an owner approval that is not yet complete. A decline names the missing feature and any alternative offered. The reviewer records whether the guest confirmed the promise in writing, and stores that confirmation with the booking.
  8. Arrival accuracy is coded by comparing the confirmation with what the guest found. A match requires each confirmed feature to be present and usable. A near match is recorded when the feature exists but differs in a way that matters, such as a bathroom that is step-free but too narrow for the guest's device. The reviewer does not rely on the guest's overall satisfaction to decide the code.
  9. Communication is coded for timing, channel, and completeness. A plan sent before the booking is distinguished from one sent the day before arrival. The reviewer notes whether the guest received the on-site contact and a backup number. A plan that omits the parking or entry detail is marked partial even when the unit description is accurate. A partial plan is treated as a missing feature, not a minor omission.
  10. Sampling takes every eligible request when the portfolio produces fewer than thirty cases in the window. Above that volume, the frame uses a fixed interval across properties and months, stratified by request type and by whether the unit was occupied. The frame is frozen before coding, and replacements are allowed only for a missing record. Small cells are suppressed in the summary.
  11. Two reviewers code the first ten cases independently for intake, confirmation, and arrival accuracy. Disagreements are resolved by the operations lead, who writes the rule used for the case. Reliability is reported as the share of matching fields. The guest is not contacted to reconstruct the interaction because the review measures the property record and the message thread. The final rule is stored with the case file.
  12. Limitations are stated before any recommendation. The sample is a local record set, not an industry rate, and a confirmed feature is not a guarantee that every guest can use it. A guest may choose a property that does not meet every preference. The report names one proposed change with an owner and a review date, and no association is described as causation.
  13. A final field records whether the property had a current access profile with measurements and photos. A request handled from an old profile is coded as a record gap even when the guest arrived without a problem. This separates a lucky match from a repeatable process and gives the owner a specific document to update. The profile is reviewed whenever the unit is renovated.
  14. The reviewer also notes whether the guest was offered a cancellation or a different property when the need could not be met. An honest decline with an alternative is coded as a good outcome, not a lost booking. A decline with no alternative is recorded as a service gap. The field is intended to show that accuracy matters more than conversion for this request type.

Findings

  • Accessible-stay requests are often phrased as a preference rather than a requirement. A guest may ask whether the unit has a few steps because they are comparing listings, not because they cannot use stairs. The coordinator should ask what the guest needs to do before deciding how much detail to collect. A short task question is more useful than a long medical one.
  • The property profile is the foundation of an accurate answer. When measurements and photos are current, the coordinator can confirm a feature without visiting the unit. When the profile is missing, the answer depends on a listing description that may have been written for marketing. The reviewed records show that a verified profile reduces the number of corrections after booking.
  • Door width is the feature most often described in vague terms. A coordinator may say the bathroom is accessible because it is large, while the doorway is too narrow for a wheelchair. The protocol requires a measurement at the actual door the guest will use. A number and a photo are more useful than an adjective. The measurement is taken at the narrowest point of the frame.
  • The route outside the unit is frequently overlooked. A level unit at the top of a gravel driveway is not a step-free stay. The reviewer records the path from parking to door, including curbs and thresholds. A guest who cannot reach the entrance has not received the feature the listing promised. The distance is recorded in paces or feet, not as a vague short walk.
  • Conditional promises create the most arrival risk. An owner may agree to install a grab bar, but the vendor date slips and the guest is not told. The protocol treats a conditional promise as incomplete until the work is done and photographed. The guest should receive a cancellation option if the condition cannot be met. The guest should not have to ask twice for the status.
  • Guests often repeat their access need in several messages because no single record holds it. The reviewed cases suggest that one access note, visible to the arrival team, reduces repetition and missed details. The note should state the confirmed features and the limitations in plain language. It should not include medical information the property does not need. The access note is the one place the whole team can check.
  • Arrival accuracy depends on the handoff more than the booking message. A correct confirmation that never reaches the greeter can still produce a failed arrival. The protocol records whether the access note was sent to the cleaner, the greeter, and the maintenance contact. A note that lives only in the reservation system is marked partial. The greeter confirms the note before the guest reaches the door.
  • An honest decline is a better outcome than a booking that fails at the door. When the property cannot meet the need, the coordinator should name the missing feature and offer an alternative. The reviewed records show that guests often accept a different unit or date when the limitation is explained early. A vague promise delays the guest's search and damages trust.
  • Temporary equipment can close a small gap, but only when it is confirmed and delivered. A shower chair that arrives after the guest does not help the first night. The protocol records the vendor, the delivery time, and the pickup plan. A borrowed item without an owner is a liability, not a feature. The pickup is scheduled before the stay begins.
  • Building rules can override a unit-level fix. A ramp in a common hallway may violate a fire code or an association rule even when the owner approves it. The reviewer notes whether the building was consulted before a temporary installation. A unit-level solution that blocks an exit is not accessible. A hallway ramp that blocks an exit is not a reasonable accommodation.
  • The arrival team needs a direct contact and a backup. A guest who calls a general number on a weekend may wait while the on-call person searches for the reservation. The protocol records the named contact and the backup before the stay. That detail is part of the access plan, not an extra courtesy. The backup is named in the reservation, not left to the front desk.
  • The limits of the measure are important. A confirmed feature can still be unusable because of a temporary obstacle, and a guest may choose not to report a problem. The sample is local and the cells are small, so the findings are operating hypotheses. The next cycle should test one change, such as a measured access profile, before treating the pattern as settled.

Research standards

Every review freezes its observation window before findings are calculated. Reviewers retain a row-level evidence ledger with the original artifact reference, timestamp, responsible role, status at cutoff, correction history, denominator, exclusions, and unresolved cases. Ambiguous records are coded independently before reconciliation, and both readings remain visible until an accountable adjudicator applies a documented rule. Missing information is treated as unknown rather than silently classified as success or failure. Sensitivity checks remove major record classes in turn so a pattern that depends on one owner, channel, event type, or reporting cycle is disclosed instead of presented as stable. Elapsed time is not translated into labor, an association is not described as causation, and local observations are not converted into external benchmarks.

Interpretation begins with counterexamples and the cases still open at the cutoff. A formally complete record may lack usable evidence, while an authorized alternative path may achieve the intended outcome without matching the expected workflow. The review therefore states the strongest alternative explanation, identifies the additional artifact that could distinguish it from the preferred reading, and records what would reverse or retire the resulting operating rule. Comparisons use the same field definitions and equivalent work classes; a material change in coverage, tooling, policy, or sample composition creates a new baseline rather than a trend. Follow-up records name the decision taken, responsible owner, anticipated signal, review date, exception path, and evidence required before a stronger intervention can be justified.

Governance checks keep only information necessary for the research question. Sensitive content is replaced with a controlled reference whenever an authorized reviewer can reproduce the classification without holding a copy. Access boundaries, retention expectations, correction ownership, disputed-interpretation routes, duplicate handling, spanning-record rules, and cutoff treatment are documented before release. Absolute counts appear beside percentages, small samples avoid false precision, and every external statement links to a listed source without implying that the publication measured the local record set. The proposed action must be proportionate, reversible, and reviewable. If the available evidence cannot support it, the gap becomes an explicit evidence request rather than an assumption.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

This research note supports the STR Virtual Assistant topical map for vacation-rental guest communication, property readiness, issue routing, and evidence-based operational follow-through.

Talk through the executive workflow that needs clearer ownership.

Bring the recurring tasks, handoffs, and access boundaries you want dependable support to manage.

Talk with our team

Sources

  1. ADA accessibility resourcesU.S. Department of JusticeChecked 2026-11-19
  2. Accessible design standardsU.S. Access BoardChecked 2026-11-19
  3. Fair housing guidanceU.S. Department of Housing and Urban DevelopmentChecked 2026-11-19
  4. Rental assistance programsU.S. Department of Housing and Urban DevelopmentChecked 2026-11-19
  5. American Housing SurveyU.S. Census BureauChecked 2026-11-19
  6. Housing topicsU.S. Census BureauChecked 2026-11-19
  7. Wage and hour guidanceU.S. Department of LaborChecked 2026-11-19
  8. Rental income and expensesInternal Revenue ServiceChecked 2026-11-19
  9. Launch your businessU.S. Small Business AdministrationChecked 2026-11-19
  10. Emergency planningReady.govChecked 2026-11-19
Accessible-stay requests and | STR Virtual Assistant