September 20, 2026 · Business

Still Scheduling Production in Spreadsheets? The Real Cost, and When to Move

This article will not tell you spreadsheets are evil. A spreadsheet schedule is rational: it costs nothing, everyone knows the tool, and it bends to whatever the week throws at you. We build Voltrus MES and even we will say it: for a workshop with one line and one product, the spreadsheet is often the right answer.

The trouble is that factories do not stay that size. The schedule that worked at one line starts costing money in specific, findable places. This article names those places, so you can tell the difference between "the spreadsheet is fine" and "the spreadsheet is the bottleneck we stopped seeing."

Why the Spreadsheet Wins at First

Give the tool credit. A spreadsheet schedule needs no procurement, no training beyond what people already have, and no agreement on requirements. It absorbs every exception: the rush order, the machine down until Thursday, the material that arrived short. A formal system needs those exceptions configured. The spreadsheet just gets edited.

That flexibility is real value, and it is why "just buy a MES" is bad advice delivered without context. The question is not whether the spreadsheet works. It is what breaks as volume grows.

Five Places the Spreadsheet Starts Costing Money

1. Version chaos

The schedule lives in one file, and production, purchasing, and sales each hold a copy. Copies drift. Someone promises a delivery date from last Tuesday's version, and the disagreement surfaces at packaging, not at planning. The cost is not the file; it is every conversation that starts with "which version are you looking at?"

2. Feedback arrives after the fact

A spreadsheet records what someone believed or typed. It does not know that line 2 stopped for forty minutes. Actual output, scrap, and downtime get typed in later, from memory or from paper travelers, and by then the number is an opinion. Scheduling decisions made on lagging, softened data drift further from the floor every month.

3. Traceability is rebuilt by hand

When a customer complains or an auditor asks, the spreadsheet cannot answer "which batches ran on which machine, with which material lot, last March?" The answer gets reconstructed from travelers, operator memory, and whatever the WhatsApp group remembers. Every reconstruction costs days, and the reconstruction is only as good as the paper it survives on.

4. Key-person risk

Every factory like this has one person who understands the file: the formulas, the hidden columns, the order things must be updated. When that person resigns, takes leave, or simply gets sick during a critical week, planning reverts to improvisation. The schedule has a bus factor of one.

5. Losses stay invisible

Downtime, scrap, and changeover time live in separate places (if they are recorded at all), so no order carries its true cost. You know the month's totals; you cannot see which orders or shifts ate the margin. Pricing becomes a guess repeated with confidence.

The Middle Path: Keep the Spreadsheet, Add the Floor

Here is the part vendors skip: you do not need to replace the spreadsheet in one move, and you should not. The pattern that works for mid-market factories:

• Digitize the feedback first: counts, scrap, and downtime recorded at the line, automatically from machine data. The schedule can stay a schedule; it just starts getting fed real numbers.
• Digitize traceability second: unit-to-machine-to-lot links accumulate quietly in the background. The first audit that would have taken a day now takes minutes.
• Move dispatch last: once the floor reports truth, the work order moves from the spreadsheet to the terminal at the line, and the schedule becomes a plan instead of a wish.

This is the order Voltrus MES follows with pilot sites, and it is why the pilot starts at one line with the data collection already handled by Voltrus SCADA or Voltrus OEE if you run them.

What Moving Actually Takes

Not the enterprise project. One line, a terminal at the station, machine data from the systems already in place, and someone from the vendor sitting with your team for the first runs. If a proposal in front of you requires new data collection wiring, a plant-wide license, and a go-live date in a different fiscal year, you are being sold the heavyweight product, and most factories should walk.

Frequently Asked Questions

Is Excel bad for production scheduling?

No. Excel is a fine tool for planning, and it remains useful even after a MES arrives (scenario comparison, what-if analysis, long-term capacity). The problem starts when the spreadsheet is also the only record of what the factory actually did. Planning in Excel and executing in a MES is a healthy combination; executing in Excel alone is the trap.

What is the smallest first step?

Automatic counting at one line. Before any scheduling change, get real output and scrap numbers flowing from the machines. Every later decision (about software, about shifts, about pricing) gets smarter the day those numbers exist. That step is small enough to run during the Voltrus MES pilot without touching your schedule file at all.

How do we know we have crossed the line where a spreadsheet stops working?

Watch for the tells: two versions of the schedule in circulation, scrap numbers nobody trusts, a traceability question that took days, or a planning process that stops when one person is away. One tell is an annoyance. Two or more mean the factory has outgrown the tool.

Keep reading

Guides What Is a MES? Manufacturing Execution Systems in Plain Language September 20, 2026 Comparison MES vs ERP: Which System Runs the Factory Floor September 20, 2026