An effective date is a chronological reference of changes to your lines of business. It serves as a historical record of your policy types and rates over a date range.

Core Concepts

Dates Matter

  • An effective date ties your lines setup and rates to a particular date in time. For example, a January 1st effective date means any policies effective on or after January 1st will reference the setup and rates of that effective date
  • An effective date is locked once its defined date passes. Once locked the effective date setup and rates can no longer be altered. For example, on January 2nd, a January 1st effective date is no longer editable
  • Once an effective date is locked, any changes to your lines setup requires a new effective date dated into the future. For example, if you have a January 1st effective date and need to make changes, your new effective date could be set for July

Policy Referencing

  • Policies reference the most recent past effective date. For example, with a January 1 effective date, all policies will reference that effective date until a new effective date is created
  • A policy references an effective date until it renews


A newly created effective date copies the data from the most recent effective date. In this way, data follows a chronological path. Consider an example where a January 1 effective date exists and a March 1 effective date is created. The March 1 effective date will copy the data from the January 1 effective date. If an October 1 is then added, it will copy the March 1 data rather than the January 1 data.

Work on one future, unlocked effective date at a time.


Once the effective date has come to pass, it can no longer be edited without IWS intervention.

BriteCore Setup

Settings > System Wide > Administrative Alerts

Effective Date Becomes Active

The below email is sent when an effective date is today:

BriteCore Alert: Effective Date Active
Effective Date: MM/DD/YYYY
Description: [Description of effective date as it appears in BriteCore]
This date has now been moved into effect and all policy types defined within will be accessible inside the policies module.
Policy Types List: [link to effective date]


How to Unlock a Locked Effective Date (IWS Only)

  1. Access the client's database
  2. Access effective_dates
  3. Locate the effective date in question
  4. Set effective_dates.overrideLock=1
  5. To relock, change the value to 0


My site is live and issuing policies against an effective date. I need to make changes to my lines of business that require a new lines effective date. Due to an unforeseen circumstance, though, the new effective date must be in the near future, which will overlap with the policy term of active policies in BriteCore. What are my next steps?

  • The picture just below illustrates this case. In the example, you have policies in BriteCore with September effective dates and are now attempting to backdate a new effective date to 8/1
  • Your effective date should not overlap with active policies in BriteCore. That is, if September policies are already active in BriteCore, you should refrain from creating an August effective date. Given this, your next step is to create an effective date at least two weeks after the last policy effective date in the system. For example, if the last effective date of policies is 9/31 then create the new effective date for 10/14. The two-week timeframe is intended to provide time for changes to be made to the new effective date prior to policies renewing onto it


To aid in the understanding of effective dates, review the questions below using the image as a reference.

Understanding the Image

  • For the exercise, today is 9/1/17
  • There are two locked effective dates, 1/1/17, 7/1/17, and one future, in-progress effective date, 1/1/18


  1. Which effective date is the 3/1/17 policy referencing?
  2. An endorsement dated 9/1/17 is performed on the 3/1/17 policy. Will the endorsement reference the 1/1/17 or 7/1/17 effective date?
  3. When the 3/1/17 policy renews on 3/1/18, which effective date will it reference?
  4. Today is 9/1/17 and changes are needed to your lines of business, to which effective date should you make changes?
  5. You mail renewal notices 30 days in advance of a policy effective date. Today is 9/1/17, which means your 10/1/17 policies just renewed. Which lines effective date will the 10/1 policies reference?
  6. Can you delete the 7/1/17 effective date?
  7. The changes that were to be implemented with the 1/1/18 effective date are no longer needed, can you delete the 1/1/18 effective date?
  8. You mail renewal notices 30 days in advance of a policy effective date. By what date will policies start to reference the 1/1/18 effective date?


  1. The 1/1/17 effective date as this is the most recent past effective date in relation to the policy's effective date
  2. The 1/1/17 effective date as a policy references an effective date until it renews
  3. The 1/1/18 effective date as a policy references the most recent past effective date. As such, the policy will skip the 7/1/17 effective date
  4. The 1/1/18 effective date as it is in the future, unlocked, and no policies currently reference it
  5. The 7/1/17 effective date as policies reference the most recent past effective date as they renew
  6. No because today is 9/1/17, which means the 7/1/17 effective date is locked
  7. Yes because no policies are currently referencing that effective date
  8. Policies will begin to reference the 1/1/18 effective date on 12/2/17 as 1/1/18 policies renew in BriteCore on that date


Report unclear or missing documentation.