Production Management By Santosh Rijal 10 min read

10 Garment Factory KPIs Every Production Manager Should Track in Real Time

Most "garment KPI" lists are copied from generic manufacturing textbooks. This one is not. These are the ten metrics that actually matter on a sewing floor, each with the exact formula, a realistic target, and a clear explanation of what to do when the number goes wrong. Bookmark this and check it every morning.

I have spent years on factory floors where the only production metric anyone checked was end-of-day output vs. target. That single number tells you nothing actionable. By the time you read it, the day is over. The decisions that would have changed it were available at 10 AM. This article is about those decisions — and the ten numbers that make them visible in real time.

40–60%
Avg sewing efficiency, South Asia (ILO)
75–85%
Global best practice target
91.86%
Non-value-added time in production (ScienceDirect)

The Morning Dashboard Routine

Before diving into each KPI, let me describe how a production manager should use these numbers. The goal is not to stare at a dashboard all day. It is to run a five-minute check at 9:15 AM (after the first 45 minutes of production have generated real data), make decisions, and then check again at noon.

Morning check sequence (9:15 AM):

  1. Attendance Rate — Do you have enough operators to meet today's target? If not, rebalance lines now, not at noon.
  2. Line Efficiency — Are lines tracking at target after the first hour? Early low efficiency almost never recovers to target by end of day.
  3. Active WIP Count — Is WIP building up? A rising count in the first two hours means a bottleneck is forming somewhere upstream.
  4. WIP Age — Any bundles sitting idle for more than 30 minutes? Find out why before the hour is up.
  5. Defect Rate — Is the quality checkpoint showing above-normal rejections? One bad operator or a machine alignment issue caught at 9:30 costs 20 pieces; caught at 3:30 costs 200.

Everything else — earnings, throughput, cycle time — is a longer-window metric you review at end of day or end of week. The morning check is for the five numbers that tell you whether today is going to be good before it is too late to change it.

The 10 KPIs (With Formulas)

1
Line Efficiency (%)
Line Efficiency (%) = (Actual Output ÷ Target Output) × 100
Target
> 85%
Red Flag
< 70% before noon
What it tells you
How much of planned capacity you are actually converting to output
Action when low
Check absenteeism, bottleneck stations, and machine downtime immediately
How QR ERP calculates it: Target output is set per line per style based on SAM × available operator hours. Actual output is the count of completed bundles × pieces per bundle, updated with every scan. Line efficiency is live on the dashboard, not an end-of-day calculation.
2
WIP Age (Hours / Days)
WIP Age = Current time − Time bundle was last scanned at any station
Target
< 1 day average
Red Flag
Any bundle > 2 days
What it tells you
Where bundles are sitting idle and for how long — the earliest signal of a bottleneck or stuck operation
Action when high
Locate the aged bundle physically, find out why it has not moved, resolve the blocker
How QR ERP calculates it: Every bundle scan records a timestamp. The system continuously computes elapsed time since last scan for every open bundle. Bundles exceeding age thresholds trigger automatic WhatsApp alerts to the supervisor and appear flagged on the floor TV dashboard.
3
Operator Piece Rate Achievement (%)
Achievement (%) = (Actual pieces completed ÷ Target pieces for shift) × 100
Target
100% (by shift end)
Red Flag
< 80% by midday
What it tells you
Whether an individual operator is on track for their earnings target and daily production quota
Action when low
Check if operator is waiting for work (starvation), has a machine issue, or is genuinely slow (skill problem)
How QR ERP calculates it: Each operator's scan history gives actual pieces per shift. Target is derived from the operation's standard minute value (SMV) and available hours. The earnings screen shows each operator their own live achievement percentage, which directly motivates self-correction without supervisor intervention.
4
Bundle Cycle Time (Hours)
Bundle Cycle Time = Time of final operation completion − Time of first operation start
Target
< 8 hours (same-day completion)
Red Flag
> 48 hours
What it tells you
How long a bundle spends on the floor from first touch to completion — a direct measure of flow speed
Action when high
Identify which operations are adding the most wait time; these are your real bottlenecks, not necessarily your slowest operators
How QR ERP calculates it: The first scan on a bundle and the completion scan together define cycle time automatically. Averaged across all bundles of a style, this gives you the actual versus planned throughput time per style — essential data for delivery planning and buyer commitments.
5
Defect / Rejection Rate (%)
Rejection Rate (%) = (Rejected pieces ÷ Total pieces inspected) × 100
Benchmark
< 3% (world class: <1%)
Red Flag
> 5% on any single operator
What it tells you
The quality level of output and how much rework is inflating your WIP and labour cost
Action when high
Identify which operation and which operator is generating the rejections; rework at source is always cheaper than end-of-line
How QR ERP calculates it: Quality check scans record pass/fail at inline inspection points. The system tracks rejection counts by operator, operation, and style. High-rejection operators appear in the daily quality report with their specific defect types, enabling targeted coaching rather than blanket retraining.
6
Active WIP Count (Bundles)
Active WIP = Total bundles in production (status: in-progress or waiting, not completed)
Target
1–2 days of output
Red Flag
Rising count without rising output
What it tells you
Whether work is flowing through the line or accumulating. High WIP with normal output = flow problem. High WIP with high output = just a large lot in progress.
Action when high
Map where WIP is accumulating by station — the station with the most waiting bundles is your current constraint
How QR ERP calculates it: Every bundle has a status (PENDING, IN_PROGRESS, COMPLETED, etc.) updated with each scan. Active WIP count is a live query against all open bundle statuses. The floor TV dashboard shows this as a bar chart by operation so supervisors can see exactly where the pile-up is without walking the floor.
7
Attendance Rate (%)
Attendance Rate (%) = (Operators present ÷ Total enrolled operators) × 100
Target
> 95%
Red Flag
< 88% — cannot meet daily target
What it tells you
Your actual available capacity for the day — which you need to know at 8:30 AM, not at shift planning the night before
Action when low
Redistribute remaining operators to highest-priority operations; inform production planning of reduced output expectation immediately
How QR ERP calculates it: Biometric attendance punches from the ZKTeco device (or any ADMS-compatible reader) are processed in real time. The supervisor dashboard shows attendance count and rate within minutes of shift start, along with which operators are absent so work can be reassigned before the line starts properly.
8
Operator Earnings vs. Target (%)
Earnings Achievement (%) = (Actual monthly earnings ÷ Target monthly earnings) × 100
Target
≥ 100%
Red Flag
< 80% by mid-month
What it tells you
Whether your piece-rate system is delivering fair earnings — and whether operators have enough work available to reach their income target
Action when low
Investigate whether the operator is receiving enough work (assignment problem) vs. not completing available work (skill or effort problem)
How QR ERP calculates it: The operator diary tracks all completed operations, piece counts, and piece rates. Earnings are calculated automatically: pieces × adjusted rate, plus machine complexity bonuses and efficiency bonuses. Operators can see their own running total on the work screen, which reduces end-of-month payment disputes to near zero.
9
First-Time Pass Rate (%)
First-Time Pass Rate (%) = (Bundles passing QC first attempt ÷ Total bundles reaching QC) × 100
Target
> 90%
Red Flag
< 80% on any style
What it tells you
The true quality output rate before rework. A factory with 95% line efficiency but 75% first-pass rate is not actually performing at 95%.
Action when low
Trace failed bundles back to their originating operations. Failures cluster by operation and operator — fix the root cause, not the symptom
How QR ERP calculates it: Quality check scans record pass/fail outcomes. Failed bundles are flagged for rework and re-scanned on re-inspection. First-time pass rate is the ratio of first-scan passes to total arrivals at the QC station, tracked separately from the overall reject rate to distinguish first-pass failures from rework success rates.
10
Bundle Throughput Per Hour
Throughput per Hour = Bundles completed in period ÷ Hours worked in period
Target
Set per style (varies by complexity)
Red Flag
> 20% below style benchmark
What it tells you
The real flow speed of your production line — how many complete bundles the line converts per hour, which directly determines delivery date accuracy
Action when low
Calculate throughput by line, not factory-wide. A low factory average often hides one underperforming line that is dragging the average down
How QR ERP calculates it: Bundle completion timestamps give exact throughput counts per hour per line. Historical data across multiple lots of the same style creates a benchmark throughput rate, so the system can flag when current throughput is deviating from what this style normally achieves on this line.

Leading vs. Lagging Indicators

Not all KPIs are equally actionable. The distinction between leading and lagging indicators is critical for how you use each number on your dashboard.

KPI Type Decision Window Check Frequency
Attendance Rate Leading Acts before production starts Once, 30 min after shift start
WIP Age Leading Predict bottlenecks 2–4 hrs early Continuous / alert-based
Active WIP Count Leading Flow problem visible before output drops Hourly
Defect Rate (inline) Leading Catch at source before it compounds Continuous / alert-based
Line Efficiency Lagging Confirms what already happened in window Hourly check
Bundle Cycle Time Lagging Measures completed bundles only End of day / per lot
First-Time Pass Rate Lagging Measures bundles already at QC End of day / per lot
Operator Earnings vs. Target Lagging Monthly pattern analysis Weekly / monthly
Operator Piece Achievement Leading Mid-shift intervention possible Midday check
Bundle Throughput / Hour Lagging Style benchmark calibration Hourly rolling average

The rule of thumb: Leading indicators tell you what your output will be. Lagging indicators tell you what it was. Build your morning routine around the four leading indicators: attendance, WIP age, active WIP count, and defect rate. Use lagging indicators for end-of-day review and continuous improvement work.

Why Most Factories Track Zero of These in Real Time

The honest answer is infrastructure. Calculating line efficiency in real time requires knowing actual output at any given moment, which requires either continuous manual counting (impossible at scale) or automatic scan data. Without QR or barcode scanning at the operator level, these KPIs exist only as end-of-day estimates.

Most garment factory management software — particularly older ERP systems — is designed around order management, not floor-level production tracking. They are good at cutting plans, shipment schedules, and costing. They have no mechanism for capturing real-time operator-level data because that data was never collected digitally.

QR bundle tracking changes this because the data capture happens as a natural part of the work, not as an additional reporting task. Operators scan to receive work and scan when they finish. Every scan is a timestamp and a piece count. The KPIs in this article are all derived from those two events — nothing more complex.

The most important thing is not which software you use. It is whether your operators are actually scanning — consistently, honestly, at every operation. A system that gets scanned 60% of the time gives you worse data than a good paper system. The implementation challenge is behavioural, not technical. Operators scan when: (1) it is faster than their alternative, (2) their pay depends on it, and (3) their supervisor actually looks at the data. All three conditions need to be true simultaneously.

Scan ERP by Country

🇮🇳 India 🇧🇩 Bangladesh 🇻🇳 Vietnam 🇳🇵 Nepal 🇦🇪 UAE 🇲🇦 Morocco

See These KPIs Calculated Automatically

Scan ERP tracks all 10 of these KPIs from QR scan data — no manual data entry, no end-of-day estimates. Live on your factory floor TV and supervisor dashboard.

Ask on WhatsApp

Santosh Rijal is the founder of Scan ERP, a garment manufacturing ERP system built for factory floor operations. He works directly with sewing lines, cutting rooms, and production supervisors across Nepal's garment manufacturing sector.