Share one code. The whole cohort starts.

Two patterns. (1) Class code — generate a shareable code in the format XX-AAAA (two letters, a hyphen, four characters, for example DH-A7B3), put it on a whiteboard or in a chat, and participants enter it and pick their own username. No email address is collected and there is no per-participant setup, which is what lets it scale to a whole year group in one sitting. (2) Invite list — paste names and email addresses into the admin box, one per line, and the platform emails each person a branded single-use magic link and then tracks that person individually. The two are meant to be mixed: class codes for the students, an invite list for the handful of staff who need their own dashboard.

A class code is instant — generate it, share it, and students are answering within seconds, with nothing provisioned per student. Emailed invites take longer to leave: they go out one address at a time, capped at 30 sends a minute. Read the plan limit carefully, because it applies to both routes equally. Your plan buys a number of PEOPLE per billing period — 80 on Team, 200 on Scale — and one person costs one unit no matter how many assessments they take, whether they arrived through a code or through an invite. Somebody who used both still counts once. When the period ceiling is reached the class-code page stops admitting new people until the period rolls over or you move up a tier, so a cohort larger than your plan is an Enterprise conversation rather than something a code quietly absorbs. What is not offered at all: there is no CSV or spreadsheet import, and no SIS roster sync.

The code itself is the separator, and it is worth being exact about the shape of that. Every result shows which code it arrived through, so a district running 12 high schools generates one code per school and reads them apart that way — that part works. What is NOT there is a box to type "Grade 9 Career Week, Lincoln HS" into: the cabinet fills a cohort's label automatically from the assessments you ticked, so what appears beside a result is the code and the test combination, not a name you chose. A human-readable label can be set, but only by creating the cohort through the API (Scale tier and up) rather than through the screen. There is no grade, school or demographic field behind any of it, and no multi-dimensional tagging — one code per slice is the whole mechanism.

Class codes plus a username scheme. Many K-12 deployments use a "first name + last initial + student ID" username pattern; the platform supports this and never requires an email address. For under-13 participants that data minimisation IS the COPPA posture — no email, no demographics, no advertising trackers, no peer-sharing. What we do not have is a verifiable-parental-consent workflow: nothing on the class-code path asks a guardian to approve a student before they take part. (There is a consent flow in the product, but it belongs to a separate Ukrainian teen programme with its own entry point and is not reachable from a B2B cohort.) If your district requires documented parental consent, that requirement is unmet today — please raise it in the form below rather than assume it is covered.

Sign in with Google, on every tier, including Google Workspace school accounts — because a Workspace account is a Google account. Google is the only sign-in you can switch on yourself, and we would rather say so than let you find out during a security review. SAML 2.0 single sign-on is built but is not a self-serve setting: we connect a district identity provider (Microsoft Entra ID, Okta and ClassLink included) for an organisation on request, for sign-in only. There is no Clever connection and no SCIM or OneRoster provisioning, so accounts are not created or deactivated automatically from your directory. If SCIM or roster provisioning is a procurement requirement for you, tell us in the form below — it is a build, not a setting, and we would rather scope it honestly than promise it here.

Yes, for people you invited by email. Admin shows completion status per invited participant, and you can trigger a reminder yourself at any point. On top of that, a daily job sends up to three automatic reminders to anyone who has not finished, on one interval you choose per invite — anywhere from 1 to 14 days, 3 by default — and you can pause reminders for an individual without revoking their invite. Participants who arrived through a class code are counted in the cohort but have no email address on file, so there is nobody to remind; that is the trade you make for not collecting emails.