Running a hotel on spreadsheets: when it stops working

What a spreadsheet is genuinely good at

It is free, it is instant, and it fits your business exactly, because you built it around how you actually work rather than around how a software company assumed you work. Nobody needs training. It works offline, which in some parts of this country is not a small thing.

For an owner-run property of a handful of rooms where one person takes every booking, that is a hard combination to beat, and swapping it for software you resent is a downgrade.

Sign one: more than one person needs it at once

This is the first crack and it is structural rather than a matter of discipline.

The moment two people need to write to the sheet, you have a version problem. Cloud spreadsheets soften it, but they do not solve the underlying issue: a spreadsheet has no idea that two cells are in conflict. It will let you sell the same room twice quite happily, because it does not know what a room is.

Sign two: you cannot answer a question about last month

Not what you earned — what you kept.

Revenue is easy to total. Profit needs your expenses, your salaries, your commissions and your supplies in the same place as your bookings, and in most spreadsheet setups those live in different files maintained by different people at different times. So the answer takes an evening, arrives two weeks late, and nobody entirely trusts it.

The tell is not that the number is hard to produce. It is that you have stopped asking for it.

Sign three: the knowledge is in one person's head

Which rooms have the working aircon. What Holy Week costs. Which agent gets which rate. Whether the guest in 204 is a repeat or a first-timer.

A spreadsheet holds data, not context — so the context stays with whoever has been there longest. That is fine until they take a week off, and expensive when they leave.

Sign four: staff have stopped updating it

Watch what happens on the floor. If housekeeping is calling the front desk to ask which rooms departed, the sheet is not the source of truth any more — it is a record that someone updates in the evening, describing a morning that has already happened.

The moment a system lags reality, people route around it, and once they have routed around it they do not come back.

What to fix first

If you recognise two or more of those, the useful move is not to replace everything at once. It is to move the thing that breaks first.

For almost every property, that is bookings and availability — because that is where the failure has a guest standing in front of it. Get every reservation, from every source, into one place that refuses a conflict, and you have removed the most expensive failure mode you have.

Rates come next, because they are the thing most often held in someone's memory. Then costs, because that is what turns revenue into an answer about profit.

Housekeeping, tasks and shifts can wait. They are real problems, but nobody has ever lost a guest over a badly organised rota.

Keep what the spreadsheet was good at

The common failure when people move off a spreadsheet is not the software. It is losing the things the sheet did well and nobody wrote down.

Before you move anything, spend an hour listing what your sheet actually holds that is not data: the rate you give the dive shop, which rooms you never sell to families, the note about the aircon in 204, the way you mark a booking that has paid a deposit but not the balance. Those are business rules, and they are the reason a generic system can feel like a downgrade in week one.

Then check the new system can hold each of them. Most can. The ones it cannot are worth knowing before you migrate, not after.

How the move actually goes

The realistic sequence for a small property is a week, not a weekend, and it is mostly not technical.

Set up your rooms and your rates first, and get them right — everything downstream depends on them. Then enter your forward bookings, which is the part people dread and which is usually two or three hours because you only need the ones that have not happened yet. History can stay in the spreadsheet; you do not need last February in a new system to make a decision this July.

Run both in parallel for a fortnight. Take every booking into the new system, and update the sheet as a backup you never consult. At the end of two weeks, either you have stopped opening the sheet — in which case delete the shortcut — or you have found the thing it did that the system does not, which is worth knowing while you still have both.

Bring the staff in during the parallel fortnight, not after it. Someone learning a room board while it is the only source of truth is a bad first week for everybody.

What moving does not fix

It is worth being clear about the limits, because the disappointment usually comes from expecting the wrong thing.

Software will not tell you what rate to charge. It will apply the rate you decided, every night, without anyone having to remember it — which is a different and more modest claim than the one you will hear on a sales call.

It will not make your staff communicate. A room board updated by nobody is as useless as a sheet updated by nobody, and if the underlying problem is that housekeeping and the front desk do not talk, a system will surface that faster rather than solve it.

And it will not survive being half-adopted. The value comes entirely from one place holding the truth; a system that takes eighty percent of bookings while twenty percent stay on Messenger is worse than the spreadsheet was, because now people trust it.

And when to stay put

If you run four rooms, take every booking yourself, and can tell us what last month made without opening anything — your spreadsheet is doing its job. Keep it.

Come back when the second person needs to write to it.