- ISO/IEC 17025:2017 expects defined competence requirements for each function, plus a process to select, train, supervise, authorise and monitor people.
- Authorisation for specific activities, such as performing tests, validating methods and authorising results, is the record assessors examine most closely.
- Method validation and measurement uncertainty are where assessors test whether competence is real, by asking staff to explain their own work.
- Keep training results, supervision, authorisation and monitoring together for each person so an assessor can trace any reported result.
Every accreditation assessment of a testing or calibration laboratory includes a moment that experienced quality managers learn to prepare for. The technical assessor stops at a bench, watches an analyst run a test and then asks to see that person's file: what the role requires, how the analyst was trained, who supervised them, when they were authorised and what has been done since to confirm they are still competent. If the file tells a clear story, the assessment moves on. If it holds a certificate from years ago and nothing else, the assessor starts looking harder.
ISO/IEC 17025:2017 sets out requirements for the competence, impartiality and consistent operation of laboratories, and accreditation bodies use it as the basis for assessment. Competent people are at the heart of it, because a valid result depends as much on the person as on the method and the equipment. This guide follows the life of a competence record, from defining what a role needs to monitoring a person years after authorisation, and shows what an assessor expects to find at each step. It is written for laboratory quality managers, technical managers and laboratory directors preparing for initial accreditation or reassessment.
What the standard expects of laboratory personnel
In business language, the personnel requirements of ISO/IEC 17025:2017 ask a laboratory to do six things for every person, internal or external, who can influence laboratory activities:
- Define competence requirements for each function that affects results, covering education, qualification, training, technical knowledge, skills and experience.
- Make sure people are competent for the activities they perform and able to judge the significance of deviations.
- Communicate duties, responsibilities and authorities to each person.
- Have a process for setting competence requirements, selecting, training, supervising, authorising and monitoring the competence of personnel.
- Authorise people for specific activities, including developing, modifying, verifying and validating methods, analysing results, and reporting, reviewing and authorising results.
- Keep records that show each of these steps took place.
The standard leaves the method to you. It does not prescribe course lengths, exam formats or a fixed interval for re-assessment. What it does expect is a system that works for every person and leaves evidence an assessor can follow.
The competence lifecycle, one stage at a time
Stage 1: define what each role needs
Start with the functions, not the people. A sample receipt technician, a chemist running chromatography, a calibration engineer, a technical manager and a person who signs reports each need something different. For each function, write down the minimum education or qualification, the training required, the knowledge and skills to be shown and any experience expected.
Assessors look for requirements that are specific enough to test against. "Suitably qualified" tells them nothing; "degree in chemistry or equivalent, training in the laboratory's sample preparation and instrument procedures, and demonstrated competence in the method on blind samples" gives them something to check.
Stage 2: select against the requirements
When someone joins or moves into a new function, compare what they bring with what the role needs, and record the result. The gap you find becomes the training plan. Experienced hires are not exempt: experience elsewhere may count toward a requirement, but the laboratory still needs to show the person can perform its own methods to its own procedures.
Stage 3: train, in theory and at the bench
Training usually combines three elements. A grounding in the management system and the standard, so the person understands why impartiality, traceability and records matter. Method-specific instruction, at the bench, from someone already authorised. And technical skills that cut across methods, such as handling validation data or evaluating measurement uncertainty.
For the first element, ISO/IEC 17025 Awareness gives every member of the laboratory team a practical introduction to impartiality, competence, valid results and the management system, with a final exam that records what each person understood.
Stage 4: supervise until competence is shown
Until a person is authorised, their work should be supervised by someone who is. Record who supervised, for which activities and for how long, and keep the results of supervised work. Assessors often ask how the laboratory knows that results reported during a training period were valid, and supervision records are the answer.
Stage 5: authorise for specific activities
Authorisation is the record assessors read most closely, because it is the laboratory's formal statement that a person may perform a named activity and that results can rely on it. Good authorisation records are specific: the person, the method or activity, the scope of the authorisation, the evidence it was based on, the person who authorised it and the date.
Many laboratories keep this as a matrix, with people down one side and activities across the top. That makes it easy for an assessor to choose a result in the report archive and check that every person who touched it was authorised at the time.
| Activity | What authorisation should rest on | Typical evidence |
|---|---|---|
| Performing a test or calibration | Training in the method and successful supervised work | Training record, results on known or blind samples, supervisor sign-off |
| Verifying or validating a method | Understanding of performance characteristics and study design | Course result, a validation or verification study the person completed |
| Evaluating measurement uncertainty | Ability to build and defend an uncertainty budget | Course result, a reviewed budget for a laboratory method |
| Reviewing and authorising results or reports | Technical depth in the method and knowledge of reporting rules and decision rules | Experience record, authorisation by the technical manager |
| Giving opinions and interpretations | Expert knowledge of the field and the applicable requirements | Qualifications, experience, documented review of past opinions |
Stage 6: monitor competence over time
Authorisation is not permanent proof. People's skills drift, methods change and some tests are run so rarely that competence fades between uses. The laboratory needs to monitor competence after authorisation and act when it slips.
Practical monitoring options include witnessing the person perform the test, re-testing retained or blind samples, reviewing their results against quality control data, checking their performance in proficiency testing or interlaboratory comparisons, and reviewing reports they authorised. Choose a frequency based on risk: a rarely used, complex method deserves more attention than a routine test run every day. Record what was done, the outcome and any action taken.
A worked example: one analyst's file
Picture a chemist who joined a food testing laboratory eight months ago and now runs pesticide residue analysis. An assessor picks a report she issued last month. Here is what a file that stands up looks like, in the order the assessor is likely to read it.
- The role profile for residue analyst, listing the qualification, training, knowledge, skills and experience the laboratory decided the function needs.
- The selection record comparing her degree and previous experience with that profile, and noting the gaps: the laboratory's own extraction procedure, its instrument software and its uncertainty approach.
- Training records for each gap: an awareness course result on the management system, bench training sign-offs from an authorised colleague, and course results for method verification and measurement uncertainty.
- Supervision records for the weeks she worked under supervision, with the batches she ran and the supervisor's review of the results.
- The authorisation, signed and dated by the technical manager, naming the method, the matrices covered and the evidence relied on. Its date is earlier than the report the assessor chose.
- Monitoring since authorisation: her results on a blind sample, a proficiency testing round she took part in and a periodic review of her quality control data, each with its outcome.
None of this is elaborate. It is simply complete, dated and in one place. The assessor can follow the line from requirement to result without asking anyone to search a shared drive, and the conversation moves on to the science.
Notice also what is not in the file: a generic line saying "trained on all methods". Broad statements like this are the most common reason an assessor asks for more evidence, because they make it impossible to see which activities a person was actually shown to be competent in, and when.
The technical skills assessors probe hardest
Two areas reveal quickly whether competence is real or only on paper.
Method validation and verification
Before a laboratory reports results from a standard method, it should show it can perform that method properly; non-standard, laboratory-developed and modified methods need validation to show they are fit for purpose. Assessors ask the people who did the work to explain their choices: which performance characteristics they assessed, why, how many replicates, what acceptance criteria and what the data showed. A person who cannot explain their own study is not yet competent to run one.
Method Validation and Verification (ISO/IEC 17025:2017) is built for analysts, calibration technicians and technical managers who plan, perform or approve these studies, from deciding when to verify and when to validate to producing records an assessor accepts.
Measurement uncertainty
Laboratories need to identify the contributions to measurement uncertainty and evaluate it, and to take it into account when a statement of conformity with a specification is made. Assessors often ask an analyst to walk through the budget for a method they perform: where each component comes from, how it was evaluated and how the expanded uncertainty was reported.
Measurement Uncertainty (ISO/IEC 17025:2017) covers Type A and Type B evaluation, combining and expanding, worked budgets and the decision rules that apply when a result sits close to a limit, so the person who builds the budget can also defend it.
Who needs which training
| Role | Core competence to show | Sterling Academy course |
|---|---|---|
| All laboratory staff, including sample receipt and administration | Impartiality, confidentiality, the management system, their own part in valid results | ISO/IEC 17025 Awareness |
| Analysts and calibration technicians | Method skills at the bench, plus validation and uncertainty for their methods | Method Validation and Verification; Measurement Uncertainty |
| Technical managers | Approving methods, authorising staff, reviewing results | Method Validation and Verification; Measurement Uncertainty; ISO/IEC 17025:2017 Implementation Training |
| Quality managers and laboratory directors | Building and running the whole system, ready for accreditation | ISO/IEC 17025:2017 Implementation Training |
| Internal auditors | Auditing technical and management requirements, including competence records | ISO/IEC 17025:2017 Internal Auditor Training |
Quality managers leading an accreditation project will find that ISO/IEC 17025:2017 Implementation Training ties the personnel process into everything else: impartiality, equipment, traceability, methods, technical records and reporting, so the competence system is designed with the rest of the laboratory rather than added later.
Audit your competence records before the assessor does
The internal audit is the best rehearsal. An internal auditor who knows the standard can pick three recent reports, trace every person who handled the samples and check that each was authorised for that activity on that date, that supervision was recorded during training and that monitoring is up to date. Gaps found this way can be closed before the assessment rather than written up during it.
ISO/IEC 17025:2017 Internal Auditor Training prepares quality staff, technical managers and analysts appointed as auditors to audit the laboratory's results, not just its quality manual.
Questions to rehearse with your team
Before the assessment, ask your people the questions an assessor is likely to ask, and check that the records give the same answer:
- Which activities are you authorised for, and when were you authorised?
- Who trained you on this method, and who supervised you before authorisation?
- How does the laboratory check that you are still competent?
- What would you do if a quality control result fell outside its limits?
- How is uncertainty evaluated for the test you just performed?
- What are your responsibilities for impartiality and confidentiality?
Keep the evidence in one place
Competence files fail most often not because the work was not done but because the evidence is scattered: course certificates in an email folder, bench sign-offs on paper, authorisations in a spreadsheet only the technical manager can open. Bring the records together, linked to each person and each activity.
Formal training is the easiest part to organise. Every Sterling Academy course ends with a final exam and a numbered certificate with a QR code that opens its live record, so an assessor can confirm the result in seconds. On the company dashboard, the quality manager can assign courses by role, follow each person's progress and download training records to place in the competence file alongside bench training, supervision and authorisation.
Bringing it together
An assessor does not need to be persuaded that your staff are skilled. They need to see a system: requirements defined for each function, people selected and trained against them, supervised until ready, authorised for named activities and monitored afterwards, with records at every step. Build that system once and every assessment becomes a matter of opening the file. Build the competence. Prove it with confidence.
Frequently asked questions
Does ISO/IEC 17025 require a training certificate for every analyst?
No. It requires the laboratory to define competence requirements, make sure people meet them and keep records. A certificate with an exam result is strong evidence for the knowledge part, but bench training, supervision and authorisation records are needed as well.
How often should competence be monitored after authorisation?
The standard does not set a frequency. Base it on risk: methods that are complex, critical or rarely performed need more frequent monitoring than routine tests run every day.
Do external or contract staff need the same competence records?
Yes, if they can influence laboratory activities. The personnel requirements apply to internal and external people alike.
Can experience at another laboratory count toward authorisation?
It can count toward the competence requirements, but the laboratory still needs evidence that the person can perform its own methods to its own procedures before authorising them.
Who should take the measurement uncertainty course?
Analysts and calibration technicians who evaluate uncertainty for their methods, technical managers who approve budgets and anyone who makes statements of conformity close to a limit.
Can we track lab staff training for an assessment on one dashboard?
Yes. A Sterling Academy company administrator can assign courses by role, track progress and download records to add to each person's competence file.