Why Spreadsheets Fail at a Second Location

The short answer

A spreadsheet works while one person holds the whole picture in their head. A second location means two people editing, two versions of the truth and no way to see the combined position. The fix is one shared system where each location enters data once and everyone sees the same numbers.

What goes wrong, in order?

The problems tend to arrive in this order.

• Two copies: each location keeps its own file. Someone emails them around, and by the time they are merged, they are out of date.
• Nobody trusts the totals: combined stock or sales is built by hand, and different people get different answers to the same question.
• No clear owner for a number: when a figure looks wrong, nobody knows who changed it, when, or why. Some spreadsheet tools keep a version history, but that is not the same as a record of who approved a change and why.
• Manual re-entry: orders typed from one sheet into another, and from there into billing, multiply errors with every step.
• No permissions: anyone with the file can change anything, including prices and formulas.

Why does a second location make it worse?

With one location, the cost of these problems is small and absorbed by one careful person. A second location multiplies the points where data is entered and removes the person who held it all together. The business gets slower at the exact moment it is trying to grow.

What should you put in place instead?

You do not necessarily need a large system. You need four things.

• One record for each thing: a product, a customer or a stock count exists once, and every location sees the same entry.
• Entry once, at the source: data is captured where the work happens and flows onward without being retyped.
• Roles: each person can see and change only what their job needs.
• A history: every change is recorded with who made it and when.

When is it time to move?

If you recognise three or more of the problems above, the cost of staying is probably higher than the cost of changing. The simplest test is whether your team spends noticeable time each week reconciling numbers rather than using them.