%20(1).svg)
Most compliance training is not a single event. A fire safety course, a privacy module or a clinical skills check has to be completed, proven, and completed again on a schedule, often for thousands of people whose roles, locations and start dates all differ.
That repeating obligation is what certifications in Totara LMS are built for. This guide is about the Totara feature specifically: how certifications work, how recertification is calculated, what happens when someone misses a deadline, and the configuration choices that are hard to reverse once learners are assigned. If you are looking for the wider picture of compliance training rather than the Totara mechanics, start at the Lambda Learning compliance platform page.
Programs and certifications: the difference that matters
Totara has two ways to group courses into a pathway.
A program is a structured sequence of courses. Once a learner completes it, it stays complete.
A certification is built the same way, from sets of courses with completion rules, but it has a validity period. When that period is coming to an end, the learner is moved back into learning and has to complete it again to stay certified.
If a requirement repeats on a predictable cycle, it belongs in a Totara certification. Typical examples: regulatory and workplace compliance training, health and safety updates, data protection and information security, licence and accreditation renewals, and clinical renewal cycles.
How a Totara certification cycle works
Think of a certification like a passport. It is valid for a fixed term, you are warned before it expires, and renewing it asks less of you than applying for the first one did.
In Totara, the cycle runs in four stages.
- Assignment. Learners are assigned automatically by organisation, position or audience, so a new hire in a regulated role picks up the right certification without anyone adding them by hand. Administrators can also allow self-enrolment into chosen certifications.
- Initial certification. The learner completes the courses on the initial path and is marked certified.
- Recertification window. A set period before expiry, the window opens. The learner is placed on the recertification path, and completion on those courses is reset so the learning has to be done again. Reminders go out through Totara's notifications.
- Renewal or lapse. If the learner completes the path before expiry, a new validity period begins. If not, the certification expires and the reinstatement rules decide what happens next.
Throughout, Totara keeps the history of every previous certification attempt. That history is what an auditor asks for.
The recertification path does not have to repeat the original
A Totara certification can hold more than one path. The initial path might be a full course set, while the recertification path is a shorter refresher covering only what changed or what matters most.
Certifications can also run multi-year recertification sequences. A common pattern is full training in year one, a short update in years two and three, and a return to the full requirement in year four. Learners can loop back to the start or progress to the next stage when each cycle ends.
This matters for two reasons. Staff are not sent through three hours of content they completed last year, and administrators can express a staggered regulatory renewal pattern inside one certification instead of maintaining several near-identical ones.
Where different groups need different renewal timing, a certification can be duplicated with different validity periods and each version assigned to the relevant audience.
Three ways Totara calculates the next expiry date
The reference date setting decides how every future deadline is worked out. It is one of the most consequential choices in the whole setup.
Completion date. The next deadline is counted from the date the learner actually finished. Someone who renews a month early moves their whole cycle a month earlier.
Expiry date. The next deadline is counted from the previous expiry date, so a learner who renews early keeps the same anniversary every year.
Fixed date. Every learner is aligned to one base date, so the whole population expires together, for example on 31 December each year. A minimum certification interval stops someone who certifies late in the year from being due again a few days later.
Fixed dates suit organisations that report compliance on a calendar or fiscal year. Completion and expiry dates suit rolling, individual cycles such as licence renewals tied to a hire date.
When someone misses the deadline
Lapses happen. What matters is that the system handles them the way your policy does.
Totara's reinstatement setting gives three options when a certification lapses: the learner stays on their current path and continues where they left off, goes back to the initial path and starts again, or is moved to a specific path you choose.
Learners can also be allowed to request an extension before their certification expires, so a legitimate delay such as leave does not automatically become a lapse.
If someone leaves an audience and is later reassigned, Totara restores their previous certification status rather than starting them from zero. If their certification expired in the meantime, the reinstatement rule applies.
What auditors see in Totara
A certification record is only as good as the evidence behind it. Totara supports this in several ways.
Certifications keep a full history of each cycle, so you can show not only that someone is certified today but that they were certified continuously.
Certificates are awarded once and cannot be reissued or deleted during recertification, which protects the integrity of the original record.
Exception reporting highlights learners who are overdue or blocked, and compliance reports can be drilled down by organisation, position or audience.
Where a completion date was recorded incorrectly, administrators correct it through the certification completion editor rather than by working around the record.
Totara's report builder answers these questions inside Totara. Where compliance status has to be joined to HR, finance or incident data for a board or regulator, that is the point at which Lambda Learning adds Zoola Analytics.
Configuration decisions that are hard to undo
These come straight from how Totara behaves, and they are where most avoidable rework comes from.
Set recertification before assigning learners. Totara's documentation is explicit that the reference date and related settings should be configured first.
Know what resets when the window opens. Quiz and SCORM attempts are cleared, assignment submissions are removed, and completions recorded through prior learning are reset too. Forum posts and seminar attendance history are kept, but completion is reset. Seminar sessions attended before the window opens do not count toward recertification.
Changing a live certification affects only some people. Learners already certified keep their status when you edit the path. The change reaches them at their next window. Learners in progress and new assignments pick it up immediately.
Assignment changes are not always instant. Due date changes can be deferred until a scheduled task runs, so a dashboard checked seconds after saving may not reflect the change yet.
None of these is a flaw. Each is a rule that makes sense for audit integrity, and each is easier to plan for at design time than to discover after thousands of learners are assigned.
Where Lambda Learning fits
Totara provides the certification engine. Most of the work is in translating a regulatory requirement into paths, windows, reference dates and reinstatement rules that match your policy, and then keeping that configuration correct as the regulation changes.
Lambda Learning implements, hosts and supports Totara for regulated organisations, and has done since 2002. For Huron Perth Healthcare Alliance, four partner hospitals in Ontario, Lambda Learning runs a managed Totara environment with Zoola Analytics. Before, a compliance report took half a day to assemble. Reports are now available on demand, with hundreds of hours recovered annually. Read the case study.
Frequently asked questions
What is the difference between a program and a certification in Totara?
Both are pathways made of course sets. A program stays complete once finished. A certification has a validity period and requires the learner to recertify before it expires.
Can recertification in Totara require less training than the initial certification?
Yes. A certification can have a separate recertification path, and multi-year sequences let the requirement change from one renewal cycle to the next.
Which version of Totara added multi-year recertification?
Multi-year recertification sequences, multiple paths within one certification, and the reinstatement options described above arrived with Totara version 20. Learner self-enrolment into programs and certifications was also added in version 20 and must be enabled by an administrator.
What happens to a learner's certificate when they recertify?
Certificates are awarded once and are not reissued or deleted during recertification. Previous certificates stay in the learner's record.
Can all learners in a Totara certification expire on the same date?
Yes. The fixed date reference option aligns every learner to one base date, with a minimum certification interval so late completers are not due again almost immediately.
Do Totara certifications work on Totara Mobile?
Learners can view and work through programs and certifications from the Totara Mobile app.
Can learners ask for more time?
If extension requests are enabled on the certification, learners can request additional time before their certification expires.
See your renewal rules built in Totara
Bring one real compliance requirement, with its renewal cycle and lapse policy, and we will walk through how it would be configured in Totara. If Totara is not the right fit for it, we will say so.
Totara is a trademark of Totara Learning Solutions Ltd. Lambda Learning Inc. is a Totara Platinum Partner.
.svg)
%20(1).svg)