A Regulatory Change Log You Keep Yourself

Announcements arrive as fragments: a council note, a platform email, a trade newsletter. A log turns fragments into a schedule you can actually keep.

Last updated: October 18, 2026

One market you can hold in your head. Three markets you can't, and the failure is quiet. A change lands in the smallest market, gets read on a phone, and is gone by the time you're back at a desk. A change log fixes that with five columns and an hour a quarter. It won't tell you what's coming. It will tell you what you already know, and what you're still guessing at.

Key Takeaways

• Memory fails at the second market, not the third. By then you're tracking the same rule in two dialects.
• Five columns hold an entry. Source, quote, status, what it touches, who acts.
• Quote before you summarise. A summary written in a hurry becomes the only version you remember.
• Proposal isn't decision. Half of what arrives is a consultation, and treating it as law costs money.
• Sweep quarterly, on a fixed date. The log only works if someone reads it when nothing's on fire.

Why memory fails at three markets

With one market, you don't need a system. You read the notice, you act, you remember roughly when it happened and roughly what it said. The shape of the rule lives in your head well enough to answer a question at short notice.

Add a second market and the shape stops transferring. Two authorities describe the same duty in different words, on different cycles, in different formats. One sends a PDF. One updates a page without telling anyone. One expects you to log in and check. You start keeping the two in your head by remembering one and inferring the other, and inference is where it goes wrong.

By the third market, something else happens. You stop noticing that a change is a change. A note arrives that reads like routine correspondence, you skim it, and three weeks later a guest asks a question that assumes you've already adapted.

There's a concrete version of this that most multi-market hosts recognise. A small market tightens something about the unit itself: what counts as a separate letting, or how many people can sleep in a room. You read it, decide it doesn't affect your two units, and move on. Six months later, one of those units has been re-let to a group of five, and the decision you made on a phone at the time was correct for the facts you had then. Nothing in the file says you made it.

That's the real function of a log. Not to predict. To make your own past reasoning visible, so a later version of you can see what it was based on.

The five columns that matter

A change log isn't a document. It's five columns and one row per event. Anything more elaborate gets abandoned in the second month.

Column one: what arrived, from whom, and when you received it. The source matters as much as the content. A platform email, an authority page, a trade newsletter and a WhatsApp message from another host are four different levels of reliability, and a month later you won't remember which one it was. Write the source name and the date you saw it, not the date on the document.

Column two: what it says, in its own words. Two or three sentences copied out, in quotation marks, with the operative sentence included. Not your summary. The reason is blunt: a summary becomes the version you remember, and the remembered version loses every condition attached to it.

Column three: status. Proposed, published, or in force, with the source of that judgement. Most confusion in this area comes from treating a proposal as a decision. Somebody announces an intention, a newsletter reports it, and within a week it's being discussed as a rule. Your column exists to stop that drift. If you can't tell, write "unclear" and give it a date to resolve.

Column four: what it touches. Which unit, which market, which duty. Specific enough that a cleaner reading it would know whether it applies to the flat they clean. "All units" is an answer, but only if it's true.

Column five: next action, owner, and the date you look again. An entry without a next step is a note. The owner is the person who does the work, and the date is when you'll come back to it, which is usually before any effective date rather than on it.

Five columns, one row, ten minutes. The discipline is in keeping the row visible after the moment passes.

Reading an announcement without panic

Most announcements are written to be read quickly and understood slowly. Four questions defuse them.

Is this a proposal or a decision? Look for the verb. Authorities consult, propose, intend, plan and consider. They also adopt, require, and come into force. A document can do both in different paragraphs, which is why the verb is the thing to read.

When does it take effect, and from when does it apply? Those are often different, and the gap between them is where a host can still act calmly.

Who does it bind? Some instruments bind platforms, some bind hosts, and some bind both with different duties. A rule that requires a platform to transmit something may leave you with a paper obligation and no portal to use. Reading who's bound saves you from building a process nobody asked for.

What does it not say? This is the question that earns its keep. A notice about registration may say nothing about advertising, or about the number of nights, or about what happens to bookings already accepted. The silence isn't permission. It's just silence, and it belongs in your log as a gap to resolve.

Then write the entry, in that order. Quote first, judge second. If you write the judgement first, the quote never gets captured, and the judgement is all you'll have in six months.

Two more habits keep the reading honest. Keep the original somewhere, as a file rather than a link, because authority pages get replaced and the old version is the one you acted on. And date every judgement. "Doesn't apply to us" is a claim with a shelf life.

The quarterly sweep

Put the sweep on a fixed date and treat it like a booking. One hour, every quarter, with the log open and nothing else running.

Five sources, read in the same order each time. The authority's own page for each market, because that's the version that counts. The platform's host updates, because platform processes change with the rules. One trade newsletter, for the things you'd otherwise miss. Your own inbox, searching for the words your markets use for the duty in question. And your local adviser, once a quarter, with a specific question rather than an open one.

Then work the log rather than the news. Close the entries that resolved. Chase the ones marked unclear. Move anything with a date into your calendar with a preparation date in front of it. Add new rows only for what you actually received, not for what you think might be coming.

The sweep produces one useful artefact: a short list of what changed since the last one, and what you decided about each. That list is worth more than a folder of announcements, because it's the only place where the decision and the evidence sit together.

Nothing in this process watches the rules for you, and no software can. What software can do is keep the operating facts straight while you do the reading. LOCALSBNB holds four direct connections — Airbnb, Booking.com, Agoda and Trip.com — in one calendar, so when a change applies to specific nights or specific units, you can see which of yours are affected. That's the matching job, and it's the part localsbnb.com already handles. The reading stays yours.

FAQ

How many entries should a year produce?

Fewer than you'd expect, and that's the point. A working log for a small portfolio tends to hold a short list of real events rather than a feed. If yours is filling with speculation, the filter is too loose; the column for status exists to keep guesses out of it.

What if I can't tell whether something is in force?

Write "unclear", name the person or page that would settle it, and give it a date. An entry that admits uncertainty is more useful than one that resolves it wrongly, because the second one stops you from looking again.

Should a co-host or manager keep the log?

One log, one owner, whoever does the work. A manager can hold it, and the owner should still read the quarterly list, because the decisions in it are about risk that sits with the owner. Two logs is the same as none.

A log like this looks unambitious, and it is. That's why it survives. It won't make you compliant on its own, and it won't tell you what your markets will do next. What it does is stop the ordinary failure of a small portfolio: a rule changed in one place, read once on a phone, and then remembered wrongly for a year. Hosts who keep their units and their dates in one place have an easier time of it, and that place is localsbnb.com.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. What applies to a short let, when it applies and what it requires differ by market and change over time; always confirm the current position with the local authority and the platform's current terms.