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
- Scoring
- Question Types
- Question Authoring
- Browsing Questions
- Content Blocks
- Media Library
- Metadata Rules & Schema
- 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
- Analytics Overview
- Test Analytics
- Question Analytics
- Per-Question Analytics
- Results Explorer
- Segment Analysis
Tasks
Steps
Steps are the building blocks of a task — each wraps a test with its own delivery rules. This section maps every panel of the step editor, from contents and pre-start gates to anti-cheating and certification.
Updated 2026/09/07
Steps are the building blocks of a task. Each step wraps one test together with its own delivery rules: what candidates read before and after, which checks they pass to start, when the step is open, how many attempts they get, what security applies while they work, and what happens when they finish. A task with one step is a simple exam; a task with several steps is a full assessment process.
Settings defined on a step apply to every candidate — but individual candidates can be given customized step settings from their ticket (different limits, relaxed security, extra attempts) without touching the step itself.
In this section
Step Profile
The step's identity: its title, whether it runs as a scored Test or a consequence-free Practice, and its weight when the task computes an overall score across steps.
Step Contents
Rich-text messaging around the exam: what candidates read on the step card before starting and what they see when they finish — instructions, expectations, and next-step guidance.
Pre-Start
The gates candidates pass before the exam starts — document acknowledgment, notice confirmation, device restrictions, the automated system check, and prerequisites — and how the pre-start sequence works.
Availability
Control when the step can be taken: an Enabled/Disabled switch, an optional start–end date window with a late-start time deduction, a check-in deadline for late arrivals, and a per-candidate attempt limit.
Anti-Cheating
Anti-cheating settings control how the exam environment is monitored and secured — each option can be enabled independently, and combining them narrows the range of devices that can take the step.
Reporting
Decide what each audience sees as the step's result: the organiser-facing admin report and the candidate-facing user report, each configured independently.
Device Compatibility
Everything that determines whether a candidate can take your exam from where they are: supported device types and browsers per configuration, internet speed requirements, and the network permissions enterprise IT teams need to grant.
Certification
Attach one or more certificates to a step so candidates who complete it and meet each certificate's conditions receive their certificate automatically in their user report.
Automated Emails
Configure step-triggered emails: completion notifications to your team with a default or fully customized template, and delivery rules for candidate-facing messages.