Starter · Part of Training and Coaching
Duplicate-enrolment guard
The system blocks accidental re-assignment of an active plan to the same agent, so progress and history never fork.
For the operator
When someone tries to assign a plan an agent is already working, the system stops it instead of silently creating a second copy. A database-level guard allows exactly one active assignment of a plan per agent, so there is never a question of which enrolment holds the real progress. Completed and cancelled assignments do not block a legitimate re-assignment later, so refreshers and re-takes still work.
Business impact
Forked progress is a quiet data-integrity problem that surfaces at the worst time, when a client audits training records. Enforcing one active enrolment at the data layer keeps completion history clean and reportable, and the bulk-assign tools supervisors lean on during a ramp cannot accidentally double-enrol a cohort.