Features that support ongoing compliance management through certification dates, automated recertification cycles, and certification status reporting.
Last updated 13/05/2026
Any topic or pathway can be assigned a Certified Date setting via the Settings tab in the Certification panel. When a learner completes the training, a certified date is automatically calculated and stamped on their enrolment record. Three options are available: a fixed number of days from the date of completion, a fixed number of days from the date of enrolment, or a specific fixed calendar date applied to all enrolments. Certified dates are only applied at the moment of completion — changing the setting after learners have completed the training does not update existing records. Existing enrolments can be updated in bulk via the Enrolments tab or CSV import.
The foundation of all compliance tracking in Tribal Habits. A certified date gives every completed enrolment an expiry — turning a one-time completion record into a managed compliance status. Admins and learners can see at a glance whether certification is current, approaching expiry, or lapsed. Without certified dates, training completion is binary (done/not done) with no ongoing currency.
Last updated 13/05/2026
When recertification is enabled on a topic or pathway, the system automatically creates a retake enrolment for the learner a specified number of days before their certified date expires. The recertification lead time is configured in days — for example, 30 days before expiry. When triggered: the existing enrolment is marked as lapsed (history retained), a new current enrolment is created, and all configured due dates and notifications fire as normal. The learner sees the new enrolment on their dashboard. The cycle repeats indefinitely on each completion — each new completion generates a new certified date, which in turn triggers the next recertification at the appropriate time. Three conditions must be met for recertification to trigger: the learner must have completed the original training, the enrolment must have a certified date, and the learner must not be excluded from recertification.
Fully automates the compliance renewal cycle. Once configured, no admin action is required to keep learners on a rolling recertification schedule — the platform handles re-enrolment, notifications, and record-keeping automatically. Eliminates the most common compliance management failure point: manually tracking and re-enrolling hundreds of staff for annual training renewals.
Last updated 13/05/2026
Recertification can be managed at either the pathway level or the individual topic level. Pathway-level recertification: the certified date is set on the pathway and triggers when the entire pathway is completed. At recertification time, retake enrolments are created for all mandatory topics in the pathway at once. Topic-level recertification within a pathway: each topic has its own certified date and recertification settings, which can vary per topic. Some topics can be excluded from recertification entirely, others can have different cycles.
Gives organisations flexibility in how they manage multi-topic compliance programmes. A single annual compliance pathway can be set up to recertify as a whole, so all topics renew at the same time. Alternatively, topics with different legislative review cycles (e.g. WHS annually, privacy every three years) can each manage their own recertification independently within the same pathway.
Last updated 13/05/2026
When configuring recertification, admins can choose whether the retake enrolment sends the learner back into the same topic or pathway, or forwards them into a different specified topic or pathway. This is the Next Certification setting. Two options: Retake this knowledge (default) — the learner repeats the same content, receiving the most recently published version if the topic has been updated. Enrol in other knowledge — the learner is moved to a designated follow-on topic or pathway at the point of recertification. This is set per topic or pathway in the Certification panel.
Enables organisations to evolve their compliance content over time without disrupting existing recertification cycles. A full induction topic can recertify into a shorter annual refresher. An annual compliance pathway from a prior year can recertify into the updated pathway for the current year. Learners are automatically transferred to the new content at the point of recertification without any admin involvement.
Last updated 13/05/2026
The Requirement element, when used within a topic, can be configured with an expiry date field. When expiry is enabled on a Requirement, an option becomes available to override the topic’s standard Certified Date for that enrolment — meaning the learner’s certification currency is tied to the expiry of the specific requirement rather than to the topic’s default certification period. If recertification is also enabled on the topic, the recertification trigger fires based on the requirement expiry date rather than the topic certified date. The Requirement element supports structured collection of evidence such as licences, certificates, or credentials, with optional assessor review.
Enables organisations to track time-sensitive licences and credentials with real expiry dates rather than fixed training cycles. For example, a forklift licence expiring on a specific date, a first aid certificate valid for two years from the date of issue, or a working with children check with a government-issued expiry. Rather than approximating these with a days-from-completion setting, the actual expiry date drives the certification and recertification cycle — keeping compliance records accurate to the real-world credential.
Last updated 13/05/2026
Individual learners can be excluded from the automated recertification cycle for specific topics or pathways. This can be done three ways: via the Enrolments tab of a topic or pathway (a Recertify Y/N column is visible when recertification is enabled, with bulk action options to Allow or Prevent); via the Topics or Pathways tab on a learner’s profile (using the Prevent/Allow Recertification bulk action); or via CSV import using the Recertify column. Deactivated users are automatically excluded from recertification without any manual action required. To move a learner from one recertification schedule to another, an admin prevents recertification on the first topic or pathway and then enrols the learner in the new one.
Provides the flexibility to manage exceptions within an otherwise automated compliance cycle. Common use cases include: a senior leader who is exempt from a particular compliance topic, an employee who has completed equivalent external training, a staff member being moved from an employee pathway to a manager pathway, or an employee on extended leave who should not receive recertification triggers while absent.
Last updated 13/05/2026
The Certification Report is a dedicated analytics report available in the Admin area under Analytics. It shows all enrolments with a certified date, filterable by topic or pathway, person, group, role, and category. Data can be displayed by certification status or by certified date. Five status labels are used: Certified (current, completed, future certified date), Renewing (lapsed enrolment with future certified date; current retake enrolment in progress), Overdue (no current certified date, due date passed), Expired (no certified date, no active enrolment to renew), and Uncertified (not yet completed). Dates are colour-coded: green (current), orange (expiring within 30 days), red (expired). Reports can be saved with filters and exported to CSV.
The primary compliance monitoring tool for admins. Provides an at-a-glance view of the organisation’s certification status across all compliance training — showing exactly who is current, who is at risk, and who has lapsed. The traffic light colour coding makes it easy to prioritise follow-up. Filterable by group, role, or category, so managers of specific teams or departments can get a targeted view of their own compliance obligations.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| __stripe_mid | 1 year | Stripe sets this cookie to process payments. |
| __stripe_sid | 1 hour | Stripe sets this cookie to process payments. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
| rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| sbjs_current | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_current_add | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_first | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_first_add | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_migrations | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_session | 1 hour | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_udata | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| Cookie | Duration | Description |
|---|---|---|
| _cfuvid | session | Description is currently not available. |
| blgj5lst | 5 days | Description is currently not available. |
| m | 2 years | No description available. |
| oxetqk28 | 5 days | Description is currently not available. |
| x4mk8hq1 | 5 days | Description is currently not available. |