What managing candidate communications is actually costing your programme team

If your programme team is tracking candidate communications from email and a mental map of who is where, the cost is real — it just doesn't show up in one place. It shows up in the time spent working out who is due a message this week, adapting the same communication for different people, and chasing candidates who haven't responded to the last one. Add it up across a full cohort intake and it's usually one of the larger quiet drains on a coordinator's working week.

What the job actually involves

Running communications for a training programme or course means knowing the stage of every candidate at every moment: who has enquired but not yet registered, who has registered but not submitted their pre-course materials, who is mid-programme, who is in a post-course project phase, and who has completed and might be worth keeping warm for the next intake. That's five or six distinct stages at minimum, each requiring a different message and a different next action.

The complication is that candidates move through those stages on their own schedules, not all at once. On any given week, a coordinator might have five people who have just registered, three who are mid-project, and one who has gone quiet two stages back and needs chasing. Working out who needs what — and making sure nobody slips — is a quiet overhead that runs alongside every other task in the role.

Where the time goes

The recurring cost is not any single communication. It's the management overhead of the queue. Before writing anything, a coordinator has to know which stage each person is at, identify who is actually due a message this week, and then write or adapt the right message for each group. On email, without a system, that means scanning an inbox, cross-referencing a spreadsheet or a mental note, and piecing it together from context.

None of that is complicated work. But it takes time, it's easy to get wrong when you're also attending meetings and fielding other enquiries, and it's hard to delegate to someone who doesn't already know the programme. The knowledge is locked to whoever has been tracking it, which makes the coordination role harder to cover when the coordinator is out and harder to hand over when the role eventually changes.

What automating it looks like

A programme admin automation holds the candidate journey in one place — stage by stage, with the right communication at each one — and tracks where every candidate is. When someone is due a message, a draft is ready: written to the correct stage, in the programme's own language and tone, waiting for the coordinator to review before it goes anywhere.

The coordinator's job shifts from working out who needs what and drafting from scratch each time, to reviewing a set of drafted messages for a queue that's already been sorted. The decisions stay with them. The tracking work and the blank-page problem are handled by the system.

This also means that if a colleague covers for a week, the queue is visible and documented. It doesn't depend on one person's mental model of where every candidate is — the system carries that instead.

What it doesn't replace

Candidate queries and concerns still need a person. A question about whether a project submission is on the right track, or a candidate who needs to pause and rejoin a later cohort, is a judgement call no communication automation makes. What the automation handles is the scheduled, stage-appropriate communication that should go out regardless — the kind that often doesn't because the coordinator was in meetings all Thursday.

What this looks like as a dooco Engagement

A programme admin automation starts with a scoping conversation to map the candidate journey your programme actually runs: the stages, the communications that belong at each one, and the tone your programme uses. The system is built and tested against your real intake before anything goes live.

This is a Starter Engagement: one workflow, properly built, that takes the tracking and communication overhead off the coordinator's desk. If the programme runs multiple cycles a year, the system keeps running across all of them without needing to be rebuilt each time.

Find out how the programme admin Pattern works and what setting one up involves at dooco.