Rejection and Rework: How to Track Quality Issues on the Shop Floor

Rejections happen in every factory.

A batch fails dimensional check. A surface finish is off. A component does not fit during assembly. A customer returns goods that do not match the sample.

The question is not whether rejections will happen. It is whether the factory learns from them or just absorbs the cost and moves on.

Most Indian MSME manufacturers handle rejections informally:

• the supervisor notes it verbally
• the operator redoes the work
• the accounts team sees higher material consumption
• nobody records why it happened
• the same issue repeats next month

That cycle is expensive. And it is largely invisible in most factory reporting.

What Rejection Actually Costs

Rejection is not just the cost of the scrapped part. The real cost includes:

Direct costs

• Wasted raw material. Material that went into the rejected piece is lost or needs reprocessing.
• Wasted labour time. The operator spent time producing something that cannot be sold.
• Rework labour. If the item can be salvaged, someone has to fix it.
• Additional material. Rework may need fresh components, welding rods, solvents, or recoating.
• Machine time. The equipment was occupied producing defective output.

Indirect costs

• Production delay. The time spent on rejected items pushes other orders back.
• Overtime. Teams work late to make up for the lost output.
• Urgent material purchases. If rejected material needs replacement, the purchase may happen at a premium.
• Customer dissatisfaction. Late delivery or inconsistent quality erodes trust.
• Repeat inspections. Once a batch fails, subsequent batches from the same setup get inspected more carefully, adding time.

For many MSMEs, the total cost of poor quality runs between 2 and 5 percent of revenue. For a factory doing Rs 5 Cr per year, that is Rs 10 to 25 lakhs. Often, nobody has calculated this number because the losses are spread across material, labour, and overhead.

Why Factories Do Not Track Quality Well

It feels like extra work

Production teams are focused on output. Recording rejection reasons, quantities, and root causes feels like paperwork that slows them down.

The system does not support it

Tally has no natural place for quality data. Excel sheets get created but not maintained. Without a simple input method, quality recording becomes inconsistent.

Rejections are seen as normal

In many factories, a certain level of rejection is accepted as "part of the process." Until someone calculates the annual cost, the urgency to improve is low.

There is no feedback loop

Even when rejection data is recorded somewhere, it often does not reach the person who can fix the problem. The machining operator does not see last month's rejection report. The purchase team does not know which vendor's material caused the most quality issues.

What to Track

At minimum, every rejection or rework event should capture:

The basics

Rejection reason categories

Define a standard list of reasons. Do not let people type free text. Free text creates a mess that is impossible to analyze.

Common categories by industry:

Metal fabrication and machining:

• dimensional out of tolerance
• surface finish defect
• burr or sharp edge
• wrong hole position
• crack or fracture
• material defect (hardness, composition)

Garments and textiles:

• stitching defect
• colour mismatch
• fabric defect
• wrong measurement
• stain or damage
• embroidery or print misalignment

Food processing:

• contamination
• under/over weight
• packaging defect
• taste or texture issue
• labelling error
• shelf life failure

Electronics and electrical:

• soldering defect
• component failure
• wrong component
• wiring error
• calibration failure
• enclosure defect

The exact list depends on your factory. The important thing is that the list exists and everyone uses it.

Rework: When Rejection Is Not the End

Not every rejected item is scrap. Many can be reworked:

• a machined part can be reground
• a garment can be re-stitched
• a surface can be re-coated
• an assembly can be disassembled and corrected

But rework has its own tracking needs:

• What was the original defect?
• What rework was done?
• How much time and material did rework consume?
• Did the item pass quality after rework?
• What is the rework cost versus scrapping and remaking?

If rework is not tracked, the factory cannot tell whether it is cheaper to prevent the defect or fix it afterward.

Building a Simple Quality Process

You do not need a full ISO quality system on day one. Start with these three practices:

1. Record every rejection with a reason

Make it easy. A dropdown on a phone or tablet is enough. The operator selects the order, the quantity rejected, and the reason from a predefined list. That takes 30 seconds and creates a record that is worth reviewing.

2. Review weekly

Every week, the production head or factory owner should look at:

• total rejection quantity and percentage
• top 3 rejection reasons
• which items or processes had the most issues
• whether any trend is worsening

This takes 15 minutes. The insights are often surprising.

3. Close the loop

When a pattern emerges (same reason, same process, same vendor's material), assign someone to investigate and fix it. Track whether the fix actually reduced the rejection rate.

Without this step, data collection is just record-keeping. With this step, it becomes continuous improvement.

Connecting Quality to Other Factory Workflows

Quality data becomes more useful when it connects to:

Vendor performance

If raw material defects are a top rejection reason, the factory should know which vendor supplied the material. Over time, this builds a vendor quality scorecard that informs purchasing decisions.

Production costing

If rework is not tracked, the production cost report looks better than reality. Including rejection and rework costs in the per-unit cost gives the owner an honest picture of margins.

Customer complaints

When a customer reports a quality issue, the factory should be able to trace back to the production order, the batch, and the inspection record. Without this link, quality disputes become arguments instead of investigations.

Dispatch decisions

Before dispatch, someone should verify that the quantity being shipped has passed quality inspection. If rejected items accidentally get packed and sent, the cost is not just the return. It is the trust lost with the customer.

Common Mistakes in Quality Tracking

1. Tracking quantity but not reasons. Knowing you rejected 200 pieces is not useful without knowing why.
2. Using free text for reasons. It creates inconsistent data that cannot be analyzed. Use a standard dropdown.
3. Recording quality data only at final inspection. By then, the defect has traveled through multiple stages. Catch it earlier.
4. Not tracking rework separately. If rework is invisible, the factory cannot see how much it really costs.
5. Blaming operators without fixing processes. Quality problems are usually system problems, not people problems.

Where FactoStack Fits

FactoStack includes quality tracking as part of the production workflow. Rejection reasons are recorded against production orders, rework is tracked separately, and quality data connects to vendor performance, costing, and dispatch readiness.

Related Guides

• How to track WIP inventory in a small factory
• Production order vs work order in manufacturing
• What is a BOM and how it works in manufacturing
• What Tally does not tell you about your factory

Frequently Asked Questions

Rejection Is Data, Not Just Waste

Every rejected piece carries information: about the process, the material, the machine, the setup, or the operator. Factories that capture that information improve. Factories that treat rejection as a cost to absorb keep paying the same price.

The starting point is not a quality management system. It is a habit of recording what went wrong, reviewing it weekly, and acting on the patterns.

• Quality Management
• Production Planning and MRP
• Shop Floor Tracking
• Manufacturing MSME Solutions