
A large share of shop-floor work in Indian manufacturing is paid by output rather than by time. Garment units pay tailors per piece, machine shops pay some operators per component and operation, press shops and assembly lines employ workers through labour contractors who bill by output or by headcount, and many factories run incentive schemes on top of fixed wages. All of these depend on one thing: knowing accurately who produced how many good parts of what.
In most factories that number comes from a supervisor's notebook, a production slip filled in at the end of the shift, or the contractor's own statement. Each is open to error and to dispute. This guide explains how to record operator output reliably on the shop floor, how to handle rates, rejections and rework, and how the same data supports contractor billing, incentives and production management.
Why output records matter beyond pay
Accurate output by operator is obviously needed for piece-rate pay. But the same records answer several other questions that matter to a factory:
- Is the contractor's bill right? Contractors often bill on their own count. Without independent records, the factory pays what it is asked.
- What does a part really cost? Labour per part, calculated from output and rates, is a key input to job costing.
- Where is capacity? Output per operator per hour by part shows real productivity, which is the basis for planning and for standard times.
- Who needs training? Large differences between operators on the same part point to skill gaps that training or better work instructions can close.
What to record
The minimum record for each booking is:
- Operator (or contractor's worker) — identified by a badge scan or selection, not by a name typed in.
- Date and shift.
- Job or work order, part and operation.
- Machine or workstation, where it matters.
- Good quantity.
- Rejected quantity, with a reason.
- Rework quantity, if rework is done by the same person.
Optionally, start and end times per job make it possible to calculate output per hour and to separate setup time from running time. For piece-rate pay alone, quantities are enough; for productivity analysis, times are needed.
Where the booking happens
There are three practical options, often used together:
- Operator books on a tablet at the workstation after each job or at intervals. This is the most accurate and gives operators ownership of their numbers. See our guide to Android tablets on the shop floor.
- Supervisor books for a group on a phone at fixed times — every two hours or at the end of the shift — from a count of finished parts. Simpler to start with, but less precise.
- Booking at the next stage: output is counted when parts are received by inspection or the next operation. This gives a verified count but attributes it later.
A common and effective combination is: operators book their own output; inspection confirms good and rejected quantities at the next stage; differences are reviewed daily by the supervisor.
Rates: by part, by operation, with history
Piece rates are set per part and operation — for example, facing and centring a shaft at one rate, turning at another, threading at a third. They change over time with negotiations, method improvements or new tooling. The rate table therefore needs:
- Part, operation and, if relevant, machine type or skill grade.
- Rate per piece (or per hundred pieces for small, high-volume parts).
- Effective date, so past output is always paid at the rate valid at the time.
- Approval: who set or changed the rate and when.
Where rates are derived from standard times — for example a standard minute value multiplied by a rate per minute — storing the standard time as well makes it easy to recalculate rates when wages change.
Rejections and rework: agree the rules first
The most common source of disputes is not the count of parts but how rejections and rework are treated. Agree the rules before you start recording, and make the software apply them consistently. Typical rules include:
- Only parts accepted by inspection are paid.
- Rejections caused by the operator are not paid; rejections caused by material or a previous operation are paid.
- Rework of the operator's own defects is unpaid; rework of other defects is paid at a rework rate.
- A rejection rate above a threshold reduces the incentive for the period.
Whatever the rules, recording a reason for each rejection — with the stage that caused it — is what makes them fair and enforceable.
Contract labour and contractor billing
Where workers are supplied by a labour contractor, the factory usually pays the contractor rather than the workers directly, either per piece produced or per worker per day. In both cases, the factory's own records protect it:
- Per piece: output booked per contractor's worker, summed by contractor, gives the expected bill. The contractor's invoice is checked against it before payment, and differences are investigated with the underlying records.
- Per worker per day: attendance records by shift and the output achieved show whether the headcount billed was actually present and productive.
Keep contractor workers identifiable in the system — with their own badges — even if they change frequently. A booking under a generic "contractor" name loses most of the value.
Showing operators their own numbers
Output recording works best when operators can see their own figures: today's output, the month's total, rejections and expected earnings. When they can check their numbers every day, mistakes are corrected while everyone still remembers the shift, and the end-of-month dispute largely disappears. A simple screen on the shop-floor tablet, or a summary on their phone, is enough.
Be open about how the data will be used. If operators believe output records exist only to find fault, entries will be resisted or manipulated. If they see that records protect them from undercounting and are used to pay them correctly, adoption is much easier.
Approvals and the monthly close
- Daily: supervisors review bookings for their section, correct obvious errors and confirm the day.
- Weekly: inspection and booking differences are resolved.
- Monthly: output is locked, earnings or contractor bills are calculated, reviewed by the production manager and passed to payroll or accounts.
Once a period is locked, changes should only be made as adjustments with a reason and an approver, so the history remains clear.
Incentive schemes
Many factories pay fixed wages plus an incentive for output above a target. The same output data supports this: the target per part and operation, output achieved, quality conditions and the incentive calculated. Keep schemes simple enough that operators can calculate their own incentive; complex schemes are distrusted and rarely improve output. Linking incentives to good parts rather than total parts keeps quality in view.
Common problems and fixes
- Bookings made at the end of the shift from memory. Make booking quicker and place the tablet closer to the work.
- Operators booking for each other. Use personal badges, and review bookings that don't match attendance.
- Disputes about rejections. Record the rejection reason and the responsible stage at inspection, with a photo for unusual cases.
- Rate tables out of date. Require a rate before a new part and operation can be booked, and review rates when methods change.
- Contractors with high worker turnover. Issue temporary badges on joining and deactivate them on leaving.
Multi-operator jobs and team output
Not all work is done by one person. Assembly lines, welding cells with a welder and a helper, and press lines with a loader and an operator produce output as a team. There are two common approaches. The first books output to the team or line and splits earnings by agreed shares — equal, by grade, or by hours present. The second books each person's operation separately where the work allows. Whichever is used, record who was present on the team for each shift, so the split is based on facts. Team output also changes how rejections are treated: a defect from one station affects everyone's earnings, which can encourage people to catch problems early — or, if the rules are unclear, to argue. Agree and publish the rules.
Standard times and fair rates
Piece rates are fairest when they are based on a realistic standard time for the operation. Many factories inherited rates set long ago, adjusted by negotiation, and some parts are known to be "good" or "bad" jobs to be given to favoured operators. Booking output with start and end times for a few weeks produces actual times for each part and operation. Comparing them across operators and shifts shows a realistic standard, and rates out of line with it can be corrected. Doing this openly, with operator representatives, reduces disputes and the informal allocation of good jobs.
Attendance, overtime and idle time
Output records and attendance records should agree. An operator booked for output on a day they were absent, or present for a full shift with no output booked, signals an error or a problem worth understanding. Idle time matters too: when a machine is down for maintenance or waiting for material, piece-rate workers lose earnings through no fault of their own. Many factories pay a time rate for recorded idle time caused by the company, which is only fair if downtime and its reason are booked at the time. Overtime output, which may carry a different rate, should be identifiable by shift. Linking output bookings with the attendance system — or at least comparing them weekly — keeps both honest and gives the payroll team a clean basis for calculations.
A worked example
An auto-component machine shop with 120 operators — about half supplied by two labour contractors — paid contractors on their monthly statements of pieces produced. The production manager suspected the statements were higher than actual output but had no records to prove it. Operators booked output in a register that the supervisor summarised weekly.
The shop moved booking to tablets shared between two or three machines, with badges for all operators including contractors' workers, and inspection confirmed quantities at the next stage. After the first month, the system's total for one contractor was noticeably below the contractor's statement; the difference was traced to double counting of reworked parts. Rates for rework were agreed, and the next month's bills matched the records. Operators could see their daily output on the tablet, and disputes at month end dropped sharply. The output data also showed the real cycle times for the shop's main parts, which became the basis for capacity planning.
Where it fits in the wider system
Output booking by operator is usually part of a manufacturing execution system or digital shop-floor app. The same bookings update work-order progress, WIP, job costs and machine utilisation. Building piece-rate calculation on top of production booking — rather than as a separate payroll exercise — means one entry serves production, quality, costing and pay.
Working with Corposol
Corposol builds custom manufacturing software for Indian SMEs, including shop-floor output booking, piece-rate and contractor calculations, and production and costing reports built on the same data. All custom code is transferred to you on final payment.
Frequently asked questions
What data is needed to calculate piece-rate pay?
Good quantity produced per operator, per part and operation, per day or shift, together with the agreed rate for each part and operation. Rejections and rework need clear rules about whether and how they are paid.
Can contractor bills be checked against shop-floor records?
Yes. When output is booked per contractor's worker and job, the factory can calculate what the contractor's bill should be and compare it with the invoice before paying.
Does recording output per operator cause resistance?
It can if it is introduced as surveillance. It is usually welcomed when operators can see their own output and earnings the same day and disputes are settled from records rather than arguments.
Does this replace payroll or statutory compliance?
No. Output records feed the calculation of piece-rate earnings or contractor bills. Payroll, statutory deductions and labour law compliance remain with your payroll process and advisers.
