There is no "class" or "group" you create and then add students to. Grouping works the other way round: you create one assessment per group, and whoever takes that assessment belongs to that group.
This is the single most useful thing to know if you work with more than one class, so it is worth setting up before you share anything.
How it works
Create a separate assessment for each group you want to keep separate — the same questionnaire each time, with a different name:
Year 11 — Autumn 2026Year 10 — Autumn 2026Class 9A — Careers Week
Each one gets its own access code, its own QR code and its own share link. Give Year 11 the Year 11 code and Year 10 the Year 10 code, and the two groups stay separate from that moment on — in your results, in your filters, and in your reporting.
Why it is worth doing before you start
You cannot move somebody between groups afterwards. A student belongs to the group whose code they used, so the grouping is decided by which code you hand out — not by anything you can edit later.
Sharing one code with the whole school works, and gives you one undivided list. That is fine if you never need to tell year groups apart. If you might, make the assessments first.
Naming them well
The assessment name is the group name — it is what you will see in every list, filter and export, sometimes years later. Two habits that pay off:
Include the period. Year 11 — Autumn 2026 rather than Year 11. You will
run Year 11 again next year, and two assessments called Year 11 are
indistinguishable once they both have results in them.
Name the group, not the task. Class 9A rather than Assessment 2. The
second tells you nothing when you return to it in six months.
Using the groups afterwards
Once people start completing:
- Assessments shows each group with its own started and completed counts, so you can see which class is keeping up and which needs a reminder.
- Participants can be filtered so you work through one group at a time.
- Approving works the same within any group — see Approving clients.
How many groups is too many
There is no limit, but each group is one assessment to share and keep track of. A group per class is normal. A group per student is not — that is what the participant list is for.
What this does not do
It does not tell the system how many people should be in a group. NexPath
knows that 24 students completed Class 9A; it does not know whether 9A has 25
students or 30, so it cannot tell you who is missing. If you need that, keep
your own register alongside — the counts here tell you how many have finished,
not how many have not started.
Related
- Creating an assessment — where a group is chosen
- The participants pipeline and Today's Focus — how grouped people appear on the roster