The 12 Insurance Dates Every Singapore SME Must Track

The Answer in 60 Seconds

A Singapore SME carrying a typical mid-sized insurance programme is tracking, in effect, twelve recurring dates across its policy stack. Each date has a specific consequence if missed - in three cases (Work Injury Compensation under the Work Injury Compensation Act 2019, foreign-worker medical under the Employment of Foreign Manpower Act 1990, and motor third-party under the Motor Vehicles (Third-Party Risks and Compensation) Act 1960) the consequence is regulatory; in the others it is operational. The 60-day premium-payment warranty under the GIA Premium Payment Framework runs alongside each renewal date and is itself the most commonly missed deadline. This article sets out the twelve dates in table form, the rule behind each, and why a spreadsheet alone is not enough to hold them.

The Sourced Detail

The renewal calendar is not a list of dates. It is a list of dates plus the brief required to renew on each date, plus the person responsible, plus the escalation if the date approaches uncovered. A simple list of dates fails at the first staff change.

The twelve dates

The table below sets out the twelve recurring dates a Singapore SME carrying a typical mid-sized programme will track. Not every SME carries all twelve covers; the table is the maximum case. Adapt to the policy stack actually held.

#	Cover	Typical Cycle	Key Rule	If Missed
1	Work Injury Compensation	Annual, aligned to policy year	Mandatory under WICA 2019 s.24 for all manual workers and non-manual employees at or below S$2,600/month	Section 25 offence; employer personally liable for the schedule and Common Law exposure
2	Foreign-Worker Medical Insurance	Annual	Mandatory under EFMA 1990; Stage 2 in force from 1 July 2025 with age-differentiated premiums and standardised exclusions	MOM enforcement; work-pass privilege impact
3	Public Liability	Annual	Most landlords and procurers require continuous cover; sub-contractor exposure typically excluded unless endorsed	Lease breach; uninsured third-party liability
4	Fire and Property	Annual, often aligned to tenancy term	Average clause penalises underinsurance proportionately on partial losses; cyber excluded under standard property wordings	Contents and building reinstatement uninsured
5	Business Interruption	Annual, with Fire	Indemnity period (typically 12 months) caps the BI claim duration; sum insured based on gross profit, not turnover	BI loss falls on cash position; cited by QBE 2025 SME survey: 74% concerned, 23% covered
6	Motor Third-Party / Fleet	Annual, often aligned to road-tax renewal	Mandatory under Motor Vehicles (Third-Party Risks and Compensation) Act 1960; driving uninsured is a criminal offence	Driving offence; uninsured liability for third-party injury/property
7	Professional Indemnity	Annual	Claims-made basis - retroactive date is critical, circumstances must be notified within policy period	Historic work falls out of cover if retroactive date moves; late-notified claim rejected
8	Directors' & Officers' (D&O)	Annual	Claims-made basis; Side A (non-indemnifiable), Side B (company reimbursement), Side C (entity securities-claim cover)	Directors personally exposed; indemnification gap
9	Group Medical / Group PA	Annual	Headcount-based; sum-insured review required as workforce changes	Underinsured if headcount grew; overpaid if it shrank
10	Cyber Liability	Annual	Standard property and liability wordings typically exclude cyber events (property cyber via Lloyd's LMA5400/LMA5401; liability cyber via separate endorsement families); PDPA Part 6A breach notification independently applicable	Silent cyber gap; PDPA breach exposure unindemnified
11	Trade Credit	Annual; buyer-level credit limits more frequent	Buyer-list and credit-limit review at renewal; undeclared buyers typically uninsured	Bad-debt exposure on the undeclared buyer falls personally
12	Performance / Surety Bonds	Per-project	Bond period typically matches contract completion plus defects liability period	Bond call risk; employer claims under the bond on default

The twelfth date - performance and surety bonds - is the only one not tied to a fixed annual cycle. For project-driven SMEs it is the most variable and the most easily missed.

The hidden thirteenth date: the 60-day premium-payment warranty

Each of the twelve dates is shadowed by a thirteenth date: the day-60 premium-payment deadline that follows inception. Under the GIA Premium Payment Framework in force since 2005, a non-life commercial policy in Singapore lapses automatically if the premium is unpaid by day 60 from inception. The day-60 deadline is itself a recurring date that needs tracking, not an administrative detail.

See the hidden cost of a missed insurance renewal for the consequences of letting the day-60 deadline slip.

Why a spreadsheet is not enough

The renewal calendar is often kept as a spreadsheet on one staff member's laptop. The spreadsheet fails in four ways:

Single point of access. When the staff member leaves, the spreadsheet leaves with them. The renewal dates are reconstructed by the replacement, often after the first lapse.

No version control. The spreadsheet is edited continuously without history. The reasoning behind a date - why a renewal was moved, why a sum insured was changed - is invisible six months later.

No notification engine. The spreadsheet does not send reminders. The user has to remember to look at it. Under operational pressure, the user does not.

No context attached. The spreadsheet holds a date but not the brief required to renew on that date - the headcount update, the revenue figure, the new premises detail, the prior-year claims experience. The renewal arrives and the brief is still being assembled.

Why a calendar reminder is also not enough

A reminder in a personal calendar - Google Calendar, Outlook - addresses the notification problem but not the others. A reminder still:

• Belongs to one person's calendar, not the company's shared workspace.
• Does not carry the brief required to renew - the reminder fires and the user then has to find the data elsewhere.
• Does not survive staff change unless the calendar is shared, which most personal calendars are not.

What the calendar should actually do

A renewal calendar that works has five characteristics, none of which are difficult to implement.

1. Lives on the shared workspace, not on any individual's account.
2. Two-person access minimum, with at least one non-leaver.
3. Triggers at T-90, T-60, and T-30, not at T-7 (which is too late for any negotiation).
4. Carries the renewal brief alongside the date - the data the IFA needs to take the renewal to market, ready to go.
5. Tracks the day-60 premium-payment deadline at each new inception, separately and explicitly.

The renewal calendar in the seven-folder structure

The seven-folder structure documented in the corporate insurance folder framework places the renewal calendar in folder 07_Renewals_Calendar as a single living sheet, separately from the policy document stores. The calendar references the folder location of the prior-year documents for each cover, so the renewal preparation can pull the IFA brief together in one workspace.

Per-project bonds need their own track

The twelfth date - performance and surety bonds - sits outside the annual cycle and needs its own track. For an SME that bids on multiple projects, the bond schedule is typically maintained as a project-by-project register, with the bond reference, the issuing bank or insurer, the bond period (contract completion plus defects liability period), the bond amount, and the underlying contract reference.

The risk on bonds is twofold: the bond is called by the employer in the event of default (whether justified or not), and the bond is not released on contract completion until the defects liability period expires. Both events have specific dates that need tracking distinctly from the annual renewal cycle.

Common Mistakes / What Goes Wrong

1. One spreadsheet, one laptop, one person. Single point of failure for the entire renewal stack.

2. Reminders set at T-7. Too late for negotiation, quote comparison, or insurer-change planning.

3. No T-90 internal review. The renewal brief assembled at T-30 is necessarily thin.

4. Renewal calendar but no day-60 premium-payment tracking. The 60-day warranty deadline is not the renewal date - it is the deadline that follows inception.

5. Calendar entries with no associated brief. The date fires but the IFA still has to be briefed from scratch.

6. Per-project bonds tracked on the annual calendar. The bond schedule needs its own cadence.

7. Group medical headcount update deferred to the renewal date. The data takes time to assemble; assembling it post-renewal results in an over- or under-insured year.

8. Claims-made covers handled as if they were occurrence-based. The retroactive date matters; circumstances notification matters; treating PI or D&O like fire is a category error.

9. The renewal calendar is not audited. Once a policy has been renewed three times in a row without review, the calendar entry is presumed correct and is not checked against the actual policy schedule.

10. The third-party-COI cadence is not on the calendar. Landlord COIs, MCST COIs, procurer COIs all have their own expiry timetables and need to be tracked separately.

What This Means for Your Business

1. Audit the calendar against the policy schedule annually - the 60-minute audit is the natural moment for this.

2. Run the calendar from the shared workspace with two-person access, not from an individual's device.

3. Set T-90, T-60, T-30 triggers on every annual renewal. The T-90 trigger is the most often skipped and the most operationally valuable.

4. Track the day-60 premium-payment deadline separately at each inception, with its own notification at T-7 from the day-60 deadline.

5. Maintain a project-by-project bonds register separately from the annual calendar.

6. For claims-made covers, log circumstances continuously through the policy period, not at renewal.

7. Match certificate-of-insurance expiry dates for landlords, MCSTs, and procurers to the underlying policy renewal dates.

8. Treat the calendar as authoritative, not as a copy of the IFA's records. If the IFA's schedule and the calendar disagree, the calendar is reconciled, not overwritten.

Questions to Ask Your Adviser

1. Can you provide a schedule of all our policies showing the renewal date, the day-60 premium-payment deadline, and the standard notification cadence for each?
2. For our claims-made covers, what is the latest acceptable date to notify a circumstance arising during the current period?
3. How do you confirm receipt of premium with us, and at what point in the 60-day window do you escalate non-receipt?
4. Which of our policies has a retroactive date, and what is the operational implication if we change insurer at the next renewal?
5. For our per-project bonds, what is your release protocol with the issuing bank or insurer at contract completion and at end-of-defects-liability?

Related Information

• The Hidden Cost of a Missed Insurance Renewal for Singapore Businesses
• Corporate Insurance Folder Structure Every Singapore SME Should Have
• How to Audit Your Existing Business Insurance in 60 Minutes

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

---