A machine downtime and scrap tracker for the plant floor

The short answer

A machine downtime and scrap tracker lets operators log every stop and every scrapped part at the machine in a few taps, with the machine, the time, the reason from a set list and a note or photo. Maintenance and supervisors are alerted to long stops, and the reports rank reasons by lost time and lost parts, so the plant fixes the causes that cost the most first. You can describe it in plain words and have it running on the floor the same day.

Every plant manager knows downtime is expensive. Far fewer can say exactly which machine, which reason and which shift cost them the most last month. On many floors, downtime lives on a whiteboard that is wiped at shift change, a paper log at the machine filled in at the end of the shift, or a spreadsheet the supervisor updates when they have time. Scrap goes into a bin and gets counted, maybe, on Friday. The numbers that reach the weekly meeting are rough, late and argued over.

A downtime and scrap tracker captures each stop and each scrapped part at the moment it happens, with a reason, and turns them into reports that rank where the time and material go. This guide covers what the current way costs, exactly what the tracker should contain, a plain-words request you can hand to FORGE, a rollout plan for the floor, the mistakes to avoid and how to measure the result. It is written for plant managers, production supervisors, continuous improvement leads and owners of small and mid-size manufacturers.

What the current way costs you

Short stops disappear. A two minute jam does not seem worth writing down. Twenty of them a shift is a lost hour that never appears anywhere.
Reasons get written from memory. At the end of the shift, a forty minute stop becomes "machine down" with no cause.
Maintenance hears late. The operator calls a supervisor, who calls maintenance, who arrives without knowing what failed.
Scrap is counted, not explained. You know how many parts went in the bin, not why, so the same defect keeps coming back.
Meetings argue about the numbers. Without trusted data, improvement meetings spend their time debating what happened.
Improvement work aims at the loudest problem. The machine that fails dramatically gets attention, while the one that loses time quietly every shift does not.
Plant systems can be heavy. Full manufacturing execution systems are powerful, but for a small or mid-size plant the cost, the setup and the integration work can delay results for a long time. Many plants just need reliable stop and scrap data first.

What the tracker should contain

Roles

Operator: logs stops and scrap at the machine, adds notes and photos.
Maintenance technician: sees open mechanical and electrical stops, records the response, the fix and parts used.
Supervisor or shift lead: sees the live status of every machine on their shift, confirms reasons, closes shift reports.
Quality: reviews scrap reasons and defects, links them to corrective actions.
Plant manager or continuous improvement lead: reports, reason lists, targets and settings.

Machines and schedule

Machine or work center name, line or cell, type, ideal cycle time or rate, and whether it is scheduled to run on each shift.
Shift definitions with start and end times and planned breaks.

Downtime events

Machine, start time, end time (or "still down"), duration, reason category, specific reason, operator, shift, note, photo, and whether maintenance was called.
Reason categories, for example: Mechanical, Electrical, Tooling, Material (shortage or wrong material), Quality hold, Changeover, Waiting on operator, Waiting on maintenance, Planned maintenance, Planned break, Other.
Specific reasons under each category, written in the words your operators use, such as "jam at infeed," "sensor fault," "die change," "no coil."
Maintenance response: time called, time arrived, what was done, parts used, root cause if known.
Statuses: Down, Maintenance called, Maintenance on site, Running, Reason confirmed.

Scrap events

Machine, time, part number, quantity, defect reason (for example, short shot, dimension out, surface defect, setup scrap, material defect), operator, shift, note and photo.
Optional cost per part, so scrap shows in dollars as well as pieces.

Screens

Machine screen: one tablet per machine or cell with two large buttons, "Stopped" and "Scrap," the current status, and the last few events. Starting a stop takes one tap, choosing a reason two more.
Floor board: every machine as a tile: green running, red down with the minutes counting, amber waiting on maintenance. This goes on a screen in the supervisor's office or on the floor.
Maintenance queue: open stops needing maintenance, oldest first, with the operator's note and photo.
Shift report: each machine's downtime by reason, scrap by reason, notes, and a supervisor sign-off.
Pareto reports: reasons ranked by total minutes lost and by scrapped parts or cost, by machine, line, shift and week.
Trends: availability and scrap rate by machine over weeks, with targets.

Notifications

Maintenance: a mechanical, electrical or tooling stop is logged, with the machine and note.
Supervisor: any stop longer than a set number of minutes, any machine down at shift change, scrap over a set quantity in an hour.
Plant manager: a daily summary and a weekly Pareto.
Quality: scrap reasons you mark as quality-related.

Rules worth building in

Short stop threshold: stops shorter than a set time can be logged with a single tap and a reason later, so operators do not skip them.
Required reason before close: a shift report cannot be signed off with stops that have no reason.
Note required on Other.
No overlapping stops on the same machine.

Example request

Example request: "Build a downtime and scrap tracker for our 18 machines across three lines and two shifts. Each machine has a tablet showing Stopped and Scrap buttons. When an operator taps Stopped, start the clock, then let them pick a category and reason from our list: mechanical, electrical, tooling, material, quality hold, changeover, waiting on operator, planned maintenance and other, each with specific reasons I will provide. Other requires a note. If the category is mechanical, electrical or tooling, notify maintenance right away with the machine, reason, note and photo, and let maintenance record when they arrived, what they did and parts used. When the machine runs again, the operator taps Running. Scrap logs a part number, quantity, defect reason and optional photo; each part number has a cost. Show a floor board with every machine green, red with minutes down, or amber waiting on maintenance. Text the shift supervisor when any stop passes 15 minutes. At the end of each shift, the supervisor reviews and signs the shift report; it cannot be signed if any stop lacks a reason. Give me weekly Pareto charts of minutes lost by reason and scrap cost by reason, by machine, line and shift, and availability and scrap rate trends by machine."

Comparing the options

Capability	Whiteboard and paper log	Spreadsheet	Manufacturing execution system	Your own tracker
Stops logged as they happen	Rarely	Rarely	Yes	Yes
Short stops captured	No	No	Often, with machine signals	Yes, one tap
Maintenance alerted at once	By phone	No	Usually	Yes
Scrap with reasons and cost	Counts only	Partly	Yes	Yes
Reasons in your operators' words	Yes	Yes	Within its setup	Yes
Time to first useful report	Weeks, by hand	Days, by hand	Usually months to implement	Days

Rollout plan

Write the reason list with operators. Sit with two or three operators per line. Use their words. Keep it to what fits on one screen per category.
Decide what counts. Are changeovers and breaks logged? What is the short stop threshold? Who confirms reasons?
Set up machines and shifts. Names that match the tags on the floor.
Mount tablets where operators can reach them with gloves, protected from coolant and dust.
Pilot on one line for two weeks. Pick a line with a supervisor who wants better data.
Review the data with the crew every day of the pilot. Show them the Pareto. When they see their reports turn into fixes, logging becomes worth their time.
Fix one top reason during the pilot, even a small one, and tell everyone.
Roll out line by line, with the pilot supervisor helping train.

Mistakes to avoid

Using data to blame operators. If downtime logs turn into a tool for blame, people stop logging honestly. Frame it as finding what gets in their way.
Too many reasons. Fifty reasons on a tablet produce random picks. Start small and split later.
Logging at end of shift. The value is in capturing the stop as it happens.
Ignoring short stops. They often add up to more time than the dramatic breakdowns.
Collecting without acting. A weekly Pareto that nobody acts on teaches the floor that logging is pointless. Commit to one improvement per week or month from the top of the list.
Not including maintenance. Maintenance response times are part of downtime. Their side of the record matters as much as the operator's.

How to measure that it works

Share of stops with a confirmed reason, aiming for nearly all of them.
Availability by machine: running time against scheduled time, week over week.
Minutes lost to the top three reasons, before and after you work on them.
Maintenance response time from call to arrival.
Scrap rate and scrap cost by machine and reason.
Time spent preparing the weekly production meeting, which should fall to minutes.

Checklist before you build

List machines, lines and shifts, and which machines run on which shifts.
Write reason categories and specific reasons with operators.
Write scrap defect reasons with quality.
Decide on planned stops, short stop threshold and alert times.
Decide who confirms reasons and signs shift reports.
Add part numbers and scrap cost per part, if you want dollars.
Choose and mount tablets for the pilot line.
Set a regular review meeting and commit to acting on the top reason.

How FORGE handles it

With FORGE, your plant manager or continuous improvement lead describes the tracker in plain words, like the example above. A panel of top AI models plans it, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, with tablet screens at the machines, a floor board for supervisors and desktop reports for the office.

Every app lives inside your company and only the people you invite can get in. Roles decide who builds and who uses, and operators, technicians and supervisors who only use the tracker are free, so every machine can have a screen without adding a bill. FORGE keeps a complete record of who did what. When you split a reason or add a machine, describe it; a change costs a small fraction of a build and only counts when something actually changes.

It is $49 a seat a month for each person who builds, with 3 builds included, and packs of 10 builds for $150 when you need more. Our team onboards every plant starting with a workflow workshop, on your real floor problems. Talk to us.

Questions people ask

What counts as downtime?

Any time a machine is scheduled to run and is not running. Decide whether planned stops such as changeovers, breaks and planned maintenance are logged as downtime with their own reasons or kept separate. Most plants log them, so the reports show the whole picture of where scheduled time goes.

How many downtime reasons should we have?

Enough to point to action, few enough that operators pick the right one quickly. A common approach is a short list of categories, such as mechanical, electrical, material, quality, changeover, waiting on operator and planned, each with a handful of specific reasons. Review the list after a month and split any reason that is too broad.

Should operators log downtime, or should the machines?

Both have a place. Sensors and machine signals capture when a stop starts and ends without anyone typing, but only a person can say why. Many plants start with operator logging, which works on any machine, and add automatic signals on key equipment later.

What is OEE?

OEE, overall equipment effectiveness, is a common measure that multiplies three things: availability (running time against scheduled time), performance (actual speed against ideal speed) and quality (good parts against total parts). A downtime and scrap tracker gives you the availability and quality pieces directly.

How do we stop people from picking 'other' every time?

Make the list match how people talk about stops, put the most common reasons first, require a note when someone picks other, and review the other entries weekly to add reasons that keep appearing.

How quickly can we have it on the floor with FORGE?

Most teams have their first real tool the same day. Start on one line or one cell, prove it for two weeks, then roll it out machine by machine.

See what FORGE builds for your team

We onboard every team ourselves, starting with the work that costs you the most time.

Talk to us