Achievements are the system record that a learner met the criteria for a completion, credential, or certification-related outcome.
They are issued at the Learner level to preserve delivery-specific truth, then surfaced at the Contact level to support longitudinal history across many events, courses, and learning journeys.
This distinction matters: the learner-level record is the operational truth for a specific participation instance, while the contact-level view is the rolled-up history used for reporting, visibility, and credential management over time.
Contents
- What achievements represent
- Achievement vs certificate vs certification
- How outcomes are produced
- Rule sources: automatic vs manual
- How delivery model affects achievement logic
- Learner issuance and contact rollup
- Why rollups matter
- Auditability and corrections
- Related references
What achievements represent
An achievement is the formal record of an outcome for a specific participation record. It is commonly used for:
- credential and certification tracking
- compliance reporting
- client evidence and verification
- learner progress and completion history
- expiry and renewal workflows where training must be refreshed periodically
Achievements are not just markers that somebody registered or attended. They represent that the required rules for a defined outcome were met.
Achievement vs certificate vs certification
These terms are related, but they are not the same thing:
- Achievement — the system truth that the learner earned a defined outcome
- Certificate — an optional document generated from that achievement record
- Certification — the business or compliance meaning attached to the achievement, often with validity, expiry, or renewal expectations
In practice, the achievement is the authoritative record. A certificate is a representation of that record, not the source of truth.
This is why reporting, compliance evidence, and learner history should be anchored in achievement data rather than in enrollment alone or in the existence of a certificate file.
How outcomes are produced
Participation data -> achievement rules -> achievement issuance -> contact-level history
This chain matters because achievements are the result of actual participation conditions being met. The exact rules may vary by delivery model, but the principle stays the same: a learner earns the outcome only when the configured criteria are satisfied.
That means achievements sit downstream of attendance, progress, assessment, LMS completion, or other required evidence.
Rule sources: automatic vs manual
Achievement issuance can occur in two broad ways:
- Automatically, based on explicit rules such as attendance, online completion, pass criteria, or a combination of those conditions
- Manually, when instructor review, assessor judgment, moderation, or exception handling is required
Automatic does not mean unguarded. It means the conditions are explicit, predictable, and repeatable.
Manual issuance is typically used when the outcome depends on human confirmation rather than a purely system-detectable signal.
How delivery model affects achievement logic
Administrate supports multiple delivery approaches, so achievement logic should reflect how the training is actually delivered.
- Classroom — outcomes often depend on attendance, participation status, or instructor-entered results
- Virtual instructor-led — outcomes may still depend on attendance or instructor confirmation, even though delivery is online
- Blended learning — outcomes may depend on both live participation and online component completion
- SCORM / eLearning / self-paced — outcomes may depend on online completion, pass score, or progress thresholds
- External learning — outcomes may be recorded manually or based on imported evidence, depending on how that activity is managed
This is one reason the achievement model is important: it gives you a consistent learner-outcome record across very different delivery models.
Learner issuance and contact rollup
Achievements are issued to Learners so Administrate can preserve event-level or participation-level truth.
That matters because the same Contact may participate in multiple Events, retake the same Course, complete a blended journey, or earn the same outcome more than once over time.
Once issued, those achievement records are surfaced at the Contact level so administrators can review longitudinal history across all of that activity.
In other words:
- Learner level preserves the truth of a specific delivery instance
- Contact level gives you the broader historical view across the person’s overall training record
Why rollups matter
Rollups make it possible to answer business questions like:
- What has this person achieved across all their training history?
- Does this contact currently hold a valid outcome?
- Which learners earned this credential during a specific period?
- Which accounts or clients need evidence that training outcomes were achieved?
Rollups are useful, but they should not be mistaken for the originating truth. When you need to understand why an achievement exists, or whether it was issued correctly, the learner- and participation-level context is the place to look.
Auditability and corrections
Achievement changes should remain traceable. Administrate favors auditability so reporting remains defensible and outcomes can be trusted over time.
This is especially important when:
- a learner is marked passed or failed manually
- attendance is corrected after the event
- online completion data changes
- an achievement is revoked, reissued, or updated
- expiry or validity needs adjustment
A strong achievement model helps you preserve both the current outcome and the operational history behind it.