Key takeaways
- Forecast and observed dates answer different questions.
- Every revision needs a source and approval state.
- Readiness depends on a defined acceptance gate.
Source record
4 cited sources
Last verified
2026-09-15
Table of Contents
Vacancy teams use a ready date for several purposes, including planning, listing, and reporting. Those uses can conflict when one field is expected to carry a forecast, a commitment, and an observed result. A reliability model starts by separating those date states.
Methodology and evidence
We reviewed four public sources on project schedule control, internal control documentation, housing inspection standards, and data quality. The review was completed on September 15, 2026. We defined three states: forecast ready date, approved public date, and observed acceptance date. The model was tested against hypothetical scope changes, failed inspections, vendor delays, early completion, and stale listing copy.
This is a qualitative operations study. It uses no property, resident, vendor, listing, or work-order data. It does not estimate average turnover duration, establish habitability, or determine when a unit may legally be offered. Those decisions depend on local requirements and authorized review.
Three dates, three claims
A forecast is a planning estimate based on known dependencies. It should retain its assumptions and calculation date. An approved public date is the date authorized for listing or applicant communication. It may include a buffer or policy decision that does not appear in the raw work plan. The observed date records when the defined acceptance gate was actually passed.
The GAO Schedule Assessment Guide addresses schedule quality in government programs. It is not a property turnover standard, but its treatment of logic, updates, and risk supports preserving assumptions behind a forecast. HUD inspection standards provide housing-program context; they do not replace a property's applicable readiness procedure.
Change evidence
Every change should keep the prior date, new date, source, reason, requesting role, and approval. A vendor message can support an updated estimate. It cannot by itself establish that all turnover work has passed inspection. An acceptance record can support the observed date when it identifies the checklist, reviewer, and outcome.
Comparing observed dates with their original forecasts may help review planning performance. The comparison must use stable definitions and the correct forecast vintage. Selecting the last forecast before completion will usually make performance look better than using the first approved forecast.
Limitations
Properties use different readiness gates and scheduling systems. Work scope can change after hidden conditions are found. Inspection and permit requirements vary. Listing dates may reflect commercial decisions rather than construction forecasts. The model cannot produce a universal benchmark or attribute delay to a vendor, resident, or employee.
Conclusion
Ready-date reliability improves when the portfolio keeps forecast, approved public, and observed acceptance dates separate. Each revision needs a source and authorization record. That structure lets teams review planning and communication without converting an estimate into a claim of completed or compliant work.
Published September 15, 2026.
Sources and verification dates
- U.S. Government Accountability Office, Schedule Assessment Guide, checked September 15, 2026.
- U.S. Government Accountability Office, Green Book, checked September 15, 2026.
- HUD, Inspection Standards, checked September 15, 2026.
- NIST, Information Quality Standards, checked September 15, 2026.