Running a training programme's admin on Microsoft Copilot alone

A coordination-heavy admin role doesn't always need new software to fix its bottleneck — sometimes it needs someone to notice that Microsoft Copilot, already sitting on the coordinator's PC, can do most of the job a bespoke system would otherwise be built for. That's the shape of a recent dooco Engagement: one programme coordinator, one Microsoft 365 licence, and a full set of processes built entirely from tools already installed.

The problem: one person, five jobs

The coordinator runs a licensed, multi-day leadership-training programme for professionals in a regulated sector — attending meetings, drafting agendas, coordinating with marketing and bookings colleagues, corresponding with the programme's licensing partner, and fielding enquiries from outside organisations interested in sending people on the course. None of that is unusual for a small coordination role. What made it hard was running it all through email and memory, with every candidate somewhere different along a multi-stage journey — enquiry, registration, the course itself, a post-course project, completion — and no shared way of knowing who needed what, and when.

Why "ask IT" wasn't the answer

The obvious next step for a role like this is usually a CRM, a cloud automation flow, or a properly built web intake form. All of those need the institution's IT department to provision, approve, or at minimum tolerate them — and in most institutional Microsoft 365 tenants, that approval step is a real bottleneck, not a formality. So the brief here was different: build the whole system from tools already licensed and already running, with zero dependency on an IT ticket ever being approved.

What we built

A prompt library — tested Copilot prompts for the coordinator's recurring writing tasks: drafting a meeting agenda from last time's open items, turning a Teams recap into formatted minutes, summarising a long email thread before handing it to another team.
A candidate journey tracker — a single Excel sheet, one row per candidate, a Stage column (enquiry, registered, pre-course, attended, project in progress, project complete, alumni), and a formula that flags anyone due their next communication.
Stage-matched email templates — one per stage, each written to do exactly one job, following the same tighter-then-tapering cadence used in good lifecycle communication generally: closer together right after someone registers, spaced further apart once they're mid-course.
Mail Merge instead of cloud automation — rather than a flow that a tenant policy could silently block, the batch-send step uses the decades-old Word/Excel/Outlook Mail Merge feature. It reads the tracker directly and sends a personalised copy of the right template to everyone due it, with no cloud connector and nothing for IT to switch off.
A sector-specific outreach plan — a messaging and content calendar for promoting the programme to the specific decision-makers who book people onto it, built around the compliance and governance pressures that audience already carries, rather than a generic leadership pitch.
A single README — plain English, step by step, tying every file to a day of the week, so the system survives beyond the person who built it.

The actual lesson

None of this required new software. It required treating Copilot, Word, Excel and Outlook as one system rather than four separate apps, and being deliberate about which lever needed nobody's permission to pull. That's usually the more useful question for a small team weighing up "AI adoption" — not which platform to buy, but what's already licensed and sitting unused.

If your team is running a coordination-heavy process on email and memory, get in touch — we'll look at what's already available to you before recommending anything new.