Three records, three different decisions
Use one row for a person, a task and a source version. A completion date shows when the learning activity ended. It does not establish practical competence or independent-work authorisation.
Use the workbook
- The first record has a completed knowledge check and a practical observation. The second still needs a practical check. The third relates to an earlier procedure version and requires a review after the change. Keep the exception owner and evidence ID visible.
- Transfer the assessed task status into the competency matrix. Keep the underlying assignment, source version, result and reviewer record so the matrix can be traced back to its evidence.
Worked example
Fictional people and local test criteria. Completion, knowledge, practical performance and permission for independent work are separate decisions. Fictional people and local test criteria. Completion, knowledge, practical performance and permission for independent work are separate decisions.
| Person / role | Task and source | Material version | Completion date | Knowledge result | Practical check | Renewal trigger | Exception owner | Evidence |
|---|---|---|---|---|---|---|---|---|
| Person DEMO 01 / packer | Label check / SOP-LAB-01 | 3 | 2026-10-20 | 8/8, local criterion 7/8 | Passed OBS-DEMO-01 on 21 Oct | Label procedure changes | Shift leader | TR-DEMO-01; OBS-DEMO-01 |
| Person DEMO 02 / operator | Line clearance / SOP-LC-02 | 2 | 2026-10-21 | 7/8, local criterion 7/8 | Not yet checked; supervised work only | Practical check before independent work | Line supervisor | TR-DEMO-02; observation pending |
| Person DEMO 03 / warehouse | Goods receipt / SOP-GR-03 | 4 | 2026-10-10 | 8/8 for version 4 | Old check applies to version 4 only | Version 5 released on 28 Oct; reassignment open | Warehouse lead | TR-DEMO-03; CHANGE-DEMO-05 |
Download without a form
Keep records that explain a decision
An employee training record should show why an activity was required, what the person completed and what the organisation concluded from it. A folder of certificates may show attendance without connecting it to current duties. A spreadsheet of green statuses may show a decision without explaining its evidence. The useful record connects both sides and gives a supervisor enough context to discuss progress without asking the employee to reconstruct their training history.
ISO's public guidance on documented information for the 2015 edition recognises different media and documentation suited to the organisation [1]. It does not establish a universal training file format or retention period. The proposed fields below are an operational method for making records interpretable, rather than a claim that every field is mandatory in every setting.
Apply data rules to every record medium
Training records can contain personal data even when they include only names, employee identifiers and results. EDPB guidance addresses purpose, minimisation, accuracy and storage limitation [2]. Its security guidance also supports appropriate access and protection measures [3]. Paper forms, spreadsheets and dedicated systems each need practical rules.
Begin by identifying the purpose. The record might support a procedure handover, task authorisation decision, development plan, contract requirement or specific legal obligation. Purpose determines the relevant evidence, recipients and retention. Keeping information merely because it might someday be interesting is not a useful design principle.
Identify the person without adding unrelated information
Use an identity method sufficient to distinguish employees reliably. A name may be ambiguous, especially where names repeat or change. A stable internal identifier can help connect assignments and historical results, provided its use and access are appropriate to the purpose. Do not automatically add a home address, national identity number or unrelated health information to the training register. Those fields usually do not help establish which procedure was completed. If a specific process requires additional information, identify its purpose and applicable basis separately.
Clarify how identity is confirmed for the activity. An authenticated account, supervised session and imported paper form provide different evidence. The record should describe the actual method where relevant. A file checksum cannot establish participant identity, and a typed name should not be described as a stronger signature than it is. Include workers outside the permanent employee roster when the requirement applies to them. Agency staff, substitutes and contractors can need site-specific instruction. Define how their records are linked and who coordinates the information. Collect only the relevant evidence; avoid copying an entire personnel file from another company to prove one local completion.
Connect the requirement to the exact material
Record the task, role, process or other source of the requirement. A course title alone does not explain why a person needed it. If the obligation follows a revised instruction, identify the document's stable identifier, release and effective date. Link the learning material to its source. A summary, presentation or exercise can have a separate version from the procedure. The record should show which release the person received, especially where later corrections change a critical step. Historical completions must not inherit new content automatically.
Retain the assessment version where a knowledge check is used. A score has little meaning without the scope and acceptance criterion. Different question sets can produce different results even when participants have similar knowledge. Avoid treating every course with the same title as an identical assessment. For an illustrative cleaning instruction, the procedure might change the response to an incomplete rinse. The completion record should identify the revised instruction and learning material, while any practical check should identify the observed task. This lets a reviewer distinguish learning about the new response from demonstrating correct execution under working conditions.
Preserve events and decisions separately
Useful events include assignment, deadline, completion, attempts and follow-up. Decisions include accepting evidence, recognising competence, granting authorisation or approving an exception. These are related but not interchangeable. The record should identify what happened and who had authority to make the conclusion. Keep unsuccessful attempts where they are relevant under the retention rules. A later successful repeat does not make the earlier event disappear. The sequence can explain additional instruction and show which topics needed clarification. At the same time, restrict access to detailed results to the people who need them for the stated purpose.
Record practical assessment distinctly. Include task scope, date, assessor, conditions, assistance and conclusion as appropriate. If a separate formal authorisation is required, link its record without presenting a learning score as the approval itself. For corrections, preserve a clear explanation. A wrong employee identifier, duplicate assignment or mistaken date may need an authorised update. State what was corrected, why and by whom where the process requires that trace. Do not add fictitious training events to repair a current status. The corrected record should describe the actual event as accurately as available evidence allows. For imported evidence, retain the origin and explain any transformation. An external course completion can be relevant without matching the organisation's local procedure. Record the recognised scope and any additional check needed for local work. If the available document does not include a result or material version, label that limitation rather than inventing the missing field. A clear incomplete record supports a sensible follow-up; a complete-looking record based on assumptions can encourage an unsupported decision.
Handle validity and retraining without erasing history
Validity can come from a specific legal rule, qualification, contract or internal requirement. Identify that source and apply its scope. There is no universal annual expiry for every employee course. Some learning needs are better reviewed after changes, incidents, unsuccessful assessments or long breaks from the task. When retraining is assigned, create a new event linked to the reason. Preserve the earlier release and result. This allows the organisation to understand what applied before the change and whether the response occurred before the person resumed affected work.
For absence and transfer, update the current requirement deliberately so the receiving leader can prepare the person's next steps instead of chasing an old assignment list. A person on leave may not need immediate access to the course, but can need the current instruction before returning to the task. A person transferred away from the process may retain historical evidence without appearing in the present assignment population. Give unresolved requirements an owner. An expired record is not controlled merely because it appears red. Someone must decide the relevant action: reassessment, supervised work, restriction, scope correction or another response under the organisation's rules. Record the decision and the evidence needed to close it.
Set retention from purpose and obligations
Create a retention rule for the relevant record category. Consider legal obligations, employment rules, sector requirements, customer contracts, potential claims and the organisation's legitimate evidence needs. Those factors differ across jurisdictions and activities, so a single invented duration cannot be applied to every training record. EDPB guidance requires storage limitation and recognises that national obligations can affect retention [2]. Once a record is no longer necessary and no applicable obligation requires it, deletion or anonymisation may be appropriate. Document how the organisation determines that point and who owns the process.
Distinguish underlying evidence from extra copies. A controlled assessment record may need retention, while a temporary export used to prepare a meeting can become unnecessary earlier. Mail attachments and local downloads can extend the information footprint without adding evidence. Include those copies in the workflow where practicable. Avoid collecting everything in anticipation of an undefined future audit. It creates a larger access and retention problem while making relevant evidence harder to find. A defined record set with reliable links is often more useful than a large archive of duplicate certificates, personal notes and unlabelled reports.
Restrict access and test retrieval
Assign access according to duties. A supervisor can need task status and next actions; a coordinator can need assignment history; an authorised assessor can need relevant results. Broad access to every employee's detailed answers is not automatically necessary for any of those roles. Review permissions after transfers and departures. EDPB security guidance recommends appropriate user identification, authentication, access review and protection [3]. Shared accounts and uncontrolled folder links can make it difficult to identify who viewed or changed a record. Use controls suited to the environment and the sensitivity of the information.
Test retrieval from two starting points. Select a person and find the applicable requirement and evidence. Then select a revised procedure and identify the affected people, completions and exceptions. If the trace depends on one coordinator's memory, improve the record relationships or agreed storage location so the leader can find what is needed before a development conversation. Prepare exports for the recipient's question. Include generation time, filters and source versions, and omit unrelated personal fields. Verify that supporting links work for the authorised recipient. A report that can be opened but cannot be explained is not a complete evidence handover.
Build a minimum record through a real example
Choose one procedure change and map the record from requirement to completion and follow-up. Identify which fields genuinely help reconstruct the decision. Add practical assessment and authorisation references where the task needs them. Remove information that contributes nothing to the purpose.
CrewShift can support procedure assignments, completion scores, history and exports. Create an account and confirm those capabilities in the actual product workflow with your sample. Ask the leader to prepare a returning employee's learning follow-up and note which record searches or duplicate updates are still needed. It does not replace the organisation's retention decision, practical competence assessment or task authorisation rules.
Define the fields and preserve their meaning
Write a short data dictionary. Define each status, date and identifier so another person can maintain the records. Include rules for absence, transfer, unsuccessful attempts and corrections. The method can remain simple while still being clear enough for handovers and review.
The record is useful when it tells a bounded, accurate story: this person had this requirement, completed this version, achieved this result and received this decision. Preserve that story for the required period, protect access and keep current requirements separate from historical events. More fields do not automatically provide stronger evidence. A clear record should help the leader spend the next conversation on the employee's work and development, with the relevant history already to hand.
Questions worth asking
Must employee training records be kept in a dedicated training system?
There is no universal rule for every organisation. The record needs to be reliable, current and reproducible. A spreadsheet may be enough for a simple process, but versions, deadlines and exceptions increase reconciliation cost as the process grows.
Can old results be deleted after retraining?
Usually the history should be retained under the organisation’s defined retention rules. Earlier results explain what applied at the time and which actions were taken. The specific retention period depends on the underlying requirements.
Does every record need a national identity number?
No. Use only information necessary to identify the person and support the defined purpose. Additional personal fields require their own justification.
Can a practical decision be kept outside the training tool?
Yes, provided it is controlled, retrievable and clearly linked to the relevant person and requirement. Do not represent a missing practical decision as a passed course.
Sources and scope
- ISO / TC176 — guidance on documented information (ISO 9001:2015)
- European Data Protection Board — data protection basics
- European Data Protection Board — secure personal data
- ISO 10015:2019 — official ISO page
This informational material does not replace licensed standards or individual legal advice.

