The workflow before#
The Hartford's risk data sat in separate policy, claims and external catastrophe systems, with different structures for each line of business. Analysts consolidated it by hand into static reports and PowerPoint decks. A comprehensive risk report took 2 to 3 weeks, metrics refreshed monthly or quarterly, and only 30 to 40% of the intended users opened the existing dashboards.
What we built#
We designed and built a set of Tableau dashboards on top of The Hartford's data warehouse, each for a specific decision: an executive risk view, underwriting risk, catastrophe exposure, claims risk and portfolio management.
Executives start from a KPI summary and drill to policy-level detail. Underwriters see risk scores, geographic concentration and appetite compliance. The catastrophe view shows probable maximum loss by peril and return period. Claims teams track loss ratios, reserve development and emerging patterns.
Data refreshes daily on Tableau Server with row-level security, so each team sees only what it should and nobody waits for a monthly cycle.
Before and after#
| Measure | Before | After |
|---|---|---|
| Full risk report | 2 to 3 weeks | 2 days |
| Risk data refresh | Monthly or quarterly | Daily |
| Ad hoc risk analysis | 1 to 2 weeks | 1 to 2 days |
| Active dashboard users | 30 to 40% of intended users | About 70% |
What's next#
Policy, claims and catastrophe data now feed one governed reporting layer. That is the foundation for an L2 risk assistant that lets underwriters and risk officers ask about exposure in plain English instead of building a new view.
