When tech E&O is needed
Tech E&O is required by:
- Enterprise customer contracts — multinational and government customers routinely require Tech E&O of S$5m to S$25m as a condition of engagement.
- MAS-regulated financial services customers — technology vendors to financial institutions face MAS Notice 644 / TRM Guidelines flow-through.
- Cloud service hyperscalers as customers — AWS, Azure, GCP partner contracts often specify E&O minimums.
- SaaS marketplace listings — Salesforce AppExchange, Microsoft AppSource require E&O.
- Tender requirements — SG government IT tenders specify minimum E&O cover.
What E&O covers
A Singapore Tech E&O policy responds to civil claims alleging:
- Software defects — bugs in delivered code causing customer financial loss.
- System integration failures — failed connection between customer systems and delivered technology.
- Performance failures — system fails to meet stated SLAs.
- Data corruption during migration, integration or processing.
- Negligent advice or service in technology consultancy — standard PI cover within Tech E&O.
- IP infringement claims — allegations that delivered code infringes third-party IP rights.
- Defamation via media or content delivered as part of the service.
Pays damages plus defence costs.
Tech E&O vs general PI
For pure technology businesses, Tech E&O is structurally different from a general PI policy:
- General PI is written for the "professional advice" trigger — legal advice, engineering calculations, accounting opinions. May not cover software defects in delivered code.
- Tech E&O specifically covers technology delivery failure modes.
- Tech E&O extensions: failure-to-deliver, breach of contract for technology services, infringement of third-party IP via delivered code.
- Many Tech E&O policies bundle cyber liability for combined limits.
Combined Tech E&O + Cyber
Modern Singapore technology businesses typically buy combined Tech E&O + Cyber policies because the boundary between the two is increasingly blurred:
- A data breach caused by a delivered software defect is both E&O (customer financial loss) and Cyber (incident response).
- A failed integration causing customer data exposure spans both.
- SaaS providers face combined exposures across the entire customer journey.
Combined policies typically have shared limit (e.g., S$10m total across E&O and Cyber) with per-claim sub-limits. Cleaner for the insured than two separate policies with seam risk.
Retroactive date discipline
Like all claims-made covers, Tech E&O requires retroactive-date discipline:
- At renewal, the new policy must carry the SAME retroactive date as the original. Forward drift creates an uninsured tail for past project deliverables.
- When switching insurer, retain the earliest retroactive date in force.
- When closing the business or selling, buy run-off cover of typically 6 years (matches Singapore limitation period) to handle late-reported claims.
- For SaaS exits and M&A transactions, the acquirer typically requires the seller to maintain run-off cover for 6 years post-completion.