Content version replacement

When a content goes through a major revision - a new edition of a mandatory training, for example - the old version can be replaced by a successor version, deciding all at once what happens to everyone who already holds a certificate for the old version. This is different from periodic recertification, which reuses the same content when each participant’s own certificate expires individually: replacement retires the whole version at once, in favor of another one.

The three certificate policies

When requesting a replacement, the institution picks one of three policies for the certificates already issued for the old version:

Automatic - certificates stop being valid on the effective date, and every already-certified participant is enrolled in the new version right away.
Notify and wait - certificates stop being valid on the effective date plus a grace period (0 to 365 days; 0 means the deadline falls on the effective date itself), and each holder receives an e-mail notice before that happens.
Keep existing certificates - certificates already issued keep their normal validity, and nobody is re-enrolled now. A learner is only routed to the new version once their own certificate naturally expires. This only works if the old version already has a certificate validity configured - without it, certificates would never expire on their own, so this policy is unavailable.

The successor version needs its own open class to receive re-enrolled participants; it does not need a certificate validity configured.

How re-enrollment happens

Every day, early in the morning, the same daily sweep that handles periodic recertification also applies any replacement whose effective date (plus the grace period, if any) has already arrived, enrolling each certified participant in the successor version.

If the successor version’s open class does not have enough seats for everyone, the participants who do not fit stay pending until a seat opens up.

Where the replacement shows up for the participant

A certificate whose version was replaced shows the Content updated - recertification required badge instead of Expired, in four places: on the completed content screen inside the class, on the participant’s profile Certificates tab, on the public certificate verification page, and - for the institution - in the status column of the Expiring certificates listing.

The old version also leaves the storefront as soon as the replacement is applied and starts refusing new direct enrollments. Participants already enrolled in it keep accessing it normally, and the history of who already completed it is not erased.

Cancelling a replacement

A replacement that is scheduled, in progress, or already applied can be cancelled at the institution’s request. On cancellation:

the old version reappears in the storefront, and its already-issued certificates go back to showing their normal validity;
participants who had already been enrolled in the successor version stay enrolled - cancelling does not undo re-enrollments that already happened.

Common questions

Does the old version disappear from the platform? No. It leaves the storefront and starts refusing new direct enrollments, but it keeps existing - the history of who already completed it is not erased.

Can I chain replacements, with version B (which replaced A) later being replaced by a version C? Yes, as long as the chain does not loop back on itself - for example, C pointing back to A.

What happens if applying the replacement fails? The Eduvem team sees the reason for the error and tries again. No certificate is affected until the replacement is successfully re-applied.