Help › For tutors

Taking on a student who already uses Strivli

If a new pupil's family has been using Strivli on their own, you can take over their account with the parent's agreement — and they keep every bit of work they've already done.

The short version Ask the parent for their child's join code, enter it under Take on an existing student, and the parent gets asked to agree. Nothing moves until they do. Once they agree the child appears in your list with their entire history intact.

When to use this

A family arrives having already used Strivli themselves — sometimes for months. Adding them as a new student would throw all of that away: every test, the streak, the topic figures, the practice calendar. This keeps it.

If the child has never used Strivli, you don't want this page. Use + Add a student and hand them a code as usual.

How to do it

Ask the parent for their child's join code. They'll find it on their child's page in the parent portal. It's the same code they'd use to set up a new tablet.
In Students, choose Take on an existing student.
Enter the code and send the request.

You'll be told the parent has been asked. At this point nothing has moved and you cannot see the child — not their name beyond what you already knew, not their work, nothing. That's deliberate: until a parent agrees, the record isn't yours to look at.

What happens next

The parent sees a message on their child's page naming you and your business, saying exactly what moves. They accept or decline. If they accept, the child appears in your student list with:

every practice test and answer they've ever done
their streak and their topic-by-topic progress
their devices still working — no new codes, no re-setup, nothing for the family to do

If they decline, nothing happens and you're not told why. Ask them directly; that conversation isn't one the software should be having on your behalf.

Using the code doesn't consume it Entering a join code here does not use it up. The parent can still set up their child's own tablet with the same code afterwards. Only enrolling a device actually spends a code.

Things worth knowing

You can't do it alone, by design. There's no way for a tutor to move a child without the parent agreeing. If there were, any tutor could help themselves to any child's record, and the whole separation between one tutor's students and another's would mean nothing.
One request per child. If another tutor has already asked and the parent hasn't answered, yours is refused. Parents don't get asked to pick between competing requests.
Requests expire after 30 days. Consent given today isn't consent to a question asked four months ago.
Cohorts don't come across. If the family had grouped them somehow, that grouping doesn't follow — add them to your own cohorts once they arrive.
It's in your audit trail. Both the asking and the arrival are recorded, so "where did this student come from" has an answer a year later.

When a student leaves you

A parent can ask for their child's account to move back to them — when lessons finish, for instance. You'll get an email and a message at the top of your student list, and you approve it from there. Their practice history goes with them; your notes about them stay with you.

There's a deadline on it, and it's worth understanding rather than being surprised by: if you haven't answered within 14 days, the parent can complete it themselves. That isn't the platform overruling you. It's because the record is about somebody's child, and not replying can't be a way of keeping it indefinitely. Two weeks is there so a busy term doesn't cost you the chance to respond — and you're told when the request arrives and again if it completes without you.

Moving a student directly to another tutor isn't built. The parent moves them back to their own family account first, then hands the new tutor a code.

← All help