Applying changes to future renewals

If a user changes a policy in the current period but a future renewal revision already exists, PolicyCenter displays a special screen. That screen asks the user whether to apply (merge) changes forward to the renewal period.

If you do not apply the changes from the current job to the renewal period, you can apply changes later when you revisit the policy change job. PolicyCenter asks again whether to apply these changes to the renewal period.

If the user says yes, PolicyCenter reapplies the changes to the future renewal branch. However, the behavior is slightly different depending on whether the future renewal contractual period is bound or unbound:

• If the future renewal period is bound, a new job is started in the renewal period to apply the changes. The new job in the renewal period always is a policy change job based on the most recently bound branch in the renewal period. The changes only include the ones you made in the prior period. If multiple jobs in the prior period are bound and the user requests to apply these changes to the renewal period, multiple jobs are created in the renewal branch. The new jobs are independent of each other (some might be bound, some might be withdrawn, as desired).
• If the future renewal period is unbound, changes are made directly to the draft renewal branch. No new job is created to handle this case. If multiple jobs in the current (pre-renewal) period are bound and you request to apply changes to the renewal period, all changes are applied to that same draft renewal branch.