
Contractor visits and access record completeness
A measurement protocol for repair visits, with an access window, a visit record, before-and-after evidence, work-order fields, and a closeout test.
The useful measure is the share of contractor visits with a closed record showing entry time, work scope, and a post-visit test or photo before the next guest arrives.
Methodology
- The unit of analysis is one contractor visit to a property, from dispatch to signoff. A case enters the population when a work order is assigned to an outside trade for a specific unit. Routine inspections that do not require access are excluded. Each case carries the property, the unit, the trade, the work order number, and the coordinator who scheduled it.
- The observation window opens when the visit is scheduled and closes when the record is signed off or the next guest checks in, whichever comes first. A visit still open at the cutoff is reported separately. The reviewer does not extend the window to capture a later invoice or a repeat repair. This keeps the measure tied to the visit that affected the stay.
- Record completeness is checked for work order, trade, entry time, exit time, scope, parts, and closeout evidence. A complete record names the person who authorized access and the person who signed off. The reviewer records each missing field rather than treating the record as a single pass or fail. A message thread alone is not a complete record.
- The access method is coded as guest present, staff present, smart lock, lockbox, or key handoff. A smart lock is narrow when the code expires at the end of the visit and wide when the guest's stay code is reused. The reviewer records the code type and the expiry. An open door or an unlocked unit is treated as a separate access exception.
- Scope is coded by the rooms the contractor was authorized to enter and the systems they were allowed to touch. A plumbing visit that requires the bathroom and the utility closet is different from one that requires the whole unit. The reviewer records any room entered outside the stated scope. A scope that was never written down cannot be checked.
- Evidence is checked for a before photo, an after photo, and a test result when the work calls for one. A lock repair should show the lock working; a water repair should show the supply on and no leak. The reviewer records whether the photo was taken in the work area or from the doorway. A photo of a clean room after the fact is weaker evidence than a before-and-after pair.
- Work-order fields are checked for the diagnosis, the parts used, and any follow-up recommendation. A replaced part should carry a model or a description. A quoted repair should be separated from a completed repair. The reviewer records whether the invoice matches the parts and the scope.
- Guest communication is coded for notice before entry and a summary after the visit. A guest who is home should know when to expect the knock and how the contractor will identify themselves. A guest who is away should receive a closing note with what changed. The reviewer records whether the property sent either message.
- Repeat visits are counted when the same trade returns for the same issue within thirty days. A second visit for a different issue is not a repeat. The reviewer records the reason given for the return and whether the first visit was signed off as complete. This separates a bad repair from a new problem.
- Sampling takes every eligible visit when the portfolio produces fewer than thirty cases in the window. Above that volume, the frame uses a fixed interval across properties and trades, stratified by access method and by whether the unit was occupied. The frame is frozen before coding, and replacements are allowed only for a missing record.
- Two reviewers code the first twelve cases independently for record completeness, access, scope, and closeout. Disagreements are resolved by the operations lead, who writes the rule used for the case. Reliability is reported as the share of matching fields. Limitations are stated before findings: the sample is local, the review does not judge workmanship, and a complete record is not proof that the repair was correct.
- A final field records whether the contractor's invoice reached the property before the next guest arrived. An invoice that arrives weeks later cannot be matched to the visit record while the details are fresh. The reviewer records the receipt time and the payment status. This separates an access or workmanship problem from a billing delay.
Findings
- Most visits in the reviewed set are scheduled while the unit is vacant, which makes access simple but leaves no guest to observe the work. The record becomes the only account of what happened. Visits with a written scope and a before photo are easier to reconstruct than visits described only in a message thread. The difference shows up months later when an owner asks about a charge.
- Entry and exit times are the fields most often missing. A contractor may arrive on time and leave without telling the coordinator. The property then cannot tell whether the cleaner had enough window or whether the guest was present. A simple check-in and check-out message from the contractor closes the gap.
- Smart locks are used well when the code is temporary and poorly when the stay code is shared. A temporary code can be limited to the visit and expired afterward. A stay code gives the contractor access for the rest of the booking. The reviewed exceptions are almost always a convenience decision made at the door.
- Before-and-after photos are uncommon but valuable. A photo taken before the work shows the condition the property handed over. The after photo shows what changed and gives the cleaner a target. Properties that require the pair resolve damage questions faster than properties that rely on memory.
- Scope creep is usually small and friendly. A plumber asked to fix a leak may also tighten a loose handle or move a shelf. The extra work is rarely the problem; the missing record is. A note that names the additional task and the person who approved it keeps the invoice explainable.
- Invoices that match the work order are approved faster. A mismatch, even a small one, sends the invoice back for a question and delays payment. The reviewed cases with a parts list and a diagnosis clear without a call. The field does not need to be detailed, but it needs to exist.
- Guest notice is inconsistent. Guests who are home sometimes learn about a visit from a knock at the door. Guests who are away sometimes return to a unit that was entered without a message. A short notice before entry and a short summary after the visit solve both cases.
- Repeat visits are a useful signal. A second trip for the same leak may mean the first repair was incomplete or that the diagnosis was wrong. A second trip for a different issue is normal wear. The reviewer separates the two before drawing a conclusion about the contractor.
- Closeout tests are the least common field and the most useful. A lock that is not tested may fail for the next guest; a faucet that is not run may leak under the sink. The test takes less than a minute and creates a record that the work was verified. Properties with a test field close more visits without a follow-up call.
- A named signoff changes accountability. When the record shows who approved the work, the next coordinator knows whom to ask. When the record is a group thread, no one owns the answer. The reviewed records with a named signoff are more likely to include the invoice and the test.
- The strongest predictor of a complete visit record is a single coordinator who opens the record before dispatch. Visits scheduled in a hurry often start with a message and end with an invoice, with no scope or test in between. The local sample cannot establish causation, so the result is a hypothesis for the next window. A second observation after a process change is required before the rule is treated as settled.
- A final check compares the invoice date with the next arrival. In several cases the work was complete and the record was closed, but the invoice arrived after the owner had already approved a different total. The reviewer records that as a billing gap rather than a visit failure. A same-day ticket request would close it.
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
- Occupational Safety and Health AdministrationU.S. Department of LaborChecked 2026-11-18
- Worker rights and protectionsOccupational Safety and Health AdministrationChecked 2026-11-18
- Indoor air qualityU.S. Environmental Protection AgencyChecked 2026-11-18
- Product safetyU.S. Consumer Product Safety CommissionChecked 2026-11-18
- Home fire preventionU.S. Fire AdministrationChecked 2026-11-18
- Business emergency preparednessReady.govChecked 2026-11-18
- Emergency planningReady.govChecked 2026-11-18
- Cybersecurity FrameworkNational Institute of Standards and TechnologyChecked 2026-11-18
- Resources and toolsCybersecurity and Infrastructure Security AgencyChecked 2026-11-18
- Wage and hour guidanceU.S. Department of LaborChecked 2026-11-18
- Recordkeeping guidanceInternal Revenue ServiceChecked 2026-11-18
- Manage your financesU.S. Small Business AdministrationChecked 2026-11-18