TCS Financial Services United States

AmTrust Financial Services, Inc.

Document Processing

AmTrust needed to turn broker-submitted Excess and Surplus policy requests into comprehensive quotes much faster, but its manual clearance process had to interpret unstructured email packages and attachments before underwriters could even begin tailoring a response.

More than 80% of submissions are processed in less than four hours after the broker submits a request for a quote.
implemented within 12 weeks
increase in quote submission volumes for the last six months
ratio of the number of quotes issues versus the policies bound has also improved for four out of the last six months

Reported impact

Business outcome

AmTrust shortened its initial underwriting response from a multi-day manual process to same or next day turnaround, processed most submissions within hours, improved broker goodwill, and created the capacity to absorb higher quote volumes without expanding the old manual clearance workflow.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

AmTrust worked with TCS to replace a manual Excess and Surplus clearance flow with a low-code, AI-based automation platform that ingests broker email submissions and their unstructured attachments, classifies each package, extracts policy-relevant fields, validates the captured data, and auto-routes exceptions for human review. TCS designed the solution with AmTrust's COO and IT team, mapping business rules and workflows so the normalized submission data could be formatted consistently and ingested into AmTrust's existing technology stack. Once the workflow completes, underwriters receive an account and shell quote ready for customization instead of starting from raw emails. The rollout covered all E&S products within 12 weeks and turned an expert-heavy intake process into a repeatable digital pipeline.

Data flow

Broker partners send new-business submissions and attachments into the clearance process, where AI based classification extracts policy data from the unstructured files. Data validation checks the captured fields, the automation workflow routes straight-through cases or exceptions as needed, and the normalized package is ingested into AmTrust's technology stack so underwriters receive a ready account and shell quote.

Solution architecture

4 components · 4 layers
  1. Compute
    • AI based classification Classifies broker submissions and extracts policy data from unstructured email attachments.
  2. Serving
    • AmTrust technology stack Receives the normalized submission package so underwriters can work from a ready account and shell quote.
  3. Orchestration
    • low-code, AI-based automation platform Orchestrates the end-to-end E&S clearance workflow and routes exception cases for manual handling when needed.
  4. Governance
    • data validation Checks extracted submission data before automated clearance continues downstream.

Architecture clues

  • Business rules and clearance workflows were mapped with AmTrust leadership and IT before implementation.
  • Cases that need manual intervention are auto-routed out of the straight-through path.
  • Normalized data is ingested into AmTrust's existing technology stack so underwriters start from a prepared quote shell.
  • The workflow handles unstructured broker submissions and email attachments.

Evidence from the source

"More than 80% of submissions are processed in less than four hours after the broker submits a request for a quote."
"The solution involves AI based classification, extraction of data from email attachments followed by data validation and automation of clearance process with provision to auto route cases that needed manual intervention."
"The solution was implemented within 12 weeks, followed by roll out to cover all E&S products."
"Using a low-code, AI-based automation platform, TCS transformed the entire clearance process"
"turn-around times for initial underwriting response have been reduced from a few days to same/next day"
Transparency Evidence & methodology 95/100 reference value · 95% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence95%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency10/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. TCS

    AmTrust partners with TCS to transform E&S clearance with AI

    First-party
    https://www.tcs.com/what-we-do/industries/insurance/case-study/amtrust-financial-services-transformation
    Source type
    Vendor-published customer story
    Published
    Feb 12, 2024
    Supports
    • Customer
    • Industry
    • Region
    • Company size
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence