Testing Center — Overview
The Testing Center lets you conduct a test for someone who is not your student.
No enrolment. No course. No onboarding. You create a sitting, load a list of names, candidates take the test once, and everyone gets a branded report and a certificate. The records stay searchable long after the sitting is over.
When to use it
| Situation | Why the Testing Center fits |
|---|---|
| Walk-in placement testing | The candidate isn't a student yet — you're testing to decide whether they become one |
| Corporate or bulk screening | An employer sends 200 people once; none of them need a portal account afterwards |
| Partner schools and colleges | You run the sitting on their behalf and hand back results under their branding |
| Entrance or exit testing | A whole cohort sits on one day, in one hall, often with no email addresses |
If the person is your enrolled student and you want them to practise, use a normal test assignment instead. The Testing Center is for one-time, on-the-record sittings.
The shape of it
Campaign → optional label shared by several sittings ("State drive, Oct 2026")
└── Event → the sitting: name, date window, which test, exam conditions, how results are released
└── Candidates → one row per person, one attempt each — with their group, venue and own slot
└── Result → score, level, PDF report, certificate, verification code
What you get
- Two ways in. Email invitations, or printed access codes for candidates with no email address.
- One paper or a pool. Point the event at a single test, or at a pool of tests and let the system hand out a different paper to each candidate.
- Rosters at any size, with the metadata you already have. Paste a handful of names, or
upload a CSV of up to 5,000 rows. A
groupcolumn (school, college, department, batch …) segregates every report, avenuecolumn gives attendance per hall, aslotcolumn gives each candidate their own start time, and any other column comes back in every export. - Sittings by day. The organisation page opens on the sittings under the day their candidates sit, with booked / entered / sat / to mark / released rolled up per day; a day view merges every sitting on that day.
- Attendance without a clipboard. Who has entered, who is still awaited, who is absent — per group and per venue, refreshing as the sitting runs.
- Each group gets its own results. One email per group (a school, a college, a department) with a CSV of released results only and a fixed, minimal column set — never phone numbers or parent emails.
- Exam conditions per sitting. Listening audio once, real-exam speaking flow and the real IELTS layout, chosen once by the organiser and applied only to papers that support them.
- Optional examiner review. Release results instantly, or hold them so an examiner can adjust a score first.
- Your branding. Reports and certificates carry the conducting organization's logo, not ours.
- Records that stay findable. Search every candidate you have ever tested by name, email or reference number. Filter by date, test type, level, score or status. Export to CSV.
- Billing per completed test. You are charged when a candidate finishes — not when you invite them, and not per student per month.
Where to find it
Language Tests → Testing Center, or go straight to
/language-tests/testing-center/.
The hub lists every organization you can conduct tests for. Open one to see its events, candidates, review queue and billing.
Next
- Conduct a test sitting — the step-by-step, including roster metadata, exam conditions, attendance and sending results to a group
- Printed access codes & seat sheets — testing without email addresses
- Test pools — a different paper for each candidate
- Results, certificates & verification
- Finding records — registry, schedule and dashboards
- How conducted tests are billed