For universities
Revision your students will actually open, on terms your procurement team will actually sign.
BodyAnswers Study is head and neck anatomy in the depth a viva demands, with the systemic medicine a BDS student is examined on alongside it — mapped to your curriculum, licensed by seat, and documented for a data protection review before you have to ask.
The mouth and teeth module is open to everyone, in full. Judge the depth before you talk to us.
What institutional access gives you
Licensed seats, managed by you
You buy a seat allowance under a contract, and your administrators assign seats. Students with a verified university email address can be admitted automatically or individually, whichever your registry process prefers. Seats are released when a student leaves and the allowance is never exceeded — that is enforced in the database, not by a spreadsheet.
Your curriculum, not ours
The platform's content and your curriculum structure are separate. You map shared content into your own years, modules and module codes, in your own order, with your own labels. Two universities can teach the same material in different sequences without either of them getting a customised copy of the library.
Add your own material without forking anything
Your course can attach its own learning objectives, notes and links to shared content — for the whole school or for one cohort. Additions are labelled as yours so a student can see what came from their course. When we correct or extend the underlying content, your additions stay put and you keep the improvement.
Cohort insight, not student surveillance
You see which topics a cohort is weak on, aggregated and suppressed below five students so an average cannot be read back as an individual. What you do not get by default is a named student's answer history — that requires a specific permission that no standard role holds, precisely so it becomes a decision recorded in a contract rather than a default nobody chose.
Roles that match how a school works
Student, lecturer, course lead and university administrator, each with a different scope, all enforced server-side. Adding a role later does not require rebuilding authorisation, because permissions are configuration rather than code.
Accessible by design
Built to WCAG 2.2 AA, with a published statement that names the exceptions rather than claiming there are none. The interactive anatomy has a full keyboard and screen-reader equivalent, so it is not a feature that quietly excludes some of your students.
How it usually goes
A conversation with the course
Usually with a course lead or an anatomy lead. What you teach, in what order, and where students currently struggle. Half an hour is normally enough to tell whether this is a fit.
A pilot with one year group
A time-limited licence for a single cohort, so the decision rests on your own students' experience rather than on a demonstration. We map your curriculum for the pilot; you do not have to configure anything.
Procurement and data protection review
Everything your DPO, IT and legal teams need is published at the trust centre — including where the gaps are. We sign your data processing agreement or offer ours, and we will complete your security questionnaire.
Rollout
Seats assigned for the cohort, administrators trained on the admin screens, and a named contact. Students sign in with their university email address.
For your DPO, IT and accessibility teams
Published rather than provided on request, including the parts that are not finished. You should not have to ask twice to find out that there is no penetration test yet.