CORA runs that chasing automatically for both training and credentials, and the reason it's worth turning on is the restraint built into it, as much as the automation itself.
Four jobs, run automatically
Four scheduled jobs run automatically, without anyone pressing a button: training reminders, checking who's behind on an assigned course or pathway; a notification sweep, refreshing what shows on the dashboard; membership renewals, keeping billing and seats in step with who's actually active; and a purge, clearing out what's been deleted and is past the point of recovery.
The first one is the one a provider actually feels. It's also the one with the most thought behind how often it's allowed to speak.
One email per worker, never one per course
A worker behind on four courses gets one email, listing all four. Not four emails landing in the same second with four different subject lines. That was a deliberate design decision, and it holds for credentials too. Someone behind on a course and holding a First Aid ticket that lapses next week gets one message covering both, not two separate systems that have no idea the other one exists.
Two guards, doing different jobs
The restraint comes from two separate rules working together, and it's worth understanding both, because either one alone would be worse than neither.
A per item window of 25 days stops the same course, or the same credential, being chased over and over in a tight loop. Once someone's been reminded about a specific course, that specific course goes quiet for 25 days before it can trigger another email, even if they're still behind on it.
A per person quiet window of 7 days sits on top of that, and it's shared across training and credentials both. Whichever system reminded someone most recently, the other one checks that same clock before it sends anything. The result is one promise CORA can actually keep: a worker will not get more than roughly one administrative nudge a week from CORA, no matter which button was pressed or which job ran that night.
The weekly digest
On top of the automated chasing of individual workers, your admin team gets its own weekly digest, a single email naming everything coming due across the whole workforce. You choose the day it lands, any day of the week, Monday by default, and you choose how far ahead it warns you, in one or more windows of 7, 14, 30, 60 or 90 days, 60 and 30 by default. A provider six months from an audit might warn at 90 and 60 days. One with a tighter roster might want every window ticked.
Four modes cover how loud any of this is allowed to be: a weekly digest only, one email per item as it crosses a warning point, both together, or a dashboard banner with no emails at all. The dashboard banner itself is always on. Everything past that is your call.
Chasing outstanding paperwork, on by default
Onboarding chasing is switched on by default. When a new starter still owes a contract, a credential from their pack, a policy acknowledgement, or an assigned course, CORA chases it the same way, because assigning a credential pack to somebody is a provider deciding they want those certificates collected, not just requested once and forgotten.
What CORA chases, and what stays yours to decide
CORA chases the refresher. The decision about what happens next, whether someone's rebooked into a course, given an extension, or spoken to directly, stays yours. What CORA does is put the right renewal in front of the right person, on a cadence that won't wear either of you out, and keep a record that it happened.
Every claim on this page is written the same way every claim on this site is written: about what CORA actually does, checkable in a demo. See the standard we hold every claim on the site to.
Training refreshers get the same treatment as tickets
A course like Infection Control and Hygiene carries its own refresher date on completion, and it's chased on exactly the same cadence as a First Aid ticket sitting in the credential register, through the same automated job, against the same quiet window. See how both feed the training register an assessor actually asks for.
Common questions
How often will a worker be reminded about the same course or credential?
No more than once every 25 days about that specific item, and no more than roughly once a week from CORA in total, across every course and credential combined.
Can I choose how CORA reminds my team?
Yes. Choose a weekly digest, one email per item, both together, or a dashboard banner with no emails, and set which day the digest lands and how many days ahead it warns you.
Does CORA remind support workers about their own credentials, or only admins?
Both. A worker whose ticket is coming up for renewal is reminded directly, and your admin team sees the same picture in the weekly digest and the register itself.