Skip to main content

Launch Assigned and Mandatory Training - Article

Prepare a reliable assignment-led service with clear participant expectations, meaningful deadlines, learning evidence and operational follow-up.
Updated: 16 Nov 2026
8 min read

Summary

Assigned learning gives a defined audience a clear expectation: this training is required, this is when it is due and this is what successful completion means. A reliable service combines accurate audience data, suitable content, meaningful evidence and proportionate follow-up.

Plan the assignment process separately from completion deadlines, access expiration and certification. Test both a new participant and a returning learner before applying a rule or import to a large population.

Use this article to:

  • Choose an assignment route that fits the audience and its source data
  • Separate required completion, learning access and credential validity
  • Prepare understandable participant communication and escalation
  • Pilot automatic and manual assignment safely
  • Operate required learning using evidence and clear exception ownership

Define what is required and why

Begin with the task, obligation or operational risk the learning addresses. Required training may support safe product use, a partner qualification, a customer procedure or an internal policy. The audience is not necessarily an employee population; customers, distributors and other authorized learners may also have required learning.

State the required outcome in language the participant can understand. Explain what they must complete, why it matters, when it is due and whom to contact if their assignment is incorrect or they cannot proceed. Avoid making a mandatory label carry the entire explanation.

Decide what evidence is sufficient. A short information update, an acknowledgement, a scored knowledge check and an instructor-reviewed practical assessment serve different purposes. Record the requirement owner’s decision and align the content, completion and certificate design with it. The platform records evidence; the organization remains responsible for deciding what that evidence means for its requirement.

Prepare the audience before automating assignment

Identify the authoritative data that determines who qualifies: a maintained organizational relationship, role, job function, product category, country or another supported profile attribute. Check which fields are present and reliable for the intended population. A rule cannot correct a business definition that is unclear or data that is missing.

Agree who owns changes when a person moves, joins or leaves the qualifying audience. Membership changes, user status changes and training participation changes are different events. Do not assume that removing an audience attribute automatically removes or cancels every related assignment.

Use Establish Audiences, Ownership, and Access for the foundation and Onboarding Rules for onboarding-rule configuration. Keep a representative excluded person in the pilot so the team verifies both inclusion and the boundary.

Choose the assignment route

RouteUseful situationControl to establish
Manual registration or a supported bulk actionA small cohort, an exception or an administrator-managed launchSelect the correct people and activity, review their current participation and confirm the intended result
User import with supported activity assignmentA prepared population supplied through a controlled spreadsheet processUse the current import template, matching rules and enabled activity column; reconcile results
Onboarding ruleAssignment should follow supported profile conditions and triggersDefine the audience, assigned content, publication and trigger; decide deliberately whether to apply to existing users immediately
Enabled organization-level activity assignmentTraining belongs to a maintained organization relationshipConfirm feature availability, membership source and the relevant assignment behavior
Integration-driven processAn external system owns the qualifying event or populationAgree identity matching, data ownership, timing, error handling and reconciliation with the integration owner

Use one clear ownership model for a particular assignment. Several routes can coexist, but avoid uncontrolled duplication where an import, rule and external integration all attempt to manage the same people without an agreed reconciliation process. Enroll and register participants and Import and Update Users in Bulk own the relevant registration and import details.

Keep the different clocks separate

A required-completion deadline is not the same as the date access ends or a certificate becomes invalid. This distinction affects participant expectations and the action your team should take when something is overdue.

ControlWhat it is forPlanning consequence
Mandatory deadlineThe expected date for completing required trainingChoose the appropriate fixed or relative basis; overdue is a status signal, not a substitute for access control
Activity or Event scheduleThe calendar of a delivered activity or sessionCoordinate the session and any schedule-dependent outcomes with the required learning deadline
Access ExpirationWhen the participant’s learning access should expireDo not unintentionally end access before the participant can meet the requirement
Certificate expirationThe validity period of an earned credentialDecide whether the requirement includes an expiring credential and what must happen before it lapses
Re-certificationA configured new attempt to earn the credential againPlan the renewal window, required evidence, participant access and follow-up separately from the first assignment

For example, a self-paced required activity may be due 30 days after enrollment. That makes the deadline personal to the enrollment date. A scheduled cohort may instead share a fixed date. Neither design by itself defines certificate validity or Access Expiration. Use Mandatory Activities and Deadlines, Access Expiration and Re-certification for the separate controls.

The Overdue label identifies an unmet deadline; it does not by itself close access. Also consider the participant’s ability to cancel a mandatory activity: the required-learning design affects available self-service cancellation. Explain the correct exception route rather than leaving people to guess how to remove an incorrect assignment.

Create the delivery and evidence pattern before bulk assignment

  1. Prepare the Course or other learning material and confirm the requirement owner’s acceptance criteria
  2. Create the representative Training Activity, add its modules and configure the intended completion behavior
  3. Enable and configure Mandatory with the appropriate deadline basis; review schedule and access conditions separately
  4. Create and attach the required certificate only when a credential is part of the intended outcome, using appropriate issuance criteria
  5. Prepare the participant-facing title, description, support route and necessary language versions
  6. Configure the assignment route and related communication in a controlled scope
  7. Pilot the complete journey, inspect the resulting participant records and only then apply it to the intended population

Test the evidence the learner actually produces. A native Course may contain a scored Question Set, an acknowledgement or other tracked elements; an Event requires attendance evidence; an Assignment requires the responsible reviewer’s action. Completion and certificate criteria must reference the intended evidence rather than an unrelated convenient status.

Make communication useful and proportionate

Tell the participant why the training has been assigned, what action to take, how the deadline is calculated and where to get help. Follow-up should help people resolve the reason they have not completed, rather than repeatedly repeat the same demand.

Coordinate standard system emails, deadline reminders and Automated Email Workflows. Decide who needs a reminder, when it becomes useful and which person is responsible for escalation. Managers, partner coordinators or instructors may need a different message from the participant, with the appropriate scope and support action.

Review the relevant message content and recipient configuration in System Email Notification Overview and Email Sending. Use Automated Email Workflows for a reusable automated workflow. Do not assume a successful configuration or a QA test proves production delivery to the intended mailbox; verify the production communication route through the approved process before a large launch.

Pilot a new and a returning learner

A returning learner may already have relevant Course progress, a certificate or an earlier participation record. Test that situation deliberately rather than assuming every assignment begins with an empty learning history. Review the selected attempt and the required renewal design where applicable.

Include a person who qualifies, a person who should not qualify, a person with incomplete profile information and an operating role that must follow up. For automatic rules, exercise the real supported trigger. Saving a rule as a draft does not apply it; publishing and immediate application can have a much broader effect than editing a single user.

Inspect the resulting enrollment, deadline, accessible learning, messages and progress evidence. Correct the pattern before widening the audience. Keep a record of the criteria, test cases, outcome and owner so later changes can be reviewed consistently.

Operate the requirement after launch

Assign an owner to review incomplete and overdue participation at a cadence that fits the requirement. Use the relevant Progress, Learning Performance and Certificates views to distinguish who has access, who has started, who has met the required evidence and who needs a renewal action. Progress, Learning Performance Analytics and Certificates Analytics & Reporting explain the reporting boundaries.

Define an exception process for incorrect assignment, absence, reasonable extensions, inaccessible content and evidence recorded outside the normal route. Keep the approval and reason with the appropriate controlled record. Do not use forced completion merely to make a dashboard look complete; it changes the recorded evidence and should follow an authorized process.

When the requirement, content or target audience changes, assess existing participants as well as future assignments. Re-test the affected rule, deadlines and evidence links before applying a live update at scale.

Verify the required-learning service

Scenario or checkExpected result or evidence
Qualifying and excluded peopleThe intended assignment route includes the right population and respects the boundary
New and returning learnerExisting progress, participation and credential history are interpreted correctly
Deadline and accessThe participant sees the intended deadline and retains the intended ability to complete
Evidence and follow-upRequired learning produces the expected completion or credential result, with appropriate reminders and escalation
Exception and maintenanceThe operating team can resolve a justified exception and assess the effect of a later change

Troubleshooting

ProblemWhat to check
The expected person was not assignedCheck source data, rule publication and trigger, existing participation and the route’s conditions
Too many people were assignedReview the audience logic, optional immediate application and competing assignment sources before applying further changes
The activity is overdue but still accessibleReview Mandatory and Access Expiration separately; overdue is not itself an access lock
Training is complete but the credential is missingInspect the certificate’s actual issuance criteria, selected attempt, relevant schedule and evidence
Messages are repeated or go to the wrong ownerReview standard emails and workflows together, including recipient scope and the person responsible for follow-up

FAQ