Training tasks
A task is one unit of training: material to read, a test to pass, and the window to do it in.
Creating one
| Setting | Notes |
|---|---|
| Title, description, tags | How you and your team identify it |
| Start and end date | The overall window for the task |
| Test | One assessment, chosen from your account |
| Test start and end date | A separate window for the test itself |
| Minimum retry wait | Hours before a failed attempt can be retried. Default 24 |
| Maximum attempts | How many tries in total. Default 3 |
The test window is separate from the task window on purpose. Give people a fortnight to read the material and open the test for the last week of it, and you avoid the pattern where someone opens the test on day one, fails, and burns a retry before reading anything.
Documents
Attach PDFs — the policy, the handbook, the slides. They are shown in the order you set, and each is acknowledged individually by the participant.
Every document must be acknowledged before the test unlocks. A participant who has not confirmed reading all of them cannot start, and is told exactly that. This is the mechanism that turns "we sent everyone the policy" into "everyone confirmed they read the policy", which is the difference that matters when someone asks for evidence.
Order the documents so the sequence makes sense on its own. Participants work through them top to bottom, and a numbered order is easier to discuss than "the second PDF".
Keep each document to one topic. One 80-page combined PDF is acknowledged with a single click that means very little; five focused documents produce five acknowledgements that each mean something specific.
Retries
Two settings work together, and the defaults — 3 attempts, 24 hours apart — are reasonable for most compliance training.
The waiting period is the important one. Without it, a failed participant retakes the test immediately and passes by elimination, having learned which options are wrong rather than the material. A day's gap makes rereading the document the easier path, which is the behaviour you actually want.
Lengthen the wait for material that genuinely needs study; shorten it when a failure is more likely to be a technical mishap than a knowledge gap.
When someone cannot start
The platform tells the participant which condition is blocking them, in plain terms:
- Documents still to acknowledge
- The test has not opened yet, with the date it does
- The test period has ended
- They have already passed
- Maximum attempts reached
- A retry wait still running, with the time it ends
Most support questions about training are one of these, so it is worth asking which message the person is seeing before investigating anything.
Tracking progress
Each task has statistics covering how far the assigned group has got. That is where you find the people who have not started with three days left — the group worth an email while it can still change the outcome.