Quality Management Basics

Information only — not legal advice.

Quality management makes it more likely that a team consistently delivers what was agreed. It connects requirements, capable people, controlled work, evidence of results and improvement when something fails.

It applies to an issued drawing, software service, inspection report or customer response. The useful starting question is: “What would make this result acceptable to the person who needs it?”

Define acceptance before doing the work

Replace vague expectations with observable criteria. “Complete handover” might mean that every maintainable asset has an identifier, required maintenance information and a working link to its accepted documentation. “Accurate report” needs agreed sources, a reporting period and checks that another person can repeat.

Include applicable contractual and regulatory requirements in that definition. Resolve contradictions before delivery rather than leaving individual authors to guess which instruction takes precedence.

Build checks into the process

For a recurring activity, identify the input, accountable owner, important steps, acceptance criteria and resulting record. Put checks where errors can still be corrected economically: confirm requirements before authoring, review the work before release and verify receipt when a handover matters.

The check should suit the consequence of error. An independent specialist review may be necessary for consequential technical work; a simple checklist may be enough for a routine administrative task. A checklist supports competent judgement rather than replacing it.

Example: a handover that looks complete

A fictional team receives 120 equipment records. All required fields contain text, so an initial completeness report shows 100%. Sampling reveals that several serial-number fields contain “TBC,” some manual links are broken and two assets share the same identifier.

The team revises its checks to distinguish field presence from valid content, unique identifiers and usable attachments. It asks the supplier to correct the affected records and determines whether the same defect occurs elsewhere in the delivery.

The lesson is practical: a metric can be perfectly calculated and still measure the wrong thing.

Correct the result and improve the process

Record a nonconformity against an actual requirement, with enough evidence to reproduce it. Contain its consequences, correct the affected output and investigate causes in proportion to the risk. Assign improvement actions and check whether they work in subsequent deliveries.

Useful indicators include acceptance at first review, recurring defects, rework effort and customer outcomes. Interpret them together. A lower complaint count may reflect satisfied users, but it may also mean the reporting route is hard to find.

Where ISO 9001 fits

At the 13 October 2026 review, ISO lists ISO 9001:2026 as the current published edition, published on 16 September 2026. It sets requirements for a quality management system. Organisations with existing certification should confirm transition arrangements with their certification body.

A management-system certificate has a defined scope; it does not certify every individual deliverable or guarantee an error-free service. Using this checklist also does not establish conformity or certification. The workflow examples above are practical guidance, not a reproduction of the standard's clauses.

Start with one frequently repeated process and one meaningful acceptance check. Continue with incident and corrective-action management and document control.

Important information

This article provides general information and does not constitute legal advice or replace a qualified professional's assessment of your circumstances. Laws, official guidance, standards and product features can change. Check current primary sources and the requirements applicable to your jurisdiction, contract and project before making decisions. Examples illustrate the discussion; they are not official rulings or instructions for a particular case. For legal decisions, consult a qualified lawyer; for technical or other specialist matters, consult the responsible professional.