
Water intrusion reports and dispatch accuracy
A measurement protocol for leak reports, with shutoff status, source location, dispatch timing, and a guest-protection record that separates repair from relocation.
The useful measure is the share of water-intrusion reports with a confirmed shutoff status and a located source before a vendor is dispatched, and the share of affected stays that end without a relocation or a repeat leak report.
Methodology
- The unit of analysis is one water-intrusion report tied to a specific stay and property. A case enters the population when a guest or staff member reports water where it does not belong, including a leak, a burst line, a ceiling stain, or a backed-up drain. A routine plumbing request for a slow fixture is excluded unless water has escaped the fixture. Each case carries the property, the unit, the report time, and the responder who took the call.
- The observation window opens at the first report and closes at the later of the repair sign-off or the next turnover inspection. A case still open at the cutoff is reported as open rather than counted as resolved. The reviewer does not extend the window to capture a second repair that occurred after the reporting date. This keeps the measure tied to the response to the original report.
- The first field is the reported location: ceiling, wall, floor, fixture, appliance, or unknown. The reviewer records whether the guest identified a room and whether the description changed after photos arrived. A report that names a room but not a source is coded as located by room only. The field is used to test whether dispatch decisions were made on enough information.
- Shutoff status is coded as confirmed closed, attempted, not attempted, or unknown. A confirmed close requires a named valve and a report that the flow stopped. If the guest was told to find the valve without a follow-up confirmation, the field remains attempted. The reviewer records the time between the report and the shutoff confirmation. This separates a protocol that exists from one that was actually used.
- Dispatch accuracy is coded by the trade sent, the parts or equipment requested, and whether the vendor arrived within the promised window. A plumber sent without the unit's shutoff location or photos is coded as an incomplete brief. The reviewer notes whether the vendor had to make a second trip for a part. A second trip is not automatically a failure, but it is recorded as a cost.
- Guest protection is coded as no disruption, a temporary fix, a room restriction, or a relocation. A room restriction includes a closed bathroom, a blocked bedroom, or a unit without running water. The reviewer records the time the guest was told about the restriction and whether an alternative was offered. A guest who discovers the problem without a message is coded as uninformed.
- The record captures the affected area and the materials involved: carpet, hardwood, drywall, ceiling, insulation, or a neighboring unit. The reviewer notes whether a moisture check or a drying service was scheduled. A repair that closes the pipe but leaves wet material is marked incomplete. The field is intended to catch a cosmetic fix that hides a larger risk. A drying record is filed with the repair note.
- Cost fields include the emergency call, the repair, drying or restoration, a guest credit, and any lost night. The reviewer reports each amount beside the response time instead of collapsing them into one total. A cheap repair with a relocation can cost more than an expensive repair that keeps the guest in place. The record keeps that tradeoff visible to the owner.
- Communication is coded for the first response time, the number of updates, and whether the guest received a written plan. A plan that states who is coming, when, and what the guest should do is coded as complete. A message that only says someone will look into it is coded as partial. The reviewer records whether the guest had a direct number for the responder.
- Sampling takes every eligible report 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 building 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.
- Two reviewers code the first ten cases independently for shutoff status, dispatch brief, and guest protection. Disagreements are resolved by the maintenance 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. The rule is stored with the case file.
- Limitations are stated before any recommendation. The sample is a local record set, not an industry rate, and a fast shutoff is not proof that the repair was correct. A guest credit may reflect a policy rather than the severity of the leak. The report names one proposed change with an owner and a review date, and no association is described as causation.
- A final field records whether the property record contained the shutoff location and a photo of the valve before the event. A report handled without that information is coded as a documentation gap even when the guest eventually found the valve. This separates a training problem from a record problem and gives the owner a concrete item to fix. The owner can then label the valve before the next season.
- The reviewer also notes the time of day and whether the report arrived outside staffed hours. An after-hours report is compared with the same property's daytime cases to see whether the response depended on who was on call. The comparison is descriptive, not a performance rating. It helps the owner decide whether an on-call plumber or a guest-facing shutoff guide is the better investment.
Findings
- Water reports often arrive with a room name and a guess about the cause. The guest may say the toilet is leaking when the water is coming from a supply line behind the wall. The protocol treats the first description as a starting point, not a diagnosis. A photo and a shutoff confirmation are more useful to the plumber than a confident guess.
- The shutoff question is the clearest divide between a contained event and a flooded unit. In the reviewed set, cases with a confirmed valve close had a shorter path to repair and a lower chance of a room restriction. The record does not prove that the valve caused the better outcome, but it shows that the first minute matters. A labeled valve is a low-cost improvement for every property.
- Guests are often asked to find a valve in a cabinet or a crawlspace they have never seen. That request can be unsafe, especially when water is near an electrical panel. The protocol separates a guest-reachable fixture valve from a building main that requires staff. The responder should send a key holder when the safe action is not obvious. A photo of the valve is better than a verbal description.
- Dispatch briefs that lack photos and shutoff status produce more second trips. A plumber who arrives without knowing the fixture may carry the wrong part or the wrong tool. The reviewed records show that a brief with a photo, the valve status, and the access code is more likely to end in one visit. The brief is a small task that protects the whole schedule.
- Ceiling leaks are frequently underreported because the guest is afraid of being blamed. A stain that is dismissed as old paint can hide an active supply line above. The reviewer should record the report time and the first inspection time, not only the repair time. A ceiling that is bulging is an immediate hazard and should trigger a room restriction.
- Relocation is sometimes the cheapest safe response. A unit without running water cannot support a normal stay, even when the repair is scheduled for the same day. The reviewed cases suggest that a clear move with one alternative produces fewer follow-up messages than a series of delays. The guest should receive the new address and the access details in one message.
- A guest credit is not a substitute for a repair record. When the property credits a stay without documenting the cause, the next coordinator cannot tell whether the problem was fixed. The protocol records both the credit and the work order. That pairing lets the owner see whether the same unit is producing repeat events. The credit is a service outcome, not evidence of a fix.
- Drying and restoration are the most commonly omitted cost fields. A pipe repair can close the leak while wet carpet and drywall continue to create a smell or a mold risk. The reviewer notes whether a moisture check was scheduled and whether the next turnover found damp material. A repair that stops the water but not the damage is incomplete.
- After-hours reports test whether the property has a real response path. A guest who calls a general number and waits until morning may spend the night moving towels. The reviewed records show that a named on-call contact and a written shutoff guide reduce the number of decisions the guest has to make. The guide should use photos of the actual valves, not a generic diagram.
- The property record is often the weakest link. A coordinator who knows the shutoff location may leave no note for the next shift. The protocol treats the missing note as a documentation gap, not a personal failure. The fix is a short field in the property profile that every responder can see before the call. The note should be updated whenever a valve or fixture changes.
- Repeat leaks in the same unit point to a cause that was never addressed. A patch on a pipe may fail again if the pressure or the fitting is wrong. The reviewer should compare the repair note with the previous work order and flag a pattern. The owner can then decide whether a larger inspection is cheaper than another emergency call.
- The limits of the measure are real. A fast response can still produce a bad repair, and a slow response can still end with a satisfied guest. 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 valve-labeling program, 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.
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
- WaterSenseU.S. Environmental Protection AgencyChecked 2026-11-19
- Indoor air qualityU.S. Environmental Protection AgencyChecked 2026-11-19
- Hygiene guidanceCenters for Disease Control and PreventionChecked 2026-11-19
- Flood safetyReady.govChecked 2026-11-19
- Manage your financesU.S. Small Business AdministrationChecked 2026-11-19
- Rental income and expensesInternal Revenue ServiceChecked 2026-11-19
- American Housing SurveyU.S. Census BureauChecked 2026-11-19
- Wage and hour guidanceU.S. Department of LaborChecked 2026-11-19
- Emergency planningReady.govChecked 2026-11-19
- Housing topicsU.S. Census BureauChecked 2026-11-19