The Mould That Ran Over and Nobody Noticed Until It Was Done

The Mould That Ran Over and Nobody Noticed Until It Was Done

By Nevil Darukhanawala | Series: Tool Die & Mould Week

Picture a mould in the middle of its build. It was quoted four months ago at a number everyone was comfortable with. The design is done, the steel is roughed out, the cavity work is underway, the first trial is a few weeks off. Walk through the shop and it looks like a job going well — people working, machines cutting, progress visible. Ask the owner how the job is doing against its quote, though, and you’ll get an honest shrug. “Looks fine.” Not because he’s careless, but because there is no running number anywhere that says how far this particular job has drifted from what he priced it at. He’ll know at the end. Right now, “looks fine” is genuinely the best answer available.

That gap — between a job that looks fine and a job you can actually see is fine — is where tool rooms quietly lose their margins. And the losses don’t announce themselves. They accumulate, hour by hour, on a job nobody is watching closely, until the job is finished and the damage is a fact.

Overruns don’t arrive. They accumulate.

The reason a mould overrun is so dangerous is that it’s never a single event you could catch. It’s a slow stacking of small, individually reasonable overruns, each one landing on a price that never moves.

The design was quoted at, say, a certain number of hours. The customer asked for two changes mid-design — reasonable requests, the kind you don’t push back on for a good client — and suddenly the design has taken half again as long as quoted. Nobody flagged it, because each change felt small in the moment. Then the cavity machining runs longer than planned — the geometry was trickier than it looked on the drawing, an electrode had to be remade, a block was scrapped and re-cut after an error. Then the trials: the first shots show a problem, so it’s back to the bench for correction, then a second trial, then a third. Every loop is days of skilled labour and machine time and material.

Not one of these is unusual. This is simply what building a complex mould involves. But here’s the trap: each overrun lands quietly, in a different part of the shop, recorded in a different place — design hours in one system, machine time in another, scrap in a third, the original quote in a job file nobody’s reopened since the job started. No single person is watching all of them stack up against the quote for this specific job. So the overruns accumulate invisibly, and the first time anyone sees the total is when the job is done and someone — maybe — adds it up.

Why “we’ll review it at the end” guarantees the loss

Most tool rooms do review jobs at the end. They’ll tot up roughly what a big job took, compare it loosely to the quote, and sigh if it ran over. The problem is that end-of-job review, by definition, happens when nothing can be done. The hours are spent. The material is consumed. The customer has been invoiced at the fixed price. Reviewing an overrun after the job ships is exactly like the manufacturer who studies last month’s losses in this month’s accounts — accurate, instructive, and far too late to change the outcome.

And because the review is loose and after-the-fact, it rarely even produces a usable lesson. “That job ran over” is not information you can act on next time. Why it ran over — that the design changes ate the margin, or that the trials looped one time too many, or that the cavity machining was systematically underquoted for that complexity of part — that’s the lesson, and it’s exactly what a rough end-of-job glance doesn’t capture. So the same kind of job runs over the same way next time, and the time after that.

The only review that actually protects a job is one that happens while the job is still running — when seeing that design hours have blown past the quote means you can still have the scope conversation with the customer, still decide whether the next trial loop is worth it, still manage the job to a better ending. Once the mould ships, you’re not managing anything. You’re just recording what happened.

What it means to be warned mid-build

Now imagine the same mould, run with visibility. Three weeks in, you can see — not guess — that the design hours have already exceeded what you quoted, because the design time logged against this job is sitting right next to the quoted figure, and the gap is plain. You can see the cavity machining is trending over too. The job that “looks fine” to everyone walking the floor is visibly, numerically drifting, and you know it now, with months of build still ahead, instead of at the end.

That single piece of early knowledge changes what you can do. You can go to the customer about the two design changes they asked for and have an honest conversation about scope and cost — a conversation that’s completely reasonable mid-build and completely impossible after you’ve delivered. You can decide whether that third trial loop is genuinely necessary or whether you’re chasing a perfection the job can’t afford. You can put your best fitter on the operation that’s eating hours. You can, in short, manage the bet while it’s still live — which is the only time management is worth anything.

None of this requires distrust of your team or hovering over every job. It requires only that the numbers already being generated — the design hours, the machine time, the material, the trials — be assembled against each job’s quote and shown to you while the job is still on the bench. The data is being created anyway, every day, as your people work. The only question is whether it reaches you in time to act, or only in time to mourn.

The job that looks best is the one to watch

Here’s the counterintuitive part that catches owners out. The job most likely to quietly ruin your month isn’t the one that’s obviously in trouble — the one with the angry customer or the visible disaster. Those get attention precisely because they’re loud. The dangerous job is the big, important one that looks like it’s going well, because looking well is exactly what stops anyone from examining it. It’s busy, it’s progressing, the customer’s happy — and underneath, the hours are quietly running 30% over quote, and nobody will know until it’s a finished, invoiced, unchangeable fact.

That’s why “looks fine” is the most expensive phrase in a tool room. A job that looks fine and a job you can prove is fine are completely different things, and the gap between them is exactly where the margin goes. The only way to close that gap is to be able to see each job’s real cost against its quote, continuously, while there’s still a build left to manage.

The takeaway

Every mould you build is months of skilled work riding on a price you fixed before you fully knew what the job would demand. Whether that job makes the margin you quoted depends on a hundred small decisions made during the build — and you can only make those decisions well if you can see how the job is tracking while it’s still running. Find out at the end, and all you’ve got is a number and a sigh. Find out mid-build, and you’ve got a job you can still steer.

The overrun nobody noticed until it was done was visible the whole time, in your own shop’s data. The only thing missing was someone — or something — putting it in front of you while there was still a mould left to save.

Part of the Tool, Die & Mould series. Start with Every Mould Is a Bet. Do You Know Which Ones You’re Winning? Related: Your Cash Is Sitting on the Shop Floor in Half-Finished Jobs.

— BODY ENDS —