Corrective action: fixing the cause rather than the symptom
A corrective action stops a problem recurring. Most of what gets recorded as one is a repair — the thing you do to the affected item, which changes nothing about the next occurrence.
Total quality control moved responsibility for quality out of the inspection department and into every job that touches the work. It predates modern quality standards and explains why most of them are written the way they are.
Total quality control is the principle that quality is produced by everyone who touches the work, not verified at the end by an inspector. It was named by Armand Feigenbaum in the 1950s, taken further in Japanese manufacturing, and it is the ancestor of nearly every quality approach in use since — including the standards that now govern how quality management systems are written.
The word doing the work is total. Not total as in thorough, but total as in the whole organisation: design, purchasing, production, sales and service all determine quality, and inspecting the finished item can only discover what those functions already decided.
The model before it was straightforward and expensive. Production made things, an inspection department checked them, and defects were scrapped or reworked. Quality was a filter at the end of the line — which meant every defect had already consumed its full material and labour cost before anyone noticed, and it meant the people who caused defects got their feedback days later from someone in a different department.
The cost-of-quality calculation was the argument that convinced managements. Once prevention, appraisal, scrap, rework, warranty and lost customers are added into one number, it is usually a large share of revenue — and the internal and external failure components dwarf what prevention would have cost.
These are related but not the same thing, and the distinction is worth keeping straight. Total quality control is a philosophy about where responsibility for quality sits. A quality management system is the documented apparatus — procedures, records, audits, corrective actions — through which an organisation demonstrates it is doing something along those lines, usually against a standard.
You can have the documentation without the philosophy, and plenty of certified organisations do: procedures written to satisfy an auditor, followed by nobody, with quality still effectively meaning the inspection at the end. The reverse also happens in small companies, where the culture is right and nothing is written down, which works until the founder is on holiday.
The most common failure is exhortation without authority. Posters about quality being everyone's job, in a company where stopping work has consequences and the shipping target is absolute, produce cynicism rather than quality. If the operator cannot stop the line, quality remains the inspector's responsibility whatever the poster says.
The second is measurement theatre — collecting defect data nobody analyses. Data that never changes a decision is a cost with no benefit, and people can tell, which is why the numbers start being made up.
Total quality control generates records almost by definition: defects, causes, the corrective action, whether it worked. Ettex Records handles this as structured entries rather than as documents — one row per issue, with fields for the defect, the process step, the cause, the owner and the outcome, so the same defect appearing eleven times is visible as a pattern instead of as eleven separate emails.
It is a record system, not a quality system: no statistical process control, no control charts, no measurement equipment integration, and no certification path. Where a standard or a customer specifies how quality must be managed, that specification governs — this holds the evidence, it does not decide what evidence you need.
The principle that quality is created by everyone who touches the work — design, purchasing, production, sales and service — rather than verified by an inspection step at the end.
Armand Feigenbaum named the concept in the 1950s; it was developed further in Japanese manufacturing and influenced the quality approaches that followed.
It is a philosophy about responsibility. A quality management system is the documented apparatus — procedures, records, audits — usually built against a standard.
Prevention, appraisal, internal failure and external failure combined into one figure. Seeing it whole is usually what justifies investing in prevention.
Yes. The underlying point — that defects are decided upstream of where they are found — applies to services and software equally.
Usually because responsibility is announced without authority, or because defect data is collected and never analysed.
Total quality control is one claim: the inspection at the end can only find what earlier decisions already put there. Measure what failure costs, move the check upstream, and give the person doing the work the authority to stop.
A corrective action stops a problem recurring. Most of what gets recorded as one is a repair — the thing you do to the affected item, which changes nothing about the next occurrence.
A conflict of interest policy is mostly a register and a habit. The point is not to forbid overlapping interests but to have them written down before anyone has reason to ask.
A record of processing activities lists what personal data you hold, why, where it goes and how long you keep it. It is dull to build and it answers half the questions anyone will ever ask you.