For that have been grandfathered in to a position/function, using the results/outcomes of the processes can be an easy and already-in-place to help demonstrate competence. If I'm trained on Process X and there are no defects (or my defect rate is meeting the acceptable target), then it sounds like I'm pretty competent at my job. If, however, I do Process X and my defect rate or customer complaints attributed to my process are high, my competency may be called into question.
I sometimes believe people become so focused on each individual clause that they miss the connections and correlations between them. It's a Business (or Quality) Management System.
A System can be defined as:
Merriam-Webster said:
...a regularly interacting or interdependent group of items forming a unified whole.
As part of an organization's BMS or QMS (and hopefully already in place to some degree before the decision to go down the route of ISO 9001), there are likely processes and tools in place to determine process outputs related to product quality, customer complaints, logistics, and so on. At the end of the day, the whole point of training is to ensure that those outputs related to product quality, customer complaints, logistics, etc. are hitting target. If targets are being achieved, then it does seem reasonable to conclude that the people performing them are competent.
There is little value, in my opinion, in creating a whole new component to the system that focuses solely on competence when the data is already there, as high-level or as granular, as you would like it to be.
Now, if targets are NOT being achieved, that doesn't necessarily mean it's a lack of competence. This is why we have that whole thing related to root cause analysis.
It's a system...not a cluster of silos...take a huge step back and look at what already exists and consider how it can be used to fulfill other requirements within the standard...while still adding value to your organization.
