Qualiopi8 min read

Qualiopi continuous improvement: building a quality loop that holds up in an audit (criterion 7)

Continuous improvement is where the National Quality Framework ends up — and one of its most misunderstood parts. Many providers reduce it to an “action plan” tab filled in the week before the audit; the auditor, for their part, is looking for a loop: feedback coming in, analyses deciding, actions going out, and evidence that all of it works over time. Here is how to build that loop with indicators 30, 31 and 32, without building a bureaucratic machine.

Criterion 7: three indicators, one single mechanism

Criterion 7 of the framework comprises three indicators, all classed as major non-conformities:

The logic is sequential: 30 and 31 are the loop’s inputs, 32 is its output. That is why an improvement plan disconnected from the satisfaction surveys and the complaints register never convinces: the auditor systematically traces each action back to its source.

The loop in four steps

1. Collect — broadly

The foundation is the trainee satisfaction survey, at the end of the course and ideally complemented by a post-course evaluation. But indicator 30 covers all stakeholders: add an annual feedback round from client companies and funders, and a formalised point with trainers (teaching meeting, trainer questionnaire). A provider that only collects trainee satisfaction leaves a visible blind spot.

2. Handle — including incidents

Handling complaints and incidents requires a single register: who complained about what, when, what was answered, and how quickly. Incidents — absent trainer, platform outage, unavailable room — are logged there too: auditors particularly appreciate providers able to show an incident handled cleanly, because it proves a system that is alive.

3. Analyse and decide

At regular intervals — a quarterly or half-yearly review is enough for a small structure — cross-reference the inputs: falling evaluation scores on a module, a recurring complaint about materials, a funder’s remark. Each significant finding produces a decision: act, monitor, or close with justification. This trace of analysis (a review report, even one page) is what is most often missing from audit files.

4. Act and check effectiveness

Each action joins the improvement plan: source of the finding, action decided, owner, deadline, status, and — the step almost always forgotten — an effectiveness check: did the module’s score recover at the next session? Did the complaint stop? Without this last column, the loop stays open.

This mechanism is none other than the PDCA cycle (Plan-Do-Check-Act) of quality management. A study by Sokovic, Pavletic and Pipan published in 2010 in the Journal of Achievements in Materials and Manufacturing Engineering, “Quality Improvement Methodologies – PDCA Cycle, RADAR Matrix, DMAIC and DFSS”, compares the main improvement methodologies and stresses that PDCA’s effectiveness lies in completing the iteration: organisations that stop after “Do” — acting without checking — capitalise on nothing. That is exactly the gap indicator 32 penalises.

What the auditor actually checks

  • At the initial audit: the existence of the system (questionnaires, register, action plan) and, if activity has started, the first closed loops.
  • At the surveillance audit: this is where criterion 7 becomes central. The auditor picks a complaint or an unfavourable evaluation and pulls the thread: handling, analysis, action, effectiveness. They also check that the action plan has been alive for 18 months — spread-out dates, statuses that evolve.
  • At renewal: the demonstration covers three years, with the underlying question: what has improved since certification?

Findings from a mock audit and non-conformities from previous audits also feed the loop: a corrected and verified gap makes an excellent action-plan line.

An example of a fully closed loop

To make it concrete, here is what a complete loop looks like in a small organisation:

  1. Collection: at the March session, three trainees score 2/5 on the end-of-course survey question “the materials were suitable.”
  2. Handling: the teaching manager records the finding in the register and contacts two respondents — the projected materials were unreadable in the virtual classroom.
  3. Analysis: the April quality review connects this feedback to a similar remark from a trainer; decision: redesign the materials in a format suited to virtual delivery.
  4. Action: a line in the improvement plan — “module 2 materials redesign, owner AB, due June”; status moved to “done” on 15 June.
  5. Effectiveness check: at the September session, the same question climbs to 4.6/5 — the score is entered in the effectiveness column, the loop is closed.

Five lines of traceability, no sophisticated tool — and solid-gold evidence on audit day: this is exactly the thread the auditor will pull.

The mistakes that betray a fictitious loop

  • An action plan written in one sitting, ten lines all dated the same month — the opposite of a living system.
  • Actions without a source: no appreciation or complaint justifies the line.
  • Loops never closed: no status, no effectiveness check.
  • A complaints register empty for two years — statistically implausible; the auditor reads it as failed collection rather than genuine perfection.
  • No trace of analysis between collection and action: the loop skips a step.

Take action

The Complete Qualiopi Kit (€297, 14-day guarantee) includes ready-to-use satisfaction questionnaires, the complaints and incidents register, the quality review template and the continuous-improvement plan — criterion 7’s complete loop, consistent from one document to the next. Building your whole system from scratch? The ebook “Create your training organisation in 30 days” (€67) lays out the method — or take the full pack (€347).

FAQ

Frequently asked questions

+What exactly does Qualiopi require for continuous improvement?

Criterion 7 requires three linked things: collecting stakeholder feedback (indicator 30), handling complaints and incidents (indicator 31), then implementing improvement measures drawn from those analyses (indicator 32). The auditor checks that the loop is closed: a detected dissatisfaction must be traceable through to the corrective action and its effectiveness check.

+Is a simple spreadsheet enough as a continuous-improvement plan?

Yes, the tool matters little. A table with columns for source, finding, action, owner, deadline, status and effectiveness is perfectly sufficient — provided it is fed regularly and contains actions genuinely drawn from the feedback and complaints collected, not generic lines written for the audit.

+Is indicator 32 a major non-conformity?

Yes. Indicator 32, like indicators 30 and 31, is classed as a major non-conformity: an absent or fictitious quality loop can block the issue or maintenance of certification. It is also one of the most scrutinised indicators in surveillance audits, because it can only be demonstrated over time.

+How many improvement actions do you need to show in an audit?

There is no quota. What counts is traceability: a few well-documented actions — each linked to a source appreciation or complaint, with an owner, a deadline and an effectiveness check — are worth more than a long list of intentions. For a surveillance audit, show actions spread across the whole elapsed period.

Read next