Quality control and release: who decides that work is good enough?
Quality control and release decides whether a product, a batch or a finished job meets the requirements and may go to the customer. The procedure describes the standard checks. The hard part is judgement — when a deviation is acceptable, which customer is stricter than the specification, which test result needs a second look. That judgement usually sits with a quality lead or a senior engineer. When they are away, releases wait or, worse, go out without the check that mattered.
The process in brief
- Requirements defined: specifications, customer demands and standards.
- Incoming and in-process checks.
- Final inspection and tests.
- Deviations assessed.
- Release decided and recorded.
- Delivery documents and certificates prepared.
- Complaints handled and fed back into the process.
Where the critical knowledge hides
| Step | Knowledge at risk | Who usually holds it |
|---|---|---|
| Requirements | Which customers expect more than the specification says | Quality lead, key salesperson |
| In-process checks | Where problems usually start, and what to watch | Production lead, operator |
| Final tests | How to read borderline results | Quality lead |
| Deviations | When a deviation is acceptable, and who may approve it | Senior engineer, quality lead |
| Release | The questions the release decision really rests on | Quality lead |
| Documentation | Which certificates and records each customer needs | Quality administrator |
| Complaints | The history behind recurring complaints, and their root causes | Quality lead |
What breaks when that person leaves
Releases start to wait for the one person whose signature everyone trusts. Stand-ins decide inconsistently — stricter on one day, looser on the next — because the reasoning behind earlier decisions was never recorded.
Customer-specific requirements get missed, complaints that were solved once come back, and audits find decisions nobody can explain.
Early signs, long before anyone leaves:
- releases wait when one person is on holiday;
- deviation decisions differ depending on who takes them;
- the same complaint returns after a few months;
- customer requirements are known, but written down nowhere.
What to capture first
- Deviation rules: acceptable, acceptable with conditions, never — per product or customer.
- Customer requirements that go beyond the specification.
- How borderline test results are judged.
- The root causes of recurring complaints.
- Who may release when the quality lead is away, and on what basis.
How MentX maps and captures this process
MentX captures how your company really works: the knowledge of your key people and the processes they run. We offer both a hands-on service approach — mapping your processes and capturing the knowledge behind them, from meetings, workshops and a guided intake — and our own personality-aware knowledge base, with full source attribution, in your own Knowledge Space. We build on the tools you already use and add best-practice solutions where they fit.
We map quality control and release end to end with the people involved, starting from recent release decisions — a straightforward one, a deviation that was accepted and one that was refused. Then we capture your operations: the knowledge per step from the table above, with an owner, the decision rules and exceptions, and the source of each. With operational excellence, your team runs on that knowledge — clear hand-overs, tested instructions, and reviews when something changes. How an engagement runs.
In your sector
Manufacturing. Batch release and deviation handling are daily decisions; their consistency depends on how explicit the criteria are.
Family-owned industrials. Long-standing customers often have requirements that were agreed informally years ago and never added to a specification.
Engineering firms. Review and approval of calculations and drawings rest on senior judgement that is hard to delegate.
Common questions
Isn't this covered by our ISO procedures?
The procedures cover the standard checks. The judgement around deviations and borderline results usually is not. See is knowledge management part of quality management?
Can AI help with release decisions?
It can prepare them: collect the results, flag deviations, and check them against captured rules with sources. The release itself stays with people. See can AI learn how your manager decides?
Who should own quality control and release?
The quality lead, in most SMEs. Deviation approvals often sit with an engineer, though; make that split explicit, with a named back-up for both.
Where do we start if our quality lead is retiring?
With the deviation decisions of the last months: which were accepted, which refused, and why. Those cases hold the judgement a successor needs most. Then add the customer requirements nobody wrote down. A skills matrix shows who could take over which part.
