Quality = meeting customer expectations
Quality means a product or service consistently meets the standard customers expect for the price paid — not the most expensive or most luxurious option. A budget airline with on-time flights and no lost luggage shows quality; a luxury hotel with dirty rooms does not. It matters because it builds reputation and loyalty, gives a competitive advantage (a USP in crowded markets), avoids the cost of failure (returns, scrap, rework) and helps meet legal safety standards.
QC vs QA vs TQM: who checks, and when
Three ways to achieve quality. QC: a separate inspection team checks products at the END, or set checkpoints — it detects faults, does not prevent them, and usually tests only a sample. QA: every worker checks their own output THROUGHOUT production, preventing faults reaching the next stage. TQM: a company-wide culture of continuous improvement (Kaizen), getting it right first time. QC leaves scrap; QA and TQM cut waste at source but need training.
Poor quality costs; quality methods pay
Poor quality triggers complaints and returns, wasted materials and rework (raising average unit cost), a damaged reputation, lost sales and market share, possible legal liability, and lower staff morale. Quality methods reverse these: fewer defects cut returns and rework costs; a quality reputation supports premium pricing and loyalty; QA and TQM cut waste at production, lowering unit costs; and worker ownership of quality can raise motivation.
Drawn from real examiner reports.
QC checks a sample, not every item
Candidates wrongly claim quality control "ensures no errors appear" or that no defective good can ever reach a customer. In reality QC usually tests only a sample of output, so a faulty item outside the sample can still slip through. QA lowers this risk because each worker checks their own work at every stage, catching faults that sampling would miss.
w22 P11 Q1(d).
Quality control ≠ quality assurance
The biggest 4.3 error is treating QC and QA as the same, or reversing them. QC: a specialist team inspects products at the END, or set checkpoints — it detects faults. QA: each worker checks their OWN output at every stage — it aims to prevent faults. Avoid calling QA a quality department, or checking at the end — both describe QC. Get the who and the when right.
Most persistent 4.3 error across all four sittings (s22 P13 Q4(e)).
QA is self-checking, not surveillance
A persistent misconception is that quality assurance means managers or inspectors "constantly watch" workers. It does not. Under QA each worker checks their OWN output at each stage and corrects a fault before passing work on. There is no separate watcher — quality responsibility is distributed across the workforce, and that ownership is what raises motivation.
s22 P13 Q4(e); recurred w23 P21 Q1(b); w23 P12 Q2(e).
Quality ≠ the most expensive option
Do not define quality as "the best" or "most luxurious" product. Quality means meeting the standard customers expect for the price paid. A budget chair that reliably does its job is quality; an expensive item that fails to meet expectations is not. Defining quality as luxury loses the definition marks and misframes any evaluation that follows.
TQM is company-wide, not one department
Total quality management is not just a production-floor procedure. TQM is a company-wide culture in which every employee and every department — sales, finishing, logistics, finance — takes responsibility for quality and continuous improvement. Treating TQM as merely "inspectors plus workers" misses its defining feature and the training and cultural change it demands.
Answer which method, not why quality
When an evaluation asks which quality method a business should use, candidates often write about why quality matters in general (reputation, loyalty, fewer returns). That earns only basic knowledge marks. The question needs the two methods compared and applied to the named firm, ending in a supported judgement — otherwise all the AO4 evaluation marks are lost.
s22 P13 Q4(e).
Evaluate = supported judgement in context
On a 6-mark "Do you think...? Justify", reach a clear decision AND say why it outweighs the alternative for this specific business (product, scale, complaint history). Listing pros and cons with no contextual judgement stays mid-band and earns no AO4.
Avoid mirror arguments
"QA gives workers responsibility while QC does not" is a mirror argument — one point, credited once, not twice. A genuine second point needs a different knowledge base, e.g. QA can raise motivation. Replace the mirrored half with a fresh reason.
Analyse = a chain, not a list
Analysis marks (AO3) need a chain: knowledge, then mechanism, then consequence — e.g. under QA workers check their own output, so fewer faults pass on, cutting scrap and raising the margin. A list of facts with no "so" link stays at knowledge marks. Analyse is not evaluate.
Match the command word
Read the command word. Define (2 marks) = a precise two-element statement. Explain / Analyse = develop a chain of reasoning. "Do you think...? Justify" = weigh both options and give a supported judgement. Writing an evaluation for a define wastes time and misses marks.
Quality is the standard of a product or service relative to what customers expect for the price they pay. A product is high quality if it consistently meets those expectations; it does not need to be the most expensive option.
Trap: do not write "quality means the most luxurious product." A budget airline that delivers on-time flights with no lost luggage is producing quality; a luxury restaurant that serves cold food is not.
| Reason | Effect on the business |
|---|
Full notes, flashcards, Q&A and the topic quiz for every premium subject.
Premium plans are US$8.99/month or US$49.99/year — first month free.
Studying with a parent's blessing? Show them this.
