Thursday afternoon, 4:40pm. A member of staff rings: am I on this Saturday? The rota lives in a spreadsheet, and the folder contains rota.xlsx, rota-final.xlsx and rota-final-sara.xlsx. You open all three before you dare answer.

That moment is the real signal. Not that the file has grown too big, but that you can no longer tell at a glance what is true.

A spreadsheet is a brilliant tool right up until it isn't

Spreadsheets are excellent for calculating, trying things out and making sense of something for yourself. They get fragile the moment they become the place where the truth lives and more than one person needs that truth at the same time.

That is not a flaw in Excel or Google Sheets. It is simply a different kind of work. A file is designed to be opened, changed and saved by one person at a time. A rota, a stock list or a quote log is worked on all day, often from a phone, often by someone who started last month.

Five signs you have crossed the line

  • Two people cannot safely edit it at once, so versions get passed around by email or WhatsApp.
  • It contains rules that are written down nowhere: Karim never works Saturdays, this customer always pays up front. New staff cannot know them, so they break them.
  • You retype data from the file into something else by hand: an invoice, an email, the calendar, the till system.
  • Somebody has to “tidy it up” every week before it makes sense again.
  • Mistakes surface because a customer calls, not because you spotted them.

One sign is normal. Three or more means your spreadsheet has quietly become a system, without anyone deciding that it should.

What breaks is not the formulas

What breaks is trust and time. Trust: you start double-checking, and double-checking costs more than the work itself. Time: twenty minutes a day of retyping is roughly seven hours a month. Multiply that by what an hour costs you and you have your budget already.

There is a hidden cost too. While the truth sits in a file on one laptop, nobody else can answer a question about it. Every query lands with the same person. You only really notice when that person takes a week off.

Don't replace the file, replace one job

The classic mistake is deciding to build a system for everything. It gets expensive, it takes months, and halfway through it is less pleasant to use than the messy file that at least worked.

Do the opposite. Pick the single action that hurts most often. Usually it is retyping, or the question “which version is right?”. Build a small web app around that one thing: one screen to enter something, one screen to see it, one button that produces the thing you used to retype. A web app here means nothing grander than a page you open in a browser, phone included, where everyone sees the same state.

Everything else stays in the spreadsheet. You can almost always export back to Excel, so you lose nothing and nobody has to switch over in one go.

A rough test before you spend money

Count the minutes: how much time goes into this one piece each week, across everybody? Under an hour a week: keep the file, tidy it, and write the rules down. Three to five hours a week: in our experience a small tool usually pays for itself within a season. Above that, waiting costs you money every month.

What to do this week

  • Open the folder and count how many versions of the same file are sitting there. Pick one as the real one and rename the rest to OLD.
  • For one week, note how many minutes a day you spend typing data from the file into somewhere else.
  • Write the rules that currently live only in your head onto a single sheet of paper. That page is the best brief you can hand anyone later.

If after that week you find you are counting hours rather than minutes, we at ITSysPro are happy to spend half an hour thinking through what the smallest useful thing to build would be. No quote required to have that conversation.