Rental Turnover Scope Change Register
A controlled register for documenting turnover scope changes, authority, cost signals, dependencies, and acceptance.
By PortfolioRental Editorial Team · · Updated 2026-09-02
Table of Contents
Turnover work changes quickly when new conditions appear. A scope change register protects the original baseline and records who authorized a revision before schedules and invoices drift apart.
Quick Overview
For each proposed change, capture the observed condition, evidence, original scope reference, requested revision, cost and schedule signals, dependencies, decision owner, authorization, and completion acceptance.
Common Mistakes
Do not overwrite the original work order, let field discussion become approval, or treat an estimate as an invoice. Avoid assigning cause from a photo alone. Safety and technical questions belong with qualified roles.
Preserve the baseline
Number each change and link it to the approved starting scope. Record the request time and source evidence before evaluation. If the condition cannot be verified remotely, mark the verification step rather than inventing certainty.
Control decision and completion
Separate requested, under review, approved, rejected, implemented, and accepted states. Only the named authority changes the decision state. Completion requires evidence matched to the approved revision, not merely a vendor message.
Common Questions Answered
Can work begin before approval?
Follow the approved emergency and authorization rules. The register should show the authority and reason for any exception.
Does acceptance confirm invoice accuracy?
No. Work acceptance and invoice review are related but distinct controls.
Ready to use this routine
Tie changes to the turnover material delivery tracker and turnover readiness check. HUD publishes housing quality resources: review HUD materials.
Published September 2, 2026. Test the register on one active turnover and verify that no approval is implied by a status note.