Performance
Every mandatory training report says ninety-something percent.
Because the people who could not reasonably complete it had their assignment quietly removed, and the denominator moved. The number is technically accurate and tells you nothing.
The design
A waiver is recorded. An assignment is not deleted.
Courses are assigned to people with a due date, and completion is tracked. Where somebody genuinely should not have to complete one — long-term leave, a role that does not apply — the assignment is waived with a reason rather than removed.
And a waiver stays in the denominator. Waiving somebody does not improve the completion percentage; it makes it slightly worse. That is deliberate, because the one move every team makes to rescue a completion figure is the one that should not work.
- Employee ACompleted
- Employee BCompleted
- Employee COutstanding
- Employee DWaived, with a reason
- Five states, and two ways to stop —
Assigned, started, completed — and then waived and cancelled, which are deliberately different things. A waiver is an exemption you stand behind; a cancellation is an assignment that should not have existed. They report separately, so the distinction survives the quarter.
- Completion can carry evidence —
A note, and a file where the certificate matters — so "they said they did it" and "here is the certificate" are not the same record.
- The same course cannot be assigned twice over —
A second live assignment of the same course to the same person is refused, and a bulk assign tells you exactly who it skipped and why.
- A retired course cannot be assigned —
So last year's version of a compliance module cannot quietly go out again alongside this year's.
- Assign to several at once —
A compliance course goes out to a group rather than being created individually four hundred times.
- Employees see what they owe —
In the portal, alongside goals — so outstanding training is visible to the person who has to do it rather than only to whoever chases it.
- Waivers carry a reason —
Which turns "why is this person exempt" into a lookup.
- Overdue is counted, per course —
Assigned, in progress, completed, overdue, waived and the percentage — one row per course, so the course nobody is finishing is visible without anybody running a report.
Being exact
It tracks learning. It does not deliver it.
›Does the course content live here?
Material can be attached to a course, or a course can point at wherever the content already lives. What it does not do is play or track progress inside the material — starting and completing are things a person asserts, with optional evidence.
›Can we assign to a whole department?
To a list of people in one action — but not by department or any other grouping, so a recurring company-wide course means selecting people each time. It is the most-felt gap here.
›Does it remind people before a due date?
No. Overdue is counted and visible on the rollup, and nothing chases anybody. The chasing is still a person's job.
›Does an annual course re-assign itself each year?
No. A yearly compliance module is assigned again by hand.
›Does it track progress inside the material?
No — starting and completing are things a person asserts, optionally with evidence. There is no player and nothing watches how far through they got.
›Why not just delete an assignment that does not apply?
Because the completion figure is then meaningless. A waiver with a reason keeps the denominator honest and answers the question later.
›What if our content is on another platform?
Point the course at it. This stays the register of who was asked, who completed and who was excused — which is the part an auditor asks for and the part a content platform does not keep.
Book a demo
Waive one and look at the numbers.
Then imagine the same report with that row deleted instead. That difference is the page.