Digital Design / Services
EU wallet tracker: building and checking a public data product
Digital Design · owned project. This is our own public data product, not a third-party client endorsement. Inspect the live tracker and read the usability study.
What shipped
The recorded 8–17 October 2026 delivery period covered 39 scoped releases, about 62 pages, a five-pillar country scorecard, two interactive maps and open data. The record reports about 1,290 file uploads. These are delivery records for that period, not current traffic or commercial results.
A separate check of the live result
Each release had a brief, a defined set of files, upload checks and a live browser review. Design and checking were kept separate from the build so a passing test did not end the review.
Lesson one: passing checks can miss broken images
Seven acceptance tests passed on a company-map release while country flags still appeared as broken images. A live browser review found a missing image attribute. The recorded fix followed in about 25 minutes; later explorer checks included proof that images rendered.
Lesson two: two releases can disagree
A scorecard update and a company-map update used different grades. Each release passed its own checks, but the live comparison found fourteen countries out of step. The build was changed to reject grades that differ from the shared data file.
Source discipline
The published account records 743 imported claims and 79 published as facts on 8 October. Company-country research narrowed 162 leads to 18 accepted associations, with 11 confirmed in a separate check on 17 October. A company-country flag needs a first-party source naming both. Leads are kept distinct from accepted facts.
What the checks support
The dated release record reports mobile performance scores of 0.92–0.99 on five key pages, no script errors across 132 page loads and no mismatches across about 2,500 compared values. Those are bounded checks of those releases. They do not prove universal accuracy, uptake or conversion.
What this means for a project
Small releases make it easier to identify what changed and fix a problem quickly. Source checking and an independent look at the live product remain essential even when automated checks pass.