Training Rules
Training Rules
Training rules control who can enroll in a training session and when attendance can be recorded.
They are evaluated in two separate stages:
- Enrollment Rules are checked when a user registers for a session
- Attendance Rules are checked when a user is marked present or checked in
This separation lets facilities apply one policy for registration and another for attendance verification.
Rule Scope and Resolution
Training rules can be applied at three levels:
- Global Training Rule Set
- Training
- Training Session
Rules are resolved in that order. The global rule set establishes the baseline, training-level rules refine behavior for a specific qualification, and session-level rules handle one-off delivery requirements.
If the same rule exists at multiple levels, the narrower scope takes precedence.
Recommended Pattern
Use the Global Training Rule Set for facility-wide defaults, Training rules for qualification-specific policy, and Session rules only for exceptions tied to a specific delivery instance.
Enrollment Rules
Enrollment rules determine whether a user is allowed to register for a training session.
Enrollment Rules Summary
| Rule | Parameters |
|---|---|
| Enforce Prerequisites | — |
| Max Enrollments | maximum |
| No Concurrent Enrollments | — |
| No Show Limit | limit |
| Session Is Not Async | — |
| Session Is Open | — |
| Training Horizon | interval |
Enforce Prerequisites
Parameters: none
Requires the user to complete all prerequisite trainings before registering for the session.
Use this when a training should only be available after foundational qualifications have already been completed.
Example:
Advanced Laser Operation
Prerequisite: Laser SafetyA user without a valid Laser Safety training record cannot register for Advanced Laser Operation.
Max Enrollments
Parameters: maximum
Limits how many confirmed training enrollments a user may hold at one time.
This counts enrollments in the Confirmed state.
Example:
maximum = 3A user who already has three confirmed enrollments cannot register for another session until one of those enrollments is completed, cancelled, or otherwise leaves the confirmed state.
No Concurrent Enrollments
Parameters: none
Prevents a user from holding overlapping training enrollments.
This rule checks for other enrollments in the Confirmed or Waitlisted state whose session times overlap the session being requested.
Use this when users should not register for multiple sessions that run at the same time.
No Show Limit
Parameters: limit
Blocks enrollment when a user has reached a configured number of No Show outcomes.
Example:
limit = 2After two no-shows, the user cannot register for additional sessions until staff review the situation or the rule is adjusted.
Administrative Recovery
If staff want to allow the user to register again, they can update a previous enrollment from No Show to Excused. This reduces the user’s counted no-show total for the rule.
Session Is Not Async
Parameters: none
Prevents normal enrollment into sessions whose delivery mode is Async.
Use this when asynchronous completion should be handled through a different workflow than live session registration.
Session Is Open
Parameters: none
Allows enrollment only when the session state is Open.
This prevents registration into sessions that have been closed, cancelled, or completed.
Training Horizon
Parameters: interval
Limits how far in advance a user may enroll in a training session.
Example:
interval = 60 daysWith this rule, users may register only for sessions that start within the next 60 days.
Attendance Rules
Attendance rules control when a participant may be marked present or checked in.
Attendance Rules Summary
| Rule | Parameters |
|---|---|
| Check In Window | startBuffer, endBuffer |
Check In Window
Parameters: startBuffer, endBuffer
Restricts when attendance may be recorded relative to the scheduled session start time.
startBufferopens attendance before the scheduled start timeendBufferkeeps attendance open after the scheduled start time
If neither buffer is set, attendance is only valid at the session start time.
Example:
startBuffer = 15 minutes
endBuffer = 30 minutesWith this configuration, the participant can be checked in starting 15 minutes before the session begins and up to 30 minutes after the start time.
How Enrollment and Attendance Work Together
Enrollment rules and attendance rules are evaluated at different points in the session lifecycle.
Typical flow:
User registers -> Enrollment rules are checked
User arrives -> Attendance rules are checked
Session completes -> Training record may be generatedThis allows you to:
- block registration until prerequisites are complete
- prevent overly early bookings
- enforce check-in timing separately from registration timing
- support both scheduled and controlled attendance workflows