Implementing AFEST: What needs to be secured in the field

Implementing an AFEST is not simply about sending an employee to learn directly in their workplace. The framework is precise: Action de Formation En Situation de Travail (AFEST), or work-based training, relies on cumulative legal requirements and genuine instructional engineering.

For an L&D department, HR department, or training organization, the challenge is not simply to identify one or more work situations. It is about turning work into a learning environment, involving the right field trainers at the right time, documenting the training action, and retaining the required evidence, as with any training activity.

In summary

● An AFEST is based on 4 cumulative legal requirements: activity analysis, prior appointment of an AFEST tutor to support the learner, reflective phases, and specific assessments.

● The approach must start from actual work, rather than from an HR framework disconnected from the position.

● The program must be equipped to document observations, the delivery of reflective phases, and competency validation without creating excessive administrative workload. This traceability is essential to meeting the requirements applicable to the training activity.

Why is implementing AFEST more complex than on-the-job training?

In simple tutoring, a field trainer generally demonstrates a task, the employee reproduces it, and the manager declares them autonomous. Knowledge and skills have been transferred, but this does not necessarily constitute an AFEST. The difference lies in the instructional engineering behind the program : which competencies are being targeted, which activity has been analyzed, how does the tutor support the employee in the workplace, and what dedicated time allows the employee to step back and reflect on the action? Above all, what records and evidence can demonstrate that the training actually took place, particularly when dealing with an OPCO?

Without a structured method, the process relies on a few heavily solicited field tutors, Excel spreadsheets, and reports reconstructed after the fact. The result: a significant operational workload and insufficient traceability in the event of an audit.

The 4 legal requirements for AFEST

The French Labour Code provides a specific framework for AFEST. Article D6313-3-2 sets out four cumulative requirements.

1. A prior analysis of the work activity

You need to examine what the person actually does: tasks, actions, decisions, and difficulties. This means going beyond the job title alone. This analysis enables the field trainer to identify learning situations and build a framework that can be used on a daily basis.

“Masters their job” tells a field tutor very little. A specific task and its success criteria do.

2. A tutor appointed before the training begins

The Labour Code provides for the prior appointment of a third party (expert, knowledgeable professional, or trainer) who can perform a tutoring function. In practice, the tutor is usually someone who knows the job on a day-to-day basis.

The person who performs a task best is not necessarily the person who knows how to teach it best. They must therefore be identified, their role clarified, and a clear framework provided so they can observe, facilitate practice, and give structured feedback.

3. Reflective phases separate from the work activity

This is the point that is most often underestimated. AFEST is not limited to observing someone at work. The field trainer must set aside dedicated time for the employee to reflect on what they have just done: Why was this decision made? What differed from what was expected? This phase, distinct from the work situation itself, transforms experience into learning.

4. Specific assessments of learning outcomes

The objective is not simply to check whether the activity was completed. The assessment must be linked to the targeted competencies and to criteria defined beforehand, using a framework that formalizes levels and observable criteria.

This is the transition from “the activity was completed” to “the competency has been demonstrated.”

Deploying AFEST without creating an administrative burden

Start with the position, not the catalog. Identify, together with your subject-matter experts and field tutors, the critical tasks and competencies to be mastered, then identify the situations in which they can be observed. At Daylindo, a competency is defined as a combination of knowledge, know-how, and behaviors expressed through observable and assessable actions. It is not simply a line in a training catalog.

Structure work-based learning situations. Select learning-oriented work situations that genuinely allow the targeted competencies to be developed and repeat them until mastery has been achieved. Give your field trainers shared observation criteria to prevent two experts from training two employees in the same position according to different standards.

Assess throughout the learning journey. Successive observations make it possible to monitor progress and determine which work situations need to be repeated, rather than waiting until the end to conduct an assessment.

Traceability: the critical challenge of AFEST

In the field, knowledge transfer is already happening. The problem is that it is difficult to prove. A field tutor has supported an employee, a debriefing has taken place, and a competency appears to have been acquired. But where is the evidence? In an Excel spreadsheet, an email, or personal notes?

This fragmentation becomes critical when an organization needs to reconstruct a learning journey for a Qualiopi audit or an OPCO funding application. The logic must be reversed: evidence should be produced as the activity takes place and timestamped, rather than reconstructed weeks later.

This is where the Daylindo approach makes a difference. The platform collects and timestamps activities, observations, and work-based learning situations directly within a coherent learning journey adapted to the learner. Tutors annotate results, while competency frameworks structure the assessment.

The result is a consistent chain:

competency framework → work situation → observation → reflective phase → assessment → evidence.

This is the difference between training data and field competency data: data that genuinely answers the question of who can do what, today, in their position.

Securing OPCO funding

The question of funding cannot be separated from the quality of the training program. To demonstrate the value of an AFEST program to an OPCO, the organization must document the reality of the learning journey: analyzed activity, identified field trainer, completed work-based learning situations, reflective phases, and assessments.

The Daylindo approach avoids manually reconstructing files after the fact. This is particularly important for training organizations and CFA apprenticeship centers, where a significant part of the learning journey takes place within companies, where traditional tools provide limited visibility.

Stop Confusing Training Completion with Demonstrated Competency

Implementing an AFEST is not simply a matter of regulatory compliance. It means structuring an approach that already exists informally in many organizations.

The Labour Code establishes the framework. Instructional engineering transforms work into learning situations. The field trainer leads the knowledge transfer. The Daylindo approach preserves a record of what has been observed and validated: the chain that takes an organization from training delivered on the job to a demonstrated and defensible field competency.

FAQ

What are the 4 requirements for implementing an AFEST?Activity analysis, prior appointment of a trainer, distinct reflective phases, and specific assessments of learning outcomes (Article D6313-3-2 of the French Labour Code).

Does an AFEST have to take place at the employee's workstation? Yes. It must also be integrated into structured instructional engineering rather than left to improvisation.

Who can be the tutor in an AFEST? A trainer appointed in advance who can perform a tutoring function. In practice, the tutor is often the person who has day-to-day expertise in the job.

How can an AFEST be documented and tracked? By producing timestamped, defensible evidence at each stage of the learning journey (work-based learning situations, support from the field trainer, reflective phases, and assessments) to document that the training actually took place and secure OPCO funding applications.

Why structure knowledge transfer with a digital tool? A digital tool does not replace the field tutor or instructional engineering. It makes it possible to structure and document a program involving multiple activities and stakeholders, while collecting evidence as the work takes place rather than reconstructing it afterwards.

How can you secure your AFEST program?Check the four regulatory components and ensure they are translated into operational processes: targeted competencies, an identified field trainer, reflective phases, and available defensible evidence.

Do you already have an on-the-job training process but no reliable view of the competencies actually acquired?

Daylindo supports organizations that want to structure the transfer of operational competencies, equip their field trainers, deploy workplace learning journeys, and document demonstrated competencies.

Would you like to know whether your AFEST program is genuinely traceable?

Request a diagnosis of your field-based training program