Interpretations

Interpretations attach explanatory text to score ranges. Where a performance level gives a band a name, an interpretation gives it a paragraph: what the score means, what strengths and gaps it typically reflects, and what the reader should do with it. They turn a score report into something a candidate or manager can act on without an analyst translating.

Setting Up Interpretations

1. Open the test's reporting settings and enable Interpretations.
2. Define score ranges and write the text for each — rich content, so you can format, add lists, or link resources.
3. Cover the full score range so every possible result has an interpretation.

Example for a sales-skills assessment, 40–60% band: “You handle straightforward customer conversations confidently but tend to lose structure in objection handling. Focus on the discovery-question framework in module 3 before re-testing.”

How Interpretations Appear

The matching interpretation renders on the score report beneath the score — in the admin view, and in the candidate report when your report template includes it. Different readers, one mechanism: write candidate-facing coaching text for training tests, or reviewer-facing decision guidance for screening tests.

Writing Useful Interpretations

• Describe behavior, not arithmetic — “you scored between 40 and 60” adds nothing; “you reliably solve routine cases but struggle with edge cases” does.
• End with a next step — study material, a recommended role fit, a re-test path.
• Keep the tone consistent across bands; candidates in the bottom band still deserve constructive text.

Interpretations pair naturally with Performance Levels: the level names the band on the chart, the interpretation explains it in prose. Define both on the same ranges for a coherent report.

Good to know