The Answer in 60 Seconds

Most Singapore SMEs run their insurance off one person's institutional memory. The renewal calendar lives in their head or in a private spreadsheet, the insurer's contact details are in their personal address book, and the operative policy schedules are attached to forwarded emails. When the staff member leaves - which the Ministry of Manpower's Q4 2025 labour market advance release shows happens routinely across the Singapore SME workforce - the entire insurance position transfers with them. The fix is not a person; it is a process that lives on the company's shared workspace, with two-person access minimum, and with the renewal data attached to the date rather than held separately in someone's head. This article sets out the five process layers - custody, calendar, brief, escalation, and handover - that together make the insurance position survivable across staff change. The structural prerequisite is the seven-folder structure described in the corporate insurance folder framework; this article is what runs on top of that structure.

The Sourced Detail

The Singapore SME landscape, per the Department of Statistics enterprise data, is concentrated in firms below 200 employees, with insurance administration typically owned by one finance, HR or office-management hire. That single point of ownership is structurally fragile in a labour market where job turnover is a steady-state feature, not an exception.

The MOM labour market data does not publish an SME-specific turnover figure, but the cumulative effect across an SME's three-to-five-year horizon is that the staff member who set up the insurance position is rarely the same staff member managing it three years later. The process must therefore survive multiple ownership changes without dropping a renewal, missing a premium-payment warranty, or losing a document.

What goes wrong when the process is tied to one person

Three failure modes recur, observed across Singapore SME advisory practice.

Silent renewal lapses. The staff member leaves; the renewal notices arrive in their now-defunct mailbox or are forwarded by the broker to a contact who no longer exists at the company. No one chases. The policy lapses at expiry or at the day-60 premium-payment warranty under the GIA Premium Payment Framework. See the hidden cost of a missed insurance renewal for the consequences.

Wrong sum insured at renewal. The renewal goes through but on the prior-year basis - the headcount has grown, revenue has changed, premises have moved, but no one updates the proposal. The average clause then applies on a partial loss, and the partial-loss payment is reduced proportionately to the underinsurance ratio.

New risks not added. A new product line is launched without a fresh underwriting view. A new sub-contractor is engaged without endorsement on public liability. A new senior hire is brought on without addition to D&O or key-person cover. The risks accumulate uninsured because the staff member who would have flagged them is gone.

The pattern is consistent: the failure is not in the policies but in the operational discipline around them.

Layer 1: Custody

The first layer is where the documents and the calendar live. Custody must sit with the company, not with a person.

The seven-folder structure described in the corporate insurance folder framework lives on the company's shared drive - Microsoft 365, Google Workspace, or an equivalent platform with access control and version history. The folder access list is maintained as a role, not as named individuals only: when the finance lead changes, the new lead inherits access automatically.

Two structural rules apply:

  1. Minimum two people with full access, at least one of whom is not the person most likely to leave (typically a director, the founder, or the long-tenured operations lead).
  2. No insurance document is stored anywhere else. Forwarded copies in personal email are not the authoritative version; the shared workspace is.

See why email and WhatsApp are the worst places to store business insurance policies for the structural reasons custody failure is the most common process breakdown.

Layer 2: Calendar

The second layer is the renewal-date timetable. It sits in folder 07_Renewals_Calendar and lists, per policy:

  • Policy expiry date.
  • Day-60 premium-payment warranty deadline at each new inception (per the GIA Premium Payment Framework).
  • Internal-review (T-90) trigger date.
  • IFA-brief (T-60) trigger date.
  • Quote-decision (T-30) trigger date.
  • Third-party certificate-of-insurance expiry dates (landlord, MCST, procurer).

The calendar holds twelve recurring dates for a typical mid-sized SME plus the project-specific dates for per-project bonds - documented in the 12 insurance dates every Singapore SME must track.

The calendar fires automatic notifications at T-90, T-60, T-30 and at T-7 from the day-60 premium-payment deadline. Notifications go to at least two people: the primary owner of the insurance process and a non-leaver (typically the finance lead or a director).

Layer 3: Renewal brief

The third layer is the data attached to each renewal date. A calendar entry without a brief is half a process. The brief, prepared at T-90 and refined at T-60, contains:

  • Current headcount (manual / non-manual / Work Permit / S Pass / EP) - relevant for the Work Injury Compensation Act 2019 mandatory cover and Employment of Foreign Manpower Act 1990 foreign-worker medical cover.
  • Current revenue (three-year trend) - relevant for business interruption and professional indemnity rating.
  • Current asset register with replacement values - relevant for fire and property.
  • Lease summary with insurance covenants - relevant for public liability sum insured and named-insured endorsements.
  • Claims experience report from the insurer for the expiring policy period - relevant for renewal rating.
  • Any business changes during the expiring period (new premises, new product, new contract, new country) - relevant to disclose at renewal.

For claims-made covers, the brief also captures the circumstances log - dated entries of any incident or complaint that could plausibly mature into a claim during the expiring policy period, to be notified before expiry.

Layer 4: Escalation

The fourth layer is what happens when a calendar trigger fires and nothing follows. Without an escalation rule, the renewal simply does not happen and the lapse is discovered downstream.

The escalation rule has three steps:

  1. T-30 trigger fires. Primary owner has 7 days to confirm the renewal-quote decision.
  2. T-23 - no confirmation. Escalation to the second-access holder (typically the finance lead or a director).
  3. T-14 - still no confirmation. Escalation to the founder / CEO with a one-line note: "Policy X expires Y date, no renewal decision recorded."

The intent is not bureaucratic; it is to ensure that no policy lapses silently. The escalation log itself is the audit trail for why a decision was taken (or not taken) in any given year.

Layer 5: Handover

The fifth layer is what happens when the primary owner leaves. A clean handover is impossible if the process lives in one person's head; a clean handover is straightforward if the process lives in the workspace.

The handover checklist:

  1. Access transferred to the replacement on the same day as the leaver's last day.
  2. Renewal calendar walked through with the replacement, with annotations.
  3. IFA introduced to the replacement, with prior-year context.
  4. Active circumstance logs (claims-made covers) explicitly flagged for continued monitoring.
  5. Open quote requests transitioned with documented status.
  6. One-page summary of the insurance position at the date of handover, filed in the shared workspace as the new baseline.

The single highest-leverage line in the handover is the one-page summary. It survives further staff changes and prevents the next reconstruction from starting from zero.

Why the IFA relationship needs to be institutional

A frequently overlooked structural issue: the IFA relationship is often a personal one between the IFA's account executive and the SME's insurance lead. When the SME's lead leaves, the IFA's institutional knowledge of the SME also degrades - the IFA's records are accurate, but the context behind decisions ("we chose this insurer because they had the right wording for our landlord's clause") is lost.

The process fix: the IFA should be briefed at every annual cycle on the SME's current insurance lead, and the IFA's account-management protocol should be confirmed at each renewal. The IFA's standard handover practice between its own staff is usually robust; the gap is at the SME's end.

What an audit-ready renewal process looks like

A renewal process that survives staff change has five observable characteristics:

  1. A new hire taking over insurance can find every active policy in under five minutes.
  2. The next renewal date and the day-60 premium-payment deadline are visible without asking anyone.
  3. The renewal brief for the next renewal can be assembled from the workspace data, not from interviews.
  4. The IFA's records and the SME's records reconcile to the same set of policies, dates and sums insured.
  5. A pre-loss claim notification - circumstance or actual claim - can be drafted within an hour from the workspace.

These five tests, applied annually, identify whether the process is working or whether the process is dependent on one person.

Common Mistakes / What Goes Wrong

  1. One person's calendar is the company's calendar. Most common, most expensive.

  2. No T-90 trigger. Renewal-quote requests at T-30 produce defensive quotes, not competitive ones.

  3. Escalation is not defined. A missed T-30 trigger has no downstream backstop.

  4. Handover happens after the leaver has gone. Tacit knowledge does not survive the gap.

  5. The IFA is the only party holding the institutional memory. Acceptable as a stopgap; structurally fragile.

  6. No documented selection rationale per policy. Two renewals later, no one knows why a particular insurer was chosen.

  7. Per-project bonds tracked on the same calendar as annual covers. Project lifecycles do not match annual cycles.

  8. Circumstance logs for claims-made covers are not maintained continuously. Late notification at renewal is structurally weaker.

  9. The renewal brief is recreated from scratch each year. The data should accumulate, not restart.

  10. No annual review of the process itself. A process that worked three years ago may not match the current business.

What This Means for Your Business

  1. Move custody of insurance documents to the shared workspace within 30 days if it is not already there.

  2. Establish the renewal calendar with T-90/T-60/T-30 triggers on every policy.

  3. Maintain a two-person access list with at least one non-leaver.

  4. Document the renewal brief as a living document, updated continuously rather than reconstructed annually.

  5. Define and document the escalation rule for missed triggers.

  6. Build the handover checklist into the standard staff-departure process - not as an afterthought but as a checkpoint.

  7. Brief the IFA on the current insurance lead at every annual cycle.

  8. Review the process itself annually alongside the 60-minute audit.

Questions to Ask Your Adviser

  1. What is your standard account-management protocol when our primary insurance contact changes?
  2. Can you provide us with a current schedule of every policy you have placed for us, with renewal dates and the day-60 premium-payment deadlines?
  3. When you change your account executive for our account, how is the institutional knowledge of our business transferred?
  4. What is your escalation if you have not heard from us by T-30 on any renewal?
  5. If we asked you tomorrow for a complete handover pack on our insurance position, what would be in it and how soon could you deliver?

Related Information

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.