The Answer in 60 Seconds

Insurance cover trigger framework distinguishes between two foundational approaches: claims-made cover (responds to claims first made during the policy period regardless of when underlying incident occurred) and occurrence cover (responds to incidents occurring during the policy period regardless of when claim is made). Public Liability cover conventionally operates on occurrence basis. Professional Indemnity, Cyber Liability, and D&O cover conventionally operate on claims-made basis. Commercial implications include retroactive date scope (claims-made), runoff cover scope (claims-made for discontinued operations), continuous cover discipline (claims-made), and considerations on long-tail commercial scope under Limitation Act 1959 framework. Specific cover trigger selection has substantive commercial implications around continuing maintenance discipline, retroactive scope, and framework for discontinued operations.

The Sourced Detail

The cover trigger framework distinguishes between substantively distinct commercial approaches.

Singapore commercial cover operates within the Insurance Act 1966 framework administered by MAS, with industry conventions documented by the General Insurance Association of Singapore (GIA).

The occurrence cover framework

Occurrence cover responds to incidents occurring during the policy period regardless of when claim is subsequently made. Operational scope considerations:

Incident timing: cover triggered by incident occurrence date.

Claim timing flexibility: claim may be made at any subsequent time within applicable Limitation Act 1959 framework.

Long-tail exposure: occurrence policies create long-tail commercial scope where claims may emerge years after policy expiration.

Continuing exposure post-cancellation: occurrence cover continues to respond to incidents occurring during policy period even after policy cancellation.

Runoff implications: occurrence policies do not require runoff cover for discontinued operations because cover continues to respond.

The claims-made cover framework

Claims-made cover responds to claims first made during the policy period regardless of when underlying incident occurred (subject to retroactive date framework). Operational scope considerations:

Claim timing: cover triggered by claim notification date.

Incident timing flexibility: incident may have occurred at any time after retroactive date.

Runoff implications: claims-made cover requires runoff cover for discontinued operations to address claims emerging post-discontinuation for incidents occurring during policy period.

Continuous cover discipline: claims-made cover requires continuous cover discipline; gaps in cover create commercial scope where incidents during gap may not be covered.

The retroactive date analysis

Inception date alignment: retroactive date conventionally aligned with original cover inception date for first-time buyers.

Continuous cover preservation: retroactive date conventionally preserved across renewals to maintain continuous cover scope.

The runoff cover framework

Discontinued operations: runoff cover addresses claims emerging post-discontinuation for incidents during prior policy period.

The cover type assignment patterns

Public Liability — conventionally occurrence basis. Framework for long-tail exposure where personal injury claims may emerge years after incident.

Product Liability extension — typically follows Public Liability occurrence basis.

Professional Indemnity — conventionally claims-made basis. retroactive date framework, continuous cover discipline, runoff cover discipline.

Cyber Liability — conventionally claims-made basis. Framework for retroactive date and continuous cover.

D&O Liability — conventionally claims-made basis. Framework for retroactive date, continuous cover, and operational runoff framework.

EPL (Employment Practices Liability) — typically claims-made basis. Framework for continuous cover discipline.

Property/Fire — typically per occurrence basis (incident-based, although technically distinct from "occurrence" liability framework).

Crime / Fidelity — variable framework. discovery framework (cover triggered by discovery of loss).

WICA / Workers Compensation — typically incident-based.

The Limitation Act framework integration

Limitation Act 1959 framework substantively shapes cover trigger framework operation. Operational scope considerations:

6-year general limitation: Section 6(1)(a) provides 6-year limitation for contract / tort actions.

3-year personal injury limitation: Section 24A provides 3-year limitation for personal injury actions.

15-year long-stop limitation: Section 24B provides 15-year long-stop for negligence actions involving latent damage.

For each Limitation Act framework, considerations on cover trigger framework integration matters substantially. Considerations on long-tail commercial scope matters particularly for occurrence cover scope.

The commercial scenario analysis

Commercial scenarios under each framework:

Long-tail Public Liability scenario — incident occurs during policy period, claim emerges 5 years post-policy. Occurrence cover responds; claims-made cover would not respond (assuming no cover at claim notification date).

Continuous claims-made Professional Indemnity scenario — incident occurs during early policy period, claim emerges during later policy period. Cover responds (assuming continuous cover preserved with appropriate retroactive date).

Discontinued operations claims-made scenario — incident occurs during operational period, claim emerges post-discontinuation. Runoff cover (where procured) addresses; standard cover would not respond.

Insurer change retroactive date scenario — incident occurs under prior insurer, claim emerges under new insurer. Considerations on retroactive date preservation matters substantially.

Mid-term cancellation: commercial scenarios around cancellation scenarios.

The commercial sophistication framework

Specific broker engagement — commercial relationships supporting cover trigger framework discipline.

Common Mistakes / What Goes Wrong

  1. Inadequate cover trigger framework distinction.
  2. No retroactive date preservation.
  3. Inadequate continuous cover discipline.
  4. No runoff cover for discontinued operations.
  5. Inadequate insurer change protocols.
  6. No Limitation Act framework integration.
  7. Inadequate tail / ERP cover during transitions.
  8. No commercial counsel engagement for operational scope.
  9. Inadequate long-tail commercial scope.
  10. No annual review covering cover trigger framework discipline.

What This Means for Your Business

For Singapore SMEs:

Cover trigger framework substantively shapes commercial scope. Public Liability conventionally operates on occurrence basis with long-tail commercial scope. Professional Indemnity, Cyber Liability, D&O, and EPL conventionally operate on claims-made basis requiring continuous cover discipline, retroactive date preservation, and runoff cover discipline. Considerations on cover type assignment patterns, Limitation Act framework integration, and continuous cover discipline matters substantially.

Questions to Ask Your Adviser

  1. For my procured covers, what specific cover trigger framework applies?
  2. For continuous cover discipline (claims-made covers), what operational discipline is appropriate?
  3. For retroactive date preservation across renewals, what operational discipline is appropriate?
  4. For runoff cover (where applicable), what specific provisions apply?
  5. As cover scope evolves, what operational considerations should I plan for?

Related Information

Published 5 May 2026. Source verified 5 May 2026. COVA is an introducer under MAS Notice FAA-N02. We do not recommend insurance products. We provide factual information sourced from primary regulators and route you to a licensed IFA who can match a policy to your specific situation.