Throughout the policy lifecycle, a policy’s status will change, as will a policy’s revision states. The policy status indicates the current phase of the lifecycle a policy is in, and the revision state indicates the phase of revision a policy is in.
Note: The policy statuses include statuses applied to quotes and/or applications.
Policy statuses indicate the current state of a policy and/or endorsement and appear on each revision. To determine the current status of a policy, access the policy, locate the most recent revision, and view the policy status in the policy header. If the policy status is Unsubmitted, Submitted, or Rejected, the most recent revision is Open but not Committed. This means that the policy and/or endorsement hasn’t been active. The statuses, Unsubmitted, Submitted, and Rejected refer to quotes/applications. Table 1 summarizes BriteCore’s policy statuses and their meanings.
Table 1: Policy statuses and their meanings.
A revision is a legal change made to a policy or amendments made to an existing policy. Another name for revision is endorsement. Revision states inform users about the revision process phase that the existing policy is in. Changes made to a policy are tracked in the Revision History. See View revision history of policies. The revision states in Table 2 indicate whether the revision’s information is in effect.
Table 2: Revision states and their meanings.
- The revision state is Open if the Commit Revision and Delete Revision buttons appear on the policy header, the Edit Revision Date link appears in the Revision section of the policy header, and Pending doesn’t appear in the Revision section of the policy header. This can happen when an application is submitted, approved, and becomes a policy but isn’t committed so the data isn’t in effect.
- The revision state is Pending if the Commit Revision and Delete Revision buttons appear on the policy header, the Edit Revision Date link appears in the Revision section of the policy header, and Pending appears in the Revision section of the policy header. This can happen when you create a new revision on an existing policy and don’t commit or delete the revision. The Pending revision state can also apply to a committed revision if a second revision is created with the same revision date as the committed revision. The committed revision is marked Prior but appears in the Revision History table as Pending until the new revision is committed or deleted.
- The revision state is Committed if the Commit Revision and Delete Revision buttons don’t appear on the policy header and the Edit Revision Date link doesn’t appear in the Revision section of the policy header.
- Revisions with the revision state Archived, are hidden from the policy header; however, archived revisions are noted in the Revision History table.
Note: As indicated in Table 2, data from archived revisions are reportable. However, if an archived revision is later deleted, then all data associated with that revision won’t be reportable.