A Storm-Season Contingency Page Your Co-Host Can Run Without You

In storm season the person who needs the plan isn't you. It's whoever is standing in the apartment while you're asleep in another time zone.

Last updated: October 5, 2026

In storm season the plan matters most to the person who isn't you. You might be asleep in another time zone while a co-host stands in the apartment, phone in hand, working out what to do about a nervous guest. One page, written in advance, answers the questions a call at two in the morning can't.

Key Takeaways

• One page beats a phone call. A written plan says the same thing whether you're awake or asleep.
• Put contacts and permission first. The top of the page tells the co-host who to call and what they may decide alone.
• Draw the line in advance. Handing out supplies is a yes. Moving money isn't.
• Booking changes wait for a person. The guest and dates are shown, and nothing changes until someone approves it.
• Review the page after every storm. Whatever a co-host had to call about is the line the page was missing.

Why storm season needs one page

A storm turns weeks of planning into hours of decision. The forecast moves, the roads close, and one guest wants to leave while another wants to stay. In that window you don't have time to explain your thinking from scratch. You need it already written down.

The person who needs the plan usually isn't the owner. It's the co-host, the cleaner, or a neighbour ten minutes away, standing in the apartment with a phone and a list of worried guests. They can see the room. They can't see the rules you keep in your head. A page closes that gap.

A phone call feels faster, and it isn't. You might be asleep, and a call wakes you without leaving the other person a written record. Half the answers are forgotten by morning. A page wakes nobody, and it says the same thing every time someone reads it.

Write the page on a calm day. A plan drafted during the storm is just a panicked list. The calm version you can test against a real booking, check for gaps, and keep. That test is what separates a plan from a wish.

There's a quieter reason too. A page protects the guest relationship. When answers come from a settled plan rather than a scramble, guests hear one consistent story. That consistency is what keeps a stressful stay from becoming a complaint once the weather clears.

Keep the page somewhere the co-host already looks. A note saved on their phone beats a document filed on your laptop, because the person who needs it can't reach your laptop.

What the page has to say first

Order matters more than length. The top of the page should answer the two urgent questions before anything else: who to call, and what the co-host may decide alone.

Put the contacts first. The co-host's own chain comes at the top, and alongside it the local emergency services for anything that puts a person at risk. That line should be impossible to miss and short enough to read in one look.

Then write the permission line. One sentence for what the co-host may decide without asking, and one for what must wait. Two sentences here remove most of the hesitation later, because the person on the ground knows where their authority stops.

Then map the place. Where the keys live. Where the breaker box sits. Where the water shut-off is. Where the spare linen, the torches, and the first-aid kit are kept. Write these as locations, not as instructions, so nothing depends on you being awake to explain a step.

Then list what not to touch. The boiler, a locked owner's cupboard, a door shared with a neighbour. Naming the boundaries keeps a helpful co-host from creating a second problem while solving the first.

Finish with the guest list and what each person needs. Who has a car, who's leaving early, who's travelling with a child. Keep these details inside the tool rather than in a group chat: in LOCALSBNB the guest name, phone number, and ID are masked automatically, so a co-host can reach the right door without the full record sitting in a screenshot.

One page. If it runs to two, the second page won't get read in the dark, and the lines that matter most will be the ones that get skipped.

Decisions a co-host can make alone

A page that allows nothing is as useless as one that allows everything. The value sits in the decisions you hand over on purpose, with a limit attached.

Give the co-host a set of clear yes decisions inside a stated boundary. Handing out the supplies on the shelf. Moving a guest to another room in the same building when the page says that's allowed. Opening the cupboard with the spare bedding. Handing over the spare key to a guest who's locked out.

Booking changes are a different kind of decision, because they move money and dates. A check-in, a check-out, an extended stay, or a room change on a platform booking runs through a confirmation step. In LOCALSBNB the tool shows the guest and the dates, and nothing moves until a person approves it. That write path is available for overseas stores, while China stores stay read-only.

The call-me list stays short by design. Anything that touches a guest's money. Anything that needs a platform decision. Anything the page doesn't already cover. A short list is one a co-host can hold in their head while the wind picks up outside.

Give the co-host permission to stop as well. If a decision feels wrong, they can pause and leave it for you. Naming that as an allowed move removes the fear of acting alone, which is often the real reason a co-host calls anyway.

Try the page against one quiet booking first. Walk a co-host through a pretend late check-out and see which line they reach for. A dry run in good weather is worth an hour of guessing in bad weather.

What still comes back to you

Some decisions stay with you, and that's the point of writing them down. A refund, a rebate, a change to a booking date, or a message that answers a platform claim all stay on your side of the line.

You also keep the guest's private information where it belongs. A co-host may need a first name and a door number, and nothing more. LOCALSBNB keeps credentials on your own device and masks guest names, phone numbers, and ID details, so access stays as narrow as the job needs.

The page works best when a co-host can act on a booking without waking you. In LOCALSBNB a booking change is shown with the guest and the dates, and it waits for a person to approve it before anything moves. See how that confirmation step fits your own setup at localsbnb.com.

Review the page after every storm. The things a co-host had to call about are exactly the lines the page was missing. Add them while the details are fresh, and the next storm runs quieter than the last.

Keep one master copy and let the co-host keep their own. When you update the contact list or the spare-key spot, tell them in one sentence so the two pages match. Two versions of a plan are worse than one, because the co-host may trust the wrong one.

FAQ

How long should the contingency page be?

One page. If it spills onto a second, the important lines get skipped. Trim the background and keep the decisions.

Who decides on a booking change during a storm?

The co-host can start it, but it waits for a person to confirm before anything moves. Money and platform claims stay with the host.

Do guests' details need to be on the page?

No. Keep a first name and a door number on the page, and keep the full record inside the tool, where names, phone numbers, and ID details are masked.

The page costs you one calm afternoon and saves a hundred panicked decisions. Write the contacts, draw the permission line, and let a co-host run the rest. To run the booking changes that need your nod from the same place, start free at localsbnb.com.

---

This is general guidance for hosts. It isn't legal, tax, or insurance advice, and rules and platform terms change by place and over time — check your local authority and the current terms of each platform you use. For anything that puts a person at risk, contact your local emergency services.