
Emotional support animal request screening time
A measurement protocol for the interval between an assistance animal request and a written decision, with separate checks for evidence completeness and guest privacy.
Screening time runs from the first guest message to a recorded decision, and a fast answer is not evidence that the decision was correct.
Methodology
- The unit of analysis is one assistance animal request attached to one booking and one property. A request enters the population when the guest asks to stay with an animal that is not a pet, whether the message includes a provider letter or not. Requests for ordinary pets are excluded and counted in a separate stream. Each case carries the booking date, the request date, the decision date, the responder, and the policy version that was applied.
- The start time is the first message in which the guest mentions the animal, not the later message that includes paperwork. A request made before booking starts at the booking inquiry, while a request made after arrival starts at the first in-stay message. The reviewer records the time zone used for each timestamp because the property and the guest may be in different regions. Messages that only ask about the pet policy without mentioning a specific animal stay outside the primary population.
- The decision time is the moment a written answer is sent that approves, declines, or requests one specific follow-up. A holding reply that says the team is checking does not count as a decision unless it states what will happen next. The reviewer keeps the exact wording and the responder. If the guest receives several replies, the first substantive decision is the one scored and later changes are recorded as revisions.
- Evidence completeness is scored on a three-part scale: the request, the supporting document if any, and the decision rationale. A case is complete when a manager who was not involved can understand what was asked and why the answer was given. A missing rationale is not the same as a missing document, because some requests can be approved without formal paperwork. The protocol reports the two gaps separately rather than merging them into a single quality score.
- Privacy is checked by listing the personal fields collected during screening. The reviewer records whether any field was unnecessary for the decision, such as a diagnosis, a medication list, or an identification number. A case is marked as over-collected when a field was requested without a policy reason. The field list is reviewed by the manager before the results are published, and the report shows counts rather than guest details.
- Sampling uses every eligible request in the window when the portfolio produces fewer than thirty cases. Above that volume, the frame uses a fixed interval across properties and booking dates, stratified by whether the request arrived before or after booking. The frame is frozen before the first message is read, and a case is replaced only when the original record is missing. The report states the eligible total, the number read, and the stopping point.
- Two reviewers code the first twelve cases independently and compare the start time, decision time, evidence state, and privacy fields. Disagreements are resolved by the property manager, who records the rule that settles the case. Reliability is reported as the share of matching fields, with the ambiguous cases listed. The guest is not contacted to reconstruct the sequence, because the review is about the property’s record.
- Cases are grouped by request timing and by property type because a request made weeks before arrival is not comparable to one made at the door. The grouping is fixed before coding, and a property that changes its policy during the window is reported under both versions. The reviewer records the group first so the comparison cannot shift after the numbers are known. This keeps a simple pre-booking approval from being averaged with an urgent in-stay request.
- The report closes with one proposed change, the role that owns it, and a date for the next observation window. The change might be a revised intake form, a saved reply, or a requirement that the manager review any decline. The report does not treat a fast approval as success, because speed can reflect a skipped check. The decision quality and the response time remain separate outcomes on purpose.
Findings
- Most delayed decisions begin with an incomplete first message rather than a slow reviewer. The guest mentions an animal without saying when it will arrive, and the coordinator waits for details that the intake form never requested. A short form with the booking reference, the animal type, and the stay dates would remove the most common pause. The review counts the missing field as a process gap, not a guest failure.
- Requests that arrive before booking are decided faster than requests that arrive during a stay, because the coordinator has more time and fewer competing messages. The gap narrows when the property uses a saved reply with a clear path. The protocol reports the two groups separately so a good pre-booking result does not hide a weak in-stay result. The difference is a scheduling effect, not evidence that one guest deserves a faster answer.
- Declines are the least documented decision in the reviewed cases. A decline often appears as a short message with no policy reference, while an approval includes the house rules and the next step. The reviewer marks the missing rationale as a completeness gap even when the decline was correct. A manager reviewing the file later cannot tell whether the guest was refused for a lawful reason or for convenience.
- Pet charges are removed inconsistently. Some cases show a refund after the guest complains, while others show the charge removed before arrival. The timing matters because a guest who sees a charge may cancel or write a negative review before the correction. The protocol records the charge state at booking, at approval, and after the stay. A charge that survives an approval is flagged for review.
- The privacy check finds unnecessary fields most often in requests that include a provider letter. The coordinator may ask for a diagnosis to confirm the letter, even when the policy only requires a statement of the disability-related need. Those requests add personal data without improving the decision. The report recommends a field-by-field review of the intake form rather than another training reminder.
- Properties with a written accommodation path show fewer revisions after the first answer. The first reply is more likely to include the house rules, the charge decision, and the next step in one message. This is an association rather than proof of cause, because those properties may also have more stable staffing. The pattern still supports documenting the path before the next busy season.
- Manager review is the slowest step in the chain, not the guest reply. A request that needs approval can wait a day while the coordinator waits for a meeting. The protocol measures the handoff time separately from the screening time so the delay is visible. A named backup approver would remove part of the wait without changing the policy.
- Guests rarely challenge a clear answer, even when the answer is no. The reviewed cases with a specific reason and an alternative path produced fewer follow-up messages than cases with a vague reply. The reviewer codes the follow-up count as a secondary measure. A decline that invites another question is more expensive than a decline that explains the rule.
- The strongest predictor of a complete record is a single owner for the accommodation path. Cases handled by rotating inbox staff are more likely to miss the rationale or collect an extra field. 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 decision in the guest message with the decision in the property record. The two can diverge when a coordinator tells the guest one thing and logs 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.
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.
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.
Sources
- HUD fair housing guidanceHUDChecked 2026-11-10
- HUD assistance animals guidanceHUDChecked 2026-11-10
- ADA service animal requirementsU.S. Department of JusticeChecked 2026-11-10
- ADA informationU.S. Department of JusticeChecked 2026-11-10
- NIST Privacy FrameworkNISTChecked 2026-11-10
- NIST Cybersecurity FrameworkNISTChecked 2026-11-10
- HUD fair housing overviewHUDChecked 2026-11-10
- FTC privacy and security guidanceFTCChecked 2026-11-10
- SBA business guideSBAChecked 2026-11-10
- DOL wage and hour recordkeepingU.S. Department of LaborChecked 2026-11-10