Designing Assignments: Direct vs. Automated
Follow

May 10, 2026 14:43

How to choose between manual and rule-driven assignment for partner enablement, customer education, channel certification, and any program where learning needs to land at the right time.

Why Assignments Exist

Content sitting in your library is potential, not learning.

A learner does not see content because it exists. They see it because someone — or some rule — said this content, for this learner, by this date.

That decision is an assignment.

An assignment is the connection point between a user and a piece of content. It carries intent (this is what they should learn), urgency (by when), and a state machine that lets you track whether the learning actually happened.

Without an assignment, even your best content goes unread by the people who needed it most.

The question is never "should we have assignments." The question is "how should this assignment get created — by a human, or by a rule?"

That choice is what this guide is about.

What an Assignment Actually Is

In Continu, an assignment is a learning object with four defining attributes:

A learner. The user who should learn the content.
A piece of content. The video, article, Track, Journey, file, SCORM package, or external link they should engage with.
A due date. When the learning should be complete.
A state. Where the learner is in the process — Not Started, In Progress, Completed, Expired, or Removed.

Every assignment in Continu has all four attributes, regardless of whether it was created by an admin clicking a button or by an automation firing on a trigger. The object is the same. The path to creation is what differs.

The Two Modes: Direct and Automated

Continu offers two ways to create an assignment.

Direct assignment. An admin selects specific learners (or a smart segment in a single point-in-time slice) and pushes a piece of content to them. One action, one cohort, one rollout. The assignment is created, and the admin moves on.

Automated assignment. A rule sits in the background, watches for a trigger, and creates the assignment when the conditions are met. A new partner is activated. A customer signs a contract. A certification expires. A hire date passes. The rule fires, the assignment lands, no admin had to be there.

The output is the same — an assignment object connecting a learner to content, with a due date and a state. The difference is operational. Direct is a one-time push. Automated is a sustained system.

Most program design failures come from picking the wrong mode for the job.

When to Use Direct Assignment

Direct assignment is the right call when:

The audience is fixed and known. A specific list of partners attending a custom kickoff. A handful of customer admins from one account. A targeted group of channel reps for a pilot.
The push is one-time. A product update everyone needs to read once. A regulatory bulletin. A specific training tied to a single event.
The content is bespoke. Custom material built for a single audience that won't generalize.
Speed matters more than scale. You need it out today, the rule could be designed later.
You want full control over the moment. No surprises, no retroactive triggers — just the people you chose, when you chose them.

The strength of direct assignment is its precision. The cost is that it doesn't repeat. New people who join the population after the push will not get the assignment unless someone re-runs it.

When to Use Automated Assignment

Automated assignment is the right call when:

The audience changes over time. Partners activate weekly. Customers sign monthly. Hires arrive on rolling schedules. New people should get the program as they qualify, not when an admin remembers.
The program is sustained, not bounded. Onboarding, compliance, certification, recurring capability — anything that should keep running for years without manual touch.
The trigger is a real event. A partner is activated. A role changes. A certification expires. A contract renews. The platform sees these as data changes; the automation responds in real time.
Consistency matters across cohorts. Every new hire should get the same onboarding. Every newly certified partner should get the same advanced track. Every renewal should get the same playbook. Automation guarantees the consistency.
You want governance you can audit. The rule is the documentation. Anyone can read it and know what gets assigned, to whom, under what conditions.

The strength of automation is leverage. One well-designed automation serves a population that grows and changes for years. The cost is that misconfigured automations create noise — fast — at scale.

The strategic question: is this a one-time push, or a sustained program? If you cannot answer in a sentence, stop and decide before you build.

Assignment Patterns You Will Reach For Most

Across hundreds of programs, the same assignment patterns show up over and over. Get fluent in them and program design becomes faster.

One-time compliance rollout. A specific regulation or policy has changed. Every employee, every partner, or every customer admin in scope needs to acknowledge it. Use direct assignment to a smart segment, with a hard due date. After the rollout, retire the assignment.

Recurring compliance. Annual data privacy training. Quarterly security awareness. Yearly anti-harassment. The audience is everyone in scope, and the program runs forever. Use automated assignment with a recurring trigger (annually, quarterly, on certification expiry).

Onboarding programs. Every new partner, customer, or employee should get the same starter program. The audience changes constantly — new people join all the time. Use automated assignment with a "User Added" or equivalent trigger, scoped by smart segment to the right audience.

Role-based capability paths. When someone moves into a new role — a partner becomes a Tier 1, a customer admin gets promoted, an employee transfers departments — they should get the right learning for the new role. Use automated assignment with a "User Updated" trigger that fires on attribute change.

Campaign-style learning. A product launch, a new feature rollout, a quarterly enablement push. Time-bound, audience-specific, high-stakes. Use direct assignment for the launch cohort, then optionally pair with automation that catches anyone who joins the audience post-launch.

Certification renewal sequences. A partner's certification is expiring in 30 days. Send the renewal track. If they don't complete in 14 days, send a reminder. If they don't complete in 7 days, escalate. Use automated assignment with date-based triggers tied to certification expiry attributes.

Cohort-based program enrollment. A specific group of partners enters a 90-day onboarding cohort. They move through together. Use direct assignment for the initial cohort, and use the cohort smart segment to drive any follow-on assignments along the journey.

Mixed-mode programs. Most mature programs use both. The launch is direct. The ongoing flow is automated. The two modes complement each other — direct for the burst, automated for the steady state.

Assignment States Explained

Every assignment moves through a defined set of states. State drives reporting. State drives notifications. State drives the entire learner experience.

Not Started. The assignment exists. The learner has not yet opened the content.
In Progress. The learner has started but not finished. For multi-part content (Tracks, Journeys), the learner is somewhere in the middle.
Completed. The learner has met the completion criteria — watched the video to the end, passed the assessment, marked the article as read, finished every step in the Track.
Expired. The due date passed without completion. The assignment remains visible but is now overdue. Reporting treats Expired differently from Not Started — they tell different program stories.
Removed. The assignment was rescinded — by an admin, by the learner being removed from the segment, or by an automation rule change. The assignment no longer counts toward the learner's plate or the program's metrics.

State changes drive everything downstream. Reports filter by state. Notifications fire on state transitions. Manager dashboards roll up state. Get the states right and the platform tells the truth. Misunderstand the states and every report misleads.

The strategic question: when an assignment goes Expired, what should happen? Auto-reassignment? Manager notification? Removal? Decide intentionally — the platform does not pick a default for you.

Assignments in the Continu Architecture

Assignments are not a standalone object. They are the meeting point of every other piece of the platform.

Smart Segmentation determines who. A direct assignment is scoped by a segment at the moment of creation. An automated assignment is scoped by a segment that updates continuously. The segmentation rule is what makes the assignment go to the right person.

Automations determine when. A trigger fires, the rule evaluates, and the assignment lands. The automation is what turns an event in the world into a learning intent on the right person's plate at the right moment.

Content is what gets assigned. The same content can be assigned to many learners through many programs. One product training video can serve customer onboarding, partner enablement, and channel certification — each with its own assignment, its own audience, its own due date.

Tracks place assignments in a journey. A single assignment is a moment. A Track is a sequence. When a learner is assigned a Track, they are assigned a series of moments — and the Track manages the order, prerequisites, and progression.

Reporting is a read on assignment state. Completion rates, overdue rates, time-to-completion — every metric a learning leader cares about is derived from the state of assignments across a population.

Notifications fire on state transitions. New assignment notifications, due-date reminders, overdue escalations, completion confirmations — all driven by assignment state moving from one value to the next.

A well-designed assignment is a smart segment + an automation rule (or a deliberate direct push) + a Track or content piece + a due date that respects the content's scope + a clear notification cadence + a clean state machine. The platform handles each piece. Your job is to design the connections.

Best Practices

Principles worth internalizing for every assignment program:

Build segmentation before assignments. An assignment is only as good as the population it targets. If your segment is wrong, every assignment misfires. Get the segment right, then build the assignment.

Match the due date to the content scope. A 5-minute video does not need a 30-day due date. A 4-hour Track does not deserve a 24-hour deadline. Mismatched due dates teach learners that deadlines don't mean anything.

Test before you scale. Run every automated assignment against a controlled segment of two or three test users first. Continu will happily fire ten thousand assignments to the wrong audience if you let it.

Use direct for bursts, automated for sustained programs. This single distinction saves more program redesigns than any other rule.

Avoid stacking overlapping assignments. If a learner is in three segments that all assign the same compliance training, they may receive three duplicate assignments. Design segments to be mutually exclusive when the underlying assignment is the same.

Use clear naming conventions. "Onboarding — Tier 2 Partners — North America — v3" tells future-you everything they need to know. "Test 2" does not.

Version, don't overwrite. When you change the conditions of an active automated assignment, version it. Compare populations before retiring the old version.

Anti-Patterns to Avoid

The mistakes we see most often:

Hand-assigning a recurring program. Manually pushing the same compliance track to new hires every Monday morning is automation waiting to happen. The cost of the rule is one-time. The cost of doing it manually is forever.
Automating a one-time push. Building a complex rule for a single launch is overkill. It also creates rules that fire unexpectedly later when conditions accidentally re-match. Direct assignment is fine for one-offs.
No due date, or unrealistic due dates. Without a due date, the assignment never goes Expired and never escalates. With a too-tight due date, every learner shows up as overdue and the program looks broken.
Assigning content that isn't finalized. Once an assignment is created, the learner sees the content. If the content is still in draft, the learner is your QA tester. Don't.
Mixing direct and automated for the same program without intent. Either is fine. Both at once is fine — for a deliberate hybrid pattern. The problem is when an admin direct-assigns a program that an automation also creates, and the same learner gets duplicate assignments.

External Audience Patterns

External audiences are where assignment design earns its keep — because the audience is large, changing, and not in your direct control.

Partner activation. Use automated assignment with a "User Added" trigger that fires the moment a partner contact is activated in your PRM. The assignment lands the same day the partner is ready to start. Pair with a Smart Segmentation rule by tier and region for personalization.

Customer onboarding. Use automated assignment scoped to "customers in onboarding" — a smart segment that includes any customer admin within their first 90 days. The Track covers product fundamentals, key admin actions, and a kickoff workshop. Renewal customers don't see this program; only new ones do.

Channel certification renewal. Use automated assignment with a date-based trigger tied to certification expiry. 60 days out, send the renewal track. 30 days out, send a reminder. 7 days out, send an escalation to both the partner and the channel manager.

Custom partner programs. When a strategic partner needs bespoke enablement, use direct assignment. The audience is named, the content is custom, and automation would be overkill. Document the rollout so the next admin can find it.

Customer enterprise rollouts. Use direct assignment for the initial cohort of admins at a large customer. Pair with an automated rule that catches new admins added to the customer's account post-launch — so the program self-extends as the customer scales internally.

A note on data hygiene: every external assignment program is downstream of your PRM, CRM, or partner portal. Test segmentation against the actual data. Audit periodically. The cleaner the source data, the cleaner the assignments.

Internal Audience Patterns

Internal assignments are simpler operationally because the HRIS is usually a single source of truth.

New hire onboarding — automated, fires on hire date, scoped by department or role.
Manager training — automated, fires when an employee gets a direct report for the first time.
Compliance renewals — automated, fires on certification expiry or annual recurrence.
Special projects — direct, named individuals, one-time.
Reorg-driven retraining — automated, fires on department or role change.

Internal assignment design is more forgiving than external because the data is cleaner. Spend less time on defense, more on design.

Known Behaviors and Limits

A few things worth knowing in advance:

Assignments persist when content is updated. If you assign a Track and then edit the Track, learners with In Progress assignments may see the updated content mid-stream. For high-stakes content, version the Track and reassign.
Bulk assignments may take time to process. A direct assignment to 10,000 learners doesn't materialize instantly. Plan rollouts accordingly.
An assignment created by automation can be removed manually. When an admin removes a single assignment, the automation does not re-create it unless the user re-enters the segment. Know this before debugging "why is this person still missing the program."

Designing Assignments: Direct vs. Automated Follow