Key takeaways
- Define response and completion separately.
- Preserve the original request time.
- Compare comparable work categories.
Source record
10 cited sources
Last verified
2026-08-12
Table of Contents
Vendor responsiveness cannot be represented by one average. Acknowledge time, arrival time, scope confirmation, completion time, and invoice submission answer different questions and should remain separate.
Evidence fields
Capture request channel, request timestamp, acknowledgment, promised next action, arrival, completion, follow-up, and exception reason. Use OSHA workplace standards, EPA indoor air quality, CPSC safety guidance, and NFPA research to flag safety-sensitive categories for appropriate review.
For vendor records, preserve the IRS recordkeeping guidance, NIST documentation principles, FTC business privacy guidance, and CISA incident reporting guidance where relevant. These are controls for evidence, not a substitute for contracts or local requirements.
Benchmarking
Compare emergency, habitability-sensitive, routine, and preventive work separately. The maintenance response-time research and vendor license record research show why scope and credential context belong beside the timing fields. Keep unresolved exceptions visible rather than hiding them inside an average.
Sources and verification notes
Use HUD housing quality standards, DOE Energy Saver, and FEMA preparedness guidance to shape category questions. Reconfirm local licensing, insurance, and emergency requirements before assigning work.