A limited pilot with a clear beginning, boundary and review point.
The purpose is to let a provider and a small student cohort examine the product in practice before either party considers a wider arrangement.
Demonstrate first. Define the pilot second.
A product demonstration comes before student invitations. If there is a potential fit, the provider and Rolebird record the practical and data boundaries of a small pilot.
- Demonstration. Review application preparation, interview practice, evidence checks and account controls using fictional material.
- Due diligence. Examine the privacy documents, data flow, support arrangements and product boundaries.
- Limited cohort. Invite an agreed group for a defined period, with voluntary participation and named support contacts.
- Joint review. Consider participation, student feedback, support issues, accessibility and staff observations.
The questions a pilot document should answer
The final scope is not assumed by this website. It would be agreed with the provider before access is issued.
Cohort and invitations
Who may participate, how they are invited, whether participation is voluntary and whether eligibility criteria apply.
Product access
Whether the cohort receives application preparation, interview practice or both, including any usage limits.
Dates and support
When access opens and closes, who answers product questions and where students take careers or pastoral concerns.
Data and reporting
What information, if any, Rolebird returns to the provider. The proposed default excludes student documents, outputs, answers and transcripts.
Review measures
What the parties will consider at the end, such as participation, non-identifying feedback, support requests, accessibility issues and staff observations.
End of pilot
What happens to access, how the review is recorded and whether either party wishes to discuss a separate arrangement.
Outcome boundary: the pilot concerns the operation and perceived usefulness of the preparation service. Rolebird does not promise interviews or employment.
A pilot does not transfer the provider's professional role to software
Rolebird would be responsible for
- Providing the agreed product access
- Explaining product and data boundaries
- Responding to product-support enquiries
- Supplying only the agreed pilot-review information
The provider would retain
- Careers advice and professional judgement
- Pastoral, cultural and accessibility support
- Control of cohort selection and communications
- The decision about any activity after the review
A pilot is evidence for a decision, not a commitment disguised as a trial.
What follows is decided after the review. If the provider finds the pilot useful, both parties can discuss a defined paid arrangement - price, volume, support and reporting agreed separately. If the product is not a fit, there is no expectation to continue.
Start with the product and the difficult questions
A demonstration can cover the student journey, evidence checks, data flow and pilot design.
Discuss a pilot