Control Vacancy Ready-Date Changes with a Simple Log

A ready date affects listing copy, showing plans, vendor schedules, and owner expectations. When that date changes in one place but not the others, the team creates avoidable rework. A small change log gives every revision a source and a follow-up path.

Pair this log with the daily vacancy exception review and the turnover evidence index.

Quick Overview

Record the unit, previous date, proposed date, reason, evidence source, requesting role, and approval state. Do not overwrite the earlier value. The sequence matters when a team later asks why a listing promised access before cleaning or inspection work was accepted.

Common Mistakes

A vendor estimate may support a planning date but not a completed-work claim. An inspection note may identify another dependency. Label each source for what it proves and what it does not. If the evidence conflicts, keep the date provisional and send the conflict to the person authorized to decide.

Common Questions Answered

After approval, identify every place that uses the ready date: the listing, showing calendar, turnover board, owner update, and internal forecast. Assign each update rather than assuming one system will synchronize the rest. Record completion time so stale copies are easy to find.

Ready to review late changes

Repeated revisions deserve a cause review, but the log alone cannot prove poor vendor performance or bad planning. It can show the sequence and missing dependencies. Use that evidence to improve the checklist without turning an administrative record into a performance verdict.

Published September 15, 2026.

See the GAO Schedule Assessment Guide for general schedule-quality context.