Walk into almost any factory and ask a simple question: “How many parts did you produce today?”
You’ll hopefully get an answer, but it’s often slower, less certain, and more manual than it should be.
Someone checks a spreadsheet.
Someone looks for a clipboard.
Someone sends a message to confirm the number.
Although a lot of manufacturers already track production output, especially those in high-throughput environments. But in many cases, production tracking is still disconnected, delayed, and difficult to trust.
And that creates a bigger problem: If your production data isn’t available in real time, you can’t use it to improve performance. Across industries, from mining to construction to automotive, manufacturers are moving away from manual paper-based part counting and toward real-time production tracking on the shopfloor.
Here’s what that shift looks like in practice.
In many factories, part counting still relies on a mix of:
Paper records
End-of-shift estimates
WhatsApp or informal messaging
Spreadsheet consolidation
Individually, these don’t seem like major issues. But together, they create a system where:
Data is delayed
Numbers are inconsistent
Reporting takes time
And decisions are based on outdated information
This inefficiency limits your ability to improve output, reduce downtime, and respond to issues as they happen. So what happens when production data and parts produced are captured in real time? In this next section, we look at three use cases from FourJaw customers who manufacture very different products, but have gained huge amounts of value after switching from manual processes to capturing production counts within FourJaw.
A manufacturer of certified, bespoke doorsets operating at multiple UK sites was already using FourJaw for CNC utilisation and downtime, but it still relied on manual/rough counts for “doors made per day”, until they made the change to incorporate FourJaw's part count into their processes.
End-of-shift estimates and notes for completed doors.
Leadership could see when CNCs were busy, but not confidently how many good doors were finished per day or month.
Manual Part Count turned on at CNCs; operators log good and scrap doors on tablets.
Counts flow into FourJaw reports alongside utilisation and downtime, feeding Louis’ and the board’s reporting.
Replaced rough, manual counts with reliable “doors per day” data.
Can now connect CNC improvement work (setup, programming, scheduling) directly to extra doors shipped, not just % utilisation.
Use case 02: High-throughput, Aggregate product manufacturer
This use case focuses on a high-throughput production process where uptime directly translates into tons of stone out the door. The work is physically demanding: when lines stop, operators are often stuck lugging bags and material around; when everything runs smoothly, they can monitor the process in a far more controlled, less physical way.
The team already understood how critical part counts and stoppage tracking were – but the way they captured that information was holding them back.
Operators sent hourly part counts via a WhatsApp group on personal phones, in an area with poor 4G.
Paper downtime books were manually typed into a big, slow Excel after the fact.
Operators log good parts and scrap directly in FourJaw on tablets; no dependence on phone signal.
Downtime reasons are logged in the same place, replacing paper and manual Excel entry.
John, the manager, sees live part counts and stoppages on his screen.
WhatsApp and the paper-to-Excel process were effectively eliminated.
Faster, clearer view of output and downtime; easier to spot recurring issues.
Strong operator buy-in because fewer stoppages mean less heavy manual handling and more time monitoring the line.
Use case 03: Discrete process, Automotive OEM Manufacturer
This use case focuses on a high mix, low volume environment with CNC machining, saws and cut and bend operations across 24 machines.
When this Automotive OEM manufacturer first deployed FourJaw, the immediate focus was on visibility: uptime, downtime and utilisation across the machine shop. Over 2025–26, they pushed utilisation from a historic ~20% up to 24% in January, 39% in February and 48% in early March, by improving downtime labelling and cleaning up unlabelled time.
But there was still a gap: how many good parts were actually being produced, and how did that compare to plan?
Part counts written on paper, keyed into spreadsheets, emailed around – disconnected from utilisation and downtime.
Hard to answer: “Are we getting the output we expected from these hours?” or “Are we overloading the machines vs the 8 operators we actually have?”
Manual Part Count enabled on tablets: operators log good and scrap parts during jobs.
FourJaw generates production quantity reports and CSV exports with job reference, machine, timestamps and quantities.
The production and operations teams use the FourJaw API to pull utilisation/downtime data into Power BI/Excel, and are beginning to tie part counts into director-level KPIs for plan vs actual.
Manual part counting is moving from ad hoc spreadsheets to a repeatable, system-driven flow, while keeping a paper backup only as needed.
Supervisors are being trained to use dashboards and counts to own their performance and brief their teams, not just rely on central reporting.
Creates a foundation where Lotus can answer “Are we getting the right parts out for the time and people we’re putting in?” with data instead of gut feel.
Manual vs real-time part counting: What actually changes
Although these manufacturers operate in very different sectors, the shift they made is fundamentally the same. They moved from manual production tracking to real-time, operator-led data capture.
Here’s how that transformation compares:
|
Manual Part Counting (Old Way) |
Real-Time Production Tracking (New Way) |
Operational Impact |
|
|---|---|---|---|
|
How data is captured |
Paper, spreadsheets, messaging apps |
Logged directly by operators on shopfloor devices |
Immediate, consistent data capture |
|
Timing of data |
End of shift or later |
Captured in real time |
Faster response to issues |
|
Data accuracy |
Inconsistent, prone to errors |
Standardised and structured |
Greater trust in production data |
|
Visibility |
Limited, delayed reporting |
Live view of output, downtime and scrap |
Better decision-making |
|
Use of data |
Historical reporting |
Active performance management |
Shift from reactive to proactive |
Most manufacturers don’t need to rethink their entire operation to improve production tracking.
They’ve already done the hard part, they care about the data, and they’re already collecting it in some form.
The opportunity is to make that data:
Real-time instead of delayed
Consistent instead of fragmented
Actionable instead of purely historical
Because once you can trust your production numbers, you can start using them to drive meaningful improvement, as the three use cases in this article have shown.
To get Part Count set up in your FourJaw account, visit our knowledge base or contact your customer success manager.