Setup Considerations for Temporal Life Events

Here are the main things to consider before you set up temporal life events.

Decision to Consider	Recommendation
Do you want to use the delivered temporal life events or create your own?	Create your own if you want to control triggering at a more granular level than at which the delivered events provide. For example, to combine age change, location, and becoming part time.
Do you want to use temporal detection rules?	If you want to control some, or all, temporal life events, such as the suppression of automatic detection of specific temporal event or suppression of detection while the application processes a specific life event, use temporal detection rules. As a best practice, leave the detection rule blank. At the very least, use the Do not detect past temporal events rule. Otherwise, the participation processes will detect all your temporal life events, all the time.
Where do you want the temporal life event to be effective?	Overall, you set up temporal life events at the highest level. For example, at the plan level, not the option level, if you expect an employee to make changes to their elections.
At what level do you want to track ineligible people?	We recommend that you don’t necessarily set it at the highest level. That's because it can result in performance issues as the process needs to work out new electable choice at all levels. Instead, we recommend that you set it at a level where the plans are effective.
Do you want to create variable profiles?	You would create a variable rate profile where the variability is controlled by age. For example, the coverage of 2x salary up to 64 years of age, thereafter reduce by 60%. You can use temporal life events to determine if a person is eligible for something. For example, the person is eligible for benefits after they’ve worked in the organization for 90 days. In such cases, you can create a regular eligibility profile instead and include the appropriate derived factors.