Competency Records and Training Evidence for Equipment Servicing
A department that cannot show who was competent to perform a task cannot demonstrate that the task was performed competently, and the two are routinely assumed to be the same thing. Competence is a…
A department that cannot show who was competent to perform a task cannot demonstrate that the task was performed competently, and the two are routinely assumed to be the same thing. Competence is a specific property: a technician trained on one platform is not thereby competent on another, and a person who has attended a course is not necessarily authorised to work unsupervised. Competency records exist to close that gap between what a person knows and what the organisation can demonstrate. This article sets out what a competence record has to show, which parts only an external party can supply, and what its absence costs.
What the Document Set Is For
The record set answers a question that arises in three different contexts: whether a person was competent to perform the work they performed, whether the organisation authorised them to do it, and whether the competence is still current. Those are separate questions, and a file that answers only one of them leaves the organisation unable to demonstrate the position it relies on.
The practical value is not only defensive. A competence record makes it possible to assign work sensibly, to identify where the organisation depends on a single person, and to plan training against gaps rather than against availability of courses. The extractable summary is this: a competence record shows what training and assessment a person has completed, which equipment and activities it covers, who authorised them to work and whether the competence remains current.
There is a second reason the record matters that is easy to overlook. Competence is not permanent, and equipment changes rather than people. A technician trained on a platform several years ago may now be working on a version of that platform with different components, different software and different service procedures, and the certificate will not show the difference. Keeping the mapping between competence and current equipment is what prevents a valid certificate from being applied to equipment it no longer describes.
| Question | What the record has to show | Where the evidence comes from |
|---|---|---|
| Is the person trained | Programme, platform, date, assessment outcome | Training provider or manufacturer |
| Is the competence current | Refresher or reassessment dates | Training provider or internal assessment |
| Is the person authorised | Scope of authorisation and who granted it | The employing organisation |
| Is the competence relevant | Equipment and activities the training covered | Training provider and the department’s own mapping |
| Has it been applied | Records of work performed within scope | Service records and work allocation |
Which Documents Only the Original Owner Can Produce
Training certificates are issued by whoever delivered the training, and the department cannot create them. Where training is delivered by a manufacturer or an accredited provider, the certificate or attendance record originates outside the organisation and should be obtained in a form that names the platform and the scope.
The assessment of competence, as distinct from attendance, is the second item in this category. A course completion record shows that a person was present; an assessment shows that they can perform the task. Where the training provider issues an assessment outcome, that outcome is the stronger evidence, and where no assessment exists, the organisation has to make its own judgement and record the basis. The third item is the manufacturer’s own service documentation, because it defines the activities that competence is being assessed against, and a department cannot create that either.
Which Documents a Dealer Can Reconstruct
The organisation can construct the whole of the local half of the record, and this is where most files are weakest. The authorisation that states what a person may do, the scope limits attached to it, and the date it was granted are internal documents that no external party provides.
The organisation can also construct the mapping between a person’s training and the equipment it actually maintains, which is the step that converts a certificate into a usable competence claim. A certificate naming a platform means little until somebody records which of the department’s devices that platform covers. The work allocation record is the third reconstruction: a record of which tasks were performed by whom, which allows the organisation to show that work was performed within scope rather than assuming it.
A fourth internal document is worth adding and is rarely produced: a statement of what the department cannot do. Where a platform has no competent person, or where a particular activity is outside everyone’s authorised scope, that gap is a fact about the department’s capability, and it determines which work has to be outsourced. Departments that record their gaps plan better than those that record only their capabilities, because the gap is where an unexpected failure becomes an emergency.
Verifying a Document Is Authentic and Current
Verification in this area is a matter of consistency between the certificate, the authorisation and the work performed.
| Check | What a failure indicates |
|---|---|
| Certificate names the platform and the activity | The competence may be broader than the evidence |
| Date and validity | The competence may have lapsed or predate a change in equipment |
| Assessment outcome, where issued | Attendance may be being presented as competence |
| Authorisation on file and matching the certificate | Work may be performed outside the granted scope |
| Equipment mapping current | The department’s equipment may have changed since the training |
| Work records within scope | Work may have been performed by someone not authorised for it |
Redaction and Confidentiality
Competence records contain personal information, and the file needs to be handled accordingly. The practical approach is to keep the technical content legible while limiting the personal content to what is necessary, and to store the records under the same access controls as other personnel information rather than in a general equipment folder.
What should remain visible is the platform and activity the competence covers, the date and validity, the assessment outcome and the authorisation. What can be limited is personal detail that does not bear on the competence question. Where records are shared with an external party, for example during a vendor assessment or a sale, the technical content is what the recipient needs, and the sharing should be limited to that rather than to the whole file.
Retention and Handover
Competence records have to be retained for at least as long as the work they support could be questioned, and the practical consequence is that the retention period is measured in years rather than months. A service record that names a technician is only supported if the technician’s competence record for that platform is still available.
Handover matters in two directions. Where a technician leaves, the records of work performed during their employment remain relevant to the equipment, so the file cannot be closed when the person departs. Where a service is outsourced, the incoming provider needs to know what competence the outgoing arrangement rested on, because that determines what has to be replaced. Where equipment is sold, the competence behind its service history is part of what makes that history credible.
What Its Absence Means for the Buyer
The absence of competence records changes what a service history can support, and the change is predictable.
- Without a named platform on the certificate, the competence may cover different equipment from the one in front of the buyer.
- Without an assessment outcome, attendance is being presented as competence, which is a weaker claim.
- Without an authorisation record, the organisation cannot show that the work was within the person’s scope.
- Without an equipment mapping, the link between the training and the device has to be assumed.
- Without work allocation records, there is no evidence that the competent person performed the work.
- Without a retention position, the records may have been destroyed before the equipment’s history ceased to matter.
Two further consequences are worth stating because they affect commercial decisions rather than only compliance. The first is that a resale file supported by competence evidence is easier to accept and easier to value, because the buyer can see that the work was performed by somebody qualified for it. The second is that the absence of such evidence shifts verification work into the buyer’s acceptance process, and that is a cost the buyer will price into the purchase whether or not they say so.
Where the destination market places expectations on equipment and its documentation, those are illustrated in one market by the MHRA guidance on regulating medical devices, and cross-market expectations for equipment and safe use are summarised by the WHO medical devices programme. Where a service conclusion rests on a measurement, the traceability of the instrument used forms part of the evidence, and the ILAC accreditation directory allows a provider’s calibration status to be checked.
Buyers who want the wider context can start from the knowledge hub, see how equipment and its service position are described on the marketplace store, or use the service material in the industry hub. Our overview of hospital equipment service management covers the function this record set sits inside. The professional framework for servicing is covered by AAMI’s medical device servicing material, independent guidance from organisations such as ECRI is a useful reference on maintenance practice, and the duty to keep equipment safe and available is framed in national workplace material such as the HSE health services guidance.
Reviewing a service history or setting up competence records for a technical team? Send the training evidence you hold and the equipment list and we will identify what the record needs to connect.
FAQ
What should a competency record contain?
It should show the training completed, including the platform and the activities covered, the date and any validity period, the assessment outcome where one was issued, the authorisation granted by the organisation with its scope and date, and the mapping between that training and the equipment the person maintains. Records of work performed within that scope are what demonstrate the competence being applied rather than merely held.
Can a course attendance record demonstrate competence?
It demonstrates attendance, which is not the same as competence. Where the training provider issues an assessment outcome, that is stronger evidence because it records that the person was assessed against defined activities. Where no assessment exists, the organisation can still rely on the training but should record the basis on which it satisfied itself that the person is competent, rather than treating the certificate as a conclusion.
Who is responsible for confirming that a technician is competent?
The organisation that employs or engages the technician is responsible for satisfying itself that the person is competent for the work assigned and for authorising them to perform it within a defined scope. Training providers supply the training and the evidence; they do not take on the organisation’s responsibility for whether the person is suitable for the specific task in that specific environment.
How long should competence records be kept?
They should be kept at least as long as the service work they support could be questioned, which usually means several years and often longer. A service record naming a technician is only supported while that technician’s competence record for the relevant platform remains available. Where equipment is retained for a long period or resold, the retention period extends accordingly.
What happens if competence records cannot be produced?
The service history becomes weaker rather than invalid. A buyer or reviewer cannot establish that the work was performed by somebody competent on that equipment or within an authorised scope, so the history supports a general claim rather than a specific one. Where the work is critical to the device’s position, the practical response is to plan verification at acceptance rather than to rely on the record.
