Improvement board: the complete file that prevents major non-compliance

Of all the Qualiopi audit topics specific to CFAs, the development council is the most paradoxical: a legal obligation known to all, an exclusively major indicator (number 20)… and yet one of the most fragile files encountered during audits. Not because the council doesn't meet—but because it doesn't leave the right traces. Here is the complete file, piece by piece, that puts the subject out of danger.

What the auditor is really looking for

The labor code requires CFAs to establish a development council that examines issues related to its organization and operation: educational project, results, integration, living conditions of apprentices, evolution of the offering. Indicator 20 makes it a full-fledged Qualiopi requirement, alongside mobility and disability referents.

But the auditor doesn't just check that the council exists. They check that it serves a purpose—and their method relies on three questions asked in this order: "show me the minutes," "who sits on it?", and the crucial question: "what follow-up actions have you taken on its recommendations?". It's on the third question that files often fall apart.

Piece n°1: a solid composition

A development council is not an expanded management meeting. Its strength—and its credibility in an audit—comes from the presence of the CFA's real stakeholders:

• CFA management, which presides;
• Teaching teams—not just managers: a field trainer has a full place there;
• Apprentices, represented by their elected delegates (this is the direct link with indicator 14: without documented elections, there are no legitimate delegates on the council);
• Employers—tutors, apprenticeship masters, representatives of partner companies or sectors.

The critical point experienced: the effective presence of apprentice delegates and employers. A council where only CFA employees sit, meeting after meeting, will inevitably trigger the question, "what about the apprentices and the companies?". Date your meetings taking into account alternating rhythms, send invitations early, and if a college is absent, note it in the minutes with the planned follow-up—documented effort counts.

Piece n°2: an agenda that addresses the core issues

The council examines the actual progress of the CFA. A solid agenda—and it's the same skeleton for each meeting, which simplifies everything—covers four blocks:

1. Quantified assessment: headcount, exam results, rupture and dropout rates (distinguishing between the two), integration of graduates;
2. Stakeholder feedback: satisfaction summaries, delegate feedback, employer feedback;
3. CFA life and projects: evolution of the offering, resources, events, partnerships;
4. Council opinions and recommendations—the block that must exist as such in the minutes, we'll come back to it.

Frequency: two meetings per year is the comfortable standard (one for assessment at the end of the training year, one for orientation during the year); one seriously conducted annual meeting remains defensible, zero never is.

Piece n°3: minutes that isolate recommendations

This is the formal detail that changes everything in an audit. Minutes that recount the meeting as it happens drown the council's opinions in the report. Effective minutes include a dedicated, clearly titled section—"Opinions and recommendations issued by the council"—followed by a second: "Follow-up actions decided by the CFA", with a reference to your action plan for each action.

The typical example of a complete loop

What does a successful recommendation → action → effect loop look like? A classic case: at the November council, apprentice delegates report difficulties with lunch catering on site. The minutes record the recommendation in its dedicated section. The CFA adds an action to its plan ("set up an equipped meal area—source: development council of 11/14"), with a pilot and a deadline. At the next council meeting, the point is reviewed: area opened in February, positive feedback from delegates, action completed.

Nothing spectacular—and that's the goal. A modest but complete and traceable loop is infinitely more valuable than a grand ambition that remains only in the minutes.

The 4 errors that weaken the file

1. The recording council: minutes where the council "takes note" of everything and never recommends anything. Solicit opinions—a final round table "what do you recommend?" is enough.
2. Orphaned follow-ups: recorded opinions for which no trace can be found in the action plan. This is the broken loop that the auditor detects first.
3. Phantom delegates: inviting unelected apprentices "to make up the numbers." Without election minutes (indicator 14), representation is not valid—the two indicators are checked together.
4. Minutes written months later: minutes dated, distributed to members within two weeks with meeting attendance, locks in the credibility of the entire system.

Your file in 5 pieces, ready for audit

Ready-to-fill templates

The Cap Certification Kit—119 documents contains the complete development council file ready for personalization: composition, invitation, standard agenda in four blocks, minutes template with pre-structured "recommendations" and "follow-up actions" sections—plus the action plan that receives the follow-up actions, the election minutes for delegates, and the expert sheet for indicator 20 with the questions actually asked in audits and your sheet to complete.

And to situate this indicator among the 31 others—especially the 17 that, like it, fall under direct major non-conformity—the Qualiopi Audit Guide deciphers them one by one in 33 pages.

Article written based on experience from actual Qualiopi audits in CFAs. Official requirements are found in the Labor Code (development council), the National Quality Framework and its reading guide—consult the current versions.