Most small workshops track their jobs on a whiteboard. It works fine until the day it doesn't, and that day always shows up the same way. The floor gets busy. Someone rubs out a line to make room. Two hours later the office phones down asking where the Mahlangu order is, and three people give three different answers.
Knowing where your work is shouldn't be this hard. It isn't, once you stop leaning on a board that one person updates, when they remember.
The board is only honest on a slow week
A whiteboard shows what someone wrote down, last time they wrote anything down. On a slow week that's close enough. The trouble starts when the work moves faster than the marker.
The office can't see the board without walking to the floor. Nothing on it is dated, so you can't tell whether a job moved this morning or last Tuesday. And once you've got forty or fifty live jobs the writing gets too small to read and people quietly stop trusting it. A spreadsheet fixes the visibility problem and hands you a worse one: the board now lives on a screen, but it's still only as current as the last time somebody stopped working to type into it, which on a busy shift is almost never. I went deeper on that trade-off in job tracking software versus spreadsheets.
What you actually need
Forget software for a minute. Any way of tracking work in progress has to handle four things, and most fall over on the first one.
It has to stay current without anyone babysitting it. If keeping the record up to date is a separate job, it won't get done, and a tracker nobody updates is worse than none because people still believe it. It has to be visible to the office and the floor at the same time. It has to remember who had the job, what step it was on, and how long it sat there. And it has to cope with what actually happens on a floor: the welder off sick, a customer who wants half the order today and the rest on Friday.
Make the update part of the work
The fix is to stop treating the record as a separate task. You let the work record itself.
Print a QR code on each job card. When a worker starts on a job they scan it and tap Receive. When their part is done they scan and hand it to the next step. The scan is the update. Nobody keeps a separate board because the board keeps itself.
CNC
scan to receive
Welding
scan to receive
Office
scan to receive
Because a job is offered to a group, say CNC or Welding, rather than to one named person, an absence never freezes it. Whoever is at the machine picks it up. And because every scan carries a name and a time, you end up with the thing the whiteboard never gave you: a full history of each job, and real numbers on how long the work takes. That last part quietly pays for itself the next time you quote.
Don't map the whole factory on day one
You don't need every step in the system before it earns its keep. Start with the one or two handovers where jobs go missing, usually the gap between two areas, and add the rest once people are in the habit of scanning.
What changes on the floor
The office stops walking down to read the board. A customer phones, and someone answers in ten seconds. Part-deliveries stop being a headache: a worker completes the forty units that are ready, those forty split off as a finished job you can invoice, and the other sixty carry on. Nothing goes out the door and then gets forgotten at invoicing, because finished work lands in one queue and waits there until someone bills it.
None of this is clever. It's the same job moving through the same steps you already run. You've swapped a marker for a scan and given yourself a memory in the process.
If you want to see the whole thing end to end, how it works walks through it. Or skip the reading and start a free trial on a handful of your own jobs.