Indicator 32 — Continuous improvement

What the auditor actually checks

Indicator 32 closes the framework and criterion 7: it verifies that the collected feedback (indicator 30) and handled complaints (indicator 31) produce real change. It is the proof-by-action indicator: the auditor does not want a quality statement of intent, they want to follow the full thread of at least one improvement:

1. The source: a survey verbatim, a falling average, a complaint, a funder’s remark, an internal finding.
2. The analysis: why this point is a problem, which cause was identified.
3. The action: what was changed — a rebuilt deck, an adjusted duration, a new format, a change of room or tool.
4. The verification: the effect measured on subsequent sessions (the score rises, no further remark on that point).

At a new entrant’s initial audit, the reading guide’s accommodation applies: with no session history, you present the planned system (a ready improvement plan, a defined circuit). Real implementation is checked at the surveillance audit — hence the importance of making the plan live from your first sessions.

Achieving compliance, step by step

1. Create your continuous improvement plan

A single table: number, date, source (questionnaire, complaint, watch, internal audit), finding, decided action, owner, deadline, status, observed effect. It is criterion 7’s central document — the auditor will ask for it within the first five minutes on this indicator.

2. Feed it at a defined rhythm

Set a quarterly review (or after each session while starting up): re-read the indicator 30 compilations and the indicator 31 register, open a row for each significant point. Three to six rows a year suffice for a small structure — what matters is that they are real and followed through to the “effect” column.

3. Close the loops

A row forever “in progress” is worth nothing. Date the closures and note the effect: “logistics score up from 3.6 to 4.4 over the next two sessions”. That kind of wording turns an administrative table into proof of effectiveness.

4. Tie the whole of criterion 7 together

Before the audit, verify the cross-traceability: every improvement must trace back to its source (a specific questionnaire, a numbered complaint), and your published results (indicator 2) must reflect the claimed progress.

Field advice

The auditor often picks a row of your plan themselves and walks the thread back to the source questionnaire. So prepare two or three complete, impeccable loops rather than a twenty-row approximate table. And think beyond questionnaires: an improvement born from your watch (indicators 23-25) or a well-handled incident shows a quality system that breathes.

Among the improvement sources auditors look at most: dropout causes. The annual review described in dropout prevention (indicator 12) feeds your action plan directly — link the two documents explicitly.

Examples of evidence that passes the audit (real cases)

Documents actually shown in audits and deemed convincing for indicator 32:

• The continuous improvement plan with closed loops: source, finding, action, person in charge, deadline, status and — above all — the “observed effect” column filled in. Three complete loops beat twenty “in progress” lines.
• One exemplary loop documented end to end: the questionnaire verbatim (“room too small, couldn’t hear at the back”), the plan line, the invoiced room change, and the logistics score rising from 3.6 to 4.4 over the next two sessions.
• Minutes of periodic quality reviews: a dated quarterly half-page listing the sources re-read (questionnaire compilations, complaints register) and the lines opened or closed.
• Successive versions of an amended document: programme v1 and programme v2 with the change driven by beneficiary feedback — material proof that feedback produces change.
• The complaints register linked to the plan: every significant complaint (indicator 31) points to an improvement line, and vice versa.
• For a new entrant: the ready-to-run system — a structured plan (even empty), a dated review procedure, a defined circuit. The auditor validates the system at the initial audit and its implementation at surveillance.

Continuous improvement procedure outline (template)

Your procedure fits on one page, structured as follows:

1. Purpose and person in charge — who steers the system, and the central document (the continuous improvement plan).
2. Input sources — questionnaires (indicator 30), complaints (indicator 31), drop-out causes (indicator 12), monitoring (indicators 23 to 25), funder remarks, incidents and audits.
3. Review rhythm — quarterly, or after each session in the start-up phase; systematic re-reading of the sources.
4. Opening and qualifying actions — one line per significant finding: cause analysis, decided action, person in charge, deadline.
5. Follow-up and closure — every line is tracked through to its observed effect, dated and quantified where possible.
6. Annual review — overall review, consistency check against published results (indicator 2), decisions for the coming year.

The complete version of this procedure, ready to customise field by field, is in sheet 32 of the kit — together with the ready-to-fill continuous improvement plan and the quality review template.