The previous chapters established what intelligence infrastructure is and why it matters economically. This chapter makes it concrete: what does infrastructure actually do in operational terms? How does the shift from “system of insight” to “system of action” manifest in daily workflows?
The distinction is simple but transformative. A system of insight provides information for humans to process. A system of action processes information and presents decisions for humans to review. The difference is who does the work.
In a system of insight, an underwriter receives intelligence and must: identify relevant policies, determine coverage applicability, calculate exposure, assess aggregation implications, draft communications, and route approvals. The intelligence informed the work. The underwriter did the work.
In a system of action, the underwriter receives: affected policies already identified, coverage applicability already determined, exposure already calculated, aggregation already flagged, communications already drafted, approvals already routed. The intelligence did the work. The underwriter reviews and decides.
This isn’t automation replacing judgment. It’s automation eliminating compilation so that judgment can focus on decisions that actually require expertise.
Crisis Response Transformation
Consider the scenario from Chapter 1: an explosion at a manufacturing facility in São Paulo affecting a Lloyd’s syndicate’s political violence portfolio.
Before (System of Insight):
9:47 AM — Event occurs. Alerts arrive from monitoring services.
10:00 AM — Underwriter begins gathering intelligence: What happened? Where exactly? What type of incident? Casualties? Property damage? Claims from multiple sources, some conflicting.
10:30 AM — Intelligence synthesis underway. Underwriter cross-references incident details against portfolio: Which policyholders have exposure in São Paulo? The policy administration system requires manual queries. Location data exists but isn’t standardised—some policies list “São Paulo,” others “São Paulo State,” others specific addresses.
11:30 AM — Four potentially affected policies identified after manual review. Underwriter pulls policy details for each: coverage terms, limits, exclusions, deductibles. Documents are in different formats, stored in different systems.
1:00 PM — Coverage analysis begins. Does this incident trigger coverage under each policy? The explosion appears industrial rather than political—but was it? Early reports are unclear. Underwriter drafts preliminary assessment with caveats.
2:30 PM — Exposure calculation. What’s the potential loss if coverage applies? Asset values, business interruption estimates, policy limits. Some information readily available, some requires broker contact.
4:00 PM — Aggregation check. Do other policies have exposure that could be affected if this incident signals broader instability? Manual review of portfolio for Brazil exposure.
5:00 PM — Communications drafted. Separate emails for each affected broker. Internal summary for management. Documentation for file.
5:30 PM — Assessment complete. Eight hours from alert to actionable output.
After (System of Action):
9:47 AM — Event occurs. Infrastructure detects incident through monitoring integration.
9:48 AM — Incident automatically categorised: explosion, industrial facility, São Paulo coordinates, preliminary casualty estimates. Categorisation draws on pre-validated incident taxonomy.
9:50 AM — Policy exposure automatically mapped. Infrastructure queries policy database using standardised location data. Four policies identified with exposure within defined radius. Policy details, coverage terms, and limits automatically compiled.
9:55 AM — Coverage analysis automatically generated. Incident characteristics compared against policy triggers. Preliminary assessment: likely covered under two policies, coverage uncertain for two others pending incident classification clarification. Specific policy language cited for each determination.
10:00 AM — Exposure calculation automatically computed. Estimated maximum loss per policy based on declared values and policy limits. Aggregate exposure across affected policies calculated. Comparison to historical similar incidents provided for context.
10:05 AM — Aggregation automatically flagged. Three additional policies with Brazil exposure identified. Current incident’s potential implications for regional risk noted. Portfolio-level exposure to escalation scenario calculated.
10:10 AM — Communications automatically drafted. Broker-specific emails prepared with relevant policy details and preliminary assessment. Internal summary generated. All documents cite source intelligence with links to evidence.
10:15 AM — Assessment ready for review. Underwriter reviews pre-compiled analysis, confirms or adjusts preliminary determinations, approves communications for sending.
10:30 AM — Response complete. Forty-three minutes from alert to actionable output.
The transformation: 8 hours reduced to 43 minutes. Not because the underwriter worked faster, but because the system did the compilation work that previously consumed seven hours and seventeen minutes.
The underwriter’s role shifted from compilation to review. The same expertise—understanding coverage, assessing exposure, making judgment calls on ambiguous situations—applied to pre-processed outputs rather than raw inputs.
Renewal Transformation
Renewal season stress is endemic to specialty insurance. The TechFreight scenario from Chapter 3—180 locations across 35 countries, 60 days to renewal—illustrates why.
Before (System of Insight):
Weeks 1-3: Evidence Compilation (180+ hours)
The renewal team begins systematic evidence gathering. For each of 180 locations:
- Pull incident history for policy period from intelligence databases
- Research current threat environment from multiple sources
- Compare conditions to policy inception baseline
- Document material changes
- Flag locations requiring detailed attention
This work is essential but systematic. Each location requires similar steps. The process could be templated, but execution remains manual. Senior analysts perform work that doesn’t require senior judgment.
Weeks 4-5: Assessment and Documentation (120+ hours)
With evidence compiled, assessment begins:
- Location-by-location risk evaluation
- Aggregation exposure analysis across portfolio
- Coverage adequacy review against current conditions
- Premium adequacy assessment based on risk evolution
- Renewal recommendation preparation
The assessment phase requires more judgment than compilation, but much of it remains systematic: applying consistent frameworks to compiled evidence, generating standardised documentation, preparing materials for underwriting committee review.
Weeks 6-8: Coordination and Communication (80+ hours)
With assessment complete, coordination begins:
- Broker communication with renewal terms
- Information request responses
- Internal stakeholder alignment
- Underwriting committee presentation
- Negotiation and final terms agreement
Total: 400+ hours across the team. Renewal completed, but at significant cost in time and senior attention.
After (System of Action):
Week 1: Foundation Review (8-12 hours)
Renewal triggered in infrastructure. System automatically generates:
- Incident summary by location: All relevant incidents during policy period, categorised and severity-scored, with comparison to pre-inception baseline
- Risk trajectory analysis: For each location, algorithmic assessment of whether risk has increased, decreased, or remained stable, with supporting evidence
- Material change flags: Locations where conditions have changed significantly, requiring underwriter attention
- Aggregation current state: Portfolio-wide exposure to regions represented in this policy, with concentration analysis
Renewal team reviews automated outputs. Focus: validating material change flags, identifying locations requiring deeper assessment, confirming trajectory analysis aligns with market knowledge.
Week 2: Judgment and Exception Handling (15-20 hours)
With systematic work complete, team focuses on:
- Flagged locations: Deep assessment of locations where automated analysis indicates material change or uncertainty
- Strategic considerations: Client relationship factors, market positioning, competitive dynamics
- Coverage adjustments: Where conditions warrant, modifications to terms, limits, or exclusions
- Pricing decisions: Premium adjustments reflecting risk evolution
This is underwriting work—the judgment calls that require expertise, market knowledge, and strategic thinking.
Week 3: Coordination and Completion (10-15 hours)
- Broker communication with renewal terms (pre-drafted by infrastructure, customised by team)
- Negotiation on contested points
- Final documentation (automatically generated, manually reviewed)
- Underwriting committee presentation (slides auto-generated from assessment outputs)
Total: 35-45 hours across the team. Renewal completed with greater rigour and less exhaustion.
The transformation: 400+ hours reduced to 35-45 hours. The reduction isn’t in corners cut—it’s in systematic work automated. Evidence compilation that consumed 180 hours happens automatically. Assessment that consumed 120 hours leverages pre-processed intelligence. Coordination that consumed 80 hours uses pre-drafted materials.
Senior expertise focuses on the 35-45 hours of work that genuinely requires senior expertise.
New Business Transformation
New business submission assessment faces similar dynamics to renewal: systematic work consuming expert time.
Before (System of Insight):
A broker submits a new multinational political violence policy. The submission includes 95 locations across 28 countries. The underwriter must:
Day 1-2: Location Assessment
- Research each location’s risk profile using available intelligence
- Score or categorise risk for each location
- Identify locations with elevated concern
- Compare submission quality to information requirements
Day 2-3: Portfolio Context
- Assess aggregation implications: Does this submission concentrate exposure in already-heavy regions?
- Identify potential clash with existing policies
- Evaluate diversification benefit or concentration risk
Day 3-4: Pricing and Terms
- Develop pricing based on location assessments
- Determine appropriate terms, conditions, exclusions
- Prepare quote for broker
Total: 3-4 days for complex multinational submission.
After (System of Action):
Broker submits new multinational political violence policy. Submission processed through infrastructure:
Hour 1: Automatic Assessment
- All 95 locations geocoded and matched to intelligence foundation
- Risk scores generated for each location based on pre-validated intelligence
- Incident history compiled for each location
- Elevated-risk locations flagged with supporting evidence
Hour 2: Portfolio Integration
- Aggregation analysis automatically generated: exposure concentration by region, country, peril type
- Clash identification: existing policies with overlapping exposure highlighted
- Portfolio impact assessment: how this submission affects overall risk profile
Hour 3: Pricing Guidance
- Algorithmic pricing indication based on location scores, historical loss patterns, portfolio context
- Suggested terms based on risk profile and policy templates
- Flagged locations where non-standard terms may be warranted
Hour 4: Underwriter Review
- Review automated outputs
- Adjust pricing based on relationship factors, market conditions, strategic priorities
- Finalise terms for broker quote
Total: 4-6 hours for complex multinational submission.
The transformation: 3-4 days reduced to 4-6 hours. The underwriter’s expertise—pricing judgment, relationship awareness, strategic positioning—applies to pre-processed intelligence rather than raw submission data.
Portfolio Management Transformation
Portfolio managers face a different challenge: maintaining current visibility across entire books of business.
Before (System of Insight):
Portfolio aggregation is typically a quarterly exercise:
- Extract policy data from administration systems
- Map policies to geographic exposure
- Compile incident data for exposure regions
- Generate aggregation reports
- Identify concentration concerns
- Prepare management reporting
The process takes 2-3 weeks per quarter. By completion, the data is already ageing. Between exercises, portfolio visibility relies on memory and ad hoc analysis.
After (System of Action):
Portfolio aggregation is continuous:
- Policy data automatically synchronised with intelligence foundation
- Geographic exposure continuously mapped and updated
- Incident data automatically integrated as events occur
- Aggregation dashboards reflect current state, not quarterly snapshots
- Concentration alerts trigger automatically when thresholds approach
- Management reporting generated on demand with current data
The portfolio manager’s role shifts from compilation to strategy:
- Reviewing automated alerts and determining response
- Analysing concentration trends and recommending adjustments
- Advising underwriters on portfolio implications of new business
- Developing strategic positioning based on market intelligence
The transformation: Quarterly exercise becomes continuous visibility. Backward-looking reporting becomes forward-looking management. Compilation work disappears; strategic work expands.
The Time Savings Reality
These transformations produce measurable time savings:
| Workflow | Before | After | Reduction |
| Crisis response | 8 hours | 30-45 minutes | 87-94% |
| Policy comparison | 2 days | Under 1 hour | 95%+ |
| Renewal evidence (season) | 400+ hours | 35-45 hours | 89-91% |
| Multi-location assessment | 3-4 days | 4-6 hours | 85-90% |
| Portfolio aggregation | 2-3 weeks quarterly | Continuous | N/A—model change |
These aren’t theoretical projections. They’re operational realities validated with practitioners who have experienced both models.
The savings don’t come from working faster. They come from eliminating work that shouldn’t require human effort: compiling data that exists in structured form, synthesising information according to consistent frameworks, generating documentation from standardised templates, routing communications through predictable channels.
What Stays Human
Infrastructure eliminates systematic work. It doesn’t eliminate—and shouldn’t attempt to eliminate—work that genuinely requires human expertise.
Complex judgment calls on edge cases: When incident classification is ambiguous, when coverage applicability depends on nuanced interpretation, when risk assessment requires contextual knowledge that defies systematisation—these decisions remain human. Infrastructure provides evidence and analysis; humans make judgment calls.
Client relationship management: Understanding client priorities, navigating sensitive communications, building trust through responsiveness and expertise—these are human capabilities. Infrastructure enables better service by eliminating delays, but the relationship remains human.
Strategic portfolio decisions: Market positioning, competitive response, risk appetite calibration, capital allocation—these strategic choices require business judgment that infrastructure informs but cannot make.
Novel risk evaluation: When new risk categories emerge, when unprecedented situations arise, when historical patterns provide no guidance—human expertise identifies, assesses, and responds. Infrastructure learns from these human assessments over time.
Exception handling: When automated outputs appear incorrect, when edge cases don’t fit templates, when something feels wrong despite systematic analysis—human review catches what algorithms miss.
The 80/20 shift:
In current workflows, approximately 80% of time goes to systematic work (compilation, synthesis, documentation) and 20% to judgment work (decisions, relationships, strategy).
Infrastructure inverts this ratio. 80% of time goes to judgment work. 20% goes to reviewing and validating systematic outputs.
The same expertise, applied to the work that actually requires it.
The Operational Reality
These transformations aren’t aspirational. They describe infrastructure that exists and operates today.
The shift from system of insight to system of action isn’t about replacing underwriters with algorithms. It’s about redirecting underwriting expertise from compilation to decision-making.
An underwriter reviewing a pre-compiled crisis assessment isn’t doing less valuable work than one spending eight hours compiling that assessment manually. They’re doing more valuable work—applying judgment and expertise to decisions rather than consuming judgment and expertise on data gathering.
The firms that adopt infrastructure operate at different velocity than those that don’t. Faster crisis response. More thorough renewal preparation in less time. Quicker new business turnaround. Continuous portfolio visibility.
The question for every operational leader: Where is your team’s expertise being spent? On the 80% that could be automated, or on the 20% that requires human judgment?
Infrastructure makes that choice possible. The economics make it inevitable. The operational reality makes it transformative.
