For colleges and universities
An institution buys a pool of research projects for the year, not a count of logins. Departments allocate projects from the pool as students begin their work.
How the pool works
You buy 50, 100, 250, 500 or 1,000+ projects a year. The per-project rate falls as the pool grows. Your administrator allocates a project to a student when they start, and sees what is used and what remains.
Who sees what
This is the part institutions ask about first, so it is worth stating plainly.
| Role | Can see | Can change |
|---|---|---|
| Student (the researcher) | Everything in their own project | Everything in their own project |
| Assigned guide or supervisor | The whole of their student’s project — plan, master chart, analyses and written sections | Nothing. A guide reviews, comments, approves or sends a section back; the student remains the author |
| Institution administrator | Members, departments, licence use and administrative reporting | Administrative records only |
| Other faculty in the institution | Nothing, unless the student shares it with them | Nothing |
An institution buys licences, not the research. An institution administrator does not see students’ research data by default. Where an institution requires administrative access to research data — for an ethics audit, for example — that must be granted explicitly and is recorded.
Pilot first
We start with a three-month pilot on a limited pool, running the whole journey with one department, before an annual licence is discussed. It is a better test of whether Chavery suits your students than any demonstration.