How we research, write and update our work
A guide about a European rule is only useful if it’s right and current. Here’s how we choose topics, check facts and keep pages up to date, so you can judge our work for yourself.
How we choose topics
We start with the questions U.S. product teams actually face. What does this rule mean for our firmware? How do we set up a vulnerability process? What should we ask an outside firm? We look at what readers ask us and what people search for. Then we favor topics where clear engineering help is hard to find.
We cite primary sources
For laws, deadlines and standards, we cite primary sources: the legal text itself and the bodies that publish or apply it, such as EUR-Lex, the European Commission, ENISA and the standards organizations.
We summarize standards in our own words. We never copy them or post copies of them.
Everything is dated
Each page shows when it was published and when it was last updated. Pages about rules or standards also carry a "not legal advice" note near the top. Proposals are labeled as proposals until they become law.
How we use AI tools
AI tools help write our pages. Each page says "Written with the help of AI tools."
Our tools show their method
Each tool explains its method, links its sources, and shows a version number and a "last updated" date. You don’t need to give us your email to see your results.
Firms we work with stay out of our research
We also offer optional introductions to engineering firms we work with. If you’re introduced to a partner firm and hire them, that firm may pay us a referral fee. Those firms don’t suggest topics, write drafts or sign off on findings. Our comparisons are dated, built from public documents, and they never rank firms. We don’t write about firms we work with by name.
When we get it wrong
We fix errors in the open and log them. Our corrections policy explains how.