Many organizations can produce a list of courses people have attended. Fewer can show that the people who run business continuity, operational resilience or AI governance can actually do the work those systems require. Attendance is not competence. Management system standards treat that distinction as a requirement, not as a training preference.
This article explains why competency development matters, what ISO 22301:2019 and ISO/IEC 42001:2023 require in clause 7.2, how a simple competency framework helps, and how to move beyond attendance certificates to demonstrated competence. It paraphrases the published requirements; audit interpretations should be made against a licensed copy of each standard. OpResONE has no affiliation with ISO, and this article is not an official interpretation of the standards.
Why attendance is not enough
A certificate of attendance answers a narrow question: did this person sit through a course, on a given date, with a given title? That can be useful. It is not the question clause 7.2 of a management system standard asks. The standard asks whether the people doing work under the organization's control, whose work affects the performance of the system, are competent to do that work, and whether the organization can show it.
The gap becomes visible at the moments that matter. A business continuity plan is exercised, and the person who is supposed to invoke it cannot do so without the author in the room. An AI system is extended into a new use, and no one in the owning team can apply the organization's impact assessment method. An auditor asks for evidence of competence, and the organization produces a folder of attendance certificates with no link to roles, no evaluation of whether the training worked, and no record of people who learned the job by other means. In each case the organization has invested in training and still cannot demonstrate competence.
Competency development is the work of closing that gap on purpose: deciding what "competent" means for each relevant role, helping people get there, checking that the help worked, and keeping evidence. It is broader than a course catalogue, and it is one of the quieter reasons management systems either hold up under scrutiny or do not.
What clause 7.2 actually requires
ISO 22301:2019, Security and resilience — Business continuity management systems — Requirements, and ISO/IEC 42001:2023, Information technology — Artificial intelligence — Management system, are both management system standards. In both, clause 7 is Support, and clause 7.2 is Competence. The clause number is not an accident of either standard; it reflects ISO's common structure for management system standards.
In ISO 22301:2019, clause 7.2 requires the organization to determine the necessary competence of persons doing work under its control that affects its business continuity performance; ensure that those persons are competent on the basis of appropriate education, training or experience; where applicable, take actions to acquire the necessary competence and evaluate the effectiveness of the actions taken; and retain appropriate documented information as evidence of competence. A note in the standard explains that applicable actions can include training, mentoring or reassignment of people already employed, or the hiring or contracting of competent persons.
ISO/IEC 42001:2023 likewise places a competence requirement in clause 7.2. In substance, the clause requires the organization to determine the competence needed for people doing work under its control that affects AI performance; ensure those people are competent on the basis of appropriate education, training or experience; take action where needed to acquire that competence and evaluate the effectiveness of the actions taken; and retain documented information as evidence of competence. Leaders should confirm the exact wording against a licensed copy of ISO/IEC 42001:2023 when they prepare for audit.
Four obligations follow from that wording, and they are easy to miss if "competence" is treated as a synonym for "we sent people on a course."
- Determine the competence required. This is a design task. The organization has to say, for the work that affects business continuity performance or AI performance, what people must be able to do. A generic course title does not do that work on its own.
- Ensure people are competent. Education, training or experience are all acceptable bases. The standard does not require a classroom course, and it does not treat a course as automatically sufficient.
- Take action and evaluate it. If there is a gap, the organization must do something about it and then check whether that action worked. Booking a course and filing the confirmation email is only the first half of this obligation, and only if a course was the right action.
- Retain evidence of competence. The evidence is of competence, not only of attendance. A signed register can support the record. It does not, by itself, complete it.
Clause 7.3, Awareness, is a related but narrower requirement: people need to be aware of policy, of their contribution, of the implications of not conforming, and, in ISO 22301, of their own role before, during and after disruptions. Awareness is not a substitute for the competence of the people whose work affects the system's performance. Both have their place. Confusing them is how organizations end up with wide awareness campaigns and thin competence where it is needed.
A competency framework that can actually be used
A competency framework is simply a structured answer to the first obligation in clause 7.2: what competence is necessary, for whom? It does not have to be a large proprietary model, and this article does not recommend a particular branded framework. It has to be specific enough that a manager, a trainer and an auditor can tell whether a person in a given role is competent.
In practice, a usable framework does four things. It names the roles that affect the performance of the management system — for a business continuity management system, that may include the executive sponsor, the continuity or resilience lead, service or process owners, people who will invoke plans, and internal auditors; for an AI management system, policy owners, implementers, system owners and internal auditors. It describes, for each role, the knowledge, skills and behaviours required, in language tied to the organization's actual system. It sets the level of proficiency the role needs, so that awareness, practitioner ability and the ability to lead or audit the system are not treated as the same. And it says how competence will be obtained and how it will be evaluated, including paths that do not run through a classroom.
Two design choices keep such a framework honest. First, write it in the language of work, not only in the language of courses: "can lead a business impact analysis for a prioritized activity," "can apply the organization's AI impact assessment method to a new use case," "can interpret a scenario-test finding for the executive sponsor." Second, review it when the system changes. New services, new AI uses, new suppliers and new regulatory expectations all change what competence is necessary. A framework that is updated only when a course catalogue is reprinted will drift away from clause 7.2.
From attendance certificates to demonstrated competence
Once the required competence is defined, the organization can choose how people will gain it and how it will evaluate whether they have done so. Training remains important. Mentoring, supervised practice, exercises, prior experience and hiring or contracting competent people are also valid actions, as ISO 22301:2019 itself notes. The quality of the evidence depends on whether it shows competence, not only participation.
| What you can show | What it tends to prove | Where it is weak |
|---|---|---|
| Attendance certificate or sign-in record | That a person was present at a learning event | Does not show that the person can apply the method in their role, or that the training was effective |
| Examination or structured assessment against the role's required competence | That, at a point in time, the person could demonstrate specified knowledge or skill | Still needs to be tied to the organization's actual system, and refreshed when the work changes |
| Observed performance: exercises, supervised work, audit participation, completed assessments | That the person can do the work in conditions closer to real use | Needs a consistent way to record what was observed, against the competence required for the role |
| A personal training certificate for an implementer or auditor role | That a person completed a provider's course or assessment | Belongs to the person; it does not certify the organization's management system, and it is not issued by ISO |
The move "beyond attendance certificates" is therefore not an argument against training. It is an argument for closing the loop that clause 7.2 already requires. After the action — a course, a mentoring period, a new hire — the organization should evaluate effectiveness. That evaluation can be an observed exercise, a work sample, a short practical assessment, or a period of supervised practice with a recorded outcome. It should be judged against the competence the role requires, not against whether the person seemed engaged on the day.
Internal audit and management review are where this becomes visible to leadership. If the only competence evidence the system can produce is a list of courses, auditors have little to test except whether the list is complete. If the system can show role requirements, actions taken, evaluations and decisions about people who are not yet competent to work unsupervised, leadership can see whether the management system is staffed for the work it claims to do. For auditor roles themselves, ISO 19011:2026, Guidelines for auditing management systems, provides guidance on audit principles, audit-programme management, conducting audits, and a framework for auditor competence and evaluation. It is a guidance standard; ISO states that using it does not itself lead to certification. It is a useful reference when an organization is defining what "competent to audit this system" means.
What leaders should do next
- Inventory the roles that affect the system's performance. Do this separately for the business continuity or resilience system and for the AI management system if you have or are building both. Do not start from the course list.
- Write the competence required for each role in the language of work. Keep it short enough to use. If a manager cannot tell whether a person meets it, it is not yet a clause 7.2 determination.
- Record how each person in those roles is competent — by education, training or experience — and where there is a gap.
- Choose actions that close the gap, then evaluate them. A course may be the right action. So may mentoring, an exercise, a reassignment, or hiring. Whatever you choose, decide in advance how you will know it worked.
- Keep evidence of competence, not only of attendance. Store attendance records if they help, but pair them with the role requirement and the evaluation.
- Review the framework when the work changes, and include the state of competence in management review, not only in a training budget discussion.
For a wider view of moving from paperwork to confidence, see From Compliance to Confidence.
How OpResONE can help
OpResONE helps organizations treat competence as a requirement of their management systems, not as a record of courses attended. OpResONE offers instructor-led and self-paced training aligned to these standards. OpResONE does not issue organizational management system certificates and is not a certification body.
We bring BRILLIANCE to RESILIENCE®.
Request a Strategy Call
If you want a focused discussion of how to define, develop and evidence competence for your business continuity, operational resilience or AI management system, talk with OpResONE.
Sources
- ISO, ISO 22301:2019 Security and resilience — Business continuity management systems — Requirements (viewed 16 November 2026)
- ISO, ISO/IEC 42001:2023 Information technology — Artificial intelligence — Management system (Edition 1, published December 2023; viewed 16 November 2026)
- ISO, ISO 19011:2026 Guidelines for auditing management systems (Edition 4, published May 2026; viewed 16 November 2026)

