Qualiopi indicator 32 (continuous improvement): expected evidence and mistakes to avoid
Indicator 32 closes the Qualiopi framework, and it closes it with a demand for proof through action: showing that the feedback and complaints you collect lead to real, traced and measured improvements. It is a major non-conformity indicator, applying to all categories of providers. Here is the evidence expected on audit day, the non-conformities that keep appearing in reports and how to reconstruct complete loops before the audit.
What indicator 32 requires
Attached to criterion 7, which it closes, indicator 32 expects the provider to implement improvement measures drawn from the analysis of feedback (indicator 30) and complaints (indicator 31) — and to demonstrate that this quality loop works over time.
Three framing points:
- the last indicator in the framework, it locks in the whole of criterion 7: collecting for indicators 30 and 31 is worth nothing if it produces no change;
- a major non-conformity in the event of a gap: a declarative plan can block certification;
- all categories concerned (training organisations, apprenticeship centres, skills assessment, VAE), with the benefit of the new-entrant accommodation.
It is the indicator of proof through action: the auditor does not want a statement of intent, they want to follow the complete thread of at least one improvement — the source (a questionnaire verbatim, a falling average, a complaint), the analysis, the action, then the measured effect. For the underlying method that keeps this cycle alive all year, see our dedicated article on the continuous improvement approach; here, we focus on what happens on audit day.
The auditor’s test: tracing an improvement back to its source
The typical question is simple: “Show me a recent improvement and where it comes from.” The auditor often picks a line of your plan and traces it back to the source questionnaire or complaint. If the thread breaks — an action with no origin, a source with no follow-up — the gap is recorded.
The defence: prepare two or three complete, consistent threads, each running through the four stages:
- the source: a verbatim from your trainee satisfaction survey, a falling average spotted in your quality dashboard, or an entry in your complaints and incidents log;
- the analysis: why this feedback justifies an action, decided in a quality review or noted as it happens;
- the action: what was changed, by whom, with what deadline;
- the measured effect: the score that rose at the next session, the complaint that did not recur, the positive feedback documented.
This dual requirement — making what works reliable and learning from what fails — is not an auditor’s whim. The study by Sim B. Sitkin, Kathleen M. Sutcliffe and Roger G. Schroeder, « Distinguishing Control From Learning in Total Quality Management: A Contingency Perspective », published in 1994 in the Academy of Management Review, shows that an effective quality approach combines two complementary logics: control (standardising and making reliable what you already do well) and learning (experimenting and improving in the face of uncertainty). That is exactly what indicator 32 demands: closed loops, and the capacity to draw real changes from them.
The evidence that convinces on audit day
The typical evidence file for indicator 32 comes down to five items:
- an up-to-date continuous improvement plan, with for each line: source, finding, action, owner, deadline, observed effect;
- the questionnaire compilations and the complaints register that feed the plan — the sources must be presentable, not merely cited;
- examples of complete loops, from the initial verbatim to the measured effect, ready to be walked through in front of the auditor;
- the minutes of periodic quality reviews where feedback is analysed and actions decided;
- the successive versions of a course material or programme modified following feedback: nothing proves better than a dated “before / after”.
No quota is required. For a small structure, three to six real, documented loops per year — including at least one taken all the way to a measured effect — are worth more than a bulky but hollow table. The auditor prefers a short plan in which every line checks out to a file of fifty unverifiable actions.
Reconstructing complete loops before the audit
If your plan is incomplete a few weeks before the audit, do not fabricate a retroactive table: honestly reconstruct what actually happened. Most providers improve without tracing it.
- Start again from the sources: reread your questionnaire compilations and your complaints register over the last twelve months, and list the feedback that actually changed something.
- Find the traces of the action: an email to a trainer, a new version of a course material, a reorganised programme, a change of room or timetable.
- Document the effect: compare scores or verbatims before / after the action, or record the absence of any new complaint on the subject.
- Record everything in the plan, with the real dates of the events — the auditor will cross-check those dates against your sessions.
This reconstruction is legitimate as long as it reflects real, dated facts. It becomes a non-conformity the moment it invents actions or effects.
The typical non-conformities on indicator 32
- The declarative quality policy: a fine continuous improvement procedure, with no traced action behind it.
- The never-closed plan: lines open for months, no deadline met, no effect measured.
- Orphan actions: impossible to link to a questionnaire, a complaint or a source finding.
- The last-week table: created just before the audit, with dates inconsistent with the sessions actually run — the auditor spots it quickly.
- The other sources ignored: monitoring, incidents, funders’ remarks and internal audits also feed improvement; a plan fed solely by questionnaires looks incomplete.
To situate indicator 32 within the framework as a whole, see the table of the 32 indicators.
The new-entrant case
A provider that has never been audited cannot show loops closed over twelve months: indicator 32 benefits from the new-entrant accommodation. At the initial audit, present:
- the structured improvement plan, even if still sparsely filled;
- the review procedure setting out who analyses what, and how often;
- the planned link with questionnaires and complaints: how the feedback from indicators 30 and 31 will feed the plan.
The actual application of the loop will be checked at the 18-month surveillance audit: start tracing from the very first session, without waiting.
Take action
The Complete Kit Certif (€297, 14-day guarantee) includes the ready-to-fill continuous improvement plan (source, finding, action, owner, deadline, effect), the quality review template and the evidence table for indicator 32. The ebook “Create your training organisation in 30 days” (€67) builds the quality loop in from creation, and the full pack (€347) bundles both.
Frequently asked questions
+How many improvement actions must you present for indicator 32?
The framework sets no quota. For a small structure, three to six real, documented loops per year — including at least one taken all the way to a measured effect — are worth more than a bulky but hollow table. The auditor judges consistency and traceability, not the number of lines.
+What does the auditor actually check on indicator 32?
They often pick one line of your improvement plan and trace it back to its source: a questionnaire verbatim, a falling average score or a complaint. They expect to follow the complete chain — source, analysis, action, measured effect. Prepare two or three complete, consistent threads before the audit.
+Is a gap on indicator 32 a minor or major non-conformity?
Indicator 32 carries a major non-conformity. A declarative quality policy with no traced action, or a plan in which no line can be linked to a real source, can therefore block certification. It is the last indicator in the framework, and one of those the auditor probes the most.
+How is a new entrant assessed on indicator 32?
Indicator 32 benefits from the new-entrant accommodation. At the initial audit, you present the structured improvement plan, the review procedure and the planned link with questionnaires and complaints. The actual application of the loop will be checked at the surveillance audit, around 18 months.