Skip to main content
Readiness Authority
Category: Policy Structure & Terms

Period of Insurance

Also known as: Policy Period, Coverage Period
Simply put

The period of insurance is the span of time during which an insurance policy is active and cover is in force. It usually runs from a stated start date to a stated end date, but it can end earlier if the policy is cancelled or otherwise terminated. Losses or events that fall outside this window are generally not covered.

Formal definition

The period of insurance is the defined timeframe during which coverage under a policy is valid and enforceable, typically set out by explicit inception and expiry dates in the policy schedule. Cover may terminate before the stated expiry where the policy is cancelled or ended in accordance with its conditions. The concept establishes a temporal boundary on coverage, but it should not be confused with related but distinct mechanisms such as a grace period for late premium payment; in cyber and other claims-made contexts, whether a given loss falls within cover can also depend on separate provisions (for example, the applicable trigger, any retroactive date, or reporting requirements) rather than the period of insurance alone. The precise operation of the period, including any conditions permitting early termination, is subject to the specific policy wording and jurisdiction.

Why it matters

The period of insurance sets the temporal boundary of a policy, and for many lines of cover it is the primary determinant of whether a loss falls inside or outside protection. If an event occurs after the stated expiry date, or after the policy has been cancelled or otherwise terminated in accordance with its conditions, cover is generally unavailable regardless of how well the insured otherwise fits the policy's scope. For risk managers and brokers, keeping track of inception and expiry dates, and ensuring renewals or replacement cover attach without gaps, is therefore a basic but consequential discipline.

In cyber insurance and other claims-made contexts, the period of insurance is necessary but not sufficient to establish coverage. Whether a particular loss is covered can also depend on separate provisions such as the applicable trigger, any retroactive date, and reporting or notification requirements. A loss can arise from conduct or an incident that predates or postdates the period yet still turn on how those other mechanisms operate. Treating the period of insurance as the sole test for coverage is a common source of error, and the interaction between the period and these other provisions should be assessed against the specific policy wording.

The period of insurance should also not be confused with a grace period, which is a separate concept relating to late premium payment rather than the span during which cover is in force. Because a policy can end earlier than its stated expiry where it is cancelled or terminated under its conditions, the practical period of cover may be shorter than the scheduled dates suggest. All of these points are subject to the specific policy wording and the relevant jurisdiction.

Who it's relevant to

Insurance brokers
Brokers must confirm that inception and expiry dates align with client needs and that renewals or replacement policies attach without gaps, since a lapse between periods can leave a client uncovered for events occurring in the interval. They should also flag that early termination provisions can shorten the effective period and that, in claims-made cyber policies, the period alone does not determine whether a loss is covered.
Risk managers
Risk managers rely on the period of insurance to understand the temporal boundary of their organization's cover and to coordinate policy timing across programs. Because cover can end earlier than the scheduled expiry through cancellation or termination, and because coverage in cyber contexts can also depend on triggers, retroactive dates, and reporting requirements, they should assess these mechanisms together rather than treating the period as the sole test.
Underwriters
Underwriters define the period of insurance in the schedule and set the conditions under which cover may terminate early. They must ensure the period wording interacts clearly with other provisions such as triggers, retroactive dates, and reporting requirements, since ambiguity about the temporal boundary of cover can lead to disputes over whether a given loss falls within the policy.
Legal and compliance professionals
When a coverage dispute arises, legal and compliance professionals examine whether a loss or event fell within the period of insurance and whether early termination or cancellation applied. They also distinguish the period from separate concepts such as grace periods for late premium payment, and assess how the period interacts with claims-made mechanics, always against the specific policy wording and applicable jurisdiction.

Inside Period of Insurance

Policy Inception and Expiry Dates
The defined start and end dates during which the cover is operative, subject to the specific wording. Losses or events falling outside these dates are typically not covered unless extended by endorsement or a specific provision.
Relationship to the Trigger Basis
How the period of insurance interacts with the policy's trigger basis matters. Many cyber policies are written on a claims-made basis, meaning the claim must be made (and often notified) during the period of insurance rather than the underlying act occurring within it. This is distinct from an occurrence or losses-discovered basis, and the applicable basis must be read from the specific wording.
Retroactive Date
In many claims-made cyber policies a retroactive date limits cover to acts, errors, or events happening on or after that date, even where the claim itself is made within the period of insurance. The period of insurance and the retroactive date are separate concepts and should not be conflated.
Notification and Discovery Windows
Conditions governing when a claim, circumstance, or incident must be notified relative to the period of insurance. Some policies require notification during the period; others allow notification of circumstances that may give rise to a claim. This is subject to the specific conditions precedent in the wording.
Extended Reporting Period (Run-Off / Tail)
An optional or automatic extension, common on claims-made forms, allowing claims to be reported after expiry for acts occurring during the original period of insurance. It extends the reporting window, not the period during which covered acts can occur.
Interaction with Waiting Periods and Time-Based Provisions
First-party covers such as business interruption often carry a waiting period (a qualifying time before loss is recoverable) that operates within the period of insurance. The waiting period is a coverage condition and is distinct from resilience metrics such as RTO or RPO.

Common questions

Answers to the questions practitioners most commonly ask about Period of Insurance.

Does the period of insurance determine whether a claim is covered, based on when the incident happened?
Not on its own. The period of insurance defines the window of time the policy is in force, but it does not by itself dictate whether a particular incident is covered. Most cyber policies are written on a claims-made basis, meaning coverage typically depends on when a claim is first made against the insured or when a circumstance is notified, rather than solely on when the underlying event occurred. Subject to the specific wording, the interaction of the period of insurance with the retroactive date, any extended reporting provisions, and the policy's notification conditions is what governs coverage. Treating the period of insurance as the sole test of coverage is a common misunderstanding.
Is the period of insurance the same as the retroactive date?
No, they are distinct concepts and should not be conflated. The period of insurance is the forward-looking term during which the policy responds, typically running from an inception date to an expiry date. A retroactive date, where present, sets the earliest point in the past from which triggering acts, errors, or events may originate and still be considered, often in claims-made wordings. The two work together but answer different questions: the period of insurance addresses when the policy is active, while the retroactive date addresses how far back the origin of a matter may reach. The precise effect depends on the policy wording.
How does the period of insurance interact with a business interruption waiting period?
A waiting period is a qualifying threshold that a covered interruption must exceed before first-party business interruption loss begins to accrue; it is not the same as the period of insurance. In many policies, the event triggering the interruption must fall within the period of insurance, but the waiting period then governs when quantifiable loss starts to count. Subject to the specific wording, an interruption that begins near the end of the term may raise questions about how loss extending beyond expiry is treated, so the indemnity period language and the interaction with the policy term should be reviewed carefully.
What happens to a claim if an incident is discovered after the period of insurance ends?
This depends heavily on the policy trigger and any reporting provisions. In claims-made wordings, discovery or notification occurring after expiry may fall outside coverage unless an extended reporting period (sometimes called run-off or a discovery period) applies or the matter was validly notified during the term as a circumstance. Some first-party covers operate on a discovery or occurrence basis with different mechanics. Because outcomes vary by wording, jurisdiction, and any applicable endorsements, insureds should confirm the trigger and notification conditions rather than assume post-expiry discovery is either covered or excluded.
How should an organization manage the transition between two consecutive policy periods to avoid gaps?
Continuity of coverage across renewals typically turns on aligning inception and expiry dates, preserving or carrying forward the retroactive date where applicable, and understanding how each policy's trigger treats matters spanning the two terms. A change of insurer or a lapse can create gaps, particularly under claims-made forms where an unbroken retroactive date matters. Insureds and brokers often review whether prior acts coverage is maintained, whether any circumstances should be notified before expiry, and how notification and reporting conditions differ between the expiring and incoming policies. The specific effect depends on both wordings.
Does the period of insurance affect how sublimits, retentions, or aggregate limits apply?
Generally, limits, sublimits, and aggregates are applied in relation to the period of insurance, so that the aggregate limit represents the maximum payable for covered matters attributable to that term, subject to the specific wording. Retentions may apply per claim or per event within the period. Where matters span more than one period, the wording determines which period's limits and retentions respond, which can be significant for related or continuing events. Because policies allocate these differently, the definitions of period of insurance, aggregate limit, and any interrelated-claims or single-event provisions should be read together.

Common misconceptions

If an incident happens during the period of insurance, any resulting claim is automatically covered whenever it arises.
This assumes an occurrence-based trigger. Many cyber policies are claims-made, so it is typically the making and notification of the claim during the period of insurance that matters, and any retroactive date, exclusions, and conditions precedent still apply. Whether a loss is covered depends on the specific wording.
The period of insurance and the retroactive date are the same thing.
They are separate. The period of insurance sets when the policy is operative, while a retroactive date, where present, limits how far back the covered acts or events can reach. A loss can fall within the period of insurance yet be excluded because it originates before the retroactive date.
Once the policy expires there is no way to claim for events that happened while it was in force.
On claims-made forms, an extended reporting period (tail or run-off) may allow claims for acts occurring during the original period to be reported after expiry. Availability, duration, and cost of such an extension are subject to the specific wording and endorsements, not guaranteed.

Best practices

Read the period of insurance together with the trigger basis (claims-made versus occurrence versus losses-discovered) and any retroactive date, since these jointly determine whether a given loss can attach.
Map notification and discovery conditions precedent to internal incident response processes so that claims or circumstances are reported within the timeframes the wording requires.
When changing insurers or forms, check for gaps between the retroactive date of the new policy and the expiry of the prior one, and consider extended reporting period or run-off cover to avoid uncovered windows.
Distinguish policy time-based provisions such as waiting periods from resilience metrics like RTO and RPO, and confirm how the waiting period interacts with any business interruption sublimit or retention.
Document the exact inception and expiry dates, retroactive date, and any extended reporting terms in the risk register, and review them at each renewal rather than assuming continuity.
Confirm with the broker or underwriter how mid-term endorsements, cancellations, or acquisitions affect the operative period and the treatment of prior acts, since these vary by wording and jurisdiction.
Promotional banner graphic asking if you are ready for PCI DSS 4.0 with a call-to-action to get the guide