This article is about what breaks first when a job shop runs multi-department production out of a shared spreadsheet, and what a replacement has to do. It is not a pitch for a platform. If your tracker works, keep it. If it only works because one person holds the whole picture in their head, read on.
What the Excel Production Tracker Is Good At
Excel earned its place on the floor. It is worth saying why, because a replacement that ignores these strengths will not get adopted.
- It is fast to start. A planner can add a purchase order as a new row in seconds, with no training and no IT project.
- Everyone already reads it. The columns are familiar, the color coding is understood, and in many shops the headers run in two languages.
- It is fine for one owner. When a single person maintains the file and order volume is low, the workbook holds together.
The trouble starts when the workbook stops being a log and becomes the way several departments find out what to do next.
What Breaks First on a Multi-Department Floor
The same four failures show up in almost every shop that outgrows its spreadsheet. They tend to arrive in this order.
1. Dates are typed, not derived
The promised ship date is real because the customer gave it to you. Every date between the order and the ship date is somebody's guess, or a formula that went stale the last time someone inserted a row. Nobody fully trusts the guidance column, so people stop reading it and ask each other instead.
2. One workbook, many editors
CNC updates a cell. Injection never sees it, because they are looking at their own saved copy. Planning finds the slip in the weekly meeting, days after it could have been absorbed. Shared workbooks do not fail loudly. They drift quietly out of agreement.
3. Dependencies are tribal knowledge
Assembly knows it cannot start until overmolding is done, because it has been burned before. The sheet does not know that. Nothing marks an order as ready or as waiting, so ready is whatever the loudest phone call says it is.
4. Delays do not cascade
A problem on a CNC step should push mould, injection, assembly, and the ship date. In a spreadsheet it pushes nothing. The order stays green until the day it is late, and by then the only options left are expediting and apologizing.
Why "Just Move It to ERP" Is the Wrong Next Step for Most Job Shops
When the workbook hurts enough, the usual advice is to buy an ERP. For a job shop that mostly needs to see the order through its departments, that tends to be the wrong leap.
- ERP is built around accounting, inventory valuation, and purchasing. It does not automatically give a department a calm queue of what to work on next.
- A full manufacturing execution system implies plant standards, scanners, and a long implementation. Most shops leaving Excel are not asking for that.
- What they are asking for is narrower: one live view from purchase order to ship date, and a queue each department can trust.
There is an honest middle between a spreadsheet and a plant-wide system. It is production planning and shop-floor execution for the order path, without pretending to run the finances.
What Good Looks Like Without the Spreadsheet
Whatever you use, the replacement should do these five things.
- Take the order once. The planner enters the purchase order and the promised ship date a single time.
- Derive the steps and dates. The order expands into department steps, and the plan is back-scheduled from the ship date using standard times instead of typed guesses.
- Give each department its own queue. Work is grouped by what can happen now: ready, in progress, problem, or waiting on upstream work.
- Let delays move the plan. A late or blocked step shifts the work that depends on it and the projected ship date, so the slip is visible the day it happens.
- Work in the languages on the floor. For shops that plan in English and run the floor in Chinese, both should show the same live data, not two parallel files.
That is the job Asytra Flow is being built for. Flow is production planning and shop-floor execution for job shops, and it is in pilot now with access by invitation. It is not an ERP and not a full MES. The Flow overview explains what it covers and what it leaves out.
Where Flow Sits Next to Trace
If you already know Asytra Trace, the split is simple. Trace runs the digital work instructions and records who did what on each serial number. Flow schedules the order across departments and tracks it from purchase order to ship date. A shop can use either one alone, or both.
Ready to Leave the Shared Workbook?
You do not have to retire Excel on day one. Start by writing down the four failures above and counting how many your shop hits in a normal month. If the answer is most of them, the spreadsheet has stopped being a log and become the system, and it was never built to be one.
Flow is in pilot, with no public pricing yet. See Asytra Flow for the overview, or contact us to join the waitlist and tell us how your departments are set up.