Scheduling software implementation: a 90-day plan for certification bodies

What does scheduling software implementation involve?

Scheduling software implementation in a certification or inspection body has five workstreams: data, rules, integrations, people and the switch-over. The software is usually the quickest part. The time goes on agreeing what your rules really are, cleaning competence and calendar records, and building planners' confidence that the new plans are right.

Ninety days is a realistic target for a controlled go-live if you keep the first scope tight: one region, one scheme family or one planning team. Larger bodies then roll out in waves. This guide assumes you have already chosen a tool, for example after an RFP and a proof of concept on your own data.

What should be in place before day one?

Most delays trace back to decisions nobody made before the project started. Settle these first.

• ✓A named business owner (usually the operations or planning lead) with authority to decide on rules
• ✓A first scope: which region, standards or schemes, and which planners
• ✓A baseline of twelve months' KPIs: utilisation, subcontracted days, travel, audits outside window, planner hours
• ✓Written success measures for day 90
• ✓Data extracts from your ERP or CRM: clients, sites, audit programmes, due dates, auditors, competence, history
• ✓Security and data protection review complete, including hosting location and the data processing agreement
• ✓The technical manager's sign-off route for competence and impartiality rules

The baseline matters most. Without it, you cannot prove the benefits you put in the business case. See scheduling software ROI for which numbers to freeze.

What does a 90-day scheduling software implementation plan look like?

The timeline below suits a mid-sized body with one planning team in scope. Adjust the lengths, keeping the order: nothing goes live before the parallel run is reviewed.

1. Days 1 to 10MobiliseKick-off, scope, baseline KPIs, data extracts, access and security set-up
2. Days 11 to 30Data and rulesClean competence records, load history, write down hard rules and soft goals
3. Days 31 to 50Configure and integrateSet rules and weights, connect ERP or CRM and calendars, test on known audits
4. Days 51 to 70Parallel runPlan a real period in both systems, compare, fix data and rules
5. Days 71 to 90Go-live and reviewLive planning with planner approval, first KPI review, plan the next wave

Data work often overruns. Our guide to audit scheduling data migration covers what to move, how much history to keep and how to test it.

How do you configure the scheduling rules?

An engine applies exactly the rules you give it. Unwritten rules, such as a client who will only accept a particular lead auditor, are the usual source of early surprises. Capture them during days 11 to 30.

1. List the hard rules with their sourceCompetence by standard and IAF code, accreditation body per standard, impartiality, rotation, audit windows and due dates, scheme rules such as unannounced audits. Record where each comes from.
2. Load competence properlyRecord qualifications by standard, technical area and role, with dates. Our guide to the auditor competence matrix sets out a structure that scheduling can use.
3. Agree the soft goals and their weightsTravel, internal share of work, client preferences, workload balance. Decide which matters most when they conflict.
4. Test on audits you knowPick 20 past audits, including awkward ones, and check the engine's choice and explanation against what your best planner did.
5. Get formal sign-offThe technical manager confirms the competence and impartiality rules; the operations lead confirms the goals.

For the logic behind hard and soft rules, see constraint-based scheduling explained.

How should you run the parallel period?

The parallel run is where planners decide whether they trust the new system. Plan a real period, such as next quarter's surveillance audits for one region, in both the old process and the new tool.

Which integrations should come first in a scheduling software implementation?

Integrate in the order that removes double keying. First, the system of record for clients, contracts and audit programmes, usually your certification ERP or CRM, so demand flows in without re-entry. Second, auditor calendars, so leave and personal blocks are respected; Outlook sync is common. Third, write-back of confirmed allocations to the system that invoices and records the audit.

Ask your vendor which connections exist today and which need the API. For example, ScheduleAI offers a REST API, webhooks, an Intact integration and Outlook sync. Our article on certification ERP integration covers the common patterns and pitfalls.

What changes for planners, auditors and clients at go-live?

Planners move from building the plan to reviewing and approving it. They still own every allocation, decide exceptions and handle clients. Train them on reading the engine's explanations and on overriding safely, and give them time in the parallel run to practise.

Auditors should see their allocations in their own calendars and know how to report availability changes. Tell clients if anything changes in how dates are proposed or confirmed. If you use AI agents for date requests or reminders, tell clients and auditors when they are dealing with one, and keep a planner approval step; AI agents for certification bodies sets out safe limits.

How do you keep improving after day 90?

Go-live starts a working rhythm. Each planning cycle produces exceptions and overrides, and each one tells you something about your data or your rules.

Report the day-90 KPIs against your baseline, then plan the next wave: another region, scheme family or team. Reported customer results give a sense of what is possible once rollout is complete.

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