The strategic playbook for designing Assignments — choosing between Direct and Automated, applying exclusionary logic, naming for clarity, and avoiding the configuration mistakes that catch most admins.
This guide covers the practical decisions you make when building Assignments. It's the operational companion to the strategic frame in Designing Assignments: Direct vs. Automated.
1. Choose the Right Type of Assignment
Continu offers two Assignment types: Automated and Direct.
Use Automated Assignments when learning should trigger based on an action — completing a course, joining a group, hitting a hire-date milestone. The Automation maintains the audience as users meet (or stop meeting) the criteria.
Use Direct Assignments when you want to manually assign content to specific individuals or teams for a one-off or time-sensitive need.
Examples of when Direct is the right choice:
- Following up on a missed compliance deadline
- Assigning training to a specific person who needs a refresher
- One-time training for a specific event or rollout
Examples of when Automated is the right choice:
- Onboarding new hires automatically on their start date
- Triggering follow-up training after a learner completes a prerequisite
- Recurring annual recertifications
2. Use Smart Segmentation as the Default Audience
For most Assignments — Direct or Automated — Smart Segmentation produces a more maintainable audience than a manually curated user list. Define the audience by attributes (role, department, hire date, tier), and the segment updates itself as users change. See Smart Segmentation.
Reserve manually curated user lists for truly fixed audiences — a specific cohort, a one-off project team, a specific set of users with no attribute-based pattern.
3. Apply Exclusionary Logic for Edge Cases
Exclusion lets you carve users out of an otherwise-matching audience. Common uses:
- Excluding External Users from internal-only assignments
- Excluding users who recently completed similar content
- Excluding overlapping Group members who should get different content
See Using Exclusionary Logic in Assignments.
4. Name Each Assignment Instance Clearly
Default Instance names inherit the content name and produce duplicates in reports. Name each Instance with audience, timing, and program context:
- "Security Awareness Annual Recert — EMEA — Q2 2026"
- "New Hire Onboarding — Sales — January 2026 Cohort"
See What Are Named Assignments.
5. Use Instances for Repeating Content
When the same content goes to multiple audiences or repeats over time, use Instances rather than separate Assignments. Instances share the underlying content but track each delivery separately — giving you per-delivery reporting and the ability to update content once for all deliveries.
See Understanding Assignment Instances.
6. Set Due Dates That Reflect the Program's Reality
A due date that's too aggressive teaches learners that deadlines don't matter (because nobody completes on time). A due date that's too generous lets the program drift.
For recurring programs, set due dates relative to the trigger ("due 30 days after the trigger fires") rather than absolute dates — the program then adapts as new users enter.
7. Test Automated Assignments Against a Small Audience First
Before activating an Automation against your full population, test against a small audience of two or three users. An Automation with the wrong trigger or audience can create thousands of incorrect assignments before anyone notices. Once verified, expand the audience.
8. Configure Notifications With Intent
Default notifications send on every event. Three thoughtful notifications (initial, mid-cycle reminder, due-soon) are more effective than ten frequent ones. Match the channel (email, Slack, Teams) to where your audience actually reads.
See Assignment and Automation Notifications.
9. Use Bulk Editing to Maintain Active Assignments
Bulk Editing handles the post-activation maintenance: extending due dates, removing users, sending reminders. Use it for one-off corrections — if you find yourself running the same bulk edit every cycle, you probably want an Automation that handles the recurring case automatically.
Common Mistakes
Forgetting to activate. The most common cause of "my Assignment isn't working."
Using Direct when Automated would maintain itself. Direct assignments are snapshots. If the audience changes, you'll have to update manually.
Skipping the test audience. Activating an Automation against the real population without testing leads to mass-assignment incidents.
Generic Instance names. "Security Training Q2" appearing five times in reports tells you nothing about which delivery you're looking at.
Notification overload. Daily reminders teach learners to ignore Continu notifications. Use frequency sparingly.
See Also
- Designing Assignments: Direct vs. Automated — strategic frame.
- Automation Design Best Practices — design principles for Automations.
- Creating a Direct Assignment — Direct flow.
- Creating an Automated Assignment — Automated flow.
- Assignments: FAQ — common questions.
Pick the right type, use Smart Segmentation, apply exclusions for edge cases, name Instances clearly, test before scaling, configure notifications with intent.