TheCleanBNB field note · 03

Turnover clean, deep clean or maintenance visit?

Define the scope before expectations blur.

Editorial operating system for an Athens rental

The short answer

The right answer is a clear system, not a general promise.

Do not judge the decision from one visit or one headline price. Define what normal turnover means, when periodic deep cleaning is needed and how maintenance reporting works. Reliability becomes visible when the result, communication and response to exceptions repeat.

Layout, occupancy, access, timing and condition change the practical requirement. A written system reduces assumptions, protects the host and gives the service partner a clear operating frame.

Normal turnover

Reset the property after an ordinary stay.

A normal turnover follows the property brief room by room: used linen is removed, agreed beds are made, bathroom and kitchen hygiene are restored, accessible surfaces and floors are cleaned, bins are handled and the agreed essentials are checked. It ends with an arrival-view inspection, not when the last cleaning task is finished.

The baseline assumes a defined layout, occupancy and condition. Heavy grease, smoke, excessive waste, biological contamination, neglected grout or months of buildup are not simply “more of the same.” They change the work, time and sometimes the equipment required.

Deep-clean triggers

Schedule accumulated work before it becomes an emergency.

Deep cleaning addresses periodic buildup: detailed limescale treatment, grout recovery, internal appliances, behind movable furniture, high dust, neglected edges or a first reset before a new operating standard begins. The trigger can be a calendar interval, visible condition or a seasonal reopening.

Keep a property-specific deep-clean register. When the same item appears repeatedly in turnover notes, decide whether it should move into the baseline or enter a planned rotation. Adding it silently to every visit hides the true schedule and cost.

Editorial inspection of the preparation stages
Clear operations connect stages, ownership and final result.

Maintenance visit

Cleaning can reveal a defect; it cannot repair every defect.

A leaking tap, loose handle, failed bulb, damaged seal, blocked drain or unstable chair should be photographed and reported with its location and urgency. The cleaner may be the first person to see the problem, but identifying it is different from authorising technical work.

Define who receives the report, who approves a repair and whether a qualified trade is required. This prevents improvised fixes, protects the property and keeps responsibility clear.

Cadence

Use a layered calendar.

Place the repeatable turnover on every departure. Add rotating detail tasks at sensible intervals and plan deeper work around seasonality, occupancy and actual condition. Maintenance checks can sit alongside this calendar without being disguised as cleaning minutes.

A layered plan is easier to price and easier to audit. Hosts can see what was done today, what is due next and what needs a separate decision.

Approval and price

Agree the boundary before extra work begins.

The property brief should name included tasks, scheduled extras and the evidence needed for condition-specific work. If the departure condition requires a different scope, send the host a concise report and obtain approval whenever timing permits.

This is not bureaucracy. It prevents surprise invoices and protects the arrival deadline by directing attention to the work that matters most.

Editorial exception identified before guest arrival
Exceptions should become visible before arrival.

Decision test

Ask which outcome the property needs now.

If the home was maintained and has completed an ordinary stay, choose turnover. If surfaces or appliances show accumulated buildup, schedule deep cleaning. If something is broken, unsafe or no longer functioning, route it to maintenance. More than one category can apply to the same visit.

The useful question is not “Can the cleaner do everything?” It is “Which scope, time, skill and approval produce a defensible guest-ready handover?”

Thirty-day calibration

Test the system before treating it as finished.

Use the first month as a controlled calibration of the scope separation. For every turnover, record guest count, length of stay, departure condition, working time, shortages and anything that required a decision. This does not need complicated software. One stable form with the same categories is enough to reveal what repeats and what was genuinely unusual.

At the end of the period, separate three kinds of information. First, predictable work that belongs in the normal scope. Second, periodic work that needs scheduling. Third, true exceptions that require approval. That separation prevents memory, assumptions and last-minute messages from quietly becoming the operating method.

Useful measurement

Measure facts that can change a decision.

Track whether handover was on time, whether the agreed result was complete, whether stock was missing, whether work had to be repeated and whether a problem was reported early enough. A large number of photographs or messages is not proof of quality by itself. Useful evidence shows the condition, its location and the next action.

Look for patterns rather than turning every incident into a new permanent rule. If the same point fails three times, adjust the brief, stock level, sequence or available time. If an exception does not repeat, keep it as a note without making the baseline unnecessarily heavy. Review the standard turnover scope, deep-cleaning extras, the working process when the evidence shows that the property needs a different scope.

Final approval

Make sure another person reads the same promise.

Ask someone who did not write the plan to read it and describe what they would do. If interpretations differ, the wording still has gaps. Confirm that timing is realistic, materials are available, responsibilities have named owners and the reporting path is clear.

Quality does not come from adding more words. It comes from removing uncertainty between the promise, the work and the final handover. Revisit the document when layout, capacity, access, equipment or the hosting model changes.

Implementation framework

Turn the decision into a written operating system.

A sound decision is not useful if it lives only in the host’s head. Record what applies to this property, who owns each action, when the check happens and what changes when reality differs from the normal setup. The plan should be short enough to use and specific enough that two people understand the same promise.

Start with the usual stay, then test the exceptions: maximum occupancy, a sofa bed, late departure, a stain, low stock, a defect or a change in access. The scope separation must still work in those cases without pushing hidden tasks into the next turnover.

Eight details to put in writing

  1. Baseline. Define the normal property setup before pricing or scheduling it.
  2. Variables. Record layout, guest capacity, linen, access, frequency and condition.
  3. Ownership. Who supplies, approves or replaces what is required.
  4. Timing. When work starts and what window is realistic.
  5. Evidence. Which points are confirmed at final handover.
  6. Exception. What is reported instead of quietly hidden.
  7. Escalation. Who decides when extra work or purchasing is needed.
  8. Review. When the plan is updated using real operating data.

Review the plan during the first turnovers and whenever layout, capacity or hosting style changes. Consistency does not mean every stay is identical. It means differences are noticed early and handled through an agreed response rather than improvisation.

For Athens hosts

Build the decision around your actual property.

Share the layout, occupancy, frequency and current operating setup. We will separate the normal turnover from linen, restocking and condition-specific work.

Request a property-specific cleaning plan →

Frequently asked questions

Short answers for real decisions.

What is the first step?

Record the normal setup and the guest-ready result expected.

Is a generic checklist enough?

No. It must reflect the property, occupancy and access.

Are photos required?

Useful for presentation and exceptions, but not a substitute for final inspection.

When should the plan change?

When layout, capacity, stock, access or recurring problems change.

How should partners be compared?

Compare scope, time, inspection, reporting, continuity and response—not only price.

Sources and further reading

Platform features and policies change. Always check the current settings in your hosting account.

Get my cleaning plan