Designing and certifying consumer electronics is not easy. There are many compliance requirements, and if you ignore them early, you will pay for it later.
Imagine you finish your design and only during final testing you discover that a component fails EMC, dielectric strength, creepage and clearance, SAR, or junction temperature limits. You can sometimes swap a component. But what if you already have pre-orders, production tooling, and warehouse inventory worth millions?
This is why hardware is hard. Compliance cannot be an afterthought.
Compliance requirements must be integrated during the concept phase, ideally when you are writing your PRD. Late failures are expensive and often lead to redesigns, shipment delays, or even recalls.
A typical hardware development lifecycle, when done properly, looks like this:
PRD feature → System requirement → Compliance requirement → Design control → Verification method → Evidence artifact → Release gate
Below is a structured example of how tablet certification actually works. I have defined the entire lifecycle for a tablet design and certification.
Disclaimer: The design lifecycle could be different at different organizations, so this is just high level overview.
A Tablet Is a Bundle of Regulated Subsystems
A tablet is not a single regulated product. It is a combination of regulated subsystems.
- Radio, Wi-Fi, Bluetooth, sometimes LTE or 5G.
- Electrical safety: Protection against electric shock, fire, mechanical hazards, overheating, charging risks, and power supply faults.
- EMC: Emissions so it does not interfere with other devices, and immunity so it survives external interference.
- RF exposure
- SAR and EMF exposure requirements for cellular and some Wi-Fi and Bluetooth use cases.
- Battery: Lithium-ion battery safety and transport compliance.
- Environmental compliance: RoHS, REACH, WEEE, battery marking and recycling obligations.
- Energy efficiency and eco-design Where applicable: Cybersecurity and privacy. Increasingly formalized, especially in the EU and UK for connected devices.
Each of these areas has its own directives, regulations, and harmonized standards.
Step 1: Define Clear Product Requirements (PRD)
Product: Tablet
Define users:
- Kids
- Adults
- Senior citizens
User definition affects risk assessment, warnings, surface temperature limits, mechanical strength, and labeling requirements.
Define sales regions early:
- United States
- European Union
- United Kingdom
- Other regions if applicable
Region selection directly determines which regulations apply.
Step 2: Create Product and System Requirements
These are functional and performance requirements.
Examples:
PR1:**** Screen size shall be 12 inch class display PR2: Battery life shall be minimum 8 hours under defined use profile PR3: Weight shall be 700 g ± 10 g PR4: Charging time shall be 0 to 90 percent within 30 minutes PR5: Battery type shall be lithium-ion PR6: Device shall support Wi-Fi, Bluetooth, optional cellular PR7: Tablet shall include touchscreen, speaker, microphone, camera PR8: Device shall charge via USB Type-C from 100 to 240 VAC external adapter PR9: Enclosure shall include metallic frame
Then create more granular technical requirements (TR):
- Exact battery voltage, capacity, chemistry, and supplier
- Charger output voltage, current, power class
- PCB creepage and clearance distances
- Antenna type and placement
- Camera module voltage and current
- Frame material grade and coating
- Thermal interface material specifications
- Maximum internal and external temperatures
- Drop performance requirements
This technical breakdown is critical because standards will apply at this level, not at the marketing feature level.
Step 3: Identify Applicable Regulations and Standards
United States
Requirements are split by domain.
Electrical safety- Certification by a Nationally Recognized Testing Laboratory such as UL or ETL is typically required for market acceptance.
Applicable standard:
Safety:
UL 62368-1 for audio, video, and ICT equipment
Battery
- UL 2054 for battery packs
- UL 1642 for lithium cells
- UN 38.3 for transport
RF and EMC- Regulated by the Federal Communications Commission.
Applicable regulations:
- FCC Part 15 for unintentional and intentional radiators
- FCC Part 22, 24, 27 depending on cellular bands
- SAR testing under FCC OET requirements
Carrier approvals may also be required for cellular devices.
European Union
CE marking is mandatory before placing the product on the EU market. CE marking means you declare compliance with all applicable EU directives and regulations.
For a tablet with radio functionality, the key legislation includes:
Radio Equipment Directive 2014/53/EU This is the primary directive for radio-enabled tablets. It covers:
- Safety
- EMC
- Efficient use of radio spectrum
Harmonized standards typically include:
- EN IEC 62368-1 for safety
- EN 301 489-1 for EMC general requirements
- EN 301 489-17 for Wi-Fi and Bluetooth
- EN 301 908 series for LTE
- EN 300 328 for 2.4 GHz wideband transmission systems
- EN 301 893 for 5 GHz RLAN
- EN 62311 or EN 62479 for RF exposure assessment
- EN 50566 or EN 62209 series for SAR
EMC Directive 2014/30/EU Applies if radio is not covered fully under RED, but for radio equipment most EMC aspects are under RED.
Low Voltage Directive 2014/35/EU For radio equipment, electrical safety is handled under RED Article 3.1(a), but EN IEC 62368-1 is still used.
RoHS Directive 2011/65/EU Restriction of hazardous substances.
Harmonized standard:
- EN IEC 63000 for technical documentation
REACH Regulation Substance control and SVHC communication under Article 33.
WEEE Directive 2012/19/EU Producer registration, marking, recycling responsibility. Not a product test directive.
Battery Regulation (EU) 2023/1542 Replaces the old Battery Directive. Includes marking, labeling, sustainability, and future carbon footprint requirements.
Eco-design This may apply and is basically about making your product eco friendly.
Cybersecurity Under RED delegated acts, cybersecurity requirements are becoming mandatory for certain radio equipment. Standards such as EN 303 645 are commonly referenced. EN 18031 series will apply once harmonized.
Step 4: Extract Compliance Requirements Into Engineering Requirements
You must read applicable standards and extract safety requirements (SR) into your internal compliance requirement document.
Examples:
SR1: Surface temperature of accessible parts shall not exceed limits defined in EN IEC 62368- 1 under normal and fault conditions. SR2: Creepage and clearance distances shall meet minimum requirements for 250 VAC working voltage. SR3: Device shall pass dielectric strength test per EN IEC 62368-1. SR4: Device shall comply with radiated and conducted emissions limits per EN 301 489-1. SR5: RF output power shall comply with EN 300 328 limits. SR6: Battery pack shall comply with UN 38.3 transport requirements.
These are no longer abstract compliance statements. They become design inputs.
Step 5: Create a Verification and Validation Plan
For every requirement, define:
- Verification method
- Test level
- Acceptance criteria
- Test setup
- Equipment used
- Responsible engineer
- Evidence artifact
Verification methods may include:
- Inspection
- Analysis
- Test
- Simulation
Standards often define test conditions such as ambient temperature, humidity, voltage tolerances, and fault conditions. Your validation plan must align with these.
Step 6: Perform Internal Pre-Compliance Testing
Before going to a certification lab, you should perform:
- Pre-compliance EMC scans
- Thermal measurements
- Dielectric strength tests
- Functional fault injection tests
- SAR pre-check simulations
Document everything:
- Who performed the test
- Date and environmental conditions
- Equipment calibration status
- Raw data
- Photos and setup diagrams
For CE marking, self-declaration is possible if harmonized standards are fully applied and complied with. However, for the US, NRTL listing requires testing by an accredited lab.
Step 7: Engage Testing Labs Early
Testing labs have long lead times. Book slots early, often many months in advance.
Labs may provide:
- Pre-test design reviews
- Feedback on common failure modes
- Clarification on interpretation of standards
Testing may take weeks. If a test fails, you may need to redesign, build new samples, and re-test. This can significantly delay launch.
What Happens When Testing Fails
Failures are common.
Typical failure areas:
- Radiated emissions
- Conducted emissions
- SAR
- Dielectric strength
- Creepage and clearance
- Thermal runaway or excessive surface temperature
If a component exceeds its temperature rating, you must determine whether:
- The component batch is defective
- The design is pushing it beyond limits
- The airflow or enclosure design is insufficient
You may need to:
- Redesign
- Add shielding
- Change power architecture
- Reduce current
- Change suppliers
- Modify firmware to reduce RF duty cycle
These changes can cascade. A thermal fix may affect mechanical design. A shielding fix may affect antenna performance. A battery change may affect certification scope.
In extreme cases:
- PRD requirements may need to change
- Certain user groups may be excluded
- Might lead to reduced rating. e.g. reduced IP rating if test failed.
- Market launch may be staged by region
Risk Management and Failure Analysis
While consumer electronics typically do not require IEC 61508 or ISO 13849 functional safety processes, structured risk assessment/management is still performed.
Under EN IEC 62368-1, hazard-based safety engineering is applied. Manufacturers perform:
- Hazard identification
- Fault condition analysis
- Thermal and fire risk assessment
In addition, companies often use:
- FMEA at system and PCB level
- Reliability analysis
- MTBF estimation
- HALT and HASS testing
These are not always legally mandated, but they are industry best practice.
Final Stage: Technical File and Declaration
For CE marking, you must compile a technical file containing:
- Product description
- Schematics and PCB layout
- Bill of materials
- Risk assessment
- Test reports
- Standards applied
- User manual and labeling
- Declaration of Conformity
The Declaration of Conformity must list applicable directives and harmonized standards.
Only after this can the CE mark be affixed and the product placed on the EU market.
Final Thought
Certification is an engineering discipline that starts at concept stage. If compliance is treated as a checkbox at the end, failures will cost you time and money. If compliance requirements are embedded into PRD, system design, and verification planning from day one, certification becomes a structured process instead of a gamble.
This is why planning early is not optional. It is part of building hardware the right way. I hope you enjoyed reading this and when you build your next hardware, this could be useful.
