Audit notification letters: what to send clients and when

What is an audit notification letter?

An audit notification letter is the certification body's formal record that the client knows what is coming: which audit, on which dates, at which sites, with which people, and against which plan. Many bodies send it as one document. In practice it works better as a short sequence of notices, each sent when its facts are fixed.

The letter matters to planners because it is the point of no easy return. Once the client has the team's names and has rearranged its own diary, every change costs goodwill and planning time. Getting it right starts with a plan that is correct before the letter goes.

What does ISO/IEC 17021-1 require before an audit?

The standard sets what must be communicated. It leaves the format and the notice period to you. The requirements below are from ISO/IEC 17021-1:2015; check the current issue and any scheme rules on top of it.

• The audit plan is communicated and the audit dates are agreed with the client in advance.
• The client receives the name of each audit team member, with background information on request, in time to object to any particular member.
• Observers are agreed by the certification body and the client before the audit.
• The role of any technical expert is agreed with the client before the audit.
• The plan covers at least the objectives, criteria, scope, dates and sites, expected duration and team roles.
• For short-notice or unannounced audits, the conditions are described and made known to certified clients in advance, and the team is chosen with extra care because the client cannot object.

Accreditation bodies have a parallel rule. ISO/IEC 17011:2017 requires them to tell the conformity assessment body the names of assessors and observers, and the organisations they belong to, early enough for a justified objection, and to confirm the dates and plan. See witness assessment planning.

When should each notice be sent to the client?

Timing is a business decision because the standard gives none. Work back from how long it takes you to replace an auditor after an objection, then add a margin. The sequence below is a common pattern for announced audits.

1. After the previous auditProgramme noticeNext audit type, window and expected duration
2. 3 to 6 months beforeDate proposalTwo or three options inside the window, from dates a qualified team can meet
3. On agreementDate confirmationDates, sites, shifts, and remote or on-site mode
4. 4 to 8 weeks beforeTeam notificationNames, roles, background on request, objection deadline
5. 2 to 4 weeks beforeAudit planPlan and agenda, confirmed by the lead auditor
6. About 1 week beforeLogisticsArrival time, contacts, safety induction, access

These are Checkfirst suggested starting points; no standard sets them. Audit scheduling lead time explains how to set each gap from your own rebooking data, and audit date confirmation with clients covers the step before the letter.

What should an audit notification letter include?

Each item should come straight from the approved audit record, never retyped. A missing item is a phone call later.

How should planners handle an objection to an auditor?

Objections are rare, and each one should be handled the same way so the decision can be shown to an assessor later. A reason might be a former employment link, a commercial dispute, or a language need the plan missed.

1. Log itRecord the objection, date, reason and the team member concerned.
2. Assess the reasonCheck it against your impartiality rules. A justified concern is accepted; a preference without a reason can be discussed.
3. ReallocateFind a replacement with the same competence codes, availability and no conflict. See conflict of interest checks.
4. Reissue the noticeSend an updated team notification and a revised plan if roles changed.
5. Close the recordNote the outcome, and add any new conflict to the auditor's record so it is caught next time.

Which audits need a different notice?

Some audits break the standard sequence, and the letter has to change with them.

• Short-notice audits for complaints, changes or suspended clients: the conditions must already be in your published certification rules, so the notice refers to them.
• Scheme unannounced audits: the client is told the rules and, for BRCGS, the year, but never the date. See unannounced audit scheduling.
• Audits with trainees or observers: name them and their role, because observers must be agreed before the audit.
• Integrated audits: one letter listing each standard and which team member covers which, so the client does not receive conflicting notices.

If a letter has to be corrected, the plan was confirmed too early or changed without a rule.

How can software send audit notification letters safely?

The letter is a view of the plan. When a planner approves an audit, the date confirmation, team notification and plan can be produced from the same record, sent at the right point in the sequence, and chased when the client has not acknowledged. Any change to the team triggers a new notice automatically, so no client is left with an outdated name.

AI agents can take on the routine traffic: sending reminders, answering date questions inside rules the planner has set, and flagging objections for a person to decide. In ScheduleAI, agents handle client date requests, reminders and exceptions, and planners approve every change before a notice goes out.

ScheduleAI is the audit scheduling software certification bodies use to plan ISO programmes from stage 1 to recertification.