Skip to main content
Contact

By Sakshi Shah · 16 November 2026 · 13 min read

Replacing Paper Job Cards: How to Digitise Production Tracking on the Shop Floor

Production tracking software for small manufacturers: what to track, how to design for operators, and how to replace paper job cards without slowing the floor.

Introduction

In many small and mid-sized factories, production is tracked the way it has been for decades. A paper job card travels with the work from cutting to machining to welding to painting. Supervisors keep a notebook. A whiteboard shows today's plan, and photos of it are shared on WhatsApp. When a customer phones to ask whether their order will ship on Friday, someone walks the floor to find the job and ask the operator.

It works — until the business grows. Then jobs get lost between operations, rework is discovered late, nobody can say how much work is sitting in front of the paint shop, and the owner spends evenings piecing together what happened from scraps of paper. Production tracking software replaces the job card and the walk around the floor with a simple digital record of each job's progress, captured as the work happens.

This guide is for owners and production managers of small and mid-sized manufacturers — particularly job shops and make-to-order businesses — who want to make that move. It covers what to track, how to design the system so operators actually use it, what managers get in return, how to connect it to your accounting or ERP, and how to roll it out without slowing the floor down.

What to Track (and What Not To)

The goal is not to record everything that happens in the factory. It is to know, at any moment, where each job is, what is holding it up, and what came out good or bad. That needs surprisingly little data.

InformationOn paper todayIn a digital system
Job or work orderJob card written up by the officeCreated from the sales order, with a QR code printed on the job card
RoutingOperations listed on the card, or known by experienceThe sequence of operations for each job: cut, machine, weld, paint, inspect
Start and finish of each operationSometimes initialled; rarely timedOne scan to start, one to finish, timestamped automatically
Quantities good and rejectedWritten at the end, if at allEntered at each operation, with a reason for every reject
Who and which machineRememberedRecorded with the scan
StoppagesMentioned to the supervisorTapped from a short list: no material, machine breakdown, waiting for drawing, waiting for inspection

Resist the urge to add more at the start: detailed material consumption, labour costing, maintenance records and quality checklists can all come later. A system that captures these six things reliably is far more useful than one that asks operators to fill in twenty fields and gets ignored.

Design for the Operator, Not the Office

Shop-floor systems succeed or fail on one question: is it faster for the operator than the paper it replaces? If recording progress takes longer than initialling a card, data will be entered late, in bulk, or not at all.

Job cardQR travels with the workScan at stationshared tablet orlow-cost phoneno login per scan:tap operator badgeOne big tapSTARTFINISH: good / rejectSTOPPED: reasonLive boardwhere every job iswhat is stuckwhat is latein the operator's own language · works offlineand syncs when Wi-Fi returns
Scan, tap, done. Recording progress should take seconds and less effort than initialling a paper card.
  • Scan, don't type. A QR code on the printed job card identifies the job instantly. Operators tap rather than type wherever possible.
  • Big buttons, few screens. Start, finish, stopped. Quantity with large number buttons. Reasons from a short picture-supported list. Usable with gloves, in poor light, by someone who is not comfortable with smartphones.
  • The operator's language. On a floor in Gujarat, that may mean Gujarati and Hindi; elsewhere, whatever your team speaks. Supervisors and the office can use English on the same data.
  • Shared, inexpensive devices. A rugged tablet or low-cost Android phone mounted at each station or cell, with operators identified by a quick badge scan rather than a username and password.
  • Offline first. Shop-floor Wi-Fi is often patchy. The app should record scans locally and sync when the connection returns, so a network drop never stops work.

Build it with operators, not just for them. Put an early version on one station, watch a shift use it, and fix whatever makes them hesitate. Their acceptance matters more than any feature.

What Managers Get in Return

Once progress is captured as it happens, the questions that used to need a walk around the floor answer themselves.

Live production board (illustrative)CuttingMachiningWeldingPaintingInspection2 waiting · 1 running1 waiting · 2 running2 waiting · 1 stopped7 waiting · 1 running1 waiting · 1 runningstopped: no materiallatelatebottleneck
Illustrative. A queue building in front of one operation, a job stopped for material and two late jobs — all visible without walking the floor.
  • Work in progress by operation — how many jobs are waiting at each station, which shows the bottleneck directly.
  • Late jobs — jobs whose remaining operations will not fit before their due date, flagged while there is still time to reprioritise.
  • Stopped jobs and why — material shortages, breakdowns, missing drawings — so supervisors fix causes, not symptoms.
  • Rejects by reason, operation and product — where quality problems actually start.
  • Actual versus estimated time — which improves future quotes, often one of the biggest commercial benefits for job shops.
  • A real answer for customers — the office can tell a customer exactly where their order is, and eventually let customers see it themselves.

If you later connect machines directly, as described in Getting Data Out of Old Factory Machines, machine running time joins operator scans to give overall equipment effectiveness and a much fuller picture of downtime. Operator tracking is the cheaper starting point, and is worth doing on its own.

Connecting to Your Accounts or ERP

Production tracking should not become another island of data. In most small and mid-sized manufacturers, two links matter most. Work orders should be created from confirmed sales orders in your ERP or accounting system rather than typed again, so the job card carries the right customer, quantities and due date. And completed quantities should flow back, so dispatch and invoicing know what is ready.

Many Indian manufacturers run accounting on Tally alongside spreadsheets for production. Tally can exchange data through its XML and ODBC interfaces or through scheduled imports and exports, and other accounting and ERP systems have their own APIs — the general approach is covered in API & Middleware Development: Connecting Systems That Don't Talk to Each Other. Start with whichever link removes the most re-typing.

Rolling It Out Without Slowing the Floor

Explain why before you explain how. Operators may worry that tracking is about watching them. Be clear that the data is for finding what holds work up — missing material, broken machines, unclear drawings — and then use it that way. Trust is built in the first few weeks by fixing the problems the data reveals.

1

Map one product line

Walk the floor with the supervisor: operations, routing, current paperwork and the stoppages that happen most.

2

Pilot one cell

QR job cards and a device per station on one line, run alongside paper for a week or two.

3

Fix and train

Remove every point of friction operators report; train supervisors first so they can support their teams.

4

Expand and connect

Roll out line by line, retire paper as each line goes live, then add the ERP or accounting links.

Packaged manufacturing execution systems and production apps are worth evaluating, especially if your process is a standard one. A custom tool often fits better when you run a job shop with a different routing for nearly every order, when operators need their own language, or when it has to work closely with your existing accounting and ERP. The general method for replacing paper or spreadsheet processes is set out in How to Turn an Internal Spreadsheet Process Into a Business Application, and the broader buy-or-build question in Custom Software Development: When Off-the-Shelf Software Isn't Enough.

Conclusion

Digitising production tracking is less about technology than about making the right information effortless to capture. Track a small set of essentials — job, routing, start and finish, quantities, rejects and stoppages. Design for operators first: QR codes, big buttons, their own language, shared devices and offline working. Give managers live work in progress, late jobs and the reasons work stops. Connect it to your sales orders and invoicing so data is entered once. And roll it out one line at a time, using the data to fix problems rather than to police people.

Still tracking production on paper, whiteboards or WhatsApp?

We will walk your floor with you, map how work actually moves, and scope a tracking tool your operators will use. See our Customer Portals & Internal Tools work or start the conversation.

Frequently Asked Questions

Do operators need smartphones of their own?

No. Most shop-floor systems use shared rugged tablets or low-cost phones mounted at each station or cell, with operators identifying themselves by scanning a badge.

What happens when the factory Wi-Fi drops?

A well-designed app records scans on the device and syncs them when the connection returns, so work never stops and no data is lost.

Can the system work in Gujarati, Hindi or other languages?

Yes. The operator screens can be in the languages your team uses, while supervisors and the office see the same data in English.

How long does it take to roll out?

A pilot on one line can usually be running within weeks. A full rollout depends on the number of lines and how much variation there is between jobs, and is best done line by line.

Should we buy an MES instead of building something?

If a packaged system fits your process and integrates with your accounting or ERP, it may be the faster choice. Custom tracking makes more sense for job shops with highly variable routings, specific language needs or close integration requirements.

Further Reading