Occupancy mismatch checks before and at arrival research visual

Guest Arrivals

Published

Occupancy mismatch checks before and at arrival

A measurement protocol for comparing the registered guest count with the people who arrive, and for timing the correction before door access and cleaning plans are set.

The useful occupancy measure is the interval between a detected count mismatch and a written correction that reaches the reservation, the access step, and the cleaner.

Methodology

  1. The unit of analysis is one reservation attached to one property and one arrival date. A case enters the population when the guest count on the reservation differs from the count stated in a message, at the door, or in a post-stay note. Reservations with no arrival during the window are excluded, as are cancellations that never produced a check-in. Each case carries the registered count, the reported count, the property limit, and the responder.
  2. The clock starts at the first record in which the mismatch becomes visible to the property. It ends when a written message tells the guest the approved count, the charge if any applies, and the next step. A question that asks the guest to clarify does not stop the clock, because the property still lacks a resolved count. The reviewer keeps both times so a fast question is not scored as a fast decision.
  3. The capacity condition is recorded from the property record, not from the guest's description. The reviewer notes the stated sleeping capacity, the linen pack size, the parking allocation, and any building limit. A unit is marked over capacity when the reported count exceeds the written maximum even if the guests could physically fit. The protocol treats physical fit and approved capacity as separate facts.
  4. The access condition is scored before the door is opened. A case is clean when the count is resolved before a code, key, or lockbox detail is shared. A case is late when access is released first and the correction follows. The reviewer records the exact access method because a code shared in a message cannot be recalled. This field separates a documentation gap from a security event.
  5. The owner rule is captured as a versioned field. The reviewer records whether a written occupancy rule existed, the extra-guest charge that applied, and the approval reference for any exception. A property that changed its rule during the window appears under both versions. The protocol does not compare a local charge with a market rate, because the owner sets the terms.
  6. The guest confirmation is recorded as its own state. A case is confirmed only when the guest accepts the corrected count and the amount in writing. A caller who says yes on the phone stays pending until the message thread carries the same answer. The reviewer notes the confirmation time after the decision time so the two are never merged.
  7. Sampling takes every eligible arrival when a portfolio produces fewer than thirty cases in the window. Above that volume, the frame uses a fixed interval across properties and arrival dates, stratified by channel and by whether the reservation was made more than seven days ahead. The frame is frozen before the first message is read. Replacements are allowed only for a missing record and must be documented.
  8. Two reviewers code the first twelve cases independently across the count, the capacity state, the access state, and the owner rule. Disagreements are settled by the operations lead, who writes the rule that resolves the case. Reliability is reported as the share of matching fields. The guest is not contacted to reconstruct the sequence, because the review measures the property record.
  9. Cases are grouped by how the mismatch was discovered: before arrival, at the door, or after the stay. The report also separates properties with a written occupancy rule from those without one. The grouping is fixed before coding so a strong pre-arrival result does not hide a weak door result. This keeps a routine correction apart from a confrontation.
  10. The report closes with the number of cases, the share resolved before access, the share with a written guest confirmation, and the share with a cleaner update. It names one proposed change, the role that owns it, and the date of the next observation window. No local result is presented as an industry rate, and no association is described as proof of cause.

Findings

  • Most mismatches in the reviewed arrivals are small and appear before check-in. A guest adds one adult, a child, or a friend for part of the stay, and the reservation count stays at the original number. The pre-arrival share matters because those cases can be corrected while the guest is still planning. The protocol separates them from door discoveries where the guest is already waiting.
  • Door discoveries are the costliest group because access and capacity are decided in the same minute. The coordinator is often talking to a tired guest while the cleaner is en route and the neighbor is watching the extra cars. Cases in this group produce more follow-up messages and more owner involvement. The report keeps the door group visible rather than averaging it with easy corrections.
  • Listing copy is associated with repeated mismatches at the same property. Units described as sleeping more people than the written limit, or with a sofa that is not a legal bed, attract groups that the rule cannot approve. The association is not proof of cause because the property may also have a larger driveway or a more permissive owner. It is still a practical place to start a fix.
  • Supply planning lags behind the count more often than access does. A coordinator corrects the reservation and messages the guest, but the linen pack and towel count stay at the original size. The cleaner then arrives to a unit that needs supplies the route did not carry. The reviewer codes this as a handoff gap rather than a guest problem.
  • Owner approvals are the slowest step when the extra guest falls outside the written rule. A case can sit for a day while the coordinator waits for a host who is traveling or in a different time zone. The protocol measures the approval interval separately so the delay is visible. A named backup approver would remove part of the wait without changing the policy.
  • Platform records diverge from property records in a minority of cases that still matter. A guest updates the count in the channel but the property system keeps the original number, or the reverse. The reviewer compares both fields and flags the mismatch as a record defect. A nightly reconciliation would catch most of these before arrival.
  • Properties with a written occupancy rule resolve cases faster and with fewer revisions. The first message is more likely to name the approved count, the charge, and the next step in one pass. This is an association rather than proof of cause because those properties may also have steadier staffing. The pattern still supports writing the rule before the next busy season.
  • Repeat properties account for a large share of late discoveries. A unit with a confusing listing or a shared driveway produces the same conversation with a different guest. The report counts repeat properties separately so the owner can see the concentration. A single listing edit may remove more cases than a new reminder to the team.
  • The strongest predictor of a complete record is a single owner for the arrival check. Cases handled by rotating inbox staff are more likely to miss the cleaner update or the written confirmation. The local sample cannot establish causation, so the result is a hypothesis for the next cycle. A second window after a staffing change is required before the rule is treated as settled.
  • A final check compares the count in the guest message with the count in the reservation record. The two can diverge when a coordinator tells the guest one thing and updates another. The reviewer codes the mismatch separately from a late decision because the guest experience depends on the message. A short end-of-day reconciliation catches the gap before the next arrival.
  • A final field records whether the cleaner saw the corrected count before the next turnover. In several cases the reservation and the guest message agreed while the linen pack stayed at the original size. The reviewer marks that as an uncorrected handoff even when the guest was satisfied. A single confirmation line to the cleaner would make the count change visible at the point of use.

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. Rental assistance programsU.S. Department of Housing and Urban DevelopmentChecked 2026-11-16
  2. Fair housing guidanceU.S. Department of Housing and Urban DevelopmentChecked 2026-11-16
  3. American Housing SurveyU.S. Census BureauChecked 2026-11-16
  4. Credit reports and scoresConsumer Financial Protection BureauChecked 2026-11-16
  5. Recordkeeping guidanceInternal Revenue ServiceChecked 2026-11-16
  6. Privacy FrameworkNISTChecked 2026-11-16
  7. Title III accessibilityU.S. Department of JusticeChecked 2026-11-16
  8. Government services directoryUSA.govChecked 2026-11-16
  9. Department of JusticeU.S. Department of JusticeChecked 2026-11-16
  10. Cybersecurity resourcesCISAChecked 2026-11-16
Occupancy mismatch checks | STR Virtual Assistant