How a national accountancy firm scheduled Copilot training for hundreds of staff without a project manager glued to a spreadsheet

The firm had committed to rolling out Microsoft Copilot training across a national footprint. The target audience was roughly 800 staff across dozens of offices, with a tight delivery window for the firm-wide programme.

The default approach would have been a project manager, a master spreadsheet and a long series of chase emails. That approach scales badly, breaks under change and turns the rollout into an admin job rather than a training one.

Manual scheduling does not survive 800 staff in a tight window. Availability moves, sessions fill, teams need to be balanced and offices need to be considered. Every change creates rework.

The firm also needed consistent communications. Joining instructions, reminders, feedback requests and certificates needed to look the same wherever and whenever staff attended.

The brief was to remove the admin burden, not to add another tool that needed managing.

• A master spreadsheet that one person had to keep alive.
• Double-bookings, missed sessions and inconsistent comms.
• Chase emails sent by hand for every reschedule.
• Certificates produced manually after each session.

Availability was captured through a Microsoft Form. Staff filled it in once, with their preferred dates, location and any team-level constraints.

A Power Automate engine read the form responses and allocated attendees into sessions based on availability, location and team mix. Calendar invites went out automatically. Reminders and joining instructions followed the same path.

After each session, feedback collection and certificate generation ran on the same engine. Everything was driven from one dataset and one set of templates.

All sessions were delivered with minimal admin overhead, near zero double-bookings and consistent attendee communications. The training team could focus on the training rather than on the spreadsheet behind it.

The same engine is reusable for any future rollout at scale. The shape works as well for a partner conference, a national onboarding cohort or a follow-up training wave.

Power Automate is often discussed as if it were limited to approval flows. This rollout shows it scales well beyond that when the design is clean and the data sits in one place.

Most large firms have programmes that could be running on the same pattern. The cost of the pattern is small. The cost of running the same programme by hand, again and again, is not.