ReviewNotes Study Guides

Assign Problems to Students Without Student Accounts

Most tools for assigning practice assume every student can make an account. For a class of ten-year-olds that assumption fails immediately: they have no email address, and a teacher cannot spend a lesson shepherding thirty sign-ups — let alone owning thirty children's login credentials afterwards.

This guide covers the way around that — a join code the whole class shares, a passcode each student picks for themselves — and the two decisions that matter once work is flowing back: when students see the answers, and which answers are worth grading by hand.

Why student accounts are the wall

Account signup asks for an email address, and an email address is exactly what a primary-school student does not have. The usual workarounds are worse than the problem: the teacher creates accounts on the children's behalf and now holds credentials for thirty minors, or parents sign up on their phones and the child can never get back in on a school computer.

There is also a quieter cost. Every account is a record of a child held by a company. If the only thing you need is "this is the same student who answered question 3 last week", an account is a heavy way to buy it.

A join code plus a passcode the student picks

The lighter design has two halves. The teacher creates a class and reads out a short join code — one value the whole room can hear. The student enters that code with their name, and then chooses a passcode of their own, usually four digits.

The join code alone cannot identify anybody: everyone in the room has it, and everyone knows everyone's name. That is why the passcode exists. It is the one thing only that student knows, and it is what lets them come back on a different device — the same code, name, and passcode on a phone at home returns them to the answers they wrote at school.

This is worth being precise about, because getting it wrong is how a classmate reads someone else's marks. A code and a name are shared knowledge, not proof of identity. Any system that lets a name alone claim existing work is one curious child away from a privacy incident. And because children forget passcodes, the teacher needs a reset — after which that student sets a new one on their next visit.

Decide when the answers appear

When students can see the correct answer is a teaching decision, not a technical one, and the right choice differs per assignment:

  • Immediately — for practice. The student finds out at once whether they were right, which is when a correction actually sticks.
  • After the due date — for anything you are assessing. Nobody can read the answer key early, and everybody gets the explanation the moment it stops being an advantage.
  • When the teacher opens them — for work you want to go through together, so the reveal lands in the lesson rather than on the bus home.

One detail carries more weight than the choice itself: even on immediate reveal, a student should not see the answer to a problem they have not attempted. Without that rule, "immediate" quietly means "here is the answer key", and the assignment measures nothing.

What grades itself, and what should not

Short answers can be checked mechanically. A multiple-choice answer or a number is either the expected value or it is not, and marking those automatically removes most of the tedium from a class set.

Written answers cannot, and the interesting question is what to do when a typed answer does not match. The tempting move is to mark it wrong. The correct move is to leave it unmarked. Answers differ in notation constantly — "54 and 99" against "54 people and 99 people" — and a system confident enough to call that wrong will tell a child who was right that they were wrong.

So automatic grading should only ever confirm a correct answer, never declare a wrong one. Everything else goes to the teacher, which is also the work worth a teacher's time: reading how a student explained their reasoning is where the teaching happens.

Grade by question, not by student

When submissions arrive, the fast way through them is one question at a time — open question 3, see all twenty answers to it side by side, mark them in one pass. Going student by student means re-reading the same question twenty times and re-calibrating your judgment on every one.

It is also the fastest way to see what the class as a whole missed. Twenty answers to the same question, stacked, show you a shared misconception in a couple of seconds — the kind of thing a per-student view hides in plain sight.

Let them print it

Plenty of students think better on paper, and plenty of parents would rather the practice not happen on a screen at all. Being able to download an assignment as a worksheet — questions, room to write — keeps those students in.

The one thing to check: the printout has to follow the same answer rules as the screen. If a PDF can be downloaded with the answer key while the assignment is still open, printing becomes the way around every reveal setting you chose.

Common mistakes

  • Letting a name alone identify a returning student — a classmate can then read their answers and marks.
  • Revealing answers immediately without excluding unattempted problems, which turns the assignment into an answer key.
  • Auto-marking non-matching answers wrong, which punishes students for notation.
  • Having no way to reset a forgotten passcode, which locks a child out of their own work permanently.
  • Grading student by student, which is slower and hides the mistakes the whole class made together.