LTD Core and Buy-up set up, if Core is auto-enroll at 3+ years

Benefits

Hello!

A bit lengthy post, looking for thoughts on how to improve our LTD setup. I think I've been thinking too hard, and community hasn't been too helpful.

We currently have 4 LTD Plans;

  1. LTD <3 Core - optional- Coverage is 50% of monthly salary, cap of $5K
  2. LTD <3 Buy-up - optional - Coverage is 60% of monthly salary, cap of 7.5K
  3. LTD 3+ Core - auto enrolled at 3 years of service - Coverage is 50% of monthly salary, cap of $5K
  4. LTD 3+ Buy-up - since everyone gets the core 50% coverage, this was set up with coverage 10% of monthly salary, cap of $2.5K

The <3 plans are fine, no issues, no fixing needed.

The 3+ plans are a bit off. The 10% of Coverage calculates out wrong for those over 3 years. For example, say you make $130,000 and 3+ YoS. You're auto enrolled in the Core, and capped at $5K coverage, then the 10% buy-up gives you $1,083 of additional coverage. BUT, 60% of your monthly salary is $6,500, which is what calculates out for our <3 buy-up plan.

The easy solution is to simply have the LTD 3+ Buy-up calc as 60% of monthly salary, but then the benefits show a bit wonky on the profile as the employee has the 50% core and the 60% buy-up. The HR team dislikes that. I'm also unsure of integration impacts of this approach.

My other thought is a complete re-work.

Create Benefit Coverage types of LTD <3 and LTD 3+.

For the LTD 3<, it would be set up with "Only one election" and not other config. Fairly straightforward.

For the LTD 3+, it would be set up with "Only one election" AND "Must elect coverage". Then, via Benefit Election Defaults, set the LTD 3+ Core as priority 1 and set up enrollment event rules to default to 'Default to Current Elections, Priority Coverage or Waive'. Putting the 3+ core plan as auto enroll here does NOT work has an error hits the user when trying to elect the buy-up plan, as the auto enroll is enforcing the 3+ core election, hence the priority coverage usage.

Any thoughts? Am I being a dummy and missing something?

Posted Apr 24, 2026, 8:28 PM UTC

03
Loading comments…