Short-Term Rental Checklist: From Setup to First Guest

Every rental launch is a countdown whether you plan it or not — the only question is whether the sequence is designed (dependencies respected, quiet weeks used, the last days calm) or discovered (the licence application that takes six weeks, filed in week seven). This checklist is the designed version: the road from decision to first guest as eight dated weeks, each with its tasks, its deliverable and its "you are here" feel — the one you pin to the fridge.

The eight weeks assume a property in hand and spare-time effort. Compress or stretch to fit your reality — but keep the order, because the sequence is where the design lives.

Weeks 8–7: the gates (permission, money, insurance)

The countdown opens with the homework that can stop it, run first precisely because of that: the local short-let rules checked at source (registration and licence applications filed now — they're the countdown's longest lead item in regulated markets), property permissions gathered in writing (lender, lease, landlord), the insurance conversation had and cover quoted, and the accountant hour booked (tax setup, record format, money separation). Deliverable by end of week 7: a written yes from every gatekeeper — or the early, cheap discovery that the project needs rethinking. Meanwhile the thinking task runs in parallel: the positioning sentence drafted, because week 6's shopping list depends on it.

Weeks 6–5: the property build

The physical fortnight, run from lists rather than aisles: the full supplies list ordered as one master shop early in week 6 (furniture lead times are the second-longest item in the countdown), the room builds executed as deliveries land — bedroom, bathroom, kitchen — the safety layer installed and certified where your jurisdiction requires it, the access hardware fitted and tested, and the segment kit per positioning (family, work, pet). Deliverable by end of week 5: a property a guest could physically stay in tonight — verified by the countdown's most useful single task, the live-in-it audit: one night's real stay, cooking, showering and sleeping your way through the gaps while there's still a fortnight to fix them.

Week 4: the listing assets

The shopfront week, while the property is at its newest: the two photography sessions (golden evening and bright morning — watch the forecast and be flexible), the title built by formula, the five-block description drafted with its honesty block, amenity fields inventoried, house rules written with their reasons, and the launch pricing set with the step-up schedule written down and diarised. Deliverable: a publish-ready listing, deliberately not yet published — because week 3 exists.

Weeks 3–2: systems before guests

The operating build, in its strict internal order: the guest guide first (two evenings in WelcomeFlo — arrival photos from week 4's shoot, Wi-Fi widget, house answers, the local list's founder's dozen, the emergency page), then the five scheduled messages written and queued (one evening), quick replies loaded, the cleaning and turnover checklists written and walked once for real, the review sequence armed, and the emergency plan's host side documented (contacts, backstop, scenarios). Week 2 closes with the countdown's second critical test: the dusk kerb-test — a friend who's never visited follows only what a guest would receive, at dusk, while you watch from a distance and take notes. Fix what the test finds; it always finds something.

Week 1: launch week

Publish Monday. Then a deliberate week of launch moves: the personal-network announcement Tuesday, the free surfaces claimed (Google Business Profile, tourism board, directories) by Friday, every enquiry answered at minutes-speed as the first bookings land at the deliberate opening rate. The property sits ready; the pre-arrival rail fires for the first booking; and the countdown's final deliverable arrives on its own schedule: the first guest, walking into a stay that eight weeks of sequence made boring in the best possible way.

Week 0 and beyond: the handover to rhythm

The countdown ends by handing itself over to the standing systems: the first five stays run in over-delivery mode (letter handwritten, sprint-speed responses, the welcome staging full), every lesson metabolised same-week (the question into the guide, the stumble into the instructions), the pricing step-up executed on its diarised dates, and the hosting calendar — daily glance, weekly close, quarterly reviews — adopted as the countdown's permanent successor. Six to eight weeks after launch, the graduation criteria close the launch phase, and the project becomes the practice.

The compressed and stretched variants

Real timelines vary; the sequence flexes two ways. The four-week sprint (property nearly ready, market unregulated): weeks 8–7 compress to days only if the gates clear fast — licence-free markets and mortgage-free properties permit it; the property fortnight compresses to the gap-fixing week; the systems fortnight is the one stage that shouldn't compress below ten days, because rushed systems are the classic launch failure. The six-month amble (renovation projects, regulated markets): the gates and any building work run long and parallel; the risk inverts to momentum loss — diarise the stages anyway, and use the long middle to over-build the cheap layers (the guide's local list, the brand, the photography across seasons) that sprint-hosts never get time for. Either way the invariant holds: gates first, systems before publish, launch as a played sequence rather than a hopeful upload.

The countdown's two critical tests, expanded

Because the eight weeks' quality concentrates in its two checkpoint rituals, each deserves its full procedure. The live-in audit (end of week 5): stay the night as a paying stranger would — arrive at dusk using only the draft instructions, cook a full dinner (the one-real-meal test), shower at morning pressure, stream something, charge your phone where the bed puts you, and pack out as a departing guest. Keep the phone's notes app open throughout; the audit reliably yields fifteen-plus fixes — the missing bottle opener, the bedroom's socket desert, the blackout that isn't — each costing pounds now and review-points later. The dusk kerb-test (end of week 2): the friend who's never visited, sent exactly what a guest would receive, followed at a discreet distance. Watch where they hesitate (a missing photo), what they ask (a guide gap), and how long kerb-to-sofa takes; then fix, and — for properties expecting night arrivals — repeat once in genuine darkness, because the after-dark variant can't be verified in daylight.

Both tests share a principle worth naming: the builder cannot audit the build — familiarity blinds you to exactly what strangers trip on, which is why the countdown schedules fresh eyes (yours-as-guest, theirs-as-arrival) rather than more owner walkthroughs. Hosts who skip the tests launch anyway and run them accidentally, on paying guests, one review at a time; the countdown's version costs one night and one favour.

The bottom line

Eight weeks, one invariant order: gates, property, listing, systems, launch — with the dusk kerb-test and the live-in audit as the two checkpoints that catch what lists can't. Pin the countdown, respect the dependencies, and let week 0 hand the project to the rhythm that runs it forever. The longest-lead item files this week; the most valuable build — the guide — waits in week 3, already half-written by everything you'll learn on the way there. Start it free in WelcomeFlo when that week arrives, and it's ready to greet your first guest before you are.