For tutors
Run your students on your own question bank
Everything a student sits here is something somebody assembled first. A tutor account gives you the side of the platform that does the assembling: the bank, the test builder, the groups, and every attempt in full detail.
What you get
Seven things, and each of them is a screen that exists rather than a plan:
- 1
A question bank you own
Write questions in the editor, tag each one with a content domain, a skill inside it and a difficulty, and attach an explanation students see in the review. Maths is typeset when you save, not in the student's browser.
- 2
Assemble tests out of it
Build a test section by section and module by module, choosing the questions in each. Set the routing threshold for an adaptive test, or leave it linear, and decide whether it is public or only for your students.
- 3
Group your students
Put students into groups, and see a group's attempts and average together rather than one student at a time.
- 4
Assign a test to a group
A test assigned to a group appears for every student in it. No links to send, no codes to distribute.
- 5
Export the lot as CSV
Every completed attempt with its scores, per-domain counts and per-question detail, in one file you can open in a spreadsheet.
- 6
Bulk import from JSON
Drop or paste a JSON tree of sections, modules and questions. You see what it parsed, and what it rejected, before anything is written.
- 7
Open any attempt
Go through an attempt question by question: what was answered, what was eliminated, how long each one took, and how often the tab lost focus.
How it fits a week of teaching
The shortest useful loop is three steps. Assemble a test out of the bank — a full length one, or a single module on the one domain a student keeps losing marks in. Assign it to the group. Then, once they have sat it, open the attempts and read what actually happened: which questions were missed, which options were eliminated before the wrong one was chosen, how long each question took, and whether the last five were rushed.
That last part is the reason the per-question timing is recorded at all. A student who gets twelve questions wrong because they spent nine minutes on question three has a pacing problem, not a content problem, and the two are fixed by completely different lessons.
Scores are never stored — only the raw counts per module — so every scaled number you see on a student’s history was recomputed from those counts when you opened the page. Old attempts and new ones are always converted by the same rule, which is what makes a progress line worth reading. The scoring policy is published in full, tables included.
What it does not do
Worth knowing before you invest a weekend in building a bank:
- No billing, and no per-student licences. There is no payment code in the platform at all, in either direction — it does not charge you and it cannot charge your students for you.
- No parent accounts and no parent reporting. A student and a tutor are the only two roles.
- No integration with a school LMS. The way data leaves is the CSV export.
- Nothing is written for you. The question bank is questions somebody typed, tagged and explained. Importing a JSON file is faster than the form, but it is still your content going in.
- Students sign themselves up. There is no roster invite flow; you add an existing account to a group.
Getting an account
Tutor accounts are set up by hand rather than through the sign-up form, because the admin side can edit the question bank every student on the platform sees. Get in touch and say roughly how many students you teach and whether you want to bring your own questions; that is the whole of what is needed to set one up.
If you would rather look before you ask, the student side is open — sit a full timed test and read the score report it produces. That is what your students will see, and it needs no account either.