Audit booking portals: letting clients confirm audit dates
How an audit booking portal should work for a certification body: which dates to offer, which audits to keep out, and how planners stay in control.
Key takeaways
- Offer clients a short list of dates that already work, never an open calendar.
- Every option must pass the same checks a planner would make: window, competence, impartiality, rotation, availability and travel.
- Keep unannounced, special and short-notice audits out of self-booking entirely.
- Clients who never log in still reply by email, so the same booking rules should apply to both routes.
An audit booking portal is a client-facing page where certified organisations choose or confirm audit dates from options the certification body offers. A good portal only shows dates inside the audit window that a competent, impartial and available team can meet. Planners set the rules and approve exceptions, and every choice updates the schedule, the auditor's diary and the audit plan.
What is an audit booking portal?
An audit booking portal lets a certified client pick or confirm its audit date online, from options the certification body has already checked. It replaces the email chain in which a coordinator proposes a date, the client declines, and the auditor's diary changes while everyone waits. For the email side of the same problem, see audit date confirmation with clients.
The design question is how much choice to give. An open calendar feels client-friendly but lets clients pick dates that break the plan. A portal that only offers dates the planner has already vetted keeps the plan intact and still removes most of the back and forth.
What should an audit booking portal show the client?
The client needs enough to decide quickly and prepare well. A useful portal page for one audit shows:
- Two to four date options, each with the audit type, the number of days on site and any remote portion
- The latest date the audit can take place, and what happens if it slips past it
- The audit team's names once assigned, with background information on request, as ISO/IEC 17021-1 expects
- A way to object to a team member with a reason, routed to a planner
- For multi-site clients, the sites in the sample and the dates for each
- The audit plan when it is issued, and what to prepare before the visit
- A named contact for anything the portal cannot answer
Showing the latest date matters. A client who can see that its surveillance must happen by 15 March rarely asks for April.
How does a date request flow through an audit booking portal?
Behind each option shown in the audit booking portal sits the same chain of checks a planner runs by hand. The portal only saves time if those checks run before the client sees anything.
- 1Window calculatedFrom decision, expiry and due dates
- 2Options generatedCompetent, impartial, available teams only
- 3Client choosesOr asks for a different week
- 4Planner approvesExceptions and out-of-window requests
- 5Date confirmedDiary, travel and audit plan updated
Two rules keep options honest. First, an offered date is a tentative hold on the auditor's diary, and it expires after a set number of working days if the client does not answer. Second, when the client picks a date, the system re-checks it before confirming, because the auditor may have been booked elsewhere in the meantime.
Portal, email or AI agent: which works best?
Most bodies end up with a mix, because some clients use portals and others only answer email. The comparison below shows why the rules matter more than the channel.
| Email and phone | Open calendar portal | Rules-based portal with AI agent | |
|---|---|---|---|
| Only offers dates inside the window | Depends on the coordinator | ✕ | ✓ |
| Checks competence and impartiality before offering | Depends on the coordinator | ✕ | ✓ |
| Handles requests to move a date | Planner by hand | ✕ | Agent proposes, planner approves |
| Works for clients who never log in | ✓ | ✕ | y, via email |
| Planner effort per request | High | Low at first, rework later | Low |
| Audit trail of what was offered and why | Scattered in inboxes | Partial | ✓ |
ScheduleAI takes the third approach: its AI agents answer client date requests with options that already pass the scheduling rules, send reminders and flag exceptions, and planners approve every change. AI agents for certification bodies explains where the limits of that work sit.
Which audits should never be self-booked?
Some audits depend on the client not choosing, or on a decision the certification body has to make first. Build these rules into the portal before launch.
| Audit type | Client choice | Why |
|---|---|---|
| Surveillance | Choose from offered dates | Window and team already checked |
| Recertification | Choose from offered dates, well before expiry | Time is needed to close major nonconformities before expiry |
| Stage 2 | Choose once stage 1 outcomes are reviewed | Stage 1 findings can change timing and team |
| Unannounced audit | None; blackout days only where the scheme allows | The date must stay unknown to the site; see BRCGS unannounced audits |
| Special or short-notice audit | None | Triggered by complaints or changes, on the body's timetable |
| Multi-site sample | Dates only | The certification body selects the sampled sites under IAF MD 1 |
How do you set up an audit booking portal?
The portal is the visible part. Most of the work is getting the data and rules right behind it.
- Clean the client dataCertification decision dates, expiry dates, sites, contacts and known shutdowns for every client in scope.
- Write the booking rulesHow many options to offer, how long a hold lasts, the minimum buffer before the latest date and who approves exceptions.
- Connect the constraintsCompetence, availability, conflicts of interest, rotation and travel, so options are checked before they are shown.
- Script the out-of-window replyA standard answer that offers the nearest compliant date and states the consequence of refusing, in line with your cancellation policy.
- Pilot with one segmentOne standard or region first, with planners reviewing every booking for a few weeks.
- Measure and widenTrack requests closed without planner work, time to confirm and audits confirmed near their latest date, then extend.
Common audit booking portal mistakes
Most failed portals fail on rules rather than on software.
MythClients want full calendar choice.
RealityA short list of dates that already work is quicker to answer and keeps the plan intact. Clients can still ask for a different week.
MythSelf-booking means planners lose control.
RealityPlanners write the rules, and anything outside them comes back for approval. Only routine, compliant choices go through without a planner.
MythThe portal replaces client emails.
RealityMany contacts will still reply by email. An agent that reads those replies and applies the same rules keeps both routes consistent.
MythClients can choose their auditor.
RealityThe certification body selects the team. The client can object to a named member with a valid reason, and the body then changes the team.
ScheduleAI is audit scheduling software built for testing, inspection and certification (TIC) organisations, with a planner approving every plan.
ScheduleAI generates date options that already pass its scheduling rules, and its AI agents handle client date requests by email and reminders, with planners approving every change and Outlook sync keeping auditor diaries current.
Book a demo Estimate your savingsQuestions
Can clients choose their auditor through a booking portal?
No. The certification body selects the audit team. Under ISO/IEC 17021-1 the client can object to a team member, and the body changes the team if the objection is valid. See auditor impartiality checks.
How many date options should a client be offered?
Two to four is usually enough. Fewer invites a refusal, and more ties up too many tentative holds in auditors' diaries.
What happens if the client ignores the portal?
Holds expire after a set period, a reminder goes out, and the audit returns to the planner before the last safe date inside the window.
Should the portal show auditor names?
Yes, once the team is assigned. The client needs the names in time to object before the audit.
Do booking portals suit inspection bodies?
Yes, for planned periodic work. Statutory inspections with fixed due dates need the same window logic; see statutory inspection scheduling.