What Boards Should Ask About Legacy Core Systems and Treaty Risk
The Board Question Legacy Core Systems Keep Avoiding
Board discussions about technology tend to focus on cybersecurity, uptime, and budget. A quieter risk sits underneath those conversations: a core system that can't model the treaty structures the market is asking for, which shapes growth and competitive position just as directly as any cyber incident would, but almost never gets framed that way in the boardroom.
Why Should This Be a Board-Level Concern at All?
It should be a board-level concern because it directly affects growth strategy and risk appetite, determining which business the reinsurer can accept rather than just how efficiently it processes existing business.
Most technology issues that reach the board are framed around cost, security, or operational resilience. This one is different: it's a constraint on the top line. A reinsurer that structurally cannot bind certain treaty types is, in effect, choosing to cede that segment of the market to competitors, whether or not anyone has framed the decision that explicitly.
What Should the Board Actually Ask Management?
The key question is how much premium and margin was declined, delayed, or simplified in the last renewal cycle specifically because the core system couldn't model the requested treaty structure.
This question forces a concrete answer rather than a general reassurance that "the team is aware of the issue." If management can't answer it with real numbers, that itself is useful information about how well the issue is actually being tracked below the board level.
How Can the Board Tell If Management Has This Under Control?
Management should be able to produce a current log of structured treaties tracked outside the core system, along with a plan and timeline for closing that gap.
The existence of the log matters as much as its contents. A management team that can point to a maintained, reviewed record of workarounds is demonstrating active control over a known risk. A management team that can't produce one is likely underestimating, or simply hasn't measured, how much of the book currently depends on informal fixes.
Is This a Risk Appetite Question or Purely a Technology Question?
It's fundamentally a risk appetite question, since accumulating workarounds outside the system of record represents data and operational risk the board should be aware it's carrying.
Every treaty tracked partly outside the core system is a small, ongoing bet that the workaround record stays accurate and current. That's a reasonable short-term bet. As a permanent operating posture across a growing share of the book, it's a risk exposure the board should be deciding to accept deliberately, not one it should discover after the fact.
| Board Question | What a Strong Answer Looks Like | What a Weak Answer Looks Like |
|---|---|---|
| How much business was affected last cycle? | A specific premium and margin figure | A general sense that "some deals were tricky" |
| Is there a current workaround log? | Yes, reviewed each renewal cycle | No formal record exists |
| Is there a fix timeline? | A scoped plan with milestones | An open-ended "we're looking into it" |
| Who owns this issue? | A named executive with cross-functional authority | No clear individual owner |
What's a Good Way to Test Whether the Board Is Getting the Full Picture?
Ask for a specific example of a recent structured deal the system couldn't handle and how it was resolved, since a concrete example exposes gaps a summary report can hide.
A summary report can say "system limitations are being managed" without revealing much. A specific example, walked through in detail, either confirms the process is sound or surfaces exactly where it's thin. A Reinsurance Audit Preparation AI Agent can help management assemble this kind of concrete evidence quickly, rather than needing to manually reconstruct examples ahead of a board meeting.
Should This Appear in Formal Risk Reporting?
Yes, if the number or value of workaround-dependent treaties is material, it belongs in operational risk reporting alongside other technology and data risk items, not treated as a separate IT-only concern.
Folding it into standard risk reporting keeps it visible over time and comparable against other risk categories the board already tracks, rather than letting it exist only as an occasional side note in a technology update.
A board that only asks whether the core system is still running is asking the wrong question. The right question is what that system is quietly preventing the reinsurer from writing, and whether the answer to that question is one the board would actually choose if it were made explicit.
Frequently Asked Questions
Why should boards care about a technology limitation like this?
Because it directly affects growth strategy and risk appetite, determining which business the reinsurer can accept, not just how efficiently it processes existing business.
What's the key question a board should ask management?
Ask how much premium and margin was declined, delayed, or simplified in the last renewal cycle specifically because the core system couldn't model the requested treaty structure.
How can a board tell if management has this under control?
Management should be able to produce a current log of structured treaties tracked outside the core system, along with a plan and timeline for closing that gap.
Is this a risk appetite issue or a pure technology issue?
It's fundamentally a risk appetite issue, since accumulating workarounds outside the system of record represents data and operational risk the board should be aware it's carrying.
What questions reveal whether the board is getting the full picture?
Ask for a specific example of a recent structured deal the system couldn't handle and how it was resolved, since a concrete example exposes gaps a summary report can hide.
Should this appear in formal risk reporting to the board?
Yes, if the number or value of workaround-dependent treaties is material, it belongs in operational risk reporting alongside other technology and data risk items.
How should a board weigh urgency against cost when this issue is raised?
Weigh the compounding cost of continued lost or workaround-dependent business against the cost of a fix, using data from recent renewal cycles rather than a general sense of urgency.
What's a warning sign that this issue is more serious than management is presenting?
A warning sign is management describing this purely as a technology upgrade item without being able to quantify how much business or margin it's currently affecting.
