Decentralised student recruitment with shared control

Decentralised student recruitment works with clear agreements on what departments do independently and what is managed centrally. Let departments look after their own activities and content, whilst marketing safeguards the shared structure. Also agree on who decides in case of overlap or changes. This keeps communication coherent for the prospective student.

A lecturer knows which taster session gives a true reflection of the course. A course coordinator knows the questions that prospective students ask. The central marketing team safeguards the wider recruitment and communications. This knowledge complements each other.

Independent organising can speed up this collaboration. A department does not have to go back to a central team for every date change. For this to work, colleagues must know what freedom they have and when coordination is needed.

Divide the work based on content and responsibility

Start with the tasks that recur regularly: creating an activity, changing practical information, drafting a message, and viewing results. Next, determine which tasks require course-specific knowledge and which could have institution-wide consequences.

A local programme is usually best managed by the department itself. A new metric definition or change to a shared template affects multiple teams and requires central coordination. Document that boundary in plain language, so that the agreement is also understandable for someone who only organises an activity a few times a year.

This is an example division of tasks, not a universal organizational model. A small institution might combine roles. At a large university, a faculty can form an intermediate layer. In both situations, make sure that every recurring task has one clear owner.

Give independence a recognisable boundary

Describe which changes a department is allowed to make directly. This could include a local programme within an existing activity or a contact person in a preparation email. Additionally, determine which changes must first go through marketing, such as a new campaign for multiple target groups.

Avoid a process where everything is formally independent, yet every change still waits for approval. Choose targeted checks for changes that have real consequences. A first activity by a new colleague can be checked together; recurring activities can run independently within the agreed guidelines.

Access should align with responsibilities. Give people the data and actions they need for their work. Also record who updates access when a colleague changes roles or leaves.

Test the agreements with a real situation

Suppose two courses invite the same prospective student to a taster afternoon. Both invitations may be relevant, but the activities take place at the same time. Who notices this? And how does the communication help that person to make a choice or find an alternative?

Discuss such a situation before the campaign runs. The solution may lie in scheduling, a combined explanation, or coordination about dispatch. An institution-wide overview only helps if someone is responsible for using it.

Also test a changed location on the morning of the activity. The department knows about the change first. Agree who updates the activity details, who informs the participants, and who is contactable if someone arrives at the old location.

Make learning part of management

After a first series of activities, schedule a brief review between marketing and the departments involved. Ask what went well independently and where confusion arose. Use concrete examples: a field that is always missing, a duplicate invitation, or a question that lands with the wrong team.

Adjust the workflow or template accordingly. In this way, the shared foundation grows through practical experience. New colleagues benefit from this without having to make all previous decisions all over again.

Also measure the collaboration itself. How many activities can departments complete independently? How many corrections are needed? Which questions keep ending up with marketing? The goal is a workable division of tasks, not the lowest possible number of contact moments between colleagues.

What the prospective student notices

For a prospective student, a central open day and a departmental taster afternoon form a single introduction to the institution. A recognisable confirmation and clear information provide coherence. Course-specific content then shows what makes that course unique.

That is where the value of joint coordination lies: the foundation is reliable, whilst leaving room for an individual programme and meaningful conversation.

How Hippocampus supports this collaboration

Hippocampus maps central and decentralised activity organisation with roles and permissions. In the Zuyd University of Applied Sciences case study, MARCOM manages the shared styling and templates, whilst departments run their own activities. The case study thus provides a concrete example of central agreements and local execution.

Which division of tasks suits you best starts with how the work is organised. Then configure access and management to support it.

Want to give departments more space to organise independently? See how Hippocampus supports activity management.