Getting Started
- What is TestInvite?
- Build Your First Test
- Run Your First Assessment
- Taking the Assessment
- Viewing the Results
- Question Bank Overview
- Common Question Features
- Question Types
- Creating Questions
- Organizing Questions
- Content Blocks
- Roles & Access
- Media Library
- Import & Export
- Question Submissions
- Question Bank Schema
- Browsing Questions
- Cloning Questions
- Bulk Updating Questions
- Tests Overview
- My Tests
- Creating a Test
- The Test Editor
- Test Settings
- Sections & Pages
- Adding Questions
- Page Builders
- Test Profile
- Reporting
- Test Papers
- Analytics
- Publishing a Test
- Test Library
- Marketplace
- Tasks Overview
- Creating a Task
- Task Dashboard
- Steps
- Task Settings
- Candidates
- Test Sessions
- Sent Mails
- Proctoring
- Analytics
Tests
Reporting
Performance Levels
Divide the score range into named bands — like Beginner, Intermediate, Advanced — so every result carries a meaningful level instead of a bare number, in reports, tables, and exports.
Updated 2026/07/13
Performance levels divide the score range into named bands — “Beginner / Intermediate / Advanced”, “A1–C2”, “Needs Improvement / Meets / Exceeds” — so every result carries a meaningful label instead of a bare percentage. A 68% means little to a hiring manager; “Upper Intermediate” communicates instantly.
Building the Level Scale
- Open the test's reporting settings and enable Performance Levels.
- Define your levels: each level has a name and a score range (from–to, as a percentage of the maximum score).
- Cover the whole 0–100% range without gaps or overlaps — the visualization shows the bands side by side so holes are immediately visible.
Example scale for a language placement test: 0–20% Starter · 21–40% Elementary · 41–60% Intermediate · 61–80% Upper Intermediate · 81–100% Advanced.
How Levels Appear
- On score reports — the level name is displayed with the score (and to candidates, if your report template includes it).
- In session results tables and exports — filter or group candidates by level.
Designing Good Bands
- Name levels in the vocabulary your report readers use — CEFR grades for language tests, competency labels for HR.
- Don't over-slice: 3–5 bands are readable; 8 bands imply precision the test rarely has.
- Validate band edges against a pilot cohort's distribution so the labels match reality.
Levels, Pass/Fail, and Interpretations are complementary layers on the same score: the level names the band, pass/fail states the decision, and an interpretation adds explanatory text for the band. Use any combination.