On this page
Designing a certification is one job. Running it is another. The design work, which includes writing the exam, deciding what earns the credential, and setting the passing score, builds the certification. Running it is everything after: people enroll, take the assessment, pass or fail, get their credential, and, because certifications expire, come back later to do it again.
The ongoing management of a certification program determines its success. A key operational decision is whether to use a single platform for enrollment, delivery, proctoring, issuance, and renewal, or to combine multiple tools and manage data across systems. This article considers the operational requirements of running a certification and explains why many programs choose Intellum's LMS platform for these tasks.
What "administering" a certification program actually involves
Once the content and passing criteria are in place, the design work is largely finished. What remains is operational, and it repeats for every learner and every renewal cycle. It largely breaks into four recurring tasks:
- Enrollment: Getting the right people into the certification, whether that is ten people or ten thousand, once or on a schedule.
- Delivery: Presenting the assessment and recording a pass or fail.
- Issuance: Producing the credential itself: the badge or certificate, its unique code, its expiration date.
- Tracking and renewal: Knowing who holds the credential, when it expires, and moving expiring holders back through recertification.
While these operational tasks may seem routine, they must function automatically at scale. The following sections outline each task, using Intellum's platform to illustrate the process.
How people actually get certified
A certification in Intellum is based on an assessment that the learner must pass. The method of delivering the exam depends on the level of control required by the program.
Standard assessments are available on demand, allowing learners to take the exam at their convenience. The platform automatically scores the assessment. This approach is suitable for lower-stakes certifications focused on competence.
Scheduled assessments are linked to specific dates and times, typically for certifications that require regulated conditions such as live proctoring. Importantly, the pass/fail outcome is determined by the assessment score, not merely by attendance.
- High-stakes certifications require defensible exam conditions to ensure the integrity of results: Intellum integrates with Honorlock for real-time proctoring, enabling browser lockdown and detection of unauthorized devices or voices. Administrators set thresholds and auto-fail rules for violations. Learners need an Honorlock account and a Chrome extension. A fully native alternative, Safe Exam Browser, requires no separate account: the learner installs the app, which locks down the assessment while it runs, with options ranging from basic lockdown to controls approaching Honorlock's. For programs that need legally defensible credentialing, these controls deliver secure, proctored exams linked to verifiable credentials.
The point worth drawing out is architectural: proctoring is integrated directly into Intellum, eliminating the need for separate exam platforms or additional systems for storing results.
- Passing, failing, and retakes: Intellum uses enrollment status as the definitive record of learner outcomes. Pass or fail is determined by the score threshold, and learners who do not pass can be reset individually or in bulk, or re-enrolled for retakes. This unified status ensures credentialing and reporting are based on a single, consistent record.
Issuing and managing the credential
In Intellum, a credential is the official record awarded for completing an activity, such as an exam, activity, or learning path. Issuance is automated: once completion criteria are met, the platform generates the credential without manual intervention. This automation enables programs to scale efficiently.
Administrators manage credentialing through the activity's gamification properties, which include the following key elements:
- Credential name and code: Both are optional. If left blank, the name defaults to the activity or path name for simplicity. Specifying a name provides more control, especially if the activity name is lengthy or too specific (for example, "Customer Support Specialist Level 1"). The code is a unique identifier; using a consistent pattern such as PROGRAM-LEVEL-YEAR simplifies reporting and audits, making it valuable for large-scale programs.
- Expiration: An expiration length in months, or blank if the certification does not expire. The expiration date then appears on the credential itself.
- Appearance: A badge image and an optional printable certificate template, designed once under Settings and reused across programs, so a sales certification and a technical certification can carry different designs.
- Sharing: An option that lets learners post the credential publicly, including on LinkedIn, with a share control on the credential page. Credentials generated in this manner can display the credential name, the learner's full name, the completion date, the unique completion ID, and, when applicable, the score, credit units, expiration date, description, and reputation points. All information is generated and stored within Intellum, without the need for external certificate generators.
The setup itself runs in two parts inside Intellum: an admin creates a reusable certificate template under Settings → Gamification, then enables Award a Credential on Completion in a course's gamification properties, with Intellum's Knowledge Base agent and documentation covering the step-by-step for each. - On Credly: For organizations already using Credly, Intellum integrates to allow learners to earn Credly badges. This integration is optional; Intellum's native credentialing fully supports the entire lifecycle independently. Credly is available for those who already use it, but is not required.
Doing it at scale
While these processes above are effective for small groups, the need to manage large, recurring cohorts across regions drives programs to consolidate onto a single platform.
- Enrollment stops being manual: Enrollment is automated through rules that assign certification activities or paths based on attributes such as group, role, or date. Bulk changes can be applied across users and activities using the Enrollments List, which also manages notifications to learners. This automation addresses the challenge of manual updates at scale.
- Delivery goes global: Programs can be delivered in over 50 languages, enabling a single certification to serve a global audience without the need for separate regional programs.
- The data stays in one place: All data, including enrollment status, scores, and credentials, is maintained within a single system. Administrators can filter live data to address audit requirements without exporting or reconciling information across multiple tools. Intellum's analytics link certification activity to business metrics such as adoption, revenue, and compliance. Integration with CRM or external reporting systems is supported, with connectors and field mappings tailored to specific needs.
Why so many certification programs run on Intellum
A well-designed certification program benefits from consolidation. Using separate tools for exam delivery, proctoring, badging, and record reconciliation introduces risks, such as data mismatches and inconsistent credentialing.
Managing certifications at scale on a single platform eliminates data gaps. Enrollment, delivery, proctoring, issuance, expiration, and reporting are unified within a single record. Proctoring and external badging integrate with this record as needed, allowing certification results to be measured against key business outcomes within the organization's reporting systems.
The clearest evidence that this holds at scale is Meta. Meta runs Meta Blueprint and its certifications on Intellum's platform, issuing millions of certifications globally. Intellum and Meta's certification team have also walked through the approach in two sessions: a certification best-practices webinar and one on how Meta drives business outcomes through certifications for the practitioner's version.
The key takeaway is that the entire credentialing lifecycle can be managed natively, with partner tools added only when needed, not due to platform limitations.
FAQs
What's the difference between a certificate and a certification?
A certificate recognizes that someone completed a program of learning. A certification goes further: a standard-setting process assesses a person's competence against defined criteria, usually through an exam, and the credential is typically time-limited and must be renewed. In Intellum, "credential" is the umbrella term. The same machinery handles both, but a certification adds an assessment, a passing threshold, and an expiration rule that drives renewal.
What does it take to administer a certification program?
Four recurring jobs: enrolling the right learners, delivering the assessment and recording a pass or fail, issuing the credential, and tracking who holds it so you can renew it before it lapses. The design of the program is a one-off effort; administration is the part that repeats for every learner and every renewal cycle.
How is a certification exam delivered and scored at scale?
Intellum delivers exams two ways. Standard assessments are on-demand and score automatically, for lower-stakes certifications. Scheduled assessments run at a set date and time, with pass or fail decided by score, not attendance. High-stakes exams add proctoring through Honorlock for live browser lockdown, or Safe Exam Browser, a native option with no separate account required.
Do certification records need to integrate with other systems, such as a CRM or a reporting tool?
Not for the certification itself to function. Intellum stores enrollment, scores, and credentials natively and can report on them in place. Many organizations do connect that data to a CRM or a central reporting system so certification status sits alongside other business data; the available connectors and field mappings depend on the systems involved.
What is credentialing software?
Credentialing software issues, verifies, tracks, and manages digital credentials — badges and certificates carrying embedded data such as who earned it, what it required, and when it expires, usually with a shareable, verifiable link. It is often bought as a standalone tool; in Intellum, this function is built in, so issuing and managing credentials does not require a separate platform.
Can you use Intellum with Credly or another external badging tool?
Yes. Intellum integrates with Credly for organizations that already use it, so learners can still earn Credly badges. This integration approach is additive. Intellum's native credentialing handles the full issue-to-expiration lifecycle on its own, so an external tool is optional, not required.
How do you track certification renewals across a large group?
Intellum tracks who holds each credential and when it expires as part of enrollment status, the single record behind reporting. Administrators filter live data to see expiring holders and move them back into recertification, individually or in bulk, using the Enrollments List, which also handles renewal notifications to learners automatically.
