Decide what the record is supposed to establish
An acknowledgement records receipt of a specified material version. Training is an activity intended to develop knowledge or skills. A competence assessment checks whether a person meets the requirements of a particular task. These records can complement one another, but each answers a different question and needs its own assessment criterion.
"I have read the procedure", "I passed the knowledge check" and "I can perform the task" are different statements. They need different evidence. Combining them into one completed status makes a report easier to scan while making its meaning harder to defend. Start by deciding which statement the organisation needs for the specific change or task.
The ISO and IAF Auditing Practices Group's public competence guidance explains that participating in training does not necessarily demonstrate competence [1]. ISO's guidance on documented information for the 2015 edition also recognises different media for records [2]. Neither source establishes that a particular click or attractive certificate is universally sufficient for every purpose.
Match evidence to the intended statement
Safety-related work adds its own context. The EU framework directive addresses appropriate instruction and training relevant to work and changes [3]. National and task-specific obligations can determine form, process and evidence. Do not market a general procedure acknowledgement as an automatic substitute for required safety instruction or practical assessment.
The method below is a proposed way to choose evidence proportionate to the intended outcome. It separates receipt, understanding, performance and authorisation. Some tasks need only one of those stages; others need several. The responsible owner should make that decision and preserve the reason, so supervisors can plan support without debating the meaning of a completion status each time.
Use acknowledgement for a genuine communication objective
Acknowledgement can show that a person received identified material and performed the defined confirmation action. It is useful for an administrative update, a revised contact route or information that does not itself require demonstrating a new skill. The record should identify the source release and date. Keep the wording within what happened. If the action is opening a page and clicking confirmation, describe it as acknowledgement of the named material. Do not label it observed competence or a passed assessment. A statement that the person understood everything can exceed what the workflow actually checked.
An illustrative example is a change to the contact responsible for ordering replacement labels. Relevant staff need the new route, while the production method remains unchanged. A targeted acknowledgement can be proportionate if no additional requirement applies. A lengthy general quiz may add burden without improving the communication objective, taking time from the employee and the leader who must follow up on it. Provide a way to ask questions. Acknowledgement should not force a person to make an inaccurate statement when the material is unclear or inaccessible. Define how they report the issue and how the owner responds. The record can distinguish outstanding clarification from simple non-completion. Silence and a clicked button are not the same as a resolved ambiguity. Consider access barriers before treating missing acknowledgement as refusal. The person may have no suitable device, an expired account or material in a language they cannot use reliably. Record the barrier and arrange the relevant support. Once access is restored, the confirmation should identify the material actually received. Do not backdate the event to the original invitation or let a coordinator click on behalf of the employee while representing it as the employee's own action.
Use knowledge checks for defined understanding
A knowledge check is useful when the person must recognise a condition, choose a decision or explain a rule. Design it against the approved source and the intended learning objective. The result should identify the material, question set and acceptance criterion used. Use realistic scenarios. An illustrative revised inspection instruction can ask what happens after two inconsistent readings. The answer should follow the approved response, including who decides the next step. A question asking for the procedure's document number checks recall of an identifier rather than understanding of the changed work.
Check question quality before publication. Avoid ambiguity, clues in the answer wording and alternatives that are all partly correct. A low result may reveal an unclear question. A high result may reflect easy guessing. The content owner should assess whether the questions actually test the required decision. State what the result means. Passing can demonstrate the assessed knowledge within the defined scope. It does not automatically establish skill in setting up equipment or applying an inspection method under production conditions. If the task needs those capabilities, retain the knowledge result as one stage and add the appropriate practical evidence.
Observe performance when the task requires it
Practical assessment examines the work itself or a suitable simulation. Define the task, conditions, critical steps and expected result. The assessor needs enough understanding to recognise errors and interpret assistance. A tick beside a name without scope tells little about the capability assessed. Consider an illustrative machine-changeover exercise. The employee must select the correct settings, verify the setup and respond to an abnormal condition. A quiz can check the decision rules, while observation reveals whether the person performs the sequence correctly. Those records complement each other without becoming interchangeable.
Record whether prompting was needed. A successful result under close supervision can be a development milestone rather than evidence of independent performance. The assessor can set further practice and a later check, using the observed difficulty to explain or demonstrate the step with the employee. Avoid converting every supervised task into a blanket competence approval. Choose assessment conditions according to risk and applicable requirements. One narrow observation may not represent complex work under varied conditions. Equally, demanding an elaborate practical assessment for a simple administrative update can create unnecessary activity. The goal is suitable evidence for the decision, rather than maximum paperwork for every communication.
Keep authorisation as an accountable decision
Authorisation answers whether a person is permitted to perform a defined activity under the organisation's rules and applicable obligations. It can depend on training, competence evidence, qualifications and other conditions. The authorising role should be identified separately from the person who administers the learning activity. State scope and limits. Permission may apply to a particular machine, task, location or supervised arrangement. A course title with broad wording should not expand that permission automatically. If a person moves to different equipment, review whether the existing evidence and approval remain relevant.
Record the decision, date and basis. A formal authorisation may be held outside the training tool, provided the relationship remains clear and retrievable. Avoid using a green training status as a substitute when the organisation's process requires a separate approval. When a requirement expires or work changes, determine the consequence deliberately. A reminder or a red status does not independently revoke or extend permission. The organisation needs an applicable rule and an owner who acts on it. Preserve the history of earlier approval while updating the current decision.
Choose the evidence level from the change
Review what changed for each role. A new telephone number, revised acceptance limit and altered physical setup do not create identical needs. Identify whether the objective concerns communication, knowledge, practical performance or permission. Then choose the relevant evidence and deadline. Use the simplest method that answers the question reliably. Acknowledgement can suit receipt; a scenario can suit a decision; observation can suit performance. A combination can be appropriate where the task needs several stages. Do not add a signature and quiz to every editorial correction merely to standardise the screen layout.
Conversely, do not reduce a critical change to acknowledgement because it is quicker. An employee may confirm reading without recognising a new stop condition. If the consequence of misunderstanding is significant, the owner should select an assessment that makes the relevant understanding or behaviour visible. Record the rationale for the chosen level where it matters. This makes later review possible and helps coordinators apply the rule consistently. An assessor or auditor can then see why a particular activity had only acknowledgement while another required practical evaluation. The difference reflects the work rather than arbitrary treatment of employees.
Design the records so their meanings remain visible
Use clear status labels: acknowledged, knowledge check passed, practical assessment accepted and authorised where applicable. If the organisation uses a combined ready status, show its acceptance rule and supporting stages. The reader should be able to see which evidence created that conclusion. Preserve source and material versions. A later procedure revision should not change what an earlier acknowledgement or result refers to. Create the relevant new assignment after an impact decision and retain the earlier event. This allows a historical review to reconstruct what applied at the time.
Keep unsuccessful attempts and follow-up under the retention rules. A later passed assessment can close the current learning gap while the earlier result explains additional instruction. Do not replace the sequence with a single status that implies first-time success. Describe confirmation methods accurately. An authenticated click, typed name and qualified electronic signature are different mechanisms. Which form is required depends on the specific process and applicable law. Do not claim that every click has the legal characteristics of a qualified signature, or that paper is universally the only permitted medium.
Pilot the distinction with one revised procedure
Select a procedure containing a communication change, a decision rule and a practical step. Ask the owner to define evidence for each affected role. Then run the workflow and inspect whether the report keeps those stages distinct. Include one unsuccessful result and a follow-up decision.
CrewShift can support procedure assignments, knowledge checks, completion history and exports. Create an account and test these capabilities for the learning elements they actually record. Ask a leader to identify who needs clarification and who needs a separate practical check, without collecting fresh status reports from everyone. Practical competence and authorisation remain decisions for the organisation, supported by appropriate evidence. A completion certificate should describe the completed activity rather than promise compliance or unrestricted capability.
Test whether supervisors understand the status
Ask a supervisor to interpret the resulting status without an explanation from the project team. Can they tell whether the person merely acknowledged information, passed a defined test or received permission for independent work? If not, revise the labels and links before expanding the workflow.
Accurate distinctions reduce confusion at the point of decision. The organisation can use a simple acknowledgement confidently when receipt is the real objective, and demand stronger evidence when work requires it. The record becomes more useful because its meaning matches what was actually checked and approved. Leaders can then direct their follow-up to the explanation, practice or decision a person actually needs.
Questions worth asking
Is an “I have read this” click a valid record?
Yes, when the organisation genuinely needs acknowledgement. It is not automatically proof of understanding, practical skill or formal authorisation.
Is an electronic signature required for every acknowledgement?
There is no universal rule for every process. The form of confirmation should follow the legal, contractual or internal requirement and the level of assurance needed.
Does a confirmation click have the status of a qualified electronic signature?
Not automatically. Different confirmation mechanisms have different characteristics. Required form depends on the specific process and applicable law.
Can a combined ready status still be useful?
Yes, if its acceptance rule and supporting evidence stages are clear. Supervisors should be able to distinguish receipt, knowledge, practical assessment and permission.
Sources and scope
- ISO / IAF Auditing Practices Group — guidance on auditing competence (2015 edition context)
- ISO / TC176 — guidance on documented information (ISO 9001:2015)
- EU-OSHA — OSH Framework Directive 89/391/EEC
- ISO 10015:2019 — official ISO page
This informational material does not replace licensed standards or individual legal advice.

