Some of the terms referenced within the restriction definitions have specific meanings within this context. These are defined as follows to help you understand how Dayforce behaves when you configure restrictions for an election set.
- Subtype: Follows the subtype selection in plan setup, except for medical and dental plans. All subtypes in an election set beginning with the word “Medical” are considered one subtype and all subtypes in an election set beginning with the word “Dental” are considered one subtype, because they relate to enrollment restrictions.
- Remain eligible: An employee or dependent was eligible for current coverage on the day before and earliest effective start date of any new election for the same subtype.
- Drop coverage: Employees or dependents cannot have a new election from the enrollment where they aren't covered for the same subtype.
- For example, an employee is covered under a particular subtype option but the enrollment doesn't include that option or any mutually exclusive option. Dayforce doesn't enforce the restriction if the options in the election set aren't in the same plan option group as the existing option. This is because it's assumed that the existing option continues being effective.
- Newly eligible dependent: Dependents that the employee has indicated as new per the event details page in the current enrollment. Existing, not new, dependents continue being covered if they are already covered.
- New coverage: Where an option provides coverage, but the employee or dependent didn't have coverage with an election of that subtype election effective as of the day before the new election's effective start date.
- Waived options: Dayforce doesn't consider options configured with the Waived Option field in plan setup as coverage, and doesn't show these options if you have set up a “may not drop coverage” restriction for an election set.
| Restriction | Description |
|---|---|
|
May not change to a different plan |
Dayforce doesn't show any options that aren't associated with a plan that is different from the plan association of the employee’s current election within the election set. |
| May not drop coverage for dependents remaining eligible |
Employees cannot submit an enrollment with selections that would result in coverage ending for any dependents who are currently covered and remain eligible for an option of same subtype within the election set. Dayforce doesn't enforce the restriction if the employee selects an option that isn’t in the same mutually exclusive plan option group as the existing option, because it's assumed that the existing option continues being effective. Example: Employee Henry has family coverage with child Ray covered. Henry marries and wants to add a spouse. Henry is eligible for his current Medical Option A, but is also eligible for Medical Option B, however Medical Option B doesn't allow for a child Ray’s age, so Ray isn’t eligible. Henry must enroll in an option that keeps Ray covered for medical. If Ray has been covered but ceases to be eligible on the day prior to Henry making his elections however, Dayforce wouldn't enforce this restriction. |
|
May not drop coverage for the employee if remaining eligible |
Employees cannot elect an option that would result in coverage being ended for themselves if they are currently covered, and remain eligible, for an option of the same subtype within the election set. In addition, Dayforce doesn't show waive options of the same subtype, unless an employee is currently enrolled in that waive option. Dayforce doesn't enforce the restriction if the employee selects an option that isn’t in the same election set as the existing option, because it's assumed that the existing option continues being effective. |
|
May not add coverage for dependents that aren't newly eligible |
Employees cannot submit an enrollment with selections that would result in new coverage of a particular subtype within the election set for dependents who aren't newly eligible. |
|
May not increase contribution |
Employees cannot select a contribution amount above the amount they are currently contributing for that option. If an employee’s current coverage is below the coverage minimum, the employee can increase it to the minimum. |
|
May not increase coverage amount |
Employees cannot select a coverage amount above the amount they currently have for that option if coverage is counted in units or using a multiplier. Dayforce doesn't enforce this restriction for child or dependent options if the option has dependencies. This restriction also doesn’t apply if an employee adds more dependents on a per dependent option, but does apply to the coverage, in units, on that option. If an employee’s current coverage is below the coverage minimum, the employee can increase it to the minimum. |
|
Will be pre-enrolled in previously elected option |
Dayforce doesn't show any option in which an employee isn’t currently enrolled and the employee cannot deselect the current option. Employees can change details of the election including dependents and beneficiaries. This also applies to employees currently not enrolled in an option within the election set; Dayforce doesn't show any options for an election set if employees aren't already enrolled in an option within that election set. |
|
May not remove spouse as beneficiary |
Employees cannot update beneficiary designations for an option where an existing beneficiary has the relationship type marked as “Is Spouse”. This restriction applies to spouses who are primary beneficiaries. In addition, employees cannot make changes to the beneficiary type (for example, changing the type from primary to contingent), nor to the percentage for the primary spouse beneficiary. Important: If any option within a bundle doesn't satisfy the restriction condition, the entire bundle doesn't qualify. |