Policy Periods and Policy-Year Experience

Introduction

Insurance records can be grouped by several different dates, and the choice affects which policies appear together in an experience summary. A policy effective late in one calendar year may provide coverage mostly in the next calendar year, while its premium record may be entered on yet another date. Policy-year experience groups policies by when their coverage begins.

This tutorial defines the policy period and the policy-year grouping convention, then applies that convention to policy-level premium amounts. The central task is to identify each policy’s effective date and consistently assign the policy to the correct group. This is aligned with the CAS Exam 5 (Basic Ratemaking and Estimated Claim Liabilities) syllabus.

Policy Period and Policy-Year Group Are Different

A policy period describes one contract’s coverage interval. For example, a hypothetical annual policy effective July 1, 2025, with coverage through June 30, 2026, has a policy period spanning portions of two calendar years. The policy’s effective date is July 1, 2025; its expiration date is June 30, 2026.

A policy-year group, in contrast, collects multiple policies using a common inception-date rule. With calendar policy years, all policies effective from January 1 through December 31, 2025, belong to policy year 2025. Thus, the July 1 policy belongs to policy year 2025 even though its policy period extends into 2026. A policy-year label identifies the inception cohort; it does not assert that every policy in that cohort starts or ends on January 1 or December 31.

For precision, treat an effective date as included and the next anniversary or expiration boundary as excluded when describing a coverage interval. For instance, a policy stated to run from January 1, 2025, to January 1, 2026, covers the interval beginning January 1, 2025, and ending just before January 1, 2026. This convention avoids counting the boundary instant in both adjoining intervals. The contract’s actual wording governs when it specifies a different convention.

Assigning Policies and Premium by Effective Date

Let \(e_j\) be the effective date of policy \(j\), and let \(p_j\) be the policy-level premium amount being analyzed. Under calendar policy-year grouping, policy \(j\) belongs to year \(y\) if its effective date falls on or after January 1 of year \(y\) and before January 1 of year \(y+1\). The group premium is the sum of the premium amounts for policies assigned to that year, provided the analysis specifies that those policy-level amounts are the premium basis.

This definition uses effective dates, not the dates on which a policy was quoted, issued, entered into a system, billed, or paid for. Those dates may be useful for other questions, but they are not substitutes for the policy effective date in this grouping rule. The premium calculation also needs a clearly specified basis. Here, \(p_j\) means the stated policy-level premium amount to be grouped; assigning it to a policy year is a grouping operation, not a claim about when accounting recognizes revenue or cash.

A different analysis may specify a non-calendar policy-year interval, such as a 12-month period beginning on a chosen date. In that case, use the stated interval’s boundaries rather than silently applying calendar-year boundaries. Whatever interval is used, state it explicitly and apply the same effective-date rule to every policy.

Why Each Policy Is Counted Once

The grouping works because the policy-year intervals form a partition of the effective-date timeline: they do not overlap, and together they cover all dates. Therefore every policy effective date is in exactly one interval. To see the effect on premium totals, define an indicator that equals 1 when policy \(j\) belongs to year \(y\), and 0 otherwise. Summing policy premiums within each year gives:

For any one policy \(j\), the sum of its membership indicators across all policy years is 1: it belongs to one group, and only one. Consequently, summing the group premiums across all years returns the sum of the underlying policy premiums:

This identity is a practical reconciliation check. If the total premium assigned across policy years does not equal the total premium for the policies being grouped, a policy may have been omitted, counted more than once, or assigned using an inconsistent date rule.

Coverage Can Extend Beyond the Inception Year

A policy’s premium is not divided between policy-year groups merely because its coverage period crosses a calendar boundary. Under the stated policy-year convention, the whole policy is first assigned by its effective date. How a premium amount is recognized or distributed in financial reporting is a separate question; this grouping alone does not determine that accounting treatment.

Effective Date Versus Record Date

The date a premium or policy record is entered can differ from the effective date. For policy-year experience, use the effective date for membership in the group. This preserves the meaning of the grouping: it describes cohorts of policies beginning coverage in a defined interval. Before calculating, confirm that the data field labeled “date” is actually the policy effective date rather than an issue, entry, billing, or payment date.

Common Errors and a Practical Procedure

Boundary dates and overlapping timelines make policy-year classification easy to misread. A reliable procedure is to write down the grouping interval, identify the effective date for each policy, assign each policy exactly once, and then total the specified premium amounts. If the result is intended to describe a policy-year cohort, avoid substituting another date merely because it is easier to retrieve.

• Using the policy expiration date. A policy effective December 31, 2025, belongs to policy year 2025 even if it expires in 2026.
• Splitting a policy because its term crosses a year-end. Do not divide its full stated premium across policy years unless the requested measure explicitly calls for an allocation rather than policy-year grouping.
• Putting January 1 in the prior year. Under calendar-year intervals, January 1 is the first date of its calendar year, not the last date of the preceding year.
• Using an entry or payment date. These dates can differ from the effective date and do not determine policy-year membership under this convention.
• Assuming every policy is a 12-month contract. Term length affects the policy period, but it does not change assignment by effective date unless a different grouping rule is specified.