Unannounced audit scheduling: keeping dates secret and fair

What is unannounced audit scheduling?

Unannounced audit scheduling is the planning work behind audits where the client does not know the date: GFSI scheme unannounced audits, notified body audits under EU medical device rules, and short-notice audits under ISO/IEC 17021-1. The audit itself is the same work. The planning is different, because the date has to be both unpredictable and inside a fixed window, and it has to stay secret inside your own organisation.

Two things can go wrong. The date leaks, through a shared calendar, a hotel booking or a habit of always auditing in the first fortnight. Or the date is so late in the window that one cancellation pushes the audit past its due date.

What rules set the unannounced audit window?

Each scheme sets its own frequency, window and blackout rules. The main ones planners work with are below; check the current issue of each document before relying on a figure.

• BRCGS (BRCGS079): at least one unannounced audit every 3 years, any time in the 4 months before the audit due date, with up to 10 non-audit days nominated by the site. The site is told the year, never the date. See BRCGS unannounced audits.
• IFS Food: at least every third audit unannounced, in a window from 16 weeks before to 2 weeks after the due date, with blackout periods limited in number and length. See IFS unannounced audits.
• FSSC 22000: at least one unannounced surveillance audit after initial certification and in each 3-year period, with blackout days agreed in advance. See FSSC 22000 unannounced audits.
• EU MDR (Annex IX): the notified body randomly performs unannounced audits at least once every five years, and must not disclose its plan for them to the manufacturer.
• ISO/IEC 17021-1: short-notice or unannounced audits for complaints, changes or suspended clients, under conditions published in advance.

How do you pick a fair unannounced audit date?

Fair means two things: the client cannot predict it, and the certification body treats every client by the same rule. A written method does both, and it gives you something to show an assessor.

Who inside the certification body should know the date?

Secrecy fails inside the building more often than outside it. Limit the date to the planner, the auditor and whoever books travel, and let everyone else see only that the auditor is busy. The scene shows what each view should contain for the same audit.

Travel is the common leak: a hotel booked in the client's town under a client reference, or an invoice sent early. Book under an internal reference and keep the event private. Auditor calendar sync explains how to write private events to Outlook.

How do you choose the auditor for an unannounced audit?

With an announced audit, the client can object to a team member and the problem gets fixed before the day. With an unannounced audit that safety net is gone, and ISO/IEC 17021-1 asks for additional care in choosing the team for exactly that reason. Put these checks before allocation:

1. Competence for every code and category in scope, including scheme-specific approval.
2. Impartiality: no recent consultancy, employment or commercial link with the client. See conflict of interest checks.
3. Rotation limits, which unannounced audits count towards like any other. See auditor rotation rules.
4. A named backup auditor with the same competence, in case of illness close to the date.
5. Travel that does not force an arrival time the site would notice as unusual.

Common myths about unannounced audits

These beliefs cause most of the problems planners describe.

What happens when the auditor arrives and cannot audit?

A site may be closed, not producing the products in scope, or may refuse entry. The schemes treat refused entry seriously and can suspend or withdraw certification, so record the facts on the day and pass them to the certification decision process.

For the planner, the question is time. A genuine closure means rebooking inside what is left of the window, which is why the buffer matters. Track these cases: if one site keeps producing failed visits, review its blackout days and production information before the next draw. BRCGS audit due dates explains what happens when a window runs out.

Unannounced audit scheduling checklist

Run through this for every unannounced audit before the date is fixed.

• ✓Frequency rule met for the cycle, and the audit type recorded as unannounced.
• ✓Window dates calculated from the correct due date.
• ✓Blackout days, shutdowns and production periods received and removed from the valid set.
• ✓Date drawn at random from the valid weeks, with the method recorded.
• ✓Auditor checked for competence, impartiality and rotation before allocation.
• ✓Backup auditor named.
• ✓Calendar events private, travel booked under an internal reference.
• ✓Buffer of weeks left before the due date for rebooking.

ScheduleAI applies audit windows, blackout days, competence, conflicts of interest and rotation as scheduling constraints, and planners approve each unannounced date before it is fixed.

ScheduleAI is audit scheduling software built for testing, inspection and certification (TIC) organisations, with a planner approving every plan.