Managing 4–15 Properties? Why Excel Isn't Enough for AL Compliance Anymore

There's a moment almost every multi-property AL host recognises: the spreadsheet that worked fine for two or three units starts creaking the moment you add a fourth.

It's not a question of being disorganised. Excel was built to store data — not to manage legal obligations that are constantly in motion.

What changes at four units

With one or two properties, you can keep everything in your head and manually confirm each task. From four onwards, complexity grows in a non-linear way:

• Simultaneous guests across different properties, each with their own check-in and registration cycle
• SIBA communications that must be submitted within a specific legal window after arrival — and multiply with every single booking
• Municipal tourist taxes (TMT) with rules that vary council by council, each needing to be collected, recorded, and declared separately
• Cleaning and maintenance logs that you need to be able to present in an organised way if inspectors come knocking
• Licences and renewals with different dates for each property

With four or more active units, any one of these can fail silently — and you won't notice until a notification lands in your inbox.

The real problem with Excel

Excel doesn't warn you. It doesn't know a guest has just checked in and that a deadline is now running. It doesn't automatically link a booking to the corresponding reporting obligation. It won't tell you that a municipality changed its TMT rules.

What actually happens in practice:

You open the file, see an unfilled row, and can't tell whether it was dealt with or just forgotten. You ask whoever did the check-in. They're not sure. You check the portal. The deadline has already passed.

That's not a discipline problem — it's a systems problem.

What Excel does well (and doesn't)

Task	Excel	Compliance system
Storing static information	✅	✅
Real-time deadline alerts	❌	✅
Linking bookings to legal obligations	❌	✅
Maintaining an auditable history	⚠️ Fragile	✅
Adapting to per-municipality rules	❌	✅
Working with a team or collaborators	⚠️ Difficult	✅

What a compliance system actually does

This isn't about replacing your judgement — it's about making sure nothing falls through the cracks while you're dealing with something else.

1. Centralised visibility

All properties, all bookings, all pending obligations in one place. You shouldn't need to open three spreadsheets and two portals just to understand where things stand today.

2. Alerts before deadlines, not after

Mandatory communications have legal deadlines. A system that warns you with enough lead time to act is fundamentally different from a log you only check when you happen to remember.

3. An auditable record

If you're ever inspected, saying you did everything correctly isn't enough — you need to be able to prove it. A log with a timestamp and a recorded action is worth far more than an Excel cell with a date typed in by hand.

4. Separation by property and by municipality

Each unit can carry slightly different obligations — taxes, registration rules, display requirements. A system that treats each property individually prevents you from accidentally applying one council's rules to another.

5. Delegation without losing oversight

If you have a cleaning team, a co-host, or a property manager, you need to be able to delegate tasks without losing visibility over what's actually been done. A shared Google Drive spreadsheet was never designed for that.

When it makes sense to switch

There's no magic number, but there are clear signals:

• You've missed a mandatory reporting deadline at least once
• You can't say off the top of your head what your pending obligations are for this week
• You're anxious about an inspection — not because you've done anything wrong, but because you're not sure everything is properly documented
• You're spending more time managing the spreadsheet than managing your guests

If two or more of those ring true, the issue isn't the volume of work — it's the absence of a system that matches the scale you're already operating at.

What you don't need

You don't need a system that makes decisions for you or takes away your control. What you need is a tool that does the monitoring work — alerting, recording, organising — so you can focus on the decisions that actually require your judgement.

AL compliance isn't complicated in most cases. What makes it hard is the repetition, the number of units, and the consequences of failing silently. A good system solves exactly that.