How to File a Notice of Circumstance Under a Claims-Made Policy: D&O, PI, Cyber, and EPL Mechanics for Singapore SMEs

A Notice of Circumstance (NoC) is the most under-used and most consequential procedural mechanism in Singapore SME commercial insurance. It is the procedural device that converts a known potential claim into a deemed claim for cover purposes — locking in indemnity under the current policy even if the actual claim arrives years later, after the policy has lapsed, after the SME has switched insurers, or after the cover has been cancelled outright.

Filed correctly, an NoC saves SMEs hundreds of thousands of dollars in uninsured tail liability. Filed incorrectly — or not filed at all — it produces the most common claim denial pattern on D&O, professional indemnity, employment practices liability, and cyber claims-made wordings: "the claim was first made after the policy period expired, and no notice of circumstances was given during the policy period."

This article walks through the NoC mechanics in Singapore. It covers what counts as a notifiable circumstance, the wording triggers that activate the NoC right, the procedural steps to file, the strategic considerations on timing, and the common errors that destroy the cover. It is built for SMEs carrying any claims-made cover — D&O, PI, EPL, cyber, management liability, technology errors and omissions, media liability — and for the licensed advisers handling those programmes. COVA is registered with the Monetary Authority of Singapore as an introducer under Notice FAA-N02 and is not permitted to advise on, recommend, or arrange any insurance product. The workflow described here is the workflow you run with a licensed adviser, who confirms the wording trigger and submits the NoC to the insurer.

The Claims-Made Architecture

A claims-made policy responds to claims first made against the insured during the policy period, regardless of when the underlying wrongful act, error, or omission occurred (subject to any retroactive date). This is the structural difference from an occurrence-based policy, which responds to occurrences during the policy period regardless of when the claim is made.

Three implications follow.

First, the date that matters is the date the claim is made, not the date of the underlying event. A wrongful act in 2022 that produces a claim in 2026 is covered by the 2026 policy (if the retroactive date is 2022 or earlier), not the 2022 policy.

Second, if the policy lapses, the cover ends. A claim notified after the policy expires is uncovered — even if the underlying wrongful act occurred during the period of cover.

Third, the claims-made structure creates a procedural escape valve. The wording typically provides that a "notification of circumstances likely to give rise to a claim" given during the policy period is "deemed" to be a claim made during that period. The deemed claim mechanism locks in cover under the current policy even though the actual claim has not yet arrived.

The NoC is the procedural device that operates the deemed claim mechanism.

What Counts as a Notifiable Circumstance

The notifiable circumstance is defined in the policy wording. The wording varies across insurers and across product lines, but the standard formulations cluster around three patterns.

Pattern 1: Broad "Likely to Give Rise"

The most common Singapore SME formulation. The insured is entitled (or required) to notify circumstances that "may" or "are likely to" give rise to a claim. The threshold is awareness of facts that could form the basis of a claim — not certainty that a claim will be made.

Examples of notifiable circumstances under the broad pattern:

A customer complaint alleging professional negligence (PI).
An employee grievance letter alleging discrimination, harassment, or wrongful termination (EPL).
A regulator's letter of enquiry or notification of investigation (D&O).
A cyber incident with potential data exfiltration but no confirmed third-party claim yet (cyber).
An audit-committee question to a director about a financial-reporting matter (D&O).
A near-miss workplace incident where the injured party has retained counsel (PL / WICA-adjacent).
A pre-litigation demand letter from a counterparty (multiple lines).
A subpoena, search warrant, or production order served on the company or a director (D&O / regulatory).

Pattern 2: Narrower "Specific Wrongful Act Identified"

Some Singapore wordings narrow the trigger. The insured must notify specific facts: the identity of the potential claimant, the nature of the alleged wrongful act, the date of the wrongful act, the potential damages, and the basis for the insured's belief that a claim may be made.

This narrower formulation makes early notification harder — the insured must have enough information to particularise — and creates a corresponding gap if the insured is aware of vague facts but cannot yet identify the specific claimant or quantum.

Pattern 3: Mandatory Notification within Defined Window

Some wordings impose a strict reporting obligation: the insured must notify any circumstance that comes to its attention within a defined window (e.g., 30 days from awareness, or "as soon as reasonably practicable"). Failure to notify is a breach of a condition precedent and can void cover for the underlying claim.

The mandatory pattern is most common on D&O and PI wordings. EPL and cyber wordings tend to use the permissive ("may notify") formulation, but the strategic case for notification is often the same.

The Wording Trigger: Read the Specific Policy

The pre-NoC step is to pull the specific policy wording and identify the notification clause. The clause typically sits in the "Conditions" or "General Conditions" section. Common headings: "Notice of Claim or Circumstance," "Notification," "Conditions Precedent," "Reporting of Claims."

Read the clause for:

The notification trigger (broad "likely to give rise" vs narrower "specific wrongful act").
The notification deadline ("as soon as reasonably practicable," "within 30 days," "within 60 days," "during the policy period").
The notification recipient (typically the insurer's claims department; sometimes a specific email or postal address).
The notification content (what facts must be included).
The deeming clause that converts an NoC into a deemed claim under the current policy.
Any consequences of failure to notify (typically loss of cover for the underlying claim).

The wording is the controlling document. Generic descriptions of "the standard NoC procedure" mislead more often than they help, because the SME's specific policy is the only one that governs.

The Strategic Decision: Notify Now, or Wait

Once a circumstance is identified that is potentially notifiable, the SME faces a strategic decision. Notify now and lock in current-policy cover, accepting that the notification will create a claim history that affects renewal pricing? Or wait, on the basis that the circumstance may not develop into a claim?

The strategic considerations:

Arguments for notifying now:

The current policy will respond to a deemed claim. The future policy may not — either because the current insurer is the better risk for the underlying wrongful act, or because the future policy may have changed wording, narrower retroactive coverage, or fresh exclusions.
Notification preserves cover against the worst-case scenario where the circumstance develops into a claim after the policy lapses.
Where the wording is mandatory ("must notify within 30 days"), failure to notify is a breach of condition precedent and risks the cover for the underlying claim.
Where the SME is approaching a renewal, switch of insurer, cancellation, or M&A event, the window to notify under the current policy is narrowing. Notification before the window closes is strategically critical.
Where the circumstance involves a regulator (PDPC, MAS, MOM, ACRA, IRAS, CAD), the regulatory exposure is rising and the cover for defence costs is most valuable in the early phase before the regulator's position crystallises.

Arguments for waiting:

The notification creates a claim history that affects renewal pricing. An adverse loss ratio can drive premium up materially or, in extremis, drive the insurer to non-renew.
Some circumstances genuinely do not develop into claims. The customer complaint is withdrawn. The employee grievance is resolved internally. The regulator's enquiry is closed without action.
The notification process is administrative work and can be a distraction from the underlying issue management.

The structural rule:

Where the wording is mandatory and the SME has actual or constructive knowledge of a circumstance falling within the trigger, notify. The cost of breaching a condition precedent is the entire cover.
Where the wording is permissive and the circumstance is borderline, consult the licensed adviser. The adviser handles claims notifications across many clients and can calibrate the call against market practice and insurer-specific patterns.
Where the SME is approaching any event that ends the current policy (renewal with switch, cancellation, M&A), notify before the event. The window will close.

The Procedural Steps

The procedural steps below assume the SME has decided to notify and has read the wording trigger.

Step 1: Gather the Facts

Before drafting the NoC, assemble:

The factual chronology of the circumstance (dates, parties, communications).
All correspondence on the matter (emails, letters, regulator communications).
The internal stakeholders' written accounts (director's statement, employee's complaint, regulator's letter).
The policy schedule, wording, and any endorsements.
Any related Notices of Circumstance previously filed (which the new NoC should reference for continuity).

Step 2: Identify Internal Counsel and Engage External Counsel If Required

NoCs touch legally sensitive material — directors' conduct, regulator investigations, employee disputes, customer claims. The internal stakeholder responsible for the NoC drafting should be senior enough to make disclosure decisions (typically the CFO, GC if present, or CEO) and the SME should consider engaging external counsel before drafting. Defence costs under D&O, PI, and cyber policies generally cover counsel engaged on a notification, subject to the policy's defence-costs cover and any panel-counsel requirements.

Where the insurer has a panel of approved external counsel for defence work, the NoC drafting can be coordinated with the panel counsel from the outset. This positions the panel counsel to take over the defence if the circumstance develops into a claim and avoids a counsel-change midstream.

Step 3: Draft the Notification Letter

The NoC should be a formal letter or email addressed to the insurer's claims department. The standard structure:

Heading: Policy number, named insured, policy period.
Identification of the NoC: "Notification of Circumstances Likely to Give Rise to a Claim under [Policy Section]."
Factual narrative: A neutral, chronological description of the relevant facts. Avoid characterising the matter as a claim. Avoid admitting liability. Use formulations like "we received correspondence dated X from Y alleging Z" rather than "we failed to comply with Z."
Identification of the potentially aggrieved party: Name, contact details if available, nature of the alleged grievance.
Identification of the wrongful act: Date(s), nature, alleged effect.
Quantum if known: A range or estimate if available, with a clear statement that quantum is uncertain.
The SME's current position: Steps taken, contemplated next steps, internal investigation status.
A statement that this is a notification of circumstances under the policy, with reference to the specific wording clause.
A request for acknowledgement of receipt and confirmation of cover position.

The letter should not admit liability. It should not opine on the merits of the underlying matter. It should not concede that a claim is likely. It should describe facts neutrally and invoke the wording.

Step 4: Notify Through the Correct Channel

The wording specifies the notification recipient and channel. Common channels:

The insurer's claims department email address (commonly published on the insurer's website and on the policy schedule).
The insurer's claims notification portal (some insurers — AIG, Chubb, Beazley — operate online claim portals).
The insurer's appointed claims handler or third-party administrator (TPA), where applicable.
Via the licensed broker as the SME's agent for notification, where the broker has the established protocol.

The notification should be sent both via the specified channel and via a secondary channel (registered post to the insurer's Singapore-licensed entity address) for evidentiary robustness. The date of receipt by the insurer is the date of notification — confirmation of receipt is therefore important.

Step 5: Maintain the Notification File

The NoC creates a file that may stay open for years. The SME should maintain:

The original notification letter and the insurer's acknowledgement.
All subsequent correspondence with the insurer on the matter.
The internal chronology and supporting documents.
Any updates to the matter that should be notified to the insurer (typically required by the wording — "you must update us promptly upon material changes").
Any related claims or notifications under other policies (the same incident may trigger multiple policies — D&O, EPL, PI — and notifications must be coordinated).

Step 6: Update the Insurer Promptly

Most claims-made wordings impose a continuing obligation to update the insurer on material developments after the initial notification. Failure to update can be treated as a breach of the duty of cooperation and can affect cover. Examples of updates to send:

A claim has been filed in court or tribunal.
A demand letter has been received with quantum.
The regulator has progressed the investigation (e.g., MAS has issued a "no further action" letter, or PDPC has issued a Decision).
The aggrieved party has retained counsel and counsel has made contact.
The matter has been resolved (claim withdrawn, complaint dropped, regulator closed file).

The Defence-Costs Mechanics

A properly filed NoC typically triggers the policy's defence-costs cover from the date the notification is accepted. Defence-costs cover varies across wordings:

Duty-to-defend policies: the insurer takes over the defence and appoints counsel. Common in some D&O wordings and most PI / Tech E&O wordings.
Indemnity policies: the insured retains counsel and the insurer reimburses fees subject to the policy's defence-costs sub-limit. Common in D&O.
Allocation clauses: where the matter involves both covered and uncovered elements, the defence costs are apportioned. This is heavily contested in practice and the SME should understand the allocation methodology.

The defence-costs sub-limit, where one applies, is often inside the policy's aggregate limit (meaning every dollar of defence cost reduces the available indemnity for the underlying loss). Some wordings carry a separate defence-costs sub-limit that sits outside the loss limit (more favourable to the insured).

The Singapore High Court in Tan Yi Lin Cheryl v AIA Singapore Pte Ltd [2021] SGHC 130 confirmed the continuing duty of disclosure under section 18 of the Marine Insurance Act 1906. The duty applies to material facts relating to circumstances notified as well as to claims; the SME must update the insurer on material developments throughout the matter's life.

Coordinating Across Multiple Policies

A single incident frequently triggers multiple policies. A cyber breach may trigger cyber, tech E&O, D&O (failure to oversee), and EPL (employee whose data was compromised). A regulator investigation may trigger D&O, PI, and EPL. An employee dispute may trigger EPL and D&O.

The NoC workflow on a multi-policy incident requires:

An incident-coordination memo that identifies every policy potentially triggered.
Separate NoCs to each insurer, drafted to fit each policy's wording trigger and notification format.
Cross-references between the NoCs to put each insurer on notice that other policies are in play.
A single internal point of contact who manages all the notifications and the resulting correspondence.
An "other insurance" analysis to determine which policy responds first and how excess layers attach.

The multi-policy notification workflow is treated separately in the multi-policy coordination article.

Common Mistakes Singapore SMEs Make on NoCs

Waiting until certain. The trigger is "likely to give rise" or "may give rise" — not certainty. Waiting until the claim arrives is too late.

Treating the NoC as a claim. The NoC is not a claim. It does not commit the SME to defending or settling anything. It preserves cover.

Drafting the NoC like a legal brief. The NoC reports facts; it does not litigate the merits.

Admitting liability in the NoC. Most policies contain a "no admission" condition. The NoC should describe facts, not admissions.

Notifying through the wrong channel. Email to the broker is not necessarily notice to the insurer. The wording specifies the channel.

Failing to update. The continuing obligation to update is in most wordings. Silence after the initial notification is a breach risk.

Failing to notify before policy events. Renewal switch, cancellation, M&A — each closes the window. Notifications must precede the event.

Failing to coordinate across multiple policies. Single incidents commonly trigger multiple covers. Notifying one and not the others can produce coverage disputes between insurers and out-of-pocket exposure for the SME.

Not engaging counsel. NoCs touch legally sensitive material. The SME's senior internal stakeholder should not draft the NoC without counsel input — typically defence-costs cover responds to this engagement.

What This Means for Your Business

If you carry any claims-made cover — D&O, PI, EPL, cyber, management liability, tech E&O, media liability — the NoC workflow above is the procedural device that protects your cover. Run an internal scan at least quarterly across all claims-made lines for any circumstance that may meet the wording trigger. Where a circumstance is identified, escalate to the CFO or GC, and decide on notification within the timeline set by the wording.

The licensed adviser handling your programme is the right party to coordinate the notification. A good adviser will draft the NoC with you, confirm the wording trigger, and submit through the correct channel. A weak adviser will resist the notification on the basis that "we don't want a claim history on your record." That is a renewal-pricing argument, not a coverage argument. The SME's interest is preserving cover; the adviser's job is to give effect to that interest.

The hardest case is the borderline circumstance — the customer complaint that may not develop, the employee grievance that may resolve internally, the regulator enquiry that may close. In those cases, the default rule is notify and document. The cost of notifying a borderline circumstance is a possible renewal pricing impact. The cost of failing to notify a circumstance that develops into a claim is the entire cover.

Questions to Ask Your Adviser

Please walk me through the notification clause in each of my claims-made policies — D&O, PI, EPL, cyber, management liability — and explain the trigger and deadline for each.
Is the wording in each policy mandatory ("must notify") or permissive ("may notify"), and what are the consequences if I do not notify?
What is the correct notification channel for each insurer — the claims email, an online portal, the broker, or registered post — and can we test the channel before we need it?
If a borderline circumstance arises, will you draft the NoC with me, run it past your claims team, and submit on my behalf?
What is the impact on my renewal pricing of filing an NoC that does not develop into a claim, and how do you negotiate the renewal where the NoC is on file?
For incidents that may trigger multiple policies (e.g., a cyber breach triggering cyber, D&O, EPL), what is your standard coordination workflow?
When does defence-costs cover activate under each of my claims-made policies — at the date of notification, at the date of acknowledgement, or at the date of an actual claim?
If a notified circumstance develops into a claim after the current policy lapses, what is the process for converting the notification into a deemed claim under the policy, and what evidence will the insurer require?

Related Information

Published 14 May 2026. Source verified 14 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.