AFEST Funding by OPCOs: The Acceptance Criteria

In summary

An AFEST pathway gets accepted by an OPCO when it combines 4 elements: structured instructional design, a genuine reflective phase, usable documentary evidence, and traceability of the whole approach.

The most sensitive criterion remains the ratio between the number of hours and the skill actually being targeted: a file needs to demonstrate proportionality, not just display hours.

The reflective phase needs to be real and observable, not just claimed, and documentary evidence matters just as much as the pedagogical pathway itself.

The regulatory vocabulary used matters too: AFEST is a way of delivering a training action, not a "scheme" in the strict sense, and confusing it with simple informal mentoring weakens the file.

At Daylindo, we support companies in structuring and tracing their AFEST pathways, from the pedagogical skeleton through to the tooling and the evidence of completion expected by funding bodies.

Why do some AFEST pathways get accepted by an OPCO, while others get challenged, delayed, or called into question?

The answer isn't just down to the quality of the tool used. Based on our experience, we've identified a few shared good practices. Because the tool doesn't do everything.

Without the right tooling, it becomes hard to track work situations, log hours, keep hold of evidence, organise reflective phases, and produce the supporting documents expected. But the tool is what makes a well-structured AFEST visible, traceable and secure. That's what an OPCO looks at: the coherence between the skills targeted, the work situations, the volume of hours, the reflective phases, the assessments, and the documentary evidence. How do you demonstrate that an AFEST pathway is solid, proportionate, and compliant?

1. The most sensitive criterion: the ratio between hours and the skill actually acquired

An AFEST pathway shouldn't just display a volume of hours. It needs to justify it. This is a major point when a file gets reviewed.

An OPCO doesn't look at hours as a simple administrative figure. It checks whether the planned time genuinely matches the skill being targeted.

The driving licence comparison is a good one: you don't spend 300 hours to reach an objective that only needs 20. The same logic applies to AFEST.

If the volume of hours looks disproportionate compared with the know-how being transmitted, the file becomes fragile. Conversely, if the hours are clearly tied to activities, practice sessions, reflective phases and assessments, the file becomes far easier to defend.

The question isn't how many hours you can get funded, but how many hours are genuinely needed to acquire, practise, analyse and consolidate the skill. It's this proportionality that carries real weight in whether the pathway gets accepted.

2. AFEST isn't ground-level time dressed up as training

AFEST rests on a simple idea: a work situation can become a learning ground. But that doesn't happen automatically.

The fact that an employee learns on the job isn't enough on its own to qualify as AFEST. You need pedagogical intent, a framework, support, a reflective phase, and an assessment.

A solid AFEST pathway needs to show clearly targeted skills, work situations chosen because they're conducive to learning, periods of support, practice sessions, reflective phases, assessments, and bundles of evidence kept on file.

It's this structure that turns a professional activity into a training pathway. An OPCO expects to see how the company genuinely organises skill development.

3. Before the "how", you need to justify the "why AFEST"

Many presentations start with the operational rundown. That's useful, but it isn't always the right starting point. Before presenting the "how", you need to explain the "why".

Why choose AFEST over classic training? Why go through work situations? Why structure learning that may already have existed informally? Why is this format relevant for this role or this audience?

This justification shows that AFEST isn't being used as an administrative dressing, but as a genuine pedagogical answer.

A good argument often starts from the ground: in many companies, a large share of learning already happens on the job. But it's informal, inconsistent, poorly traced, and hard to assess. AFEST makes it possible to structure this learning.

The tool gives a framework to what was scattered, and supports this shift.

4. The reflective phase needs to be real, not just claimed

The reflective phase is one of AFEST's essential markers. It shouldn't be treated as a formality. An AFEST expert will try to understand how it actually plays out in practice.

Does the learner answer alone? Does the mentor step in? Is the exchange live or delayed? What questions get asked? Is a record kept? Does the analysis genuinely allow the learner to look back on the action?

This decisive phase is what turns experience into learning. Without reflectivity, you're still close to a simple supported practice session. With genuine reflectivity, you move into structured training territory.

The tool can help a great deal here, particularly when it structures the questions, keeps records, and makes it easier for the mentor to give feedback. If artificial intelligence gets involved, it needs to stay a support. It shouldn't replace human exchange.

5. Documentary evidence matters as much as the pathway itself

A pathway can be pedagogically coherent but weak on the documentary side. This is often an underestimated point.

An AFEST expert or a legal department will want to know what can be produced in the event of an inspection. Did the training genuinely take place? Was the learner present? Are the hours justified? Are the reflective sequences recorded? Are the assessments kept on file? Is there an equivalent to a sign-in sheet? Is there a certificate of attendance?

These are very concrete questions.

The tool plays a central role here. It needs to allow a shift from a self-reported logic to an evidence-based one. So you need to be able to show the corresponding documents or exports: a record of attendance, hours tracked, an assessment grid, evidence of a practice session, a record of the reflective phase, a summary of the pathway.

A digital tool doesn't necessarily need to reproduce traditional paper documents identically. But it needs to produce equivalents that are readable, usable and defensible. It's this capacity for evidence that secures the file.

6. Funding also comes with its own criteria

An OPCO obviously looks at the funding framework. Depending on the scheme used, the criteria can vary: minimum duration, eligible audience, the recognition being targeted, certification, collective bargaining agreement, professionalisation contract, skills development plan, and so on.

The file therefore needs to be clear on several points: total volume of hours, the split between formats, any regulatory thresholds, mandatory and optional blocks, the effects of personalisation, the recognition being targeted if any, and the training provider's status.

Personalisation deserves particular attention. Adapting a pathway to the learner's starting level is good practice, of course, without losing control of the framework (hours tracked, blocks completed, evidence available, and thresholds to respect).

7. Regulatory vocabulary matters

This point might seem secondary. AFEST isn't a "scheme" in the strict sense. It's a way of delivering a training action. Using the right terms shows that the company has a firm grasp of the framework.

Loose vocabulary can create distrust. A precise presentation, by contrast, reassures.

It's best to avoid phrasing like: "We do AFEST because employees learn on the job."

It's better to show that the company doesn't confuse work, informal mentoring, and structured training. Prefer saying: "We've designed a training action that includes an AFEST format, with work situations conducive to learning, reflective sequences, assessments, and associated documentary evidence."

8. What a good AFEST tool needs to be able to demonstrate

In an AFEST project, the tool needs to serve the pedagogical design. It shouldn't just track a pathway. It turns pedagogical design into a file that's readable, traceable and defensible. It needs to help prove it.

AFEST tooling therefore needs to clearly answer several questions: which skill is being targeted? Which work situation makes it possible to acquire it? How many hours are planned? Why is this volume of hours coherent? Which practice sessions took place? Which reflective phases happened? Which assessments were carried out? Which evidence can be produced?

At Daylindo, the tool is designed to structure and give value to a well-designed AFEST: structuring the AFEST, making mentors' work easier, tracking learners' progress, and producing the evidence needed for stakeholders.

What Daylindo brings to the strength of your AFEST file

Beyond the tool, what Daylindo brings is the ability to connect the 4 elements that get an AFEST pathway accepted by an OPCO, pedagogical design, the reflective phase, documentary evidence, and traceability, within a single platform. This approach connects with the logic of a skills-based organisation: what happens on the ground needs to feed through to the funding file without any break or re-entry of data.

Evidence from companies that have structured their AFEST pathways on this basis confirms the point made in this article: a defensible AFEST file is above all a demonstrable file, not just a well-intentioned one.

Conclusion: an accepted AFEST pathway is a demonstrable pathway

Validating an AFEST pathway doesn't rest on a general impression. It rests on a demonstration. An OPCO wants to know whether the pathway is coherent, proportionate, traceable and defensible.

The driving licence image sums up the challenge well: you don't spend 300 hours on an objective that only needs 20. But nor do you claim to seriously train someone in a complex skill without enough time, without practice, without reflectivity, and without evidence.

This balance is what determines how solid an AFEST file is. The goal is to make AFEST demonstrable: pedagogically, regulatorily, and documentarily.

If you want to check where your next file stands on this balance, a conversation or a demo of the Daylindo platform can make things clear within minutes.

FAQ

What does an AFEST pathway need to look like to satisfy an OPCO?

A pathway that combines coherence between hours and the skill targeted, a genuine reflective phase, and usable documentary evidence.

How many hours does an AFEST need?

There's no standard volume. The volume needs to be proportionate to the skill genuinely being targeted, neither under-sized nor inflated.

Is the reflective phase mandatory?

Yes. Without it, the approach stays a supported practice session, not an AFEST in the regulatory sense.

What evidence can an OPCO ask for?

A record of attendance, hours tracked, an assessment grid, evidence of a practice session, and a record of the reflective phase.

Is a digital tool enough on its own to secure an AFEST file?

No. The tool makes the pedagogical design visible and traceable, it doesn't replace it.

How does Daylindo get involved in this process?

Daylindo supports the structuring and traceability of the pathway, from the pedagogical skeleton through to the evidence expected by funders.