Accenture Media and Entertainment United States

ESPN

Document Processing

ESPN wanted to expand sports coverage for smaller leagues and more teams, but editorial processes could not scale written recaps fast enough to serve every fan segment economically.

Reported impact

Business outcome

ESPN can create more sports coverage for underserved leagues, deliver more personalized fan experiences, and expand recap production without scaling editorial headcount one story at a time.

  • Customer Experience
  • Productivity Improvement

Solution

Accenture helped ESPN build a generative AI content workflow that produces game recaps for leagues that previously received less written coverage. The solution ingests ESPN and league-licensed sports data including box scores, play-by-play feeds, rosters, standings, schedule pages, and audio transcripts when they are available. That data is processed by a gen AI summarization layer that drafts recap narratives designed to help fans quickly understand what happened in each match. The output is not published autonomously: ESPN editors review and refine the generated copy before it appears on ESPN.com and the ESPN app, preserving editorial control while increasing throughput. By combining structured sports data, optional transcript inputs, AI drafting, and human review, ESPN created a scalable publishing pipeline that broadens coverage without requiring a linear increase in newsroom labor.

Data flow

Licensed game data and available audio transcripts are gathered for each match, passed through ESPN's gen AI recap workflow, and then reviewed by editors before publication. Approved recaps are distributed through ESPN.com and the ESPN app to extend coverage across more sports and teams.

Solution architecture

5 components · 4 layers
  1. Ingest
    • ESPN and league-licensed data Provide box scores, play-by-play records, rosters, standings, and schedules used to ground each recap.
    • audio transcripts Add supporting game context when transcripts are available for the summarization workflow.
  2. Compute
    • gen AI solution Generates draft game recap narratives from structured match data and transcript inputs.
  3. Serving
    • ESPN.com and the ESPN app Serve the finished recaps to fans across ESPN's digital channels.
  4. Governance
    • ESPN editors review workflow Applies human review before AI-written recaps are approved for publication.

Architecture clues

  • Editors remain in the loop before publication.
  • Outputs are published to ESPN.com and the ESPN app.
  • The recap workflow uses a combination of structured sports data and audio transcripts.

Evidence from the source

"ESPN editors review the content before it is published on ESPN.com and the ESPN app."
"The solution leverages a dataset that includes a combination of ESPN and league-licensed data such as box scores, play-by-play data, rosters, standings and schedule pages, and audio transcripts (where available)."
"Through the power of gen AI, ESPN is scaling the creation and distribution of content to fans across an even wider variety of sports games and moments"
"the use of generative AI (gen AI) to provide coverage of more sports for more fans"
Transparency Evidence & methodology 71/100 reference value · 85% 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 value71/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 specificity16/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability17/25
    8 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 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 specificity8/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. Accenture

    Generative AI in Sports | ESPN Case Study | Accenture

    First-party
    https://www.accenture.com/en/case-studies/ai-data/espn-scores-with-generative-ai
    Source type
    Vendor-published customer story
    Published
    Oct 3, 2024
    Supports
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Oct 3, 2024 · Accenture · First-party
    Open date source
Not separately sourced Customer, Industry, Region, Company size, Metrics. Treat these normalized attributes as lower-confidence until a dedicated source is added.