Classes & Analytics
TeachFORGE.ai
Classes & Analytics / Creating a class
Creating a class
From nothing to a roster, with the pattern settled first.
Pattern first. Everything else follows.
Pattern before class
The page opens by telling you the order: choose the student ID pattern your school uses, then create the class. That is not a suggestion — the pattern decides what handles are allowed, and it is awkward to change afterwards.
Where your organisation requires one, the page says so instead: your organisation requires this pattern for every new class, and the choice is locked.
The fields
| Field | Notes |
|---|---|
| Class Name | Required. A name your learners will recognise, such as their year group and subject. |
| Student ID pattern | The list of available patterns, your organisation's default marked as such, plus the random option. |
| Student IDs (one per line) | With a pattern chosen. Each line must match. |
| How many random IDs | With random chosen instead. Between 1 and 200. |
| Class exam date (optional) | Compresses spaced review before the exam. Leave blank if it is not set yet. |
A capacity line above them shows where you stand: how many classes of your allowance you have used, how many learners a class may have, and your total.
The errors you will meet
- Class name is required.
- Choose a student ID pattern before creating the class.
- Confirm that you want randomly generated IDs, or choose a school pattern. — the tickbox is deliberate friction.
- Token count must be 1–200.
- A per-line list when pasted IDs do not match, headed These IDs could not be added. Nothing was saved.
Plan limits produce their own: you have reached the maximum number of classes, a class may have at most so many students, or you have reached your total.
When the IDs already exist
In an organisation, handles are unique across the whole organisation rather than per class. So pasting IDs that already belong to learners elsewhere does not create duplicates — it enrols the existing learners, and the page tells you which ones.
This is the behaviour you want and it surprises people. A learner taught by two teachers keeps one record, one password and one history. Seeing these IDs already belonged to students in your organisation and were enrolled means it worked.
Arriving from a learning platform
When a class is created from an LMS launch, the name is taken from the course title and is read-only, and the roster note explains that students come from that platform: create the class, then sync the roster from the class page.