Analytics, AI, and How to Read Our Data

yoUPC is a work in progress — and that is by design. We are building this platform together with the people who use it. This post covers what has changed since our last update, how AI fits into what we do, and what to keep in mind when working with our data.

Where We Are

As of April 2026, yoUPC tracks:

• 1,793 decisions and orders from the UPC, fully searchable
• 1,512 cases with procedural metadata
• 554 patents linked to cases and judgments
• 147 judges
• 2,500+ citations between decisions, extracted and classified

These numbers grow as the UPC publishes new decisions and as we improve our data pipeline. All data is sourced from official UPC publications and enriched through a combination of automated processing and manual review.

New: UPC Analytics

We have rolled out an analytics suite at youpc.org/analytics. The hub brings together data across cases, judgments, patents, and judges — with interactive charts and cross-filtering.

What you can explore:

• Court activity — filings and decisions per division, broken down by year, type, and technology area
• Patent landscape — IPC classification treemap showing which technology sectors see the most litigation, with drill-down from section to subgroup level
• Top litigants — the most active claimants and defendants across the UPC

All charts are interconnected. Clicking a filter in one chart updates every other chart on the page. This is an early version — we are actively adding new dimensions and improving the visualizations based on what users find useful.

New: UPC Graph

The UPC Graph is an interactive network visualization. Starting from any judgment, case, patent, law provision, judge, or party, you can explore the web of relationships: which decisions cite each other, which cases share judges or patents, and how the UPC's case law is interconnected.

The graph currently maps over 53,000 relationships, including:

• Judgment citations — which decisions cite, follow, distinguish, or refer to each other
• Case relationships — appeals, counterclaims, related proceedings, consolidations
• Patent links — which patents are at issue in which cases and decisions
• Judicial assignments — who decided what

This is one of the features we are most excited about — and one where your feedback matters most. What connections would be most valuable to you?

How We Use AI

We use AI extensively in building and running yoUPC — for generating parts of this website, transforming court decision PDFs into structured text, automated translations, suggesting keywords, and powering semantic search through embeddings.

We are doing our best to make good use of these new tools while not contributing to slop. Where AI has touched content, we highlight it with a robot emoji so you can tell which is which.

Reading Our Data: What to Keep in Mind

We want our data to be genuinely useful. That means being upfront about where it stands today.

The data is not complete. The UPC publishes most decisions on its main overview page, but some are only available as part of individual case documents. We source decisions from the main overview only, so our database does not include every decision the court has issued. Some entries may also have incomplete metadata. We cover a large share of published UPC output, but this is not an official or exhaustive record.

AI-processed content may contain errors. Summaries might miss nuance. Citation extraction might produce false positives or miss references. Translations are machine-generated. Always check the original decision.

Analytics reflect the data we have. Court activity charts and citation counts are only as good as the underlying data. Where data is incomplete, the numbers will be too.

This is not legal advice. yoUPC is a research tool. It is designed to help practitioners find and understand UPC case law more efficiently — not to replace reading the original decisions and forming your own legal judgment.

For the full legal disclaimer, see our Legal & Privacy page.

Growing Together

yoUPC is built for the UPC practitioner community. We are a very small team, and this is still early days. If you spot an error, have an idea for a feature, or simply find something confusing — we want to hear about it. Reach out at mail@youpc.org.

Thank you for being part of this.