Revisioning rewrite jobs

A rewrite job starts from a copy of the canceled policy. In most cases, the rewrite gets a copy of the policy at the cancellation date. When there is a lapse in coverage, the copy comes from the canceled portion.

There are several special different conditions to keep in mind:

  • If a rewrite starts after the cancellation date, it gets a duplicate of the canceled policy as of the start date of the rewrite. In this case, the copy of the policy as of the cancellation date can have multiple slices, such as if the rewrite is out of sequence to other policy changes.
  • If the start date is after the original end date, PolicyCenter duplicates the rewritten policy from the last day of the canceled policy. In this case, there is a single slice. Everything on the rewrite job has the same effective and expiration dates. This is, however, a rare case.

If the start date of a PolicyPeriod moves forward to a later date, PolicyCenter moves the effective date of all objects on the policy graphs forward to that date. All information about the original start date of the PolicyPeriod and its subobjects start date no longer appears as data in the PolicyPeriod graph. This is the intended and defined behavior. However, in some edge cases the result can be difficult to understand and can look strange or incorrect, so keep in mind how it works.

For example, suppose the following sequence occurs:

  • You create personal auto policy, one vehicle, one driver, 9/1/09 through 3/1/10.
  • You change the policy, effective 12/1/09, adding a second vehicle.
  • You start a midterm rewrite, with the effective date initially set to the cancellation date (the default), 11/5/09.
  • You bind this policy as is then in the policy term that resulted. Vehicle 1 has an effective date of 11/5, and vehicle 2 has an effective date of 12/1 (correctly). However, you might expect a one month lapse in coverage, so you change the effective date of the rewrite to 12/5/09, and save the draft.
  • If you bind the policy at this point, on the policy term that results, both vehicle 1 and vehicle 2 have an effective date of 12/5 (correctly).
  • However, you decide there was not supposed to be a lapse in coverage, so you change the effective date of the rewrite back to 11/5. This is unusual but possible. That branch in PolicyCenter no longer has the information about what the PolicyPeriod looked like before 12/5. Thus, PolicyCenter stretches back the PolicyPeriod to make everything that has an effective date of 12/5 have an effective date of 11/5. This results in vehicle 1 and vehicle 2 having an effective date of 11/5, which might seem incorrect but is the defined behavior in this case.