Eight people, three tasks and a missing substitute
Start with tasks that need a different assessment or permission. For each person, record knowledge, practical performance, authorisation and presence separately. In this example, only four confirmed fields count as independent coverage.
Use the workbook
- DEMO 05 is the only available person authorised for goods receipt on the evening shift. There is no substitute for that task. DEMO 07 has a practical check for line clearance but no independent-work authorisation, so the workbook does not count that person as cover.
- The workbook counts coverage by shift and task. It does not schedule simultaneous tasks or create authorisations. Check workload, timing, absence and the underlying evidence before changing an assignment.
Worked example
Fictional team. 1 = confirmed, 0 = not confirmed. Knowledge, practice, independent-work authorisation and presence must all be 1. Counts of two or more are a substitute check for this example, not a staffing standard. One person cannot cover overlapping tasks at once. Task cells: knowledge / practice / independent-work authorisation. 1 = confirmed, 0 = not confirmed.
| Person | Shift | Label check | Line clearance | Goods receipt | Present |
|---|---|---|---|---|---|
| DEMO 01 | Morning | 1 / 1 / 1 | 1 / 1 / 1 | 1 / 0 / 0 | 1 |
| DEMO 02 | Morning | 1 / 1 / 1 | 1 / 1 / 1 | 1 / 1 / 1 | 1 |
| DEMO 03 | Morning | 1 / 1 / 1 | 1 / 0 / 0 | 1 / 1 / 1 | 1 |
| DEMO 04 | Morning | 1 / 1 / 1 | 1 / 0 / 0 | 1 / 0 / 0 | 1 |
| DEMO 05 | Evening | 1 / 1 / 1 | 1 / 1 / 1 | 1 / 1 / 1 | 1 |
| DEMO 06 | Evening | 1 / 1 / 1 | 1 / 1 / 1 | 1 / 0 / 0 | 1 |
| DEMO 07 | Evening | 1 / 1 / 1 | 1 / 1 / 0 | 1 / 0 / 0 | 1 |
| DEMO 08 | Evening | 1 / 1 / 1 | 1 / 0 / 0 | 1 / 0 / 0 | 0 |
Download without a form
A matrix should answer an operational question
A training matrix becomes useful when it helps a supervisor decide who can perform a task today, where supervision is needed and which gaps will matter next week. A wall of coloured cells can look complete while concealing obsolete requirements, missing workers and unverified competence. Design the matrix around decisions before designing its appearance.
ISO 10015 frames competence management and people development as connected activities [1]. The APG’s public guidance also distinguishes course participation from evidence of competence and discusses assessment methods suited to the context [2]. These sources support a structured approach, but a matrix is an organisational method rather than a universal form prescribed for every employer. Its value depends on the meaning of each status and the evidence behind it.
Distinguish knowledge, performance and permission
Separate knowledge, observed performance and authorisation. A person can know a procedure without being competent to perform its most difficult step. They can demonstrate a task under supervision without holding a required formal authorisation. If all three become a single green cell, the matrix invites decisions that its evidence cannot support.
Write down the decision each view supports. A shift planner needs current task eligibility. A training coordinator needs upcoming assignments. A process owner needs coverage of a changed instruction. These views can use the same records while displaying different fields, sparing each leader the work of rebuilding a separate list before a team discussion.
Model requirements independently of people
Create a requirement catalogue before populating individual rows. Each requirement should identify its source, scope, owner and acceptance criterion. Sources can include a procedure, safety assessment, customer contract, role description or formal authorisation rule. The catalogue explains why the organisation expects particular evidence. Avoid creating a new requirement simply because a course exists. A course is one possible development activity. The requirement should describe the knowledge, behaviour or permission needed for a task. Otherwise the organisation accumulates courses without a clear relationship to work.
Use task assignments to supplement job titles. Two technicians with the same title may work on different equipment. A warehouse employee who acts as a relief operator needs the relevant production requirements as well. A supervisor covering another area may need a different escalation instruction. Preserve the relationship between the person and the task that creates the requirement. Consider an illustrative food production example. All staff entering a controlled area need applicable hygiene instructions. Employees changing product need the line-specific changeover method. People verifying allergen cleaning need an additional assessment appropriate to that duty. Creating separate requirements lets the organisation target learning instead of assigning every course to every person.
Define evidence and status before choosing colours
For each requirement, identify the evidence needed to recognise fulfilment. It may be acknowledgement, a knowledge result, an observed task, an external qualification or a documented approval. Include the acceptance criterion and the role allowed to make the decision. The matrix should show which stage has been reached. Useful states include not yet assigned, assigned, awaiting assessment, fulfilled, unsuccessful, expiring and overdue. A separate exception state can be useful where a defined restriction or supervision arrangement exists. Give every state a clear meaning and next action. Avoid a vague intermediate colour that different managers interpret differently.
Derive states from records and rules where possible. A validity date should change the status consistently. A new material version should trigger the owner's impact decision rather than silently turn every cell red. An unsuccessful assessment should remain visible until the appropriate follow-up is completed. Use text as well as colour. Status labels support people who cannot distinguish particular colours and make exports easier to interpret. Include a short legend with the acceptance rules. A reader should not need to ask the spreadsheet owner whether pale green means trained, experienced, approved or simply invited.
Keep individual evidence separate from the current view
The matrix is a view of current relationships and evidence. It should not become a second manually maintained register that takes the supervisor away from coaching each time a result changes. Preserve the underlying requirement, assignment, attempt and assessment records, then use them to calculate the status shown for each person. This distinction matters when a worker moves between tasks. The current view may stop showing an old requirement, while the historical record still explains work performed previously. Similarly, a revised procedure can create a new assignment without rewriting the older completion. History belongs to the event that actually happened.
Link each fulfilled status to the evidence supporting it. Identify the person, source release, assessment date, result and assessor where relevant. If an external qualification is used, retain enough information to verify its scope and validity under the organisation's rules. Do not treat a decorative certificate as more persuasive than a clear record of an observed task. When evidence arrives from another system, decide which record is authoritative. Copying scores into several files introduces reconciliation work. A stable reference can be preferable to duplicating an entire document, provided access and retention remain sufficient to reconstruct the decision when needed.
Plan validity around the requirement
Validity can arise from legislation, an external qualification, a contract or an internal risk decision. Record the applicable source. Do not give every course a twelve-month expiry simply because an annual cycle is easy to administer. A new critical procedure step may need action tomorrow; an unchanged low-risk topic may not justify annual reassessment. Include event-based review as well as calendar dates. A role change, new equipment, long absence, repeated error or incident can change the relevance of existing evidence. The requirement owner should decide what happens after each event. For practical skills, the period without performing the task may matter more than the time since a generic course.
Define how expiring evidence affects planned work. Can the person work under supervision? Must a formal authorisation remain valid? Who may approve a temporary arrangement? These questions belong to the operational process. A training matrix can expose the condition but cannot make the organisation's safety or authorisation decision by itself. Distinguish a reminder from closure. Sending an email thirty days before expiry is an action taken by the system. It does not establish that a place was booked, the assessment happened or the person may continue working. Give the unresolved gap an accountable owner.
Use the matrix to identify coverage problems
Review coverage at the task and shift level. A plant can have many trained employees overall while lacking anyone available for a specific line on a particular shift. Availability, competence and authorisation are separate inputs. A useful planning view brings them together without altering their meaning. An illustrative scenario makes the issue clear. Four people have evidence for a specialist inspection, but two are on leave and one has moved to another area. The headcount suggests resilience; the schedule reveals dependence on one person. The response may be development of another inspector, a change in work allocation or a defined contingency arrangement. Use the gap to plan supervised practice with a colleague before the team depends on a single available person.
Prioritise gaps by consequence and timing. A missing critical task capability before a scheduled production run deserves attention before a low-risk administrative acknowledgement due next month. This is a management decision informed by the matrix, not a claim that every overdue cell has equal importance. Use the same logic for new starters. Identify what they need before entering an area, before supervised work and before independent work. A staged plan provides more control than assigning the entire course catalogue on the first day. It also helps the new worker understand which activities they may perform at each stage.
Review data quality when the organisation changes
Assign responsibility for changes to employment status, role, team and task allocation. A matrix built on an old roster will produce misleading percentages even if each formula works correctly. Define how departures, transfers, agency staff and temporary substitutions reach the record owner. Review a sample from both directions. Select a person and inspect whether their actual duties match assigned requirements. Then select a critical task and check whether all people performing it appear in the matrix. The second direction often reveals people missed by title-based assignment.
Check for duplicated identities and ambiguous names. A stable employee identifier can prevent results being attached to the wrong person, but access to identifiers should remain appropriate to the purpose. EDPB guidance emphasises minimisation, accurate personal records and a defined purpose [3]. Do not add personal details merely to make a report look comprehensive. Status and evidence should be sufficient for the decision at hand. Exports need a generation time, scope and legend. A dated spreadsheet can be a useful review snapshot. Once managers start manually updating exported copies, it becomes a competing register. Decide whether changes must return to the authoritative source and make that workflow explicit.
Introduce the matrix through one real process
Begin with a team and a set of tasks that have meaningful differences in evidence. Include one new starter, a substitute role, an upcoming expiry and a changed procedure. This gives the pilot enough variation to reveal weaknesses without demanding a company-wide data cleanup before learning anything.
Agree success criteria before the pilot. A supervisor should be able to identify the people eligible for a selected task, open supporting evidence and see the owner of any gap. A coordinator should be able to reproduce the population affected by a revision. These are observable outcomes, unlike an impression that the dashboard looks tidy.
Repair definitions before expanding
CrewShift can help organise procedure assignments, completion results, history and exports. Those records can support a matrix, provided the organisation defines what each requirement means and retains practical assessment or authorisation evidence where needed. Create an account and confirm the current product workflow with your sample process. Check whether leaders can find the learning evidence needed for a development conversation without reconciling several files. A score must not automatically become permission to work.
Review the pilot's exceptions before expansion. Missing role ownership, unclear validity rules and inconsistent assessment decisions will follow the data into any tool. Fix those definitions first. A matrix stays current when work changes feed its requirements and records. That upkeep should give leaders a usable basis for deciding who needs practice or support; a colourful file does not maintain itself.
Questions worth asking
Can a spreadsheet still be used as an export?
Yes. It is useful as a dated, filtered snapshot as long as it is not manually maintained as a second register afterwards.
How often should the matrix be reviewed?
After material changes to roles, procedures or the team, plus a risk-based periodic review. A calendar alone does not replace change-triggered review.
Does a fulfilled training requirement mean a person is authorised?
Only if the defined requirement includes the appropriate authorisation decision and its evidence. Knowledge, observed performance and permission should remain distinguishable.
How do substitute duties affect the matrix?
Requirements should follow actual tasks as well as job titles. Add the relevant requirements when the person is assigned substitute work and preserve their historical evidence.
Sources and scope
- ISO 10015:2019 — competence management and people development
- ISO / IAF Auditing Practices Group — guidance on auditing competence (2015 edition context)
- European Data Protection Board — data protection basics
This informational material does not replace licensed standards or individual legal advice.

