The Hidden Dependencies Between CE, FCC, and UKCA Requirements

Regulations are not isolated requirements. They are interconnected systems that evolve over time. Teams that treat CE, FCC, and UKCA as three separate checklists tend to discover the connections between them at the worst possible moment.

Three frameworks that look independent and are not

A connected hardware product sold across the EU, the US, and Great Britain is subject to three regimes. In the EU, radio equipment falls under the Radio Equipment Directive, 2014/53/EU. In the US, the FCC regulates radio frequency emissions under 47 CFR Part 15. In Great Britain, since 1 January 2021, the Radio Equipment Regulations 2017 apply under the UKCA mark, enforced separately from the EU regime.

On paper these are distinct legal instruments with distinct marks and distinct declarations of conformity. In practice they share a great deal of underlying technical substance, and that shared substance is exactly where the dependencies hide.

Where the connections actually live

The clearest example is the relationship between the EU and UK regimes. When the UK left the EU framework, it transposed the existing requirements into domestic law. UK Designated Standards are, at present, largely identical to EU harmonised standards, and a single test campaign frequently supports both CE and UKCA marking. That is the dependency: a change in an EU harmonised standard has a direct bearing on the UK position, because the two currently track each other.

But the same source also carries the warning that matters most. UK Designated Standards are largely identical to EU harmonised standards today, but may diverge over time. A team that assumes permanent equivalence is building on an assumption that the regulators have explicitly reserved the right to break. The dependency is real, and it is also unstable.

The EU and US regimes connect differently. Both regulate the same physical behaviour, radio frequency emissions, but through different limits, different test methods, and different conformity routes. A device engineered to one is not automatically compliant with the other, yet the underlying engineering decisions, shielding, layout, antenna design, affect performance against all of them at once. A change made to pass one can move a product closer to or further from the others.

Why a checklist cannot capture this

A checklist treats each requirement as a standalone box to tick. It has no way to represent the fact that a UK requirement is derived from an EU one, that an EU harmonised standard and a UK designated standard currently share content, or that a single design change propagates across all three regimes. The relationships exist whether or not the tool models them. If the tool does not, the engineer has to hold the dependency graph in their head, and that is where things get missed.

The Crado perspective

This is the case for modelling compliance as a structured system rather than a set of documents. Crado represents frameworks, standards, and the relationships between them as a knowledge graph, so that a dependency between a UK designated standard and its EU counterpart, or a shared limit across regimes, is explicit rather than implied. When something changes, the affected requirements can be identified rather than rediscovered late. The aim is to make the connections between CE, FCC, and UKCA visible at the point of design, not at the point of test failure.

Key takeaways

• CE (2014/53/EU), FCC (47 CFR Part 15), and UKCA (Radio Equipment Regulations 2017) are distinct regimes with overlapping technical substance.

• UK Designated Standards are currently largely identical to EU harmonised standards but may diverge over time.

• A single engineering decision can affect a product's standing under all three regimes at once.

• Checklists hide these dependencies; a structured model makes them explicit.

Want to see the dependencies in your target markets before you commit a certification pathway? Request an enterprise demonstration.