Direct answer

A strong rental turnover scope should tell every person involved what condition exists, what outcome is required, which tasks are included, which tasks require specialist handling, which materials or standards apply, what must be documented, and what counts as complete.

The simplest useful structure is:

Property baseline → room-by-room scope → trade/specialist scope → portfolio standards → allowances/approvals → sequence/dependencies → evidence → closeout.

The template below is designed to create a common baseline before work is assigned or priced.

Why a turnover needs a scope at all

Without a written scope, “make it rent-ready” can mean five different things to five different vendors.

One person may include:

• patching;
• full repainting;
• floor cleaning;
• hardware replacement;
• final cleaning.

Another may hear only:

• clean;
• touch up paint;
• fix obvious damage.

Both can believe they completed the request.

A scope converts a vague outcome into a shared operational definition.

Turnover scope template

1. Property identification

Record:

• property address;
• unit number if applicable;
• property type;
• vacancy/possession date;
• target ready date;
• access instructions;
• owner or manager contact path;
• emergency escalation path;
• known occupancy or leasing deadline;
• portfolio standard version being used.

Do not put sensitive access codes in a public-facing template or broadly shared document. Store them in the appropriate controlled system.

2. Existing-condition baseline

Before writing work items, summarize the current condition.

Include:

• date of condition capture;
• who captured it;
• photo/video reference;
• prior inspection or move-out documentation available;
• known tenant damage;
• known deferred maintenance;
• open service calls;
• known water, electrical, HVAC, structural, pest, roof, or other specialist concerns;
• missing appliances, remotes, keys, fixtures, or owner property;
• trash-out status.

This baseline helps distinguish prior condition from damage created during turnover work.

3. Define the ready standard

State the property-level finish line.

Example:

Property is to be delivered clean, secure, functional for intended ordinary use, visually consistent with the portfolio finish standard, free of open turnover punch items, and documented with final-condition evidence. Specialist or regulated work must be separately completed or explicitly carried as an open exception.

Tailor that statement to the portfolio.

4. Room-by-room scope

For each room, use a repeatable block.

Room: ____________________

Existing condition

• walls:
• ceiling:
• flooring:
• trim/base:
• doors/hardware:
• windows/coverings:
• lighting/fixtures:
• outlets/switches observed:
• cabinets/storage:
• plumbing fixtures observed:
• appliance/equipment present:
• cleaning condition:
• other:

Required work

• demolition/removal:
• repair/preparation:
• paint/finish:
• flooring:
• carpentry/hardware:
• fixture work:
• cleaning:
• specialist/trade follow-up:
• final evidence required:

Completion standard

Describe what the room should look or function like when done.

5. Whole-property tasks

Keep building-wide items separate from room work.

Possible sections:

Trash-out and hauling

• tenant-left material;
• construction debris;
• exterior debris;
• appliance or furniture disposal;
• documented disposal restrictions if applicable.

Cleaning

• construction clean;
• final clean;
• appliances;
• windows;
• cabinets;
• bathrooms;
• floors;
• exterior entry.

Paint

• portfolio color;
• sheen by surface;
• full repaint versus touch-up standard;
• walls included;
• ceilings included;
• doors/trim included;
• cabinets included or excluded.

Flooring

• material standard;
• repair versus replacement area;
• transitions;
• base/shoe scope;
• disposal;
• moisture/subfloor escalation rule.

Doors and hardware

• lock/rekey policy;
• interior hardware standard;
• damaged doors;
• stops;
• closet hardware;
• blinds/window coverings.

Exterior/site

• lawn/landscape reset;
• entry condition;
• fence/gate items;
• exterior lighting tasks;
• pressure washing if included;
• visible exterior repair items.

6. Licensed-trade and specialist work

Do not bury regulated or diagnostic work inside a general maintenance line.

Create explicit sections for conditions involving, as applicable:

• plumbing;
• electrical;
• HVAC/mechanical;
• gas;
• roofing;
• structural concerns;
• water intrusion;
• mold or environmental concerns;
• pest/termite conditions;
• fire/life-safety systems;
• permit or inspection requirements.

For each, record:

• observed condition;
• who needs to evaluate it;
• whether the work is part of the turnover schedule or a separate project;
• impact on ready date;
• evidence/closeout required.

7. Materials and portfolio standards

For recurring finish items, define the exact standard where practical.

Examples:

• wall paint manufacturer/color/sheen;
• trim paint;
• LVP line/color;
• carpet standard;
• cabinet hardware;
• door hardware;
• faucets;
• light fixtures;
• blinds;
• smoke/CO alarm standard where applicable;
• thermostat standard;
• appliance finish or model family;
• plumbing trim finish.

If the exact selection is not fixed, use an allowance or approved-equivalent rule rather than vague language such as “builder grade.”

8. Repair-versus-replace authority

The scope should state what a vendor may decide without owner approval.

Example structure:

Pre-approved repair

Vendor may complete the defined repair when condition falls within the documented scope and threshold.

Replacement requires approval

Replacement of a component not already included requires:

• condition evidence;
• repair option if reasonable;
• replacement option;
• price/schedule impact;
• owner authorization.

Immediate escalation

Conditions involving active damage, safety risk, regulated work, or major scope expansion should be escalated regardless of ordinary approval thresholds.

9. Allowances and unknowns

Turnovers often reveal conditions only after cleaning, removal, or access.

Use three separate buckets:

Known fixed scope

Work already understood and priced.

Allowance

Known category, uncertain final selection or quantity.

Unknown condition

Condition not yet sufficiently observable or diagnosed.

Do not hide unknown conditions inside a generic contingency line.

10. Sequence and dependencies

List the expected order where it matters.

Example:

1. access and trash-out;
2. condition verification;
3. specialist diagnostics/invasive work;
4. drywall/carpentry repair;
5. paint preparation and paint;
6. flooring;
7. fixtures/hardware;
8. final clean;
9. punch correction;
10. rent-ready verification.

Add property-specific dependencies rather than treating this sequence as universal.

11. Scheduling fields

For each work package, record:

• responsible party;
• earliest start;
• expected duration or completion date;
• predecessor/dependency;
• access requirement;
• materials required before start;
• inspection dependency;
• status;
• blocker.

This turns the scope into something that can actually be coordinated.

12. Evidence requirements

Specify evidence by work type instead of saying “send pictures.”

Examples:

• before condition;
• concealed condition before closure where relevant;
• material installed;
• completed repair;
• model/serial label;
• final room condition;
• final walkthrough;
• permit/inspection document where applicable;
• invoice/warranty document.

The evidence requirement should be proportional to the decision value.

13. Change handling

Any work outside the baseline scope should record:

• trigger;
• evidence;
• added/removed/changed scope;
• cost impact;
• schedule impact;
• approval;
• revised completion expectation.

Small turnover projects still benefit from disciplined change records because recurring “little extras” are where portfolio maintenance becomes hard to understand.

14. Closeout fields

At completion, record:

• original scope complete?;
• approved changes complete?;
• punch complete?;
• accepted exceptions;
• deferred items;
• specialist follow-up still open;
• final evidence captured;
• invoices reconciled;
• warranties/documents stored;
• access reset;
• ready verification completed;
• property history updated.

A condensed turnover-scope table

How this connects to OttoServ

The purpose of a managed turnover workflow is not to create more paperwork. It is to reduce ambiguity before dispatch, reduce handoff failures during execution, and create a reusable property record after completion.

The operating model is:

Describe the result → normalize the scope → coordinate the right work → surface exceptions → verify the ready condition → learn from the property history.

FAQ

Should one contractor receive the whole turnover scope?

Not necessarily. The master scope can be split into work packages while preserving one property-level baseline and finish line.

Is a turnover scope the same as a bid request?

It can support bidding, but its primary purpose is defining the work. A bid request may add commercial terms, response format, schedule, and selection requirements.

Should every turnover start from a blank template?

No. A portfolio should reuse a standard structure and populate only the property-specific condition and exceptions.

How detailed should the scope be?

Detailed enough that different people can understand the intended result and responsibility boundaries without relying on private verbal context.

What is the biggest mistake in a turnover scope?

Using vague phrases such as “make ready,” “fix as needed,” or “touch up everything” without defining the expected result or approval rules.