Tool Life & Wear Tracker: Change Cutting Tools Before They Make Scrap
Log every cutting-tool and insert as it runs, accumulate usage against the tool's expected life, and alert when a tool is near end-of-life — so a lead approves the change-out before bad parts start, and you don't toss tools with life left.
A logged-in web app where operators log tool usage (which tool ran which job, on which machine, for how many parts or minutes), the tool accumulates usage against its expected life, the app alerts when a tool is near end-of-life, a lead reviews and approves the change-out or a life-extension, and the replacement is recorded — plus an exportable tool-life log and a consumption report for perishable reorder.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your list of tool types with their expected life (parts, run-minutes, or wear) and a sample of how you record usage today
- Claude Code or any AI coding agent
The problem this kills
A carbide insert is rated for maybe 300 parts. Nobody's counting. So one of two things happens, and both cost you. Either the operator runs it too long — the edge breaks down, the finish goes off, and you find out three bins of parts later that everything since lunch is scrap or rework. Or the operator plays it safe and swaps a perfectly good tool with half its life left, and you quietly burn through your perishable-tooling budget changing inserts that were fine.
The knowledge of "how many parts is this tool good for" lives in a binder, a setup sheet, or somebody's head. There's no running count tied to the actual tool that's in the spindle right now, no warning before it's about to go, and — worst of all — when a tool does fail, no record of which jobs ran on it, so you can't go find the suspect parts. You don't need a six-figure tool-management system to fix this. You can build exactly the tracker your shop needs, this afternoon.
What you'll build
An internal web app for your shop floor. An operator logs a usage entry — this tool ran this job on this machine, and made this many parts (or ran this many minutes). The app accumulates that usage against the tool's expected life and shows a simple gauge: how much life is left. When a tool crosses your warning threshold (say 85% of rated life), it lands on a near-end-of-life list and emails a lead. The lead reviews and makes the call: approve the change-out, or extend the life by a set amount when this particular tool is clearly still cutting clean. Either way it's recorded with who decided and why. When a tool is changed, the new instance starts a fresh count, and the old one's full history — every job it ran — stays on file. The whole thing exports a tool-life log and a consumption report you can hand to whoever buys perishable tooling.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your shop — how you define tool life (parts cut, spindle minutes, or a wear measurement), your real tool and insert numbering, which machines you run, how an operator records usage today, your warning thresholds, who's allowed to approve a change-out or a life extension, and the messy edge cases like a tool that gets reground, an insert with multiple cutting edges you index, or a tool that breaks early. It reads a short spec back to you for a thumbs-up, then builds the tracker around your shop instead of a generic template. From there it walks the agent through the data model, the usage-logging screen, the life accumulation and gauges, the near-end-of-life alerts, the approve-change-or-extend gate, the replacement flow, and the log and consumption exports. Every step ends with a ready-to-copy prompt.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls a real operation needs: login so only your team can use it, row-level security so a shop or site only ever sees its own tools and usage, and a complete audit trail of every usage entry, alert, approval, extension, and change-out — who, what, and when. The human gate is the whole design: a near-end-of-life tool is never auto-retired and a life is never auto-extended; a named lead or engineer reviews the alert and approves the change-out or the extension before anything is committed to the tool record. And a duplicate guard keyed on the tool instance plus the usage entry stops the same run from being logged twice and double-counting a tool toward end-of-life.
Who it's for
Machinists, CNC operators, setters, and manufacturing engineers who are tired of either making scrap from a worn tool or throwing away tools with life left — and who want, for the first time, a record of which jobs ran on the tool that just failed. If you can tell me how you measure when a tool is "used up," you can build this.
You've got this — open the plan, paste the first prompt, and you'll be logging your first tool's life this afternoon.