Separate training attendance from permission to perform a task

Training attendance records what learning activity took place. A competence assessment records what an appropriately qualified assessor evaluated and concluded. Authorisation records the organisation's decision to permit a specified activity, subject to its procedures and conditions. These records may be linked, but they should not be collapsed into one green tick.

The UK HSE's description of competence combines knowledge, skills, experience and the ability to apply them in the relevant work. It supports the distinction between attendance and capability; it is UK guidance, not a statement of Indian licensing requirements. Applicable qualifications and statutory conditions need separate qualified review.

A matrix should therefore show enough evidence for an authorised decision-maker to act. It should not calculate permission from a weighted score across unrelated training courses. Several completed courses cannot compensate for an unmet mandatory prerequisite.

Consider a fictional worker who attended electrical training at Site A and was assessed for a defined maintenance task there. The worker transfers to Site B, which has different equipment and site procedures. The training record remains part of their history. The Site A authorisation does not automatically become a Site B authorisation.

The receiving manager reviews the task requirements, relevant assessment evidence and any local prerequisites. If further assessment or familiarisation is required, the matrix records pending review and the owner. It should not erase previous competence, but it should withhold the new permission until the authorised process reaches a decision.

Suppose the manager approves only a limited task under specified supervision. Record that condition explicitly. A broad label such as electrically competent would be too vague for the next supervisor making an assignment. The worker and supervisor should both be able to see the permitted scope in language they understand.

The full evidence store may contain course records, assessment outcomes, assessor details and supporting documents. The assignment view should answer a narrower question: is this person authorised for this task here, at this time, under these conditions?

Useful fields include person identity, task or equipment scope, site or system, authorising person, issue and review dates, current status, restrictions and the source decision. Where a permission has no simple expiry date, record the review trigger or condition rather than inventing one.

Use distinct labels for not assessed, assessment pending, authorised, suspended, expired and revoked. Explain what each means for assignment under the organisation's procedure. A blank cell should never be interpreted as unrestricted permission. Keep the assessment details accessible only to roles that need them.

Permissions can be affected by an equipment change, revised procedure, lapse in a required qualification, new information from an incident or a change in role. Define who can initiate a review and who can suspend or restore permission. The software should record the reason and effective time without rewriting the earlier authorisation.

When a worker is already assigned, a status change needs an operational handoff. Notify the responsible supervisor through the approved site process and obtain acknowledgement where required. A dashboard update alone may not reach someone in the field.

Test what happens to a device that cached yesterday's matrix. Show its last synchronisation time and prevent stale data from being presented as current approval. The project must define the permitted offline process. The application should expose uncertainty and direct the user to that process, rather than guessing that an old authorisation is still valid.

Even a currently authorised individual may need a separate permit, isolation confirmation or other prerequisite for the actual work. The matrix can establish one input to that process; it cannot grant the work release by itself. The HSE's permit-to-work guidance treats permits within a wider control system, not as a substitute for risk assessment.

In the interface, avoid a button labelled safe to work if it merely checks training records. Use a precise label such as authorisation record current for selected scope. Link the relevant work-control process where appropriate, with separate owners and statuses.

This distinction also helps procurement and subcontract management. A contractor's general capability statement may support prequalification, while named people still need assessment and assignment permissions under the project's arrangements. Neither record should be used as a shortcut around the other.

For a small site, a controlled register with a disciplined update and verification process may work. A workforce platform becomes useful when scopes, transfers and review cycles are numerous. A learning management system may be strong on course history but need integration for task authorisation. Compare the ability to answer the assignment question, not the number of certificate templates.

Demonstrate an expired permission, a revoked permission on an offline device, a transfer and a limited authorisation. Verify that a supervisor can distinguish all four without opening confidential assessment notes. Check who can override restrictions and whether the actual procedure permits that action.

A good matrix makes both the permission and its limits clear. It protects the meaning of training records while giving site managers a dependable basis for the next authorised step.

1. Choose one task family and define the scope needed for an assignment decision.
2. Separate existing attendance, assessment and authorisation records for that task.
3. Have qualified owners review ambiguous or transferred permissions.
4. Test status changes and offline use before relying on the matrix during allocation.