Qualiopi indicator 31 (handling complaints): register, procedure and expected evidence

Criterion 7 of the Qualiopi framework opens with gathering feedback (indicator 30) and logically continues with handling it: that is the purpose of indicator 31, devoted to complaints, difficulties encountered by stakeholders, and incidents occurring during the course of a service. Sanctioned as a major non-conformity, it is often underestimated by people setting up a training organisation, who think they have “never had a problem” — which does not exempt them from having a circuit ready to operate. Here is what the auditor actually checks, the evidence that makes the difference, and the pitfalls that keep coming up in audit reports.

Three distinct matters under a single indicator

The indicator 31 fact sheet actually covers three situations that the auditor clearly distinguishes, even though a single arrangement can handle them all:

• complaints: any written or verbal expression of dissatisfaction calling for a response — a trainee unhappy with the organisation, a funder disputing an invoice, an employer flagging a gap between the advertised programme and the content actually delivered;
• difficulties: obstacles encountered by a beneficiary during training — dropping out, conflict with a peer, unsuitable equipment — which directly overlap with indicators 10 (adapting the service) and 12 (preventing drop-outs);
• incidents: events that disrupt the service independently of the beneficiary’s will — an unavailable trainer, a closed room, a platform outage, a session cancelled for lack of enrolment.

At audit, the most frequent question remains direct: “tell me about a recent complaint or incident, and how you handled it.” A provider who answers with a concrete example, a date and a supporting document reassures the auditor far more than one with a theoretical procedure that has never been put to the test.

Building the circuit, step by step

1. Define what triggers the circuit

One sentence is enough in your quality procedure: “any expression of dissatisfaction, written or verbal, made by a stakeholder and calling for a response, constitutes a complaint.” Specify the preferred entry channel (a dedicated email address, a mention in the internal rules or the welcome booklet) and a workable acknowledgement deadline — 48 to 72 working hours is realistic for a small provider as much as for a CFA.

2. Keep a usable register

A table is enough, provided it documents the whole circuit: number, date, origin, description, severity, corrective action taken, person responsible, handling deadline, closing date. This register, however modest, is the first piece the auditor asks for. Lacking any genuine complaints in the first year, also log minor difficulties that were actually handled: they lend credibility to an arrangement that would otherwise remain purely declarative.

3. Write a continuity plan for incidents

One page is enough: list the five most likely incidents in your activity and the response planned for each — an absent trainer (an identified replacement or postponement within two weeks), an unavailable room (a fallback venue or a switch to a virtual classroom), an LMS platform outage (sending materials through an alternative channel), insufficient enrolment (postponing the session). Specify who informs trainees and the funder, and within what timeframe: this point, often forgotten, is the one audit reports flag most.

4. Close the loop with continuous improvement

Every significant complaint or incident should, where warranted, feed into your continuous improvement plan under indicator 32. The auditor follows this logical thread — a complaint identified, analysed, acted on, and its effectiveness checked — and a complaint handled with no visible follow-through on that plan leaves an impression of being unfinished, even if the initial response was satisfactory.

What research says about complaint handling

The framework’s requirement to document a procedure, a deadline and a traceable response — not just a final outcome — echoes a solid finding from services marketing research. A landmark study by Stephen S. Tax, Stephen W. Brown and Murali Chandrashekaran, published in 1998 in the Journal of Marketing, shows across several hundred complaint incidents that customer satisfaction depends as much on procedural fairness (timeliness, clarity of the steps) and interactional fairness (the quality of the human exchange) as on the outcome obtained itself (see the study). In practice for a training organisation: a prompt acknowledgement and a clear explanation often weigh, in a trainee’s or a funder’s perception, as much as a commercial gesture.

That said, do not count on a well-handled complaint to turn a dissatisfied customer into a better advocate than if nothing had ever gone wrong: a study by Stefan Michel and Matthew L. Meuter, published in 2008 in the International Journal of Service Industry Management and covering more than 11,000 customer interactions in banking, shows that this “service recovery paradox” is a rare phenomenon, with measurable but limited effects (see the study). For indicator 31, the practical conclusion mirrors that of indicator 12 on preventing drop-outs: it is better to prevent incidents through a solid continuity plan than to rely solely on the quality of after-the-fact handling.

The evidence that convinces the auditor

• the written procedure: definition of a complaint, receiving channel, acknowledgement and handling deadlines, designated person responsible;
• the up-to-date register, or one ready to use for a new entrant with no history yet;
• real examples of handled complaints: the initial email, the acknowledgement, the response given, a trace of closure;
• the incident continuity plan, with the fallback solutions planned and the circuit for informing stakeholders;
• evidence of handling a real incident: a collective information email, a session-postponement amendment, a trainer-replacement confirmation;
• mention of the complaints circuit in contractual documents or the welcome booklet, so beneficiaries know how to trigger it.

New entrant: a ready arrangement, with no history to present

A provider going into its initial audit before having handled any genuine complaint presents the procedure, the blank register and the continuity plan: the auditor then assesses the arrangement, as detailed in our article on the accommodations for new entrants. Vigilance shifts to the following surveillance audit, eighteen months later: a register still empty, with no minor difficulty logged, while sessions did take place in between, becomes a legitimate point of attention.

The most frequent mistakes

• Having no register at all, or one created the day before the audit with not a single genuine entry;
• handling complaints verbally without ever putting the response given in writing;
• overlooking incidents: no continuity plan for an absent trainer or an unavailable room, even though these situations are statistically the most common;
• confusing a complaint with a negative rating on a satisfaction questionnaire, which falls under indicator 30 — specify in your procedure the threshold beyond which a very negative rating triggers an entry in the complaints register;
• failing to link closed complaints to the continuous improvement plan of indicator 32, which gives the impression of case-by-case handling rather than a structured quality approach.

If disagreement persists despite a written response consistent with your procedure, recourse to the consumer mediator remains the last-resort channel, complementary to your internal circuit — and its mandatory mention in your terms and conditions is itself checked by the auditor.

Take action

The Complete Kit Certif (€297, 14-day guarantee) provides the complaint-handling procedure template, the ready-to-use register and the incident continuity plan expected for indicator 31, along with the evidence for the other 32 indicators of the framework. The ebook “Create your training organisation in 30 days” (€67) builds this circuit in from the creation of your organisation, and the full pack (€347) bundles both to approach your initial audit without improvising.