What to do when several people need the same spreadsheet

Key takeaways

The most common way a spreadsheet fails, and the one that goes unnoticed longest because nothing breaks. What cloud sharing fixes, what it does not, and the smallest thing that makes it stop.

This is the most common way a spreadsheet fails, and the reason it goes unnoticed for so long is that it does not look like a failure. Nothing breaks. No error appears. The numbers are wrong, quietly, from a Tuesday afternoon onwards.

Here is what is actually going on, what cloud sharing does and does not fix, and the smallest thing that makes it stop.

The failure is silent, which is why it is expensive

Two people open the file. Both make sensible edits. One saves, then the other saves. The second save wins and the first person's work is gone, along with any record that it was ever there.

Nobody gets told. The person whose work vanished finds out a fortnight later, or never. And the real damage is not the lost hour: it is that from then on nobody is quite sure whether any figure in the file is current, so everybody starts keeping their own copy to be safe. That is the point at which one spreadsheet becomes six and reconciliation becomes somebody's job.

Loud failures get fixed. Quiet ones get absorbed.

What cloud sharing fixes

Putting the file in Microsoft 365, Google Sheets or a shared drive with co-authoring on is worth doing, costs almost nothing, and genuinely solves the worst of it. Several people can type at once without overwriting each other, and there is a version history to go back to.

If you are still emailing the file around as attachments, do this first. It is not the whole answer but it is the cheapest useful step by a wide margin, and plenty of businesses need nothing more.

What it does not fix

It still accepts nonsense. Co-authoring stops two people clashing. It does nothing about somebody typing a date into a quantity column, or a discount of 150%, or a customer reference that does not exist.

It cannot tell you who is allowed to change what. Everybody with the link can edit everything. There is no way to let the warehouse update quantities without also letting them change prices.

The history is not an audit trail. Version history tells you a cell changed. It does not readily answer "who approved this figure, and when", which is the question an auditor, an insurer or a buyer will actually ask.

It still cannot act. No email when a figure crosses a line, no refusal to proceed when a step is missing, nothing happening at 2am.

Two people can still disagree. Co-authoring removes the technical clash and leaves the human one. If two people hold different views about what a column means, the file now records both at once.

The smallest fix that works

For a surprising number of businesses the answer is not a system. It is one form.

A single screen that will not accept nonsense, feeding the three or four columns that actually matter, with a record of who entered what. The spreadsheet stays exactly where it is, and carries on being the place people look at a hundred rows at once and spot the odd one.

That is a job of days rather than months, and it removes the two failures that cause nearly all the damage: bad data going in, and no record of who put it there.

When it is worth more than a fix

If several of these are true at once, the one form is a sticking plaster and worth recognising as one:

  • The file is the only record of something you would be in trouble without.
  • Somebody outside will ask for its history.
  • The formulas contain business logic nobody can fully explain.
  • A mistake in it has already cost money.
  • One person is the only one who understands it.

None of that means a big project is the answer. It means the first piece of work is finding out what the file really does, before anybody builds anything.

What we do

There is no minimum, so "several of us need this file and it keeps going wrong" is ordinary work here rather than something to be bundled into a bigger engagement.

Send the actual file and say what goes wrong and how often. It gets graded by size and you get a price in writing before anything starts. Nothing begins until you approve it, and if the number is wrong for you, you walk away owing nothing.

If the honest answer is "turn on co-authoring and spend an hour fixing three formulas", we will tell you that, in writing, and charge you for the hour rather than the project.

The price changes with the size of the job. The standard never does.

Matt Houldsworth, Founder, Software Delivered

Matt Houldsworth

Founder, Software Delivered

Matt has spent thirty years building software that has to work, from systems handling a hundred million database transactions an hour to ecommerce platforms turning over millions of pounds a month. He founded Software Delivered to price development honestly and to rescue the projects other people walked away from.

Software that needs rescuing?

Tell us what is going wrong and we will price the fix up front. No hourly billing, no commitment.