Coordinating a holiday let cleaner or co-host without duplicating your checklist

A common mistake when someone else starts doing your holiday let changeovers is handing them the checklist you wrote for yourself. It was written for someone who already knows the property, so it leaves out the context they need, and you end up checking their work against a second list in your head. This guide shows you how to rebuild it as one shared checklist that explains itself, with a few photo proof points, a place you both use, and a first changeover to test it.

Why handing over your list doesn't solve the problem

The obvious fix looks like it should work. You've got a checklist. Someone's helping now. Give them the checklist.

It rarely holds up, for a reason that's easy to miss because it's invisible to you specifically. A checklist you wrote for yourself is full of shorthand you don't notice as shorthand. "Check the usual spots." "Reset the boiler if needed." "Make sure everything looks right before you go." Every one of those phrases means something exact to you, built from months or years of doing the job yourself. To someone new, they mean almost nothing specific at all.

Here's what that shorthand looks like next to what a helper needs.

So the helper follows the list as best they can, filling every gap with their own judgement instead of yours, because the list didn't tell them what your judgement was. The job gets done. It might even get done well. But it wasn't done to your standard, because your standard was never written down, only implied, and implied information doesn't transfer.

That's the moment you start keeping your own checklist running quietly in parallel, because the written one isn't carrying the weight you need it to.

The gap between your list and someone else's understanding

The size of that gap depends entirely on how much of your list relies on things you know but never wrote down. Where the fuse box is, not just "check the fuse box." What "smelling fresh" specifically means to you, as opposed to just clean. Which stain or mark on a particular surface is a known cosmetic issue you've decided to live with, versus something new that needs reporting.

None of this is obvious to someone standing in the property for the first few times. It's obvious to you because you've been there, repeatedly, building context the list never had to spell out because you were the only one ever reading it.

This is the actual source of the duplication problem. It's not that the helper is careless, and it's not that you're being controlling by checking their work. It's that the document doing the coordinating was never complete enough to be the single source of truth, so a second, informal, undocumented standard, the one in your head, keeps running alongside it out of necessity.

Two kinds of checklist

There's a distinction worth making explicit here, because most checklists blend two different things without separating them, and that blending is exactly what causes the duplication.

There's a process checklist. This is the sequence of actions: strip the beds, run the dishwasher, restock the essentials, check the smoke alarm, and so on. It tells someone what to do and roughly in what order.

Then there's a standard checklist. This is the proof that the process checklist achieved the outcome you need. Not "did they run the dishwasher" but "is the kitchen guest-ready by the definition that matters to you, and how would either of you know that without you personally walking through it."

Most checklists are entirely process. They tell the helper what to do but never build in a way to verify the result met the standard, other than trusting the person's own judgement about whether it looked finished. When there's no verification built into the document, you end up doing that verification yourself, separately, which is the second checklist you didn't mean to create.

The fix is building the standard verification directly into the process document, so the verification happens through the document, not through you re-inspecting after the fact.

Rebuilding the list so it explains itself

Take your current checklist and go through it slowly, imagining someone who has never been to the property reading it for the first time with no ability to ask you questions. If you're starting from nothing, building a changeover checklist from scratch sets out the full list first.

Wherever you find a phrase that relies on things only you know, rewrite it as a specific instruction instead. Not "check the usual spots," but the actual named spots, listed out. Not "reset if needed," but the exact steps for resetting whatever it is, written as if for someone who's never had to do it before, because eventually someone won't have.

Wherever the list assumes a standard without stating it, write the standard directly next to the task. Not just "wipe down surfaces" but what finished looks like, specifically enough that two different people would reach the same conclusion about whether it's done.

This takes longer than writing the original list did, because you're translating knowledge that currently only exists in your own head into something explicit enough for someone else to use as their sole reference. It's worth doing once properly rather than compensating for it forever through your own repeated inspection.

Adding proof without inspecting everything

Rewriting the list solves the instruction problem. It doesn't solve the verification problem on its own, because a written standard still needs some way of confirming it was met, without you needing to be physically present or walking through in person every single time.

The practical fix is building a small proof step directly into the checklist itself, tied to specific points rather than everything. Not a photo of every task, which soon becomes a chore that lapses and a pile of images that never get checked. A photo at a handful of points that matter most, the ones where a problem would affect a guest and where a quick visual check tells you enough to trust the rest followed the same standard.

Choose those points deliberately. Bed made and dressed, a specific angle of the kitchen once reset, the bathroom once finished, anything unusual noted separately with its own photo. Keep it to a short, fixed list rather than letting it expand task by task, because a proof step that takes real effort to complete stops happening reliably fairly quickly.

This isn't proof that the property is spotless or safe in every sense, and it's worth acknowledging that limit. A photograph tells you the surface looks right at that moment. It doesn't verify function, hygiene at a level a photo can't show, or anything safety related. Treat it as a presentation check, not a guarantee, and keep any safety checks as their own separate, explicit item on the list rather than folding them into the photo habit and assuming that covers it.

Where the single list lives and who edits it

A checklist that lives in your head, a text message thread, or a printed sheet taped inside a cupboard has an obvious problem: it can't be the single source of truth if it's not accessible to both of you at the same time, and it can't be trusted if there's any question about which version is current.

Put it somewhere both of you can open at any time, on a phone, without needing to ask the other person for it first. A shared document works. A simple shared note works. The specific tool matters far less than the two conditions: always accessible to both people, and only one current version, not a printed copy that quietly falls out of date while a digital version gets updated separately.

Decide upfront who can propose changes and how those changes get confirmed. The point isn't to make editing bureaucratic. It's to prevent a situation where the helper quietly adapts their own version because something in the written list didn't quite match reality, and now there are two versions again without either of you deciding that on purpose.

What to agree before the first changeover

Most friction between hosts and changeover help isn't about the cleaning. It's about the things that were never agreed at the start. Settle these in writing before the first visit:

how much, and how and when they're paid; who supplies and launders the linen; what gets restocked, from where, and who pays for it; how damage or breakages are reported, with a photo and a message the same day; what happens to anything a guest left behind; and how they get in, ideally with their own door code rather than the guests' code.

If linen is part of the job, settle first whether it is hired or owned and how many sets each bed has. The guide to holiday let linen covers both.

Agree, too, which contents they count at each changeover and how they report anything short. A shared holiday let inventory gives them one list to check against.

If you're paying someone to work at the property, check your insurance covers it before their first visit.

Making sure they know when the changeovers are

A perfect checklist doesn't help if your helper finds out about a same-day changeover the night before. Share the booking calendar, or a view of it, so they can see check-outs and check-ins as soon as bookings land. Agree how much notice they need, and what happens when a booking arrives inside that window.

Some hosts use a scheduling app that sends the helper each changeover automatically and collects the checklist and photos in one place. Choosing software around the problem that's costing you most helps you decide whether that's worth it for you.

Running the first changeover on the new list

Once the list is rewritten with explicit instructions, a stated standard, and a handful of proof points built in, run it for real rather than assuming the improvements will hold up untested.

For the first changeover, be available, even if not present, to answer anything unclear as it comes up rather than after the fact. Anything that needs explaining in the moment is evidence the list still has a gap, and it's far cheaper to fix that gap immediately than to discover it three changeovers later after it's already happened the same way each time.

Review the proof points against the stated standard afterwards, specifically checking whether the standard as written was met, rather than whether it generally looked fine. It's the same discipline as bringing in help for your holiday let without losing control

Reading the results without redoing the job yourself

The entire aim of this rebuild is to get to a point where you can trust the document enough that you stop needing to personally re-walk the property to feel confident it's ready. That trust has to be earned across a few cycles, not assumed the first time it goes smoothly.

Track it loosely. Note, even briefly, whether each changeover matched the standard based on the proof points and any feedback, and whether anything needed correcting that the list should have covered but didn't. After a handful of cycles, a pattern will be obvious. Either the list is holding up and your own inspection habit can reduce, or specific gaps keep recurring and the list still needs work in those exact spots.

Resist the urge to keep doing a full personal check "just in case" once the pattern shows the list is holding. That habit, kept going out of leftover anxiety rather than evidence, is exactly how the second checklist creeps back in even after you've done all the work to remove it.

When to step back in and when not to

There will be moments worth stepping back into closer checking. A change of helper, a change to the property itself, a period where something's gone wrong once and you want more certainty for a few cycles until you trust it again. That's a reasonable, evidence-based reason to increase checking temporarily.

What's worth resisting is stepping back in simply because a slow week gave you spare time, or because checking has become a habit that feels responsible even once the evidence says it's no longer necessary. The document exists specifically so that your ongoing personal inspection isn't the thing keeping standards in place. If it's still doing that job after the list has proven itself, the list isn't the source of truth yet, whatever it says on paper.

Keeping the list up to date

A checklist that gets written once and never touched again slowly drifts out of date as the property changes, as seasons change what needs doing, as small lessons accumulate that never make it back into the document. When you review it, move the slow periodic jobs to a separate holiday let deep clean checklist for longer gaps between bookings, and keep anything the next guest needs on the changeover list.

Build in a light habit of revisiting it, not constantly, but at a sensible interval, alongside any moment where something new comes up that the list didn't cover. Whoever notices the gap, whether that's you or the helper, should have a clear, easy way to flag it, and the document should get updated rather than the fix living only as a verbal note that fades within a few weeks.

Moving to one shared checklist

The duplication was never about the cleaner or the co-host doing a bad job. It was about a checklist that was only ever complete enough for someone who already knew everything it left unsaid, being handed to someone who didn't.

Rebuild it to explain itself, add a handful of proof points rather than an inspection regime, keep it somewhere you both use, and review the results after the first few changeovers. Once it is holding the standard on its own, you can stop running the second list in your head.