Ask a CNC shop owner how work is tracked and the answer is often, "I know it." Jobs, priorities, who is waiting for what, which customer is nervous: it is all in a few heads, and it works. The shop ships. Customers come back.

So the fair question is: what is it costing, if it works? The cost is real, but it is hidden. It does not show up on an invoice, a machine report or a balance sheet. It shows up as owner hours, as surprises at dispatch, and as a shop that gets quieter and slower when one person is not there.

This article lists what a shop loses when it runs on memory and calls, what a workflow system changes, what it does not change, and how to put a number on your own loss in one week, before you spend anything.

What Running on Memory Looks Like

None of these is a failure of people. They are what happens when information lives only in someone's head or in a phone call:

WhenWhat happens without a system
A customer asks for a dateThe answer is a guess from memory, or a walk and two phone calls. Sometimes it is wrong and you hear about it late.
A job is ready to startIt reaches the machine before the drawing, material or tools are confirmed. The operator stops, or makes it anyway.
The shift changesHandover is a chat at the gate. The next shift finds the real state by asking, or by making a mistake.
Something goes wrongIt is reported by phone, remembered by one person and forgotten by the next day. The same fault comes back.
One person knows how it is doneA setting, a program or a customer habit lives in one head. If that person is away, the job slows or stops.
You want the picture at day endYou ask three people and add up the answers. You have what you were told, not what happened.

If a row sounds familiar, you are not unusual. Most shops that grew by getting good work done are run this way, because it is quick, it costs nothing, and it worked at the size the shop was.

The Four Things It Costs

1 Owner time

If the owner is the source of every answer, the owner is also the bottleneck for every answer. Operators wait for a decision, customers wait for a reply and the day goes on status questions instead of selling, quoting or improving. This is the same pattern we describe in why the shop can't run without the owner, seen from the cost side.

2 Late surprises

When nobody can see a job's state, a delay is found at the end, not when it starts. A job that has waited three days for material looks the same as one that is on track, until the customer calls. The loss is not only the late job. It is the lost chance to warn the customer, move the schedule or chase a supplier while there was still time. Where jobs actually lose their time is a topic of its own, covered in machines busy but jobs still late.

3 The same problems, again

A breakdown that is reported by phone and fixed the same day feels handled. But if nobody wrote down what happened, who acted and how long it took, you cannot see that it is the third time this quarter. Fixing a problem once is firefighting. Seeing a pattern is how it stops coming back. When every job is urgent is often this loop: a cause nobody recorded, producing an emergency again.

4 Dependence on one person

Some knowledge is in one setter's hands, one supervisor's memory or one clerk's notebook. Nothing is wrong until that person is away, leaves, or gets busy. A written handover helps, which is why we wrote the shift handover checklist. The point is the same: what is written can be used by more than one person.

What a Workflow System Changes

A workflow system, in plain terms, is the working rules of your shop written down plus a simple tool that holds them, so that each job has a status, a person and a next step that anyone can read. What it is meant to change:

  • "Where is this job?" is answered by looking, not by walking or phoning. (More on that here.)
  • A job is marked ready only when what it needs is in place, so the gap is named before the machine is loaded.
  • Each job carries a written status, where it stopped and the next step, so the next shift reads it.
  • A problem has a named owner and a record from reported to closed, so repeats become visible.
  • What is needed to run a job is written against the job, so more than one person can pick it up.

These describe what a system is designed to change. Whether it does so in your shop depends on your shop, which is why we confirm targets at a Review and never promise results in advance.

What It Does Not Change

This is the part sellers skip, and it is where shops get hurt:

  • It does not set your rules. If nobody has decided what counts as urgent, who may approve a rush job or what a job needs before it starts, a system will record the argument. Write the rules first. We explain that order in Excel vs ERP vs a Workflow System.
  • It does not run on its own. If operators do not update it, it is only a nicer way to be wrong. A system needs a few minutes of discipline a day, and coaching until that is routine.
  • It does not fix capacity. If you have more orders than machines, you have a capacity problem. A system will show it sooner, which is useful, but it will not make hours.
  • It is not needed by every shop. A shop with a handful of jobs and one person who sees everything may do very well with a board and three written rules. Be wary of anyone who says otherwise without looking at your floor.

Measure Your Own Loss in One Week

You do not need software or a consultant to find out whether this is costing you. For five working days, keep a simple log on one sheet of paper. Ask the supervisor or planner to keep one too, if you can.

What to writeWhy
Each time you or the supervisor is asked "where is job X?" or "what runs next?": a tick and the minutes it took to answerShows how much of the day goes on status questions
Each time an operator waits for a decision, drawing, tool or material: what for and for how longShows waiting that nobody sees
Each problem that happens (breakdown, mix-up, rework): what, when, who acted, time to closeShows whether the same ones repeat
Each job that will be, or is, late: when you first knewShows how late you hear about delays
Anything only one person could do or explainShows dependence

At the end of the week, add up three things: owner and supervisor minutes on status questions, operator waiting minutes, and the number of repeat problems. Those are your figures, from your shop, in your own hours. If they are small, you have saved yourself a project. If they are not, you now know where to look first.

To see what the waiting in the second row ties up in money, use the WIP calculator with your own numbers. If you are unsure whether a floor-level system or something else fits, the Software Fit Check takes a few minutes and sends nothing unless you choose to.

When to Act, and What to Do First

The signs that it is time to act are simple: the owner is the answer to everything, the same problems repeat, delays are found at the last minute, and the shop slows down when one person is away. If two or three of these are true, the one-week log will probably confirm it.

What to do first is not a purchase. It is to write down the few rules that decide how work moves: who can approve what, what counts as urgent, what a job needs before it starts. Then make the status of each job visible, on a board if it has to be. Only when the number of jobs is more than people can keep current by hand does a tool earn its place.

How We Solve This

At KeshRaghTech we start with a free floor walk: we look at how work actually moves through your shop and tell you honestly whether you need a system at all. If the problems are there, the Operational Workflow Review traces real jobs, finds what each one waited for, and sets out the few rules that cut the biggest loss, for a fixed fee told up front. Only then do we build a workflow application around how you run, and we coach your team until working this way is routine. Many shops need less than they expect, and we say so.

Book a free floor walk