Pareto Analysis
Pareto analysis ranks categories of defects, deviations, complaints or loss so a team can see where focused investigation is most likely to matter. The chart prioritises evidence; it does not prove root cause or turn the 80/20 observation into a rule.

On this page · 16 sections
- 1What Pareto analysis means
- 2Prepare data before drawing the chart
- 3Build and read a Pareto chart
- 4Manufacturing examples
- 5Common mistakes and better controls
- 6Inside V5: using connected quality records
- 7Explain it for your operation
- 8Choose frequency, cost, time or risk deliberately
- 9Stratify before deciding where to act
- 10Combine Pareto priority with quality risk
- 11Use the same measure to check improvement
- 12A practical worked example
- 13A proportionate implementation plan
- 14Internal review questions
- 15Records and evidence to retain
- 16Questions to ask when evaluating software
How does Pareto Analysis apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What Pareto analysis means
A Pareto chart places categories along the horizontal axis, bars for count, cost or another defined measure in descending order, and often a cumulative-percentage line. The left side shows the categories contributing most to the selected measure. The method is named for the Pareto principle, but real manufacturing data do not have to divide into exactly 80 and 20 percent.
The analysis is a prioritisation device. A tall bar says a category is frequent or costly under the chosen definition; it does not say why it occurs, whether its records are independent, or whether it carries the highest patient, consumer or business risk.
02Prepare data before drawing the chart
Define the question, period, population and unit first. Complaint count, rejected units, downtime minutes and cost of poor quality produce different rankings. Use mutually understandable categories and retain a route back to the underlying records.
Clean obvious duplicates, decide how repeat events are counted, and separate missing or unknown classifications. A large ‘other’ bar usually signals weak coding rather than a useful cause category.
03Build and read a Pareto chart
Total the selected measure for each category, sort categories from largest to smallest, calculate each category's share and the cumulative share, then plot bars with a clearly labelled scale. Show the time window, population and exclusions beside the chart.
Start investigation with the important categories, but check severity and detectability before acting. A rare sterile-barrier breach may deserve earlier action than a common cosmetic defect. Compare both counts and rates when production volume changes.
04Manufacturing examples
A packaging team can rank label rejects by mismatch, print quality, position, damaged stock and scanner failure. A quality team can rank deviations by process step or confirmed cause. Maintenance can compare downtime minutes by asset or failure mode. Supplier quality can compare incoming defects by material and supplier.
Each view answers a different question. Do not merge categories merely to make a dramatic chart, and do not compare sites until coding rules and denominators are aligned.
05Common mistakes and better controls
Common mistakes include treating the tallest bar as root cause, mixing severity with frequency, changing category definitions between periods, using percentages without the denominator, and allowing one event to be counted multiple times without explanation.
Keep the data definition with the chart, review the source records behind a selected bar, and pair Pareto analysis with a method such as 5 Whys, fishbone analysis or designed experimentation. Re-run the chart after action using comparable periods and rates.
06Inside V5: using connected quality records
V5 quality records can keep deviations, complaints, nonconformances, owners and affected production records connected. Those records can provide a consistent dataset for review when the team uses controlled categories and checks the underlying cases.
V5 does not infer root cause from a bar chart or decide which risk is acceptable. A qualified person still defines the measure, reviews severity and context, selects the investigation and approves action.
07Explain it for your operation
Choose one decision you need to make, such as where to focus the next defect-reduction effort. Write the population and denominator, agree category definitions with the people who create the records, test a sample for coding consistency, and draw both count and rate views where volume varies.
Record why the selected category was prioritised, what deeper analysis will follow and when the same measure will be reviewed. This turns a picture into a traceable improvement decision.
08Choose frequency, cost, time or risk deliberately
The vertical measure changes the decision. Event count highlights recurrence, rejected quantity reflects output impact, downtime captures capacity, and cost includes labour or disposal. Build separate views when measures cannot be combined honestly. If one complaint affects many units, show both complaints and affected units rather than choosing the more dramatic number.
Rates need an exposure denominator: defects per thousand units, deviations per batch, complaints per shipment or downtime per scheduled hour. Compare like with like, state whether categories overlap, and retain the extraction date so a later refresh can be reconciled.
09Stratify before deciding where to act
A broad Pareto may hide a local pattern. Break an important category down by product, line, shift, supplier, defect location or process step, while protecting against tiny groups that create unstable percentages. A second-level chart should still reconcile to its parent category.
Use stratification to test useful questions, not to search indefinitely for a flattering picture. Record which splits were examined and why the team selected one for further investigation.
10Combine Pareto priority with quality risk
Frequency and impact are not the same. Review severity, detectability, affected population and regulatory significance beside the ranked bars. A separate risk assessment may override the chart's apparent order.
The transparent conclusion is not ‘Pareto says fix A’. It is ‘A represents this share of the defined measure, risk review found these consequences, and the team therefore chose this investigation’. That sentence preserves both evidence and judgement.
11Use the same measure to check improvement
Freeze the baseline definition before action: category rules, source systems, denominator, period and exclusions. After enough exposure, compare the same rate and examine whether the problem moved into another category.
Improvement can be obscured by higher production or more accurate reporting. Show absolute counts and normalized rates, explain changes in capture, and avoid claiming causation when several changes occurred together.
12A practical worked example
Suppose 240 packaging defects are coded across eight categories. Misapplied labels account for 86, poor print for 54 and damaged cartons for 33. Those three categories represent 173 events, but the team should still compare defects per packaging run and assess severity. Reviewing the 86 label events may reveal several distinct mechanisms rather than one cause.
After a verified alignment change, compare a defined number of runs using the same coding. Show whether misapplied-label rate fell, whether another reject category rose, and whether inspection or reporting changed. This is stronger than presenting a new chart without baseline reconciliation.
13A proportionate implementation plan
- Confirm the applicable requirement, product scope and decision owner.
- Map the current method and the records already available.
- Define terms, responsibilities, evidence and exception handling in the approved procedure.
- Pilot the method on one representative process and challenge a difficult exception.
- Train affected roles, approve the change and monitor whether the method works as intended.
- Review after significant change and retain a transparent history of decisions.
Scale the formality to risk and complexity. A small operation still needs clear responsibilities and reconstructable evidence, while a multi-site operation also needs harmonised definitions, governance and comparison rules.
14Internal review questions
- Can a reviewer identify the source, owner, method and current approved version?
- Do summaries reconcile to original records and include unfavourable or missing evidence?
- Are exceptions visible, assessed and linked to the affected material, product or process?
- Are actions assigned, overdue items escalated and effectiveness reviewed?
- Have changes in product, supplier, equipment, method or regulation triggered reassessment?
- Does the record distinguish system support from the decision an authorised person made?
15Records and evidence to retain
- Approved scope, definitions and responsibilities for pareto analysis.
- Source records and identifiers that let a reviewer reconstruct the work.
- Methods, assumptions, calculations, exclusions and any data-quality limitations.
- Exceptions, investigations, decisions, approvals and resulting actions.
- Version history showing when the approach changed and why.
Records should be proportionate to the decision and usable by someone who was not present. Preserve original evidence and corrections rather than replacing it with an unexplained summary.
16Questions to ask when evaluating software
- Can users trace every summary value back to its source record and version?
- How are roles, permissions, signatures and corrections recorded?
- Can the workflow reflect our approved procedure without inventing a universal rule?
- What happens during an outage, and how are later entries distinguished?
- Can we test the highest-risk exception with realistic data before committing?
- Which decisions remain explicitly assigned to an authorised person?
Frequently asked questions
Q.What is pareto analysis?+
Pareto analysis ranks categories of defects, deviations, complaints or loss so a team can see where focused investigation is most likely to matter. The chart prioritises evidence; it does not prove root cause or turn the 80/20 observation into a rule.
Q.Is pareto analysis required in every operation?+
The applicable product rules, market, risk and approved quality system determine what is required. The method should be justified for the operation rather than copied without context.
Q.Can software make the final quality decision?+
No. Software can organise records, calculations and workflow, but authorised people remain responsible for scientific, quality and disposition decisions.
Q.How should a site start?+
Choose one bounded process, define the decision and evidence, test the method with real records, correct gaps, then expand under change control.
Q.What evidence should be retained?+
Keep the approved method, source records, assumptions, exceptions, review, decision, approval and any resulting action with enough context to reconstruct the work.
Q.How often should it be reviewed?+
Use the applicable requirement and a risk-based cycle, with earlier review after significant change, failure, complaint, deviation or new knowledge.
Primary sources
Want to see how Pareto Analysis could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
