Show where the requirement comes from
For each competence, identify the role, process, risk or document that creates the need. An auditor can then move from an obligation to the affected person instead of reviewing an isolated course list.
Give the requirement an owner and fulfilment criterion. A trained status alone does not say whether attendance, a test result, task observation or formal authorization is required.
Separate completion from effectiveness
Completing material confirms that an action happened. Effectiveness may require a result, work observation, error review or a manager's decision. Match the method to task risk.
When the criterion is not met, record the response: repeat training, additional explanation or temporary task restriction. This demonstrates an operating system rather than document storage alone.
- competence requirement and criterion
- material and source version
- person and completion date
- result or another effectiveness assessment
- action after the criterion is not met
Build a trace that can be reconstructed
A useful export lets you start with a person and see requirements, or start with a procedure and see every affected person. Both directions should lead to the same records.
Keep the report generation time, filters and version identifiers. They explain why a historical report may differ from the current view.
Questions worth asking
Is a certificate mandatory?
The required record depends on the requirement. A reliable link between person, scope, date, result and source version matters more than certificate appearance.
Does a test always prove competence?
No. A test checks knowledge within a defined scope. Practical tasks may also require observed performance or formal authorization.