
Utility shutoff notices and reservation exposure
A measurement protocol for utility shutoff notices, with a verified window, an exposure count, and a review of relocation, reschedule, and prepared-stay decisions.
The useful count is the number of reservations exposed to a confirmed shutoff window and the share resolved before the guest arrives, reported with the service and the decision path.
Methodology
- The unit of analysis is one confirmed utility shutoff notice that overlaps at least one reservation or owner stay. A case enters the population when the utility or building confirms a window for water, power, gas, or a shared service. An unconfirmed door hanger is held in a verification queue and is not counted as a case. Each case carries the property, the service, the window, and the coordinator.
- The notice is verified by a named person at the utility or the building, with the date and time of the call. A notice that names a range of hours is recorded as a range, not converted into a point estimate. A second-hand notice from a neighbor is not accepted until the utility confirms it. The reviewer records the confirmation source because a false notice produces unnecessary relocation.
- The exposure count includes every reservation whose stay overlaps the window by at least one night or whose arrival or departure falls inside it. A same-day turnover is counted separately because the cleaner may need the service even when no guest is present. Owner stays and vendor visits are included when they depend on the affected service. The count is frozen before the first remedy is offered.
- The service dependency is coded by what stops working: water, hot water, power, heat, cooling, internet, or a shared building system. A water shutoff may also stop a boiler, a lift, or a sump pump, so the reviewer records the second-order dependency. A power shutoff may disable a door hub even when the unit has backup lighting. The coding is based on the property record, not on the utility's general notice.
- The decision path is coded as relocate, reschedule, prepare, or no action. Relocate moves the guest to another unit. Reschedule moves the dates. Prepare keeps the stay with a supplied workaround such as water containers or a battery pack. No action is used only when the window does not affect the guest's use of the unit. The path is recorded before the outcome is known.
- The owner approval is recorded as a separate field. A relocation that costs more than the original booking needs an approval reference. A reschedule that creates a vacancy needs an owner decision. A prepared stay may need approval for supplies or a credit. The reviewer notes the approval time so a slow decision is not hidden inside the exposure count.
- The guest communication is coded for timing and accuracy. A case is clean when the guest receives the confirmed window and the chosen plan before the original arrival time. A case is late when the guest learns at the door. The reviewer also records whether the guest was told what the property controls and what the utility controls. A vague promise is coded as inaccurate.
- Sampling takes every confirmed notice in the window when the portfolio produces fewer than thirty cases. Above that volume, the frame uses a fixed interval across properties and service types, stratified by whether the property has a backup system. The frame is frozen before the first guest remedy is read. Replacements are allowed only for a missing record and must be documented.
- Two reviewers code the first twelve cases independently for verification, exposure, decision path, and guest communication. 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 sequence because the review measures the property record and the message thread.
- Cases are grouped by service and by lead time: more than seven days, two to seven days, and less than forty-eight hours. The report also separates properties with a written outage plan from those without one. The grouping is fixed before the results are summarized so a strong planned case does not hide a weak short-notice case. This keeps a routine repair apart from an emergency.
- The cost field records relocation difference, unused nights, guest remedy, and staff time. The reviewer does not combine those amounts into a single score because the owner may value a saved booking differently from a saved night. The amounts are reported beside the operational result. A case with no direct cost can still consume the next arrival's buffer.
- The report closes with the number of confirmed notices, the number of exposed reservations, the share resolved before arrival, and the share with a written guest plan. 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 confirmed notices arrive with enough lead time to move a booking, but the short-notice cases create most of the guest impact. A notice that lands less than forty-eight hours before arrival leaves little room for a relocation. The report separates the lead-time bands because the available remedies are different. A single average would hide the hard tail.
- Water shutoffs produce more second-order failures than the notice suggests. A building water shutdown can stop a boiler, a lift, or a cooling system that the utility did not mention. The coordinator who reads only the first line misses the dependency. The reviewer records the building systems that share the supply.
- Relocation is the cleanest remedy when the service is essential and the stay is short. The cases that go well have a replacement unit confirmed before the guest is told. The cases that go badly promise a move and then search for a unit. The report recommends confirming the destination before opening the conversation.
- Rescheduling protects the property from a bad stay but can create a vacancy that the owner did not approve. The decision needs a cost comparison, not only a guest preference. A reschedule that fills the original dates with another booking may be better than a relocation. The reviewer records the outcome on both reservations.
- Prepared stays work for daytime outages when the guest is out and the property can supply what is missing. They fail when the guest works from the unit or needs hot water. The report treats the guest's use of the unit as part of the decision, not as an afterthought. A prepared stay without a check-in call is an unverified plan.
- Guest communication is the most common soft failure. The property often knows about the shutoff before the guest does, but the message arrives after the guest has planned the day. A confirmed window and a named contact would remove most of the confusion. The reviewer codes the message timing separately from the physical outcome.
- Properties with a written outage plan resolve cases faster and with fewer owner escalations. The association is not proof of cause because those properties may also have more staff. The practical difference is that the plan names who decides and what the guest is told. A plan written after the first outage is still useful for the next one.
- Short-notice cases cluster in older buildings with shared risers and in regions with seasonal utility work. The property cannot control the timing, but it can keep a current guest contact and a relocation list. The report recommends the list before the next planned maintenance season. A list that is not tested is only an intention.
- The strongest predictor of a clean case is a verified notice. Unverified notices produce unnecessary relocations and erode guest trust when the shutoff does not happen. The local sample cannot establish causation, so the result is a hypothesis for the next cycle. A second window after a verification step is required.
- A final check compares the notice window with the restoration time. In several cases the utility finished early and the property could have kept the guest. In others the work ran long and the relocation was justified. The reviewer records both times so the decision can be reviewed against the actual event, not the original estimate.
- A final field records whether the cleaner and vendor calendars were updated. A shutoff that is known to the guest but not the cleaner can cancel a turnover or leave a vendor without water. The reviewer marks that as an uncorrected handoff even when the guest was satisfied. A single calendar entry would make the restriction visible at the point of work.
- A final field records the guest's decision and the reason. A guest who chooses to stay through a short outage may be satisfied, while a guest who was not offered a choice may complain later. The reviewer treats the offer as part of the record. The property should be able to show that the guest had a real option.
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
- Energy SaverU.S. Department of EnergyChecked 2026-11-17
- Indoor air qualityU.S. Environmental Protection AgencyChecked 2026-11-17
- Emergency preparednessReady.govChecked 2026-11-17
- Federal Emergency Management AgencyFEMAChecked 2026-11-17
- Rental assistance programsU.S. Department of Housing and Urban DevelopmentChecked 2026-11-17
- American Housing SurveyU.S. Census BureauChecked 2026-11-17
- Rental income and expensesInternal Revenue ServiceChecked 2026-11-17
- Recordkeeping guidanceInternal Revenue ServiceChecked 2026-11-17
- Product safetyU.S. Consumer Product Safety CommissionChecked 2026-11-17
- Workplace safety and healthOccupational Safety and Health AdministrationChecked 2026-11-17
- Manage your businessU.S. Small Business AdministrationChecked 2026-11-17
- Cybersecurity best practicesCybersecurity and Infrastructure Security AgencyChecked 2026-11-17
- Privacy FrameworkNational Institute of Standards and TechnologyChecked 2026-11-17
- Data security guidanceFederal Trade CommissionChecked 2026-11-17