Training planning and CPD records that connect to operational need
Training planning works best when it is driven by the gaps the operation actually has. connects the annual and monthly plan to role requirements, then records what was delivered, who attended and what was assessed.
The working planner captures date, duration, objectives, target competencies and attendees. It compares current and if-released crew coverage before people leave duty, names broken requirements and applies a warning or block with an authorised reason. Delivery, individual completion and actual completed CPD hours follow; a completed session alone does not sign off competence.
Planning against requirement
Planning against role requirements gives a dated training session a purpose. Where a competency is due to expire or a position is repeatedly uncovered, that becomes a planning input rather than something discovered later.
A PER19-style annual and monthly template is available in the guided demonstration as an illustration, not as an arbitrary custom template builder.
Planned versus delivered
Before a person is released for training, the planner compares coverage now with coverage if released, names any broken requirement and applies a warn or block policy with an authorised reason. Then teams start the session, record individual attendance and completion, and award CPD only for actual completed hours without duplicates.
Planned sessions with date, duration, objectives, target competencies and attendees
Forecast current and future crewing before releasing attendees
Attendance recorded against each delivered session
Assessment outcomes and assessor sign-off retained
CPD records and hours held on the person's passport
Supporting evidence stored with the record
Evidence that keeps its value
Training evidence tends to be needed long after the session, usually by someone who was not there. Keeping attendance, assessment outcomes, CPD and supporting material on the individual's record means the evidence remains attributable and dated.
It also closes the loop back to readiness: a delivered and assessed session updates the person's competence status, which updates their operational availability, which updates the team's position.
Being clear about what this does and does not mean
Not an LMS
is not a course delivery platform. It plans activity against operational need, records what happened and retains the evidence, so training effort connects to readiness rather than to a catalogue.
Attendance and assessment stay separate
An attendance record shows participation. An assessment record shows a judged outcome against a standard. The two are never merged.
Questions worth asking of your own operation
How much of last year's training plan was actually delivered, and how do you know?
Is your plan built from competency gaps or from last year's plan?
Where are assessment evidence and CPD hours stored today?