A Property Manual That Survives Staff Changes

A manual isn't a document you write once. It's the shortest route between a new cleaner and a flat that looks the same as it did last week.

Last updated: October 4, 2026

Most property manuals fail for the same reason: they were written for the person who already knew the job. A manual that survives staff changes is written for someone who's never seen the property, holds only the parts of the job that stay the same, and gets updated a section at a time. If that sounds like less work than the manual you're picturing, that's the point.

Key Takeaways

• A manual is for the stable parts of the job. Access, order, standard and contacts. Anything that changes weekly belongs somewhere else.
• Write one action per step. A stranger should be able to follow it without stopping to work out what you meant.
• Update by section, not from scratch. Stamp each section with a date and change only the part that moved.
• Test it on someone new. The first day of a new clean reveals the gaps faster than any review will.
• Say who can see what. A manual that names the areas each role can reach saves a conversation every time someone joins.

What belongs in the manual and what doesn't

The first decision isn't how to write the manual. It's what to leave out of it.

A manual should hold the things that stay the same between one stay and the next. Where the keys and codes live. The order the work happens in. What a finished room looks like. Where the linen is stored and where the used linen goes. Who to call when the boiler won't fire, and which problems wait until the morning. Seasonal quirks count too: the window that sticks in winter, the tap that needs two turns, the neighbour who complains about noise after ten.

What it shouldn't hold is anything that changes often. Rates, current guest names and the details of this week's arrivals change constantly, and putting them in a manual means rewriting the manual constantly. Those belong in the system that already holds them, and the manual should point there rather than copy them.

The distinction is easier to hold if you think of it as instructions against data. Instructions are stable and belong in the manual. Data moves and belongs in the calendar, the inbox or the booking record. A manual that mixes the two goes stale on its first busy week, and a stale manual is worse than none, because people stop trusting it.

There's a third category worth naming early: anything you'd only ever explain in person. If a job depends on a knack, a shortcut or a judgement call, that's a sign the step needs writing out properly rather than leaving it to whoever's watching.

Writing steps a stranger can follow

Good manual steps share a shape, and it takes less effort to write them that way from the start.

Make each step one action. Not "prepare the bedroom", but the four or five moves inside it. A step that hides three actions inside one line is the step a new person gets wrong, because it assumes the sequence you have in your head.

Start each step with a verb and name the object. "Return the key to the lockbox by the front door" leaves nothing to guess at. "Put the key back" leaves the reader wondering which key, and a manual that leaves questions unanswered is one that gets replaced by a phone call.

Put the steps in the order the work happens, not in the order you remembered to write them down. A manual read start to finish should walk someone through a turnover in sequence, so they never have to work backwards.

Say what finished looks like. A step that ends with a state, rather than an activity, tells the reader when to move on. "The bed is made with the flat sheet tucked and the spare blanket folded on the chair" is a finish line. "Make the bed" isn't.

Cut the soft qualifiers. "As needed", "if necessary" and "where appropriate" all mean the writer knew the answer and didn't write it down. Replace each with the condition that decides it, so the reader applies your rule rather than their own.

Where a standard is visual, use a photo. Two or three images of a finished room carry more than a paragraph, and they survive translation better than any description.

Then decide who reads which part. Not everyone who works on a property needs the same pages. A cleaner needs the turnover steps and the supplies; they may not need the finance side of the arrangement. LOCALSBNB lets you scope access by area — orders, finance, availability and rates — so each person reaches the parts their role needs rather than the whole account. Credentials stay on your own device rather than in the manual.

One more writing habit is worth building. Write for the reader's first day, not their hundredth. The test isn't whether the manual makes sense to you; it's whether it makes sense to someone standing in the property with nothing but the page.

Keeping it current without a monthly rewrite

A manual dies in one of two ways: nobody updates it, or updating it becomes such a chore that it stops happening. Both are avoidable if you stop treating it as one document.

Split it into sections and date each one. The access section, the turnover steps, the supplies list and the contacts each carry their own last-changed date. When one thing moves, you change one section, which turns an afternoon's work into a two-minute edit.

Keep a short change log at the front. One line per change, with the date and what moved, so anyone can see what's recent. A change log is also the fastest way to spot a section that hasn't been touched in a long time, which is usually the section that's quietly wrong.

Update on triggers rather than on a schedule. A calendar reminder to review the manual tends to get postponed; an event doesn't. Change the manual the moment something changes: a lock is replaced, a supplier switches, a guest flags a problem the steps didn't cover, or the property starts running on a different language, time zone or currency.

That last one matters more than it sounds. Language, time zone and currency settings follow the property rather than the person reading the manual, and LOCALSBNB supports six languages with English as the fallback where one is missing. When settings like these change, the manual should say so, so the next person doesn't discover it halfway through a booking.

Then, once a season, read the whole thing end to end and delete anything that's no longer true. A manual that only grows becomes a document nobody finishes. Cutting the dead steps is what keeps the live ones credible.

Testing it on someone new

The only honest test of a manual is a person who hasn't used it. Everything else is guesswork.

Hand it over and watch where they pause. A pause is a gap. It might be a step out of order, a term they don't recognise, or a photo that doesn't match the room. Note every pause, then fix the manual rather than the person. If two new people pause in the same place, that step is wrong rather than the reader.

Ask them to do the job without calling you. The aim isn't to prove they can; it's to find out whether the written steps hold up in a real turnover, on a normal day, with nobody standing beside them. Whatever they have to ask you is a line that belongs in the manual.

Test the access side at the same time. Can the new person reach the pages they need for their role, and no more? Does the manual point them to the right system for the details it deliberately leaves out, such as rates or a booking's specifics? localsbnb.com is where the scoped view and the property's settings sit, so the manual can point to it instead of copying from it.

Finally, date the test instead of the document. Knowing when the manual was last used by someone new tells you more about its currency than any revision date does. A manual that survived a new person last week is current in a way a manual edited last month isn't.

FAQ

How long should a property manual be?

Short enough that a new person reads it on their first day. Length isn't the measure; coverage of the stable steps is. If a section runs long, it's usually holding something that belongs in a system instead, and moving that out will shorten it without losing anything that matters.

Should the manual include guest names or this week's arrivals?

No. Those change with every booking, and a manual that holds them has to be rewritten constantly. Keep the manual to the steps that stay the same and let it point to the calendar, the inbox and the booking record for anything that moves.

What if the manual exposes too much to a new cleaner?

That's what scoped access is for. Decide which areas each role needs — orders, finance, availability or rates — and give them that view rather than the whole account. A new cleaner usually needs the turnover steps and the supplies, not the money.

A manual earns its keep on the day someone new has to do the job alone. Write the steps for a stranger, keep only what stays the same, update by section, and test it on the next person who joins. localsbnb.com keeps the property's settings and the scoped views in one place, so the manual can point there rather than carry what changes. With the person who wrote it away, the manual is what's left doing the explaining.

---

This article is general guidance for hosts rather than legal, tax or insurance advice. Local rules, staffing arrangements and platform terms differ by place and change over time; check your own setup and the current terms of each platform you use.