Case study: ten hours a month back for one training programme's coordinator
A licensed leadership and governance training programme for the Irish health sector now runs its candidate communications and meeting admin entirely on Microsoft Copilot, Excel and Outlook. Since it went live, the system has tracked seven candidate journey stages automatically and given the programme's coordinator back roughly 10 hours a month, without a single new piece of software or an IT ticket raised.
The problem it was solving
One coordinator was running five jobs at once: attending and minuting recurring meetings, drafting agendas from a blank page each time, liaising with marketing and bookings colleagues, corresponding with the programme's licensing partner, and answering enquiries from hospitals interested in sending staff on the course.
Underneath all of that sat the harder problem. Every candidate was somewhere different in a multi-stage journey — enquiry, registration, the course itself, a post-course quality initiative, completion — and there was no shared way to see who needed what communication, and when. In practice that meant candidates were chased ad hoc, by memory, whenever something came to mind rather than when it was actually due.
A CRM, an intake form, or a cloud automation flow is the usual answer to this. All three need a university IT department to provision or approve them, and that approval step was never going to move at the coordinator's pace. Whatever got built had to run on tools already licensed on the coordinator's own PC.
What went in
No new platform. The system sits entirely on top of Microsoft 365 tools already installed: a Copilot prompt library for the recurring writing tasks (agendas, minutes, licensing-partner correspondence, inbox triage), a candidate journey tracker in Excel with a Stage column and a formula that flags anyone due their next communication, a set of stage-matched email templates written to do exactly one job each, and Mail Merge as the batch-send step — deliberately in place of a cloud automation flow, since Mail Merge has no cloud connector for a tenant IT policy to block.
It went live the same way it was used afterwards: as ready-to-use Word and Excel files on the coordinator's existing PC, with a plain-English README tying every file to a day of the week so the system doesn't depend on whoever built it also being the one running it.
What changed, in numbers
- ~10 hours a month given back to the coordinator
- 7 candidate journey stages tracked automatically, from enquiry to alumni
- 0 IT tickets or new software required
The coordinator now reviews one tracker once a week instead of chasing candidates from memory, and sends a whole cohort its next communication in one Mail Merge pass instead of one email at a time. Meeting agendas now start from a Copilot draft of last time's open items rather than a blank document.
What it doesn't do
The system doesn't decide anything that needs judgement. A candidate asking whether their project submission is on track, or one who needs to pause and rejoin a later cohort, still gets a person's attention. What it handles is the scheduled, stage-appropriate communication that should go out regardless of how busy the week is — the message that used to not get sent because the coordinator was in back-to-back meetings instead.
Could this work for your organisation?
The shape of this problem isn't specific to training programmes. Any coordination-heavy role tracking people through a multi-stage process — onboarding, compliance renewals, a membership pipeline — on email and memory alone is a candidate for the same kind of system, and it doesn't need new software or an IT approval cycle to get there. See how the programme admin Pattern works and what setting one up for your team would involve.