How to Set Up a Scrap Reduction Campaign: Step-by-Step Guide

A scrap reduction campaign is a structured, focused corrective action initiative aimed at reducing the scrap rate of a single, specific defect type. The deliberate focus on one defect type is not a limitation — it is the source of the campaign's effectiveness. Diffuse improvement programs that simultaneously address five or six defect types typically make slow progress on all of them.

A campaign has four defining characteristics:

• A single target: One specific defect type (e.g., "dimensional rejection on part #P-204"), not "reduce overall scrap."
• A defined time box: A start date, a target end date (typically 8–12 weeks), and a formal close when the target is achieved.
• A named owner: One person who is accountable for the result — not a committee.
• A measurable target: A specific percentage reduction versus a documented baseline (e.g., "reduce dimensional rejections from 82/month to 60/month").

A campaign is not a project to redesign the production process. It is not a root cause analysis exercise (though root cause analysis supports it). It is not a quality audit. It is an operational initiative to drive a measurable number down. Pareto Base Campaign Management provides the structure — baseline tracking, weekly progress charts, and result documentation — so the campaign owner can focus on the corrective action work itself.

Campaign target selection should always be data-driven, not intuition-driven. Run a Pareto analysis on your scrap data from the past 30 days to rank defect types by frequency or cost. The defect type at the top of the Pareto ranking — the single largest contributor to total scrap — is your campaign target.

This might feel counterintuitive if there is a defect type that is currently generating complaints or attention from management — but unless that defect is also the top Pareto contributor, it is not where corrective action effort will have the greatest impact. Let the data drive the selection.

Pareto Base's Pareto chart automatically identifies the top contributor so you can launch a campaign directly from the analytics dashboard without manually calculating rankings.

A 20–30% reduction in the targeted defect's scrap rate over 8–12 weeks is a realistic and achievable target for most discrete manufacturing operations without capital equipment investment. This range is based on what is consistently achievable through process discipline, operator training, and tooling adjustments — the corrective actions available to quality managers without a capital approval cycle.

More aggressive targets (50%+) are sometimes achievable but typically require root cause analysis revealing a specific, fixable problem — a worn die, a miscalibrated gauge, a training gap on a specific operation. If your root cause investigation reveals such a specific cause, a larger target may be justified. If it does not, setting an aggressive target risks campaign failure and team demoralization.

Pareto Base Campaign Management accepts both the baseline count and the target count when you set up a campaign, and displays progress as both absolute numbers and percentage improvement throughout the campaign lifecycle.

The baseline is the historical scrap rate for the targeted defect type against which campaign progress is measured. It must be calculated from clean, representative data — typically four weeks of production before any corrective action begins.

"Clean data" means data collected under normal operating conditions without changes specifically intended to address the target defect. If operators know a campaign is starting and change their behavior before the baseline period ends, the baseline will be artificially low, making improvement harder to demonstrate.

Assign a single campaign owner — one named person who is accountable for the outcome. Campaigns assigned to teams, departments, or committees without a single accountable individual consistently underperform compared to campaigns with a named owner.

The campaign owner does not need to personally perform the root cause analysis or corrective action — they can delegate technical work to a process engineer or maintenance technician. But they are responsible for ensuring the work happens, escalating when it stalls, and reporting progress to plant management.

Pareto Base Campaign Management assigns the campaign to a named user, making ownership visible to the entire team. The campaign owner receives automated weekly progress summaries so they always have current data before the review meeting.

Weekly reviews are the operating cadence of a campaign. Monthly reviews are too infrequent — a developing problem that appears in week two can become a crisis by week six if not caught. Daily reviews are too granular — scrap counts have day-to-day noise that obscures the underlying trend.

Each weekly review should cover three questions:

Pareto Base displays the campaign progress chart — actual vs. baseline vs. target — so the weekly review can begin with data on screen rather than the campaign owner pulling numbers from a spreadsheet. The review meeting time is then spent on decisions, not data collection.

A campaign is formally closed when the target reduction has been achieved and sustained for four consecutive weeks. The four-week sustainability requirement distinguishes genuine process improvement from a temporary improvement driven by heightened attention — the "Hawthorne effect" that often produces short-term gains that evaporate when the campaign is closed.

The closure document — which serves as the ISO 9001 Clause 10.2 corrective action effectiveness record — should capture:

This document is your ISO 9001 Clause 10.2 corrective action record. It demonstrates root cause identification, corrective action taken, and effectiveness verification — the three requirements auditors check when reviewing your corrective action program for recurring defects.

Pareto Base Campaign Management generates the closure record automatically from the campaign data — baseline, target, corrective actions logged, and post-campaign actuals — reducing the documentation burden to a review and sign-off rather than a document-creation task.