Loading your school…
Every class
| Class | Teacher | Learners | Working | Stopped | Below 40% | How it is going |
|---|
Everyone on your staff
Every teacher who has registered with your teacher code, including colleagues who have not made a class yet. Totals, so you can see where to put support — not a ranking. A teacher with the hardest class will always look worst on numbers alone.
| Teacher | Classes | Learners | Stopped | Below 40% |
|---|
Your school’s teacher code
This is the one thing a teacher cannot start without. A colleague registers on Stratford and enters this code; without it, anyone who knew your school’s name could join it and read your learners’ work. Give it out in person, not in a group chat.
Write it down now. Stratford stores it scrambled and cannot show it again. The previous code stopped working the moment this one was made.
What has happened to your school’s account
Who created the teacher code, who was invited, whose password was reset, who was removed — with the date each happened. You do not have to ask Stratford to find out what was done to your school.
This is your school’s administrative history and nothing else. No learner appears here, because no route on this page returns one.
| When | What happened | Who | About |
|---|
A teacher cannot get in, or has left
Ask Stratford. A reset code and the removal of a colleague’s account are both handled by Stratford operations, with your school’s reference above, and both are recorded in the audit log.
This is deliberate. Holding another adult’s password is not a reporting function, and a school’s account security should not depend on whoever happens to run it that year.
When a teacher leaves, tell Stratford who should take their classes. Nothing is deleted — the learners, their work and their access all stay exactly where they are.