Evidence limits in STR power-outage status updates

Methodology

1. Scope and unit of review: one property-linked outage report during an occupied or arriving stay, including guest wording, local time, utility status, outage identifier, property observations, affected systems, access implications, vulnerable-person report, next utility estimate, and manager. Freeze the observation window before reading the final outcome. Include only records tied to a named short-term rental and a live operating consequence. Exclude general questions that never reached a reservation, turnover, access, vendor, or property workflow. Which sources should an STR coordinator reconcile before sending a power-outage status update to an occupied property? Keep the original artifact in its approved system and use a controlled reference in the review table. The unit is an administrative case, not a guest, worker, or property score. [Review unit: str-power-outage-status-evidence-review]
2. Evidence selection: Airbnb documentation provides channel context. NIST, CISA, FTC, NARA, and PlainLanguage.gov provide boundaries for access, privacy, incident handling, records, security, and clear communication. Topic-specific government publications provide additional context where relevant. None of the selected sources tests this exact STRVirtualAssistant process. The review treats external publications as context, property records as local observations, and the proposed workflow as analysis. A citation does not transfer the publisher's authority to a property-specific decision. [Review unit: str-power-outage-status-evidence-review]
3. Collection: A guest report describes conditions they observed. A utility map describes the provider's known service state. A smart-device disconnect shows loss of contact, not necessarily loss of power. Each source has different coverage and can be stale. For each field, record the source, observer or system, timestamp, applicable property, correction history, and person who can resolve a conflict. Use confirmed, reported, conflicting, stale, and unknown as separate states. Do not code a missing reply as agreement. Preserve both values when systems disagree. A second reviewer should attempt to reproduce a sample from the same source artifacts before the team relies on the classification rule. [Review unit: str-power-outage-status-evidence-review]
4. Authority protocol: STRVirtualAssistant can gather reports, quote the utility's current notice, keep an update clock, and route approved messages. The utility and qualified trades own technical restoration; the manager owns entry, relocation, spending, and guest remedies. The case table separates information retrieval, message drafting, coordination, approval, technical judgment, and binding action. Record the requested action, deadline, reversibility, missing evidence, standing rule if one exists, escalation owner, and next review time. Suspected danger uses the operator's urgent route at once. The team should never delay an urgent response merely to complete research fields or obtain a tidy denominator. [Review unit: str-power-outage-status-evidence-review]
5. Analysis: report absolute counts and denominators for complete cases, missing sources, contradictions, corrections, premature actions, escalations, and cases still unresolved at cutoff. compare a utility-wide event where one property retained power with a property-only breaker or equipment issue that did not appear on the public map. Remove the largest property, channel, or event group as a sensitivity check. Do not translate response time into labor saved, guest satisfaction, financial value, safety improvement, or reduced risk. Record the strongest alternative explanation and the additional artifact that could change the reading. [Review unit: str-power-outage-status-evidence-review]
6. Limitations: Public maps can lag, restoration estimates change, devices lose connectivity for other reasons, and remote observations cannot establish electrical safety. This review does not replace emergency services, the utility, or a licensed electrician. Interfaces, permissions, contracts, property procedures, and operating conditions change. A complete record proves only that required administrative fields were captured under the stated rule. It cannot by itself establish physical condition, legal compliance, causation, fault, safety, or a correct business decision. Findings apply to the observed cases and definitions. They should not be published as an industry rate or represented as measured STRVirtualAssistant performance. [Review unit: str-power-outage-status-evidence-review]