Education
Education Programme Directory And Admissions Workflow
Programme directories are usually a grid of cards that nobody can filter. A prospective student looking for a part-time course in a specific subject, at a specific start date, within travelling distance, gives up quickly and applies by phone instead.
So the directory was built around filtering first, with the filters drawn from the attributes that actually vary between programmes: subject, level, mode, start date and campus. When a programme is missing an attribute, it is flagged to the staff who own that record rather than silently disappearing from results.
Admissions is a workflow rather than a form. Enquiries are triaged by programme and intake, each has a status, and a reminder surfaces anything that has been waiting too long. The staff view is deliberately plain, because the people using it are admissions officers working through a list, not enthusiasts.
Content is staff-editable per programme, including deadlines and entry requirements, because those change more often than anything else on the site and a developer should not be in that loop.
Testing covered the filters against a realistic dataset including programmes with missing attributes, and the accessibility of the results list with a screen reader.
Handover included who owns which record and how to add an intake, since that is the task that happens every year.
Programme directories are usually a grid of cards that nobody can filter. A prospective student looking for a part-time course in a specific subject, at a specific start date, within travelling distance, gives up quickly and applies by phone instead.
So the directory was built around filtering first, with the filters drawn from the attributes that actually vary between programmes: subject, level, mode, start date and campus. When a programme is missing an attribute, it is flagged to the staff who own that record rather than silently disappearing from results.
Admissions is a workflow rather than a form. Enquiries are triaged by programme and intake, each has a status, and a reminder surfaces anything that has been waiting too long. The staff view is deliberately plain, because the people using it are admissions officers working through a list, not enthusiasts.
Content is staff-editable per programme, including deadlines and entry requirements, because those change more often than anything else on the site and a developer should not be in that loop.
Testing covered the filters against a realistic dataset including programmes with missing attributes, and the accessibility of the results list with a screen reader.
Handover included who owns which record and how to add an intake, since that is the task that happens every year.
- Industry
- Education
- Category
- CMS Development, Directory
- Project type
- Website and web application
- Project date
- 2024-11
Technologies
Project highlights
- Filtering built from the attributes that actually vary between programmes
- Records with missing attributes flagged to staff instead of hidden silently
- Admissions tracked as a triaged workflow with ageing reminders
- Plain staff view designed for working through a list
- Programme content and deadlines staff-editable without a developer
- Filter set tested against a dataset with incomplete records
