Tasks Reporting

Admin Report

The Admin Report is what your team sees for each completed session of a step. Three settings shape it: the report template, an optional benchmark, and a custom header.

Updated 2026/10/15

The Admin Report is the result your team sees when it opens a completed session in a step. It is set per step, not per test. The same test can be reported one way in a hiring task and another way in a training task, and the test itself does not change.

To open it, go to the task, open Steps, select the step, and choose Reporting → Admin Report. The step overview also has a summary card with the current report template, benchmark, and custom reporting.

The three settings

SettingWhat it controls
Report TemplateWhich layout builds the report: the test's default, the Standard layout (with an optional custom report added), or one of the test's custom reports.
BenchmarkThe reference group each candidate's result is compared against: none, this task, all tasks using the test, or a saved norm.
Custom Report HeaderRich text at the top of the report, such as scoring guidance or internal notes for reviewers.

Report Template

The template decides how the report looks and which sections it shows. It never changes how the session is scored. The options are:

  • Test's Default Report Template — follow the test, so the step changes whenever the test's default template does.
  • Standard — always the Standard Template. Turn on Extend with Custom Template to add a custom report too: pick it under Custom Reporting (or Default for the test's default custom report) and set its Location, top or bottom.
  • A specific custom report — every custom report of the test is listed by title.

Benchmark

A benchmark puts each score in context. Instead of a bare 72%, reviewers see how that result compares with a reference group: other candidates in this task, everyone who has taken the test across all your tasks, or a norm saved on the test.

Custom Report Header

The header is a short block of formatted text at the top of the report. Use it for things that apply to this delivery only, such as the role being hired for, a scoring rubric, or a confidentiality note. Candidates never see it, because it belongs to the Admin Report only.

How the test and the step share the work

The test defines what reporting options exist: its report templates, pass/fail rules, performance levels, interpretations, and norms. The step picks which template the Admin Report uses and adds the two things that depend on the delivery: the benchmark and the header.

Admin Report vs. Candidate Report

The two reports are set up separately. Changing the Admin Report never changes what candidates receive. What candidates see is controlled in the Candidate Report settings. This means your team can work with a full, detailed report while candidates get only what you choose to release.

The Admin Report is built from the step's current settings every time someone opens it. A new template, benchmark, or header shows up on sessions that are already completed, and you don't need to recalculate anything.
Good to know

The Report Template dropdown has four kinds of options. They differ in two ways: which layout they produce, and whether the step follows changes to the test or stays fixed.

  • Test's Default Report Template uses whatever template is set as the default on the test's Reporting → Templates tab. If someone changes that default later, this step switches to the new one automatically.
  • Standard always uses TestInvite's built-in layout, whatever the test's default is. The test's Standard template settings decide which sections appear. This is the only option that lets you add a custom report to the layout.
  • A named custom report (listed with the subtitle Custom Template) fixes this step to that exact report. Later changes to the test's default don't affect it.
  • Default Custom Reporting uses the custom report the test marks as its default. It is greyed out when the test has no default custom report.

Which one to use

SituationChoose
You want every task using this test to report the same way, managed in one placeTest's Default Report Template
You want the platform layout here, even if the test's default is a custom reportStandard
This step needs a particular custom report, for example a client-branded oneThe named custom report
You want the standard layout plus an extra custom sectionStandard + Extend with Custom Template
The dropdown only lists custom reports that already exist on the test. To add one, create it on the test's Reporting → Templates tab first. It then appears in this list for every step that uses the test.
Good to know

Choosing a custom report as the template replaces the standard layout entirely. Extend with Custom Template adds a custom report to the Standard layout instead. Reviewers still get the familiar standard sections (scores, dimensions, pass/fail, levels) and also see the content your custom report produces.

Setting it up

  1. Set Report Template to Standard. The option only appears with Standard.
  2. Tick Extend with Custom Template.
  3. Under Custom Reporting, choose what to add. The Default Custom Reporting option uses the custom report the test marks as its default, shown with its name, and follows the test if that default changes. A named custom report fixes the step to that exact report.
  4. Under Location, choose Top to show the custom content before the standard sections, or Bottom to show it after them.

Typical uses are a branded cover section, a client-specific summary, or an extra calculation that the standard layout doesn't show.

The checkbox is disabled when the test has no custom reports, and the Default Custom Reporting option is disabled when the test has no default custom report. Create them on the test's Reporting → Templates tab first. If the selected custom report is later removed from the test, the Admin Report still opens and shows only the standard content.
Good to know

A benchmark answers the question "is this a good score?" by showing each result next to a reference group. You choose one option for the step:

OptionCompares against
DisabledNothing. The report shows the result on its own.
This TaskResults from other sessions of this test in this task only.
All TasksResults from every task in your organization that uses this test.
A saved norm (listed by name)A fixed reference distribution saved on the test, such as a pilot group or a published norm.

Live groups and the cache duration

This Task and All Tasks are calculated from real results, so the group grows as more candidates finish. To keep reports fast, the group is calculated once and reused for the Cache Duration you pick next to the option: from 4 hours up to 1 year, or Forever. When that period ends, the next report that is opened recalculates the group. The default is 8 hours.

Use a short duration while a task is collecting results and the group is still changing. Use a long duration, or Forever, when you want every candidate compared against the same stable group.

Choosing between live groups and norms

Live groups need no setup, but early candidates are compared against a small and shifting group. A saved norm gives every candidate the same reference from day one, which matters when results need to be comparable across time or across cohorts.

The benchmark set here applies to the Admin Report. The Candidate Report has a separate Include Benchmark option, which uses this same comparison when it is switched on.
Good to know

The Custom Report Header is a block of formatted text shown at the top of the Admin Report for every session in this step. Because it belongs to the step, the same test can carry different context in different tasks.

Common uses

  • The role, cohort, or client the assessment was run for.
  • Scoring guidance or a rubric reminder for reviewers.
  • A confidentiality or internal-use-only notice.

What it supports

The editor supports text formatting such as headings, bold, italics, lists, and colors. Media, links, tables, attachments, and formulas are turned off, so the header stays a short, clean block of text.

The header is rendered by the Standard layout. That includes Test's Default when the test's default is Standard. When the step uses a custom report as its template, the custom report controls the entire page, so put any header text in the custom report itself.
Good to know

Yes. The Admin Report isn't saved as a finished document when a session completes. It is built every time someone opens it, from the stored result and the step's current reporting settings. If you change the template, benchmark, or header, every completed session in the step uses the new settings the next time its report is opened.

What changes and what doesn't

ChangeEffect on completed sessions
Report template, custom extension, or headerShows the next time a report is opened.
Benchmark optionShows the next time a report is opened. Live groups (This Task, All Tasks) also refresh when their cache duration ends.
Scores, pass/fail outcome, stored answersNot affected. The reporting settings only change how results are presented.

You don't need to recalculate results after changing these settings. Recalculation is for scoring changes, such as a corrected answer key, not for presentation changes.

Because past sessions follow the current settings, a report someone downloaded last month can look different from the same report opened today. If you need a fixed record, save a copy of the report before you change the step's reporting settings.
Good to know
Go back