The context
We know that there are specific activities providers undertake when a recruitment cycle is closing. This research was to understand provider needs for:
- ending a recruitment cycle
- handling “edge case” applications
- planning a new cycle
- data and reporting to DfE
We also wanted to assess design changes for:
- reasons for rejection
- adding a way for providers to see the question guidance shown to candidates
- sorting controls, adding the ability to sort by Reject By Default (RBD) date
Approach
One to one, moderated, semi-structured sessions
Discussion guide
Who we researched with
Provider users, typically ITT administrators or ITT Directors from:
- 7 SCITTs
- 2 Schools Direct
Analysis
End of cycle Miro board analysis
New user needs identified
New need categories:
- End of cycle
- Making a deferral
- Know the DfE deferral policy
- Allow candidates to defer without their needing to re-apply
- Defer at any point after an offer is accepted
- Deferrals should not impact my statistics
- Change the course for a deferred offer
- Change the location for a deferred offer
- Add or change conditions for a deferred offer
- Shortlist candidates for next year
- Next cycle
Needs also added to the following categories:
- Recruitment
- Data and tracking
- Repeat need Download all candidate data as CSV
- Course onboarding
- Manage data