How an audit is scheduled changes what it finds. An announced audit measures a site as it presents itself on the chosen day; a surprise audit measures a site as it actually operates. A mature program needs both - and the scheduling machinery to handle both honestly.
Calendar scheduling: the predictable baseline
Programmed audits run on the calendar: monthly food-safety checks, quarterly branch reviews, annual certification cycles. The value is rhythm - the operation internalizes audit readiness and the program's coverage becomes a forecast. The platform's job is to lighten the administration: scheduled instances carry the target date, the assigned auditor, and the site, ride out recurrences automatically, and remind everyone as dates approach. Mandatory coverage stops being a tracking spreadsheet and becomes the schedule itself.
Ad-hoc audits: the field's motion
Not every audit is premeditated. Ad-hoc instances - raised on the spot, by the auditor, for the situation in front of them - capture the "while we're here" energy (an engineer inspecting one machine checking three others) and the reactive case (an incident, a complaint, a customer audit trigger). Ad hoc keeps the audit library mobile rather than desk-bound.
Surprise audits with delayed visibility
The strictest class: audits whose subject must not know they are coming - cash verification walks in finance, spot checks on loading docks, unannounced hygiene inspections. The honest mechanics: the administrator schedules the instance now, names the auditor, and sets delayed visibility - the instance simply does not appear in the auditor's worklist until a programmed window (a day, an hour, a moment) before its time. The auditor cannot leak what they cannot yet see, and the schedule holds. The same machinery makes corporate surprise audits defensible instead of theatrical.
Combining the three
The strongest programs run all three in layers: calendar coverage for the baseline, ad hoc for field initiative, and a handful of invisible instances per month to keep the baseline honest. Scheduling platforms that support all three without ceremony make the layer cake manageable.
Predictability finds what the site knows to show. Surprise finds what the site actually is. A program that can schedule both - without administrative gymnastics and without leaking - is running the full playbook.