Mistral Public Sector Europe

European Patent Office

Document Processing

The European Patent Office needed a near-error-free way to transcribe millions of patent pages into ST36-compliant structured output, but standard OCR tools struggled with the formulas, tables, figures, multilingual text, and high-volume reliability requirements of patent processing.

400,000 pages/day throughput
<1% character recognition error rate
Lead time from up to 5 days down to a few minutes

Reported impact

Business outcome

The EPO reduced transcription lead times from days to minutes while maintaining less than 1% character recognition error at 400,000 pages per day, giving the office a scalable compliant workflow and freeing expert staff to focus on patent examination rather than manual transcription cleanup.

  • Compliance
  • Productivity Improvement
  • Scalability

Solution

The European Patent Office worked with Mistral on a three-month proof of concept to automate patent transcription without losing the accuracy and standards compliance the grant process requires. At the core is a 1B OCR model fine-tuned on more than 150,000 PDFs representing 50,000 unique patents, so the system can read dense multilingual documents containing tables, formulas, figures, and scientific notation that defeat standard OCR tools. The model feeds a pipeline that converts outputs from Markdown to HTML and then into ST36 XML, producing structured patent data instead of plain extracted text. Mistral and EPO also delivered a scalable, fault-tolerant application ready for on-premises deployment, giving the office a reliable way to process very large document volumes while keeping the workflow aligned to operational and compliance requirements.

Data flow

Patent PDFs containing text, tables, formulas, figures, and multilingual content are read by the 1B OCR model, converted through a Markdown-to-HTML-to-ST36 XML pipeline, and delivered as structured output for the patent grant process through a scalable application designed for reliable on-premises use.

Solution architecture

3 components · 3 layers
  1. Compute
    • 1B OCR model Transcribes complex patent PDFs and was fine-tuned for the scientific and technical structures common in patent documents.
  2. Orchestration
    • Markdown to HTML to ST36 XML pipeline Transforms OCR output into the structured format required by the patent workflow.
  3. Uncategorized
    • scalable, fault-tolerant application Packages the transcription workflow for reliable, compliant operation and on-premises deployment.

Architecture clues

  • The OCR model was fine-tuned on over 150,000 PDFs representing 50,000 unique patents.
  • The delivered application was built for reliability, full compliance, and on-premises deployment.
  • The workflow converts patent documents from Markdown to HTML and finally into ST36 XML.

Evidence from the source

"400,000 pages/day throughput"
"<1% character recognition error rate"
"Lead time from up to 5 days down to a few minutes"
"The core of the solution included a 1B OCR model, specifically fine-tuned on over 150,000 PDFs, representing 50,000 unique patents."
"The team developed a sophisticated pipeline that successfully converts complex, multifaceted patent documents from Markdown, to HTML, and finally into the required ST36 XML format."
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 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 transparency8/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. Mistral

    European Patent Office customer story

    First-party
    https://mistral.ai/customers/epo/
    Source type
    Vendor-published customer story
    Published
    Apr 24, 2026
    Supports
    • Customer
    • 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

  • Published on source page Apr 24, 2026 · Mistral · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.