Technical expert scheduling: booking the specialist with the audit
Technical expert scheduling for certification bodies: when a specialist is needed, how to book them with the auditor, and the rules on audit time.
Key takeaways
- Decide the need for a technical expert at application review, when the scope is known, so the booking is made with the audit and never after it.
- Book the expert against a named auditor and only for the sessions that need their knowledge, since they must be accompanied throughout.
- Technical expert time sits outside audit time under IAF MD 5, so it never shortens the auditor days the client pays for.
- Treat experts as scarce resources: hold their dates early, record their competence like an auditor's and check impartiality before naming them to the client.
Technical expert scheduling is booking a specialist to join an audit on the same days, at the same site, as the auditor they support. Under ISO/IEC 17021-1 the expert's role is agreed with the client before the audit, the expert does not act as an auditor and is accompanied by one, and IAF MD 5 excludes their time from the calculated audit time.
What is technical expert scheduling?
Technical expert scheduling is the planning task of getting a specialist to the right audit, on the right days, alongside the auditor who will supervise them. It sounds like one more calendar entry. In practice it is where many plans fail late: the expert is booked after the auditor, has no free dates in the audit window, or turns up at a site where their role was never agreed with the client.
This article covers the scheduling side. For how technical experts fit into team composition as a whole, see audit team selection.
A person who provides specific knowledge or expertise to the audit team, for example on a process, a technology, a sector or a language. Under ISO/IEC 17021-1 a technical expert does not act as an auditor and is accompanied by an auditor during the audit.
When does an audit need a technical expert?
An audit needs a technical expert when the team, taken as a whole, lacks knowledge the scope requires and no available auditor can supply it. That gap is usually visible at application review, once the scope, the technical area and the processes on site are known. Waiting until the team is picked turns a planning decision into a scramble.
| Trigger | Example | Scheduling consequence |
|---|---|---|
| Scarce technical area | An IAF code where few or no auditors hold full competence | Book the expert as soon as the audit window opens; they are likely needed elsewhere too |
| Specialist process or technology | Heat treatment, sterilisation, software development practices | Book only the sessions that audit that process |
| Sector regulation | Legal requirements particular to the client's industry | Align the expert's time with the document review and the process interviews |
| Competence development | An auditor working towards a code, supported by an expert | Plan it as a pairing over several audits, recorded in the competence matrix |
Language support is a separate case. Translators and interpreters also supplement the team, and must not unduly influence the audit, but they are planned as their own role.
What do the rules say about technical experts?
ISO/IEC 17021-1:2015 allows the knowledge of the lead auditor and auditors to be supplemented by technical experts, translators and interpreters. The role of the technical expert must be agreed by the certification body and the client before the audit. The expert does not act as an auditor and is accompanied by an auditor.
For audit time, IAF MD 5:2023 (clause 3.8) states that the audit time calculated from its tables does not include the time of auditors in training, observers or technical experts. The ISO 9001 Auditing Practices Group gives the same guidance and adds that each expert should be assigned to a specific auditor and sign a statement on conflicts of interest and confidentiality. Check the current issue of each document before you rely on it; see how IAF MD 5 sets audit duration.
How do you book a technical expert with the audit?
Treat the expert and their supervising auditor as one booking. Fix the auditor first, then place the expert inside the auditor's days, so the pair can never drift apart when the audit is moved.
- 1Flag the needAt application review, name the missing knowledge
- 2Shortlist expertsCompetence, impartiality, signed agreement on file
- 3Pair and placeLink to one auditor, book needed sessions
- 4Agree the roleConfirm role and name with the client
- 5Move togetherAny date change moves both bookings
The last step matters most. Most failures happen when an audit is rescheduled and the auditor is moved but the expert is not. If your planning tool cannot link two bookings, keep a manual rule: no date change is confirmed until the expert has accepted the new dates. The expert's name goes into the audit notification with the rest of the team, so the client can object in time.
How do you track technical expert availability and competence?
Record experts in the same competence matrix as auditors, with their own role, so the planner can see at a glance who can support which technical area. Store their availability the same way: leave, other commitments and the days they are willing to travel. Many experts are external, part-time or retired specialists, so their free dates are fewer and fill faster.
| IAF 17 metals | IAF 19 electrical | IAF 33 IT | Signed agreement | |
|---|---|---|---|---|
| Expert A (external) | ||||
| Expert B (internal) | ||||
| Expert C (external) | ||||
| Auditor D (as expert) |
ApprovedApproval in progressNot approved
Two points stand out in this example. Expert C has the only IT coverage but no signed agreement on file, so they cannot be booked until it is in place. Auditor D is approved to support metals and electrical audits in an expert role, which gives the planner a second option when Expert A is busy. External experts are also subject to the same conflict of interest checks as auditors.
Common mistakes in technical expert scheduling
These errors come up in client complaints and accreditation assessments.
MythA technical expert can cover for a missing auditor.
RealityA technical expert does not act as an auditor. If the team lacks an auditor for part of the scope, find one or change the plan.
MythThe expert's days can reduce the auditor days.
RealityIAF MD 5 excludes technical expert time from audit time. The auditor days stay as calculated.
MythThe expert can visit a second site on their own to save travel.
RealityThe expert must be accompanied by an auditor. Plan multi-site audits so each expert session sits inside an auditor's day at that site.
MythRemote attendance removes the scheduling problem.
RealityA remote expert still needs agreed times, an accompanying auditor and a working connection. See planning remote audits under IAF MD 4.
How can software help with technical expert scheduling?
The planning problem is small per audit and hard across a year. A handful of experts support many audits, often in the same busy months, and each booking depends on an auditor booking. Scheduling software helps when it treats the expert need as a requirement of the audit, links the expert to an auditor, and checks competence, impartiality and availability for both at the same time.
ScheduleAI handles this as part of team formation, using the same scheduling parameters it applies to auditors, and planners approve every proposed team. Where experts are external, the same rules apply as for subcontracted auditors: agreements, records and a clear line on who pays for travel.
See how ScheduleAI's audit scheduling software applies these rules across a whole programme in minutes.
What should a planner still decide personally?
Whether the knowledge gap is real, which expert suits a sensitive client, and when a pairing should become a competence development plan for an auditor. Software can show the options and the constraints behind each one; the judgement stays with the planner.
ScheduleAI books technical experts as part of the audit team, checking competence codes, conflicts of interest and availability for the expert and the accompanying auditor together, and planners approve each team before it goes to the client.
Book a demo Estimate your savingsQuestions
Does technical expert time count toward audit time?
No. IAF MD 5 states that calculated audit time does not include the time of technical experts, auditors in training or observers.
Can a technical expert audit on their own?
No. Under ISO/IEC 17021-1 a technical expert does not act as an auditor and is accompanied by an auditor.
Does the client need to agree to a technical expert?
Yes. The role of the technical expert is agreed between the certification body and the client before the audit, and the client can object to any named team member.
Who can act as a technical expert?
Anyone the certification body has approved for the specific knowledge needed, including an auditor who is not qualified to audit that area. Keep records of their competence and a signed agreement covering confidentiality and conflicts of interest.
When should a technical expert be booked?
As early as the scope makes the need clear, ideally at application review, and always with the auditor they will support. See audit scheduling lead time.
Should the same technical expert return every year?
Continuity can help, but experts should be checked for impartiality like any team member, and familiarity with the client counts as a threat to manage.