Rental Unit Turnover Checklist And Make-Ready Tracking Template: Fields, Statuses, and Rules

The most useful rental unit turnover checklist and make-ready tracking template is a small operating record. It should answer what is happening, who owns it, what evidence exists, and when the next decision occurs. This structure works in a spreadsheet, database, or focused application.

Recommended record fields

| Field | Why it exists | Update point | |---|---|---| | Property and unit | Prevents the record from depending on memory or an inbox search | Complete the move-out inspection | | Target ready date | Prevents the record from depending on memory or an inbox search | Define repair and cleaning scope | | Inspection findings | Prevents the record from depending on memory or an inbox search | Schedule dependent vendors | | Task dependency | Prevents the record from depending on memory or an inbox search | Capture readiness evidence | | Vendor and appointment | Prevents the record from depending on memory or an inbox search | Approve listing or move-in readiness | | Estimate or approval | Prevents the record from depending on memory or an inbox search | Complete the move-out inspection | | Completion photo | Prevents the record from depending on memory or an inbox search | Define repair and cleaning scope | | Blocker | Prevents the record from depending on memory or an inbox search | Schedule dependent vendors | | Final approver | Prevents the record from depending on memory or an inbox search | Capture readiness evidence |

Suggested statuses

Use workflow statuses that describe reality: Complete The Move Out Inspection → Define Repair And Cleaning Scope → Schedule Dependent Vendors → Capture Readiness Evidence → Approve Listing Or Move In Readiness. Add Waiting only when you also capture a waiting reason and review date. Add Closed—Not Completed when an item legitimately ends without the desired outcome.

Follow-up rules

• When a predecessor task slips past its dependent appointment, assign a next action and review date.
• When a finding changes the approved repair scope, assign a next action and review date.
• When the target ready date is at risk, assign a next action and review date.

Avoid reminders with no stop condition. A rule should say when it starts, who receives it, what counts as a response, and when a person should take over.

Example records

• Floor repair pushes cleaning and photography into the same afternoon
• An inspection reveals an appliance issue requiring owner approval
• The unit looks ready in photos but a smoke-alarm check is undocumented

For each example, write the current status, next action, owner, and supporting evidence. This makes the template testable with real work rather than idealized sample data.

Quality-control rules

• Readiness blockers are distinct from cosmetic preferences
• Dependent work cannot be marked ready out of sequence
• Every task has room-level evidence
• One named person approves the final ready state

Before adding automation, run the template manually for a week. Remove ambiguous fields and confirm that two different users classify the same situation the same way. Consistency matters more than having a long form.

Next step

Explore the Unit Turnover Runbook workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Maintenance Triage Board.