Key takeaways
- Measure waiting time separately from work time.
- Give every decision a requested-by date.
- Escalate missing context before urgency becomes noise.
Source record
10 cited sources
Last verified
2026-08-12
Table of Contents
Decision latency is the time between a clearly stated request and an owner’s usable decision. It is different from vendor response time or repair duration. Measuring it helps a portfolio team find stalled handoffs without assigning blame from incomplete records.
Measurement design
Record created, clarified, sent, acknowledged, and decided timestamps. Add the property, issue, requested decision, evidence links, and next operational consequence. The NIST documentation guidance and Census data quality guidance support explicit definitions and source dates.
Use FTC privacy and security guidance, CISA small-business security, IRS recordkeeping guidance, HUD housing quality standards, and the NIST Privacy Framework to keep requests appropriately scoped and documented.
Interpretation
Sort the queue by age, consequence, and missing evidence. A long wait with a complete request is different from a long wait caused by an unclear scope. The owner report reliability research and approval queue routine provide useful internal comparisons. Do not turn a latency measure into a legal, tax, or personnel conclusion.
Sources and verification notes
Reference the BLS CPI data system, Census housing data, Census housing topic page, and NIST privacy engineering when deciding what context belongs in a record. Recheck sensitive data handling with qualified counsel.