Vendor Operations research
Measuring Vendor Arrival Windows Without Overclaiming
A research brief on measuring vendor arrival windows in property management, separating the scheduled window, the actual arrival, and the cause of a delay.
| 3 sources sources
Table of contents
A vendor promises a two-hour arrival window and shows up four hours later. The resident waited, the manager fielded a call, and the work order slipped. The property team remembers the delay but cannot say whether the vendor was late, the window was unrealistic, or the request changed after it was scheduled. Vendor arrival windows are a useful operating measure because they connect resident experience to dispatch discipline. They are also easy to misread. A vendor who arrives late may have been sent to the wrong address, blocked by a gate code, or asked to handle an emergency first.
Research question
How can a property team measure vendor arrival windows so that the measure shows the schedule, the actual arrival, and the cause of variation without turning a single delay into a claim about vendor quality? The question matters for maintenance coordination, resident communication, and contract reviews. A second question concerns fairness. A measure that ignores the scheduled window or the reason for a change will punish the wrong party. The team needs a small record that separates the promise, the arrival, and the explanation.
Methodology
This brief reviews public guidance on records, internal control, and privacy, and maps it to a private vendor dispatch process. The sources support documentation and review discipline. They do not prescribe an arrival target, a vendor ranking, or a resident satisfaction score. We tested the model against four common cases: a vendor who arrived inside the window, a vendor delayed by a gate code, a resident who rescheduled, and a work order that was upgraded to an emergency. The proposed stages are an operating design rather than a benchmark.
Define the window before dispatch
Record the window offered to the resident, including the date, the start time, and the end time. Distinguish the vendor's availability from the window the resident accepted, because those are not always the same. A vendor who is available all morning may still be scheduled for a narrow slot. State the time zone and whether the window is a firm commitment or an estimate. A firm window supports a resident expectation, while an estimate supports planning. Mixing the two produces disputes that the record cannot settle.
Record the actual arrival separately
Record when the vendor arrived on site, not when the vendor called or when the work began. The arrival time is the moment the vendor reached the property or the unit. If the vendor checked in at a gate or a front desk, use the check-in time and note it. Keep the scheduled window and the actual arrival as separate fields. A single "arrived late" flag hides whether the delay was minutes or hours. The difference matters when the team reviews a pattern or discusses the contract.
Capture the cause in a short list
Use a small set of causes rather than free text only. Common causes include traffic, a previous job running long, an access problem, a missing part, a resident reschedule, and a dispatch error. Add a note field for the detail that does not fit the list. The cause should be recorded by the person who has the information, not guessed later. If the cause is unknown, record it as unknown rather than assigning blame. An honest unknown is more useful than a confident guess.
Separate the resident change from the vendor delay
A resident who reschedules is not a vendor failure, and a vendor who arrives inside a revised window is not late. Record the revision as its own event with a time and an owner. The original window stays in the record so the change is visible. The same principle applies to an upgraded work order. If the job became an emergency and the vendor was redirected, record the upgrade and the authority behind it. The arrival measure should reflect the schedule that was actually in force.
Report the distribution, not a single score
Report the number of jobs, the share inside the window, the share outside, and the median delay. Add the cause breakdown so the reader can see whether delays cluster around access or parts. A single percentage without the cause is easy to quote and hard to act on. Break the report down by property and by vendor only when the sample is large enough to be meaningful. A vendor with three jobs and one delay should not be ranked against a vendor with thirty. Small samples are a check, not a verdict.
Use the measure in the operations review
Bring the window data to the maintenance review with the open work orders and the resident complaints. Ask which delays were preventable and which were outside the team's control. The conversation should produce one or two changes, such as a better gate-code step or a clearer parts check. Record the change and the date. A measure that never changes a process is a report, not a control. The review should also confirm that the vendor received the access information before the window started.
Protect resident and vendor information
Arrival records can include addresses, phone numbers, and access details. Keep them in the approved system and limit access to the people who coordinate the work. Do not share a vendor's individual performance in a broad channel. Set a retention period with the property's records policy. An arrival log kept indefinitely creates risk without adding insight. The record should be long enough to support a contract review and short enough to protect the people involved.
Keep the sample honest
A review of one month and one portfolio is a check, not a benchmark. Say so in the report. Include the count and the job types so the reader can judge the evidence. A small sample can show a pattern but cannot support a percentage for every property. Repeat the review before a conclusion is treated as stable, and state the limits in the same document as the result.
Keep the window visible to the resident
A resident who knows the window and the vendor name is less likely to call the office for an update. Send a short confirmation with the window, the vendor, and the work scope before the visit. If the window changes, send the revised time and the reason rather than letting the resident discover it. The confirmation also gives the team a timestamp that can be compared with the arrival record. The update should name the person to contact if the vendor does not arrive within the window. That step turns a missed visit into a follow-up rather than a surprise.
Bounded pilot
Review one month of vendor arrivals. Record the window, the arrival, the cause, and any revision. Report the distribution and the open causes. Ask a reviewer who did not dispatch the jobs to explain where the delays sit. If they cannot separate a resident change from a vendor delay, the fields need work.
Limitations
This brief describes an operating measurement model. It does not establish an arrival benchmark, a legal standard, or a measure of vendor quality. The cited sources support general records and control principles. Results depend on the accuracy of the timestamps and the honesty of the cause record.
Sources
- The Green Book; U.S. Government Accountability Office; checked November 11, 2026.
- Records Management; U.S. National Archives and Records Administration; checked November 11, 2026.
- Privacy Framework; National Institute of Standards and Technology; checked November 11, 2026.
Conclusion
Vendor arrival windows are useful when the scheduled window, the actual arrival, and the cause are recorded separately. The measure cannot prove that a vendor is unreliable. It can show where the dispatch process waits and which access or scheduling change would help. For related workflows, see the owner approval aging brief and the property management VA services overview.