Finding Records — Registry, Schedule & Dashboards
Scrolling stops working somewhere around the second page. Everything below is built so that you never have to.
The five surfaces
| Surface | Where | Answers |
|---|---|---|
| Hub | /language-tests/testing-center/ |
Which organizations are running tests, and who has a review backlog |
| Org dashboard | Open an organization from the hub | This school's events, candidates, review queue and billing |
| Overview | Overview button | How many, what levels, what scores, how fast reviews are moving |
| Registry | Registry button | One person, among everyone you have ever tested |
| Schedule | Schedule button | Who sits when — by day, by month, and what is still to come |
Registry — finding a person
The registry is a searchable list of every candidate across every sitting.
Search by name, email address or reference number. Partial matches work — typing
marg finds Margaret, and typing part of a roll number finds the candidate holding it.
Filter by:
- Organization
- Event
- Date range
- Test type
- Status — invited, started, completed, awaiting review, released, cancelled
- Level (CEFR) and score range
Filters combine. "Every candidate at Campus B who reached B2 or above in March" is a few clicks, not an export-and-spreadsheet job.
Export the filtered set as CSV. The export streams, so a large result set downloads rather than timing out, and it is safe to open directly in Excel.
Schedule — who sits when
Three views of the same thing:
- By day — a grid of the coming days with the number of candidates scheduled on each
- By month — the same at a month's resolution, for planning a term
- Forward capacity — what is already booked over the next stretch, so you can see where there is room before promising a partner school a date
Overview — the numbers
Available platform-wide, and per organization:
- Volume over time — sittings completed, by day
- CEFR mix — the distribution of levels achieved
- Score distribution by test type — where a cohort actually lands
- Review ageing — how long held results have been waiting
- Per-organization comparison — when you run tests for several schools, how they compare side by side
An administrator overseeing several schools gets both: the roll-up across all of them, and each school's own view, without switching accounts.
Speed at volume
Every list is paginated and every filter is applied by the database, not after loading. That means a filter returns the right set no matter how many records exist — the result does not depend on how many rows happened to be fetched first.
Score, level, test type and completion date are stored on the candidate record at the moment they finish. That is why a question like "every B2 in March" is instant rather than something the system has to work out row by row.