Skip to content

Manage staff training

Assign learning, maintain courses, review evidence and monitor renewals.

Checked against the screens:

Every organisation can choose its own words for the people and roles it works with. When you are signed in, this guide uses your organisation’s words. Otherwise it uses the product’s own.

Screenshots show website controls checked on 13–14 October 2026. Captions identify live-site captures and local training examples made with the actual website components. No real person’s record is shown. Your permissions, enabled features and organisation’s wording may change what you see.

Open Staff training to see requirements, evidence waiting for review, approaching renewals and overdue learning. Managers and admins can monitor and assign training. Only admins maintain the catalogue and import history.

Steps

  1. Use Overview for compliance. Select a figure to open its records.
  2. Use By employee for one person's learning, or By course for course coverage.
  3. Open Manage training and Set required training. Select employees, courses and their deadline. Check the requirement total, then save.
  4. Open an employee, enter completed learning and choose Save completion. A manual submission waits for an independent review.
  5. Inspect pending evidence. Choose Verify completion, or Return for correction with a clear reason.
  6. Admins use Create a course for audience, named employees, deadline, renewal and evidence rules. Use Create new version for a change, or Archive course after active work is resolved.
  7. Admins use Manage categories to Create category or rename one with Save changes. Move active courses before Archive, Restore when needed, or Delete unused when never used.
  8. Admins use Import records, check every preview issue, then choose Import reviewed rows. Existing decisions are not silently replaced.

If it goes wrong

Staff training overview with compliance and action summaries
Training example: the overview uses fictional names and figures. Select a metric or row to open the records behind it. Select the image to enlarge it.

How compliance is calculated

Compliance uses required learning only. Current verified completions count as compliant. Missing, expired, overdue, superseded-version and awaiting-review requirements remain outstanding. Optional courses do not create gaps unless they are assigned to a person.

A first deadline is based on when both the course and employee record existed, unless a manager sets an explicit date. Editing a course description does not move that deadline.

Roles and access

Evidence, renewals and versions

A renewal period calculates an expiry date from the completion date. Due-soon and overdue views include first completions as well as renewals, so upcoming work is visible before compliance is lost.

Where evidence is mandatory, an imported or manually recorded completion remains pending until another authorised person verifies it. Returning evidence never deletes the submission or its correction reason.

Course versions preserve what the rule was at the time. Requiring the latest version is a deliberate compliance decision; leave it off when wording or administration changed but existing learning is still valid.

Audience and exceptions

Everyone creates a requirement for every active employee. Selected job titles create requirements only where the staff record matches one of those titles. Optional leaves the course available without turning every missing completion into a gap. Named employees adds specific people alongside any broad audience rule.

Use Named employees while editing a course when the named group is part of that course's normal audience. Use an individual requirement for a one-off exception, such as somebody temporarily covering another role. If a person is not required to complete an otherwise mandatory course, record an exemption and its reason. Do not weaken the course audience for everybody to solve one exception.

Save a named audience separately from a new course version. You can set its shared deadline. Removing somebody requires a reason and withdraws only the named-audience requirement; one-off assignments and broader everyone or job-title rules remain intact. Use an exemption for a genuine exception.

Diagram showing a course audience becoming an employee requirement and training outcome
The course audience supplies the broad rule. Named employees add specific people; individual requirements and reasoned exemptions handle genuine exceptions without weakening the rule for everybody. Select the image to enlarge it.

Workbook reconciliation

The workbook preview separates matched requirements, completions, exemptions, new courses, unresolved names and date problems. Rows with an unknown or ambiguous person are not guessed. Correct the workbook or the staff roster, then preview again.

Applying the preview is one database transaction. If any accepted row fails, the whole batch rolls back. The batch summary records unresolved outcomes and conflicts, so a partly reconciled import cannot be mistaken for a complete migration.