About the data

EU Tracker holds every main vote the European Parliament has taken since its term began on 16 July 2024: how every member voted, by name, by political group and by member state. The chamber has 720 seats. This page says where that comes from, how complete it is, and what has been done to it.

Where the votes come from

When the Parliament takes a recorded vote, it registers who voted for, who voted against and who abstained, member by member, and publishes that register on its open data portal. That register is the source. Everything here derives from it.

Four things, all published by the Parliament at data.europarl.europa.eu, are all this project reads:

An automated job reads them during each sitting and again each night. Whether a text carried is published later than the votes themselves, so a same-day import states the result as derived from the totals, and the later run replaces it with the Parliament's own.

How complete this is

Checked on 24 August 2026, vote by vote, against the Parliament's own record of every sitting of this term:

So every vote on a text for which the Parliament publishes individual ballots is here, and every tally matches theirs. The remaining 32 are votes the Parliament records without publishing who voted how; there is nothing to hold. The check is a script in the repository, it runs monthly, and its result is written to data/reference/coverage.json — so this table is a checked number rather than a claim.

Amendment votes — the other 5,212 — are deliberately not imported. A plenary produces hundreds, almost all procedural, and importing them would bury the decisions a reader came for. The importer can take them on request.

What has been done to it

• Nothing has been interpreted. A member state is coloured by where most of its delegation voted, which is arithmetic. There is no scoring, ranking, or judgement of members, groups or countries anywhere in this project.
• Only main votes are imported. A plenary produces hundreds of roll calls, mostly on amendments. The archive keeps the vote on each text as a whole; the importer can take everything with one flag.
• Identities are stored once. Each vote records pairs of member id and position rather than repeating names, which is why a five-year term is about 100 MB of static files rather than 0.9 GB, and why the site costs nothing to run.
• Every record is checked before it is published. A validator refuses records whose ballots name members the directory does not know, whose group totals do not add up, or whose sources are missing.

How to check it, and how to correct it

Every record is a JSON file in the repository, with its sources inside it. Nothing is edited silently: a correction is a commit, visible in the history. If you find an error, open an issue against the repository.

Political group marks

Each political group is shown by its own mark, as that group publishes it. The Parliament does not publish them: ten of its pages were searched — every member page, the members' directory and its search, the pages on the political groups, and the election results site — and they carry members' portraits, the Parliament's emblem and interface icons, nothing else. So each mark comes from that group's own site, out of its own header, and the exact address every file was taken from is recorded in assets/groups/sources.json.

These are the groups' trademarks, used here to identify the groups themselves — the ordinary use of a mark, and the reason each row can be read at a glance. Nothing is recoloured, cropped or redrawn. A group whose mark has not been found, and the non-attached members, who are not a group at all, carry instead a tile in the colour that group is conventionally drawn in on a seat chart; those colours are approximations kept in one place in the code, not official brand values.

The portraits

Every member's photograph is the official portrait the Parliament publishes, taken from the address its own record of that person gives. Copies are kept here rather than loaded from the Parliament on every visit: a page showing seven hundred members would otherwise send seven hundred requests to their servers, and a portrait that is part of a record should not vanish when a file is renamed at the source. They are refreshed monthly.

© European Union, europarl.europa.eu — reused under the Parliament's reuse notice, which allows reproduction with the source acknowledged. Where the Parliament has published no portrait, the member's initials appear on the colour of their political group instead.

How to cite it

Every vote has its own address: open the vote and use Copy link. That address opens the same record for anybody, so it can go in a footnote or a message.

For a published piece, cite the Parliament rather than this site — the vote is theirs. A form that works:

European Parliament, vote of 9 July 2026 on the establishment of the digital euro (procedure 2023/0212), via EU Tracker, volters-cell.github.io/We-Volt, consulted on 27 August 2026.

If a figure here disagrees with the Parliament's own, theirs is right and this is a bug: the links on every record go straight to their record of the same vote, and an issue gets it fixed.

Licence

• Code: AGPL-3.0-or-later. Copy it, change it, run your own — and publish your changes under the same licence. Section 13 is the one that matters for a website: anyone running a modified version where other people can reach it has to offer those people their source. Taking this site, renaming it, and keeping the changes is the one thing the licence does not allow.
• Data authored here: CC BY 4.0.
• The votes themselves: the Parliament's public record, reused under its own reuse notice. Not ours to license, and nobody needs our permission to read them.
• Boundaries: public-domain Natural Earth geometry, simplified for display only. They imply no position on any border.
• The political groups' marks and the Volt wordmark are their owners' trademarks, shown to identify them. See NOTICE.

<iframe 
  src="https://volters-cell.github.io/We-Volt/embed.html?vote=VOTE_ID" 
  width="100%" 
  height="500" 
  frameborder="0" 
  allowfullscreen></iframe>