Foreword – Why ScopeRight Was Founded

Why does the greatest uncertainty arise long before the first laboratory test?

When companies think about product compliance, they often think of testing laboratories, certifications, or the CE marking. In reality, however, the most critical part of a successful compliance project begins much earlier. Long before the first test sample is shipped or a laboratory is contacted, countless regulatory questions need to be answered. It is during this early stage that the greatest uncertainties arise—and, at the same time, where the greatest opportunities exist to reduce costs, shorten timelines, and minimize project risks.

ScopeRight was founded by two TIC professionals, each with nearly 20 years of experience in sales, project management, and testing, together with an experienced software engineer specializing in structured decision logic and scalable software systems. Throughout our careers, we have supported manufacturers from a wide range of industries through national and international testing and certification projects. Despite working with different products, technologies, and markets, one observation remained remarkably consistent.

The biggest challenge is rarely the certification itself.

The biggest challenge is knowing how to get there.

Many manufacturers develop technically outstanding products, yet at the beginning of a project they often lack regulatory clarity. Which directives and regulations apply? Which standards are actually relevant? Which tests are required? Which technical documentation must be prepared? Can existing test reports be reused? And how do the requirements change when a product is intended not only for the European market but also for North America, Japan, Australia, or dozens of other countries?

There is rarely a single source that answers all of these questions.

Testing laboratories play an essential role in evaluating products and demonstrating compliance. However, their primary focus is naturally centered on the testing and certification services they provide. The structured preparation that comes before testing—understanding regulatory requirements, defining the actual compliance scope, planning the certification strategy, and estimating project effort—often remains the manufacturer’s responsibility.

This is exactly the gap we set out to close.

ScopeRight was not founded to become another testing laboratory or traditional consulting company. Our vision was to create an independent platform that supports manufacturers at the earliest stages of product development by making regulatory knowledge structured, accessible, and actionable. By combining decades of practical TIC experience with intelligent software, we help manufacturers make informed decisions before investing significant time and budget in testing and certification activities.

Our approach is deliberately independent. We are not driven by the goal of selling more testing services or creating unnecessary regulatory complexity. Instead, our mission is to give manufacturers the transparency they need to understand their compliance obligations before entering the certification process. When companies know which requirements apply—and why—they can make better engineering decisions, avoid unnecessary costs, and approach laboratory testing with confidence rather than uncertainty.

We firmly believe that regulatory expertise should not exist exclusively outside an organization. It should become part of every manufacturer’s product development strategy. Companies that understand the regulatory landscape from the beginning are better equipped to develop compliant products, reduce project risks, and accelerate market access around the world.

This guide was written with exactly that philosophy in mind. It walks through the complete compliance journey—from the initial product concept and regulatory assessment to compliance scoping, testing strategy, technical documentation, and global market access. Along the way, it demonstrates how structured processes and modern software can transform compliance from a reactive obligation into a strategic advantage.

Because successful compliance does not begin in the laboratory.

It begins with making the right decisions—long before a product ever reaches one.

1. Compliance Starts Long Before the First Test

When does compliance actually begin?

One of the most common misconceptions in product development is that compliance only becomes relevant once a product is fully developed and ready to be sent to a testing laboratory. In reality, this mindset is responsible for countless project delays, unnecessary costs, and late design changes that could often have been avoided through better preparation.

Compliance does not begin with an EMC test, a radio performance measurement, or the creation of a Declaration of Conformity. It begins the moment the first technical decisions are made.

From the earliest concept phase, engineering choices shape the regulatory path a product will ultimately follow. Selecting a wireless module, choosing a power supply, designing the enclosure, or defining the target markets all have a direct impact on which regulations apply and which testing and certification activities will eventually be required.

At first glance, these decisions appear to be purely technical.

In reality, many of them have significant regulatory consequences.

A manufacturer developing a product exclusively for the European market faces a very different regulatory landscape than one planning a global product launch. Likewise, adding Bluetooth®, Wi-Fi, or another wireless technology immediately expands the project’s compliance scope. Radio testing, EMC evaluations, RF exposure assessments, and country-specific approval requirements suddenly become part of the certification process. When these implications are only discovered shortly before testing begins, project schedules are disrupted, budgets increase, and product launches are often delayed.

This is why compliance should never be treated as the final milestone of product development. It should be considered an integral part of the development process from the very beginning.

This does not mean engineers need to master every applicable standard before development starts. What matters is gaining early visibility into the regulatory landscape surrounding the product. That visibility enables realistic project schedules, reliable budgeting, and engineering decisions that reduce the likelihood of costly surprises later in the project.

Another common misconception is that compliance is simply about satisfying legal requirements. In reality, a successful compliance project extends far beyond meeting the minimum obligations of regulations and standards. It requires strategic planning across the entire product lifecycle. Which markets will the product enter? Which tests can be combined? Which test reports can be leveraged for approvals in additional countries? Which technical documentation should be prepared alongside product development? How might future hardware or firmware changes affect existing certifications?

Companies that wait until just before market launch to answer these questions often find themselves working under significant pressure. Engineering teams are forced to implement last-minute design changes, laboratories must accommodate urgent testing requests, and product launches are postponed by weeks—or sometimes even months.

Fortunately, many of these situations are entirely avoidable.

In our experience, certification projects rarely fail because regulatory requirements are exceptionally difficult. Far more often, problems arise because critical information is unavailable when important engineering decisions are made, or because regulatory planning begins only after the product design is largely complete.

For this reason, compliance should be viewed as a continuous process that accompanies product development from concept to market launch. The earlier regulatory requirements are understood, the easier they can be incorporated into engineering decisions. What is often perceived as a regulatory obligation instead becomes a structured and predictable part of the development process.

This philosophy is at the heart of ScopeRight. Rather than becoming involved only when a product is ready for laboratory testing, our goal is to provide manufacturers with regulatory clarity during the earliest stages of development. Companies that understand the compliance implications of their products from the beginning are able to make better technical decisions, reduce project risks, and plan certification activities with greater confidence.

Before directives, standards, and testing requirements can be determined, however, one fundamental question must first be answered:

What exactly is the product that needs to be assessed?

That is where the next chapter begins.

2. Understanding the Product

Why is understanding the product the foundation of every compliance assessment?

Before identifying applicable regulations, selecting standards, or planning testing activities, one fundamental question must be answered:

What exactly is the product that needs to be assessed?

Although this may seem obvious, it is one of the most underestimated steps in the entire compliance process. Many projects begin with questions such as, “Which standards apply to our product?” or “What testing is required for CE marking?” The reality is that these questions cannot be answered accurately without first understanding the product itself.

From a regulatory perspective, a product is far more than its name or technical specification. Two devices that appear almost identical may be subject to completely different regulatory requirements because of a single design decision. Adding a wireless module, selecting a different power supply, or changing the intended use may significantly alter the required testing, documentation, and certification strategy.

For this reason, every successful compliance project begins with a structured product assessment.

The first step is understanding the product’s intended purpose. What problem does it solve? Is it a standalone device or a component integrated into a larger system? Is it intended for industrial environments, commercial applications, healthcare, or consumer use? Will it be installed permanently, carried by users, or operated as portable equipment? The answers to these questions influence not only the applicable regulations but often determine which standards and test methods will eventually apply.

The technologies integrated into the product must also be carefully evaluated. Modern electronic devices frequently combine multiple communication interfaces such as Bluetooth®, Wi-Fi, cellular connectivity, NFC, UWB, or proprietary radio technologies. Every wireless technology introduces additional regulatory considerations, while interactions between multiple radios can further influence the testing strategy and future global approval requirements.

Power architecture is another critical factor. Is the product powered directly from the AC mains, supplied by an external power adapter, operated by rechargeable batteries, or powered solely through USB? Does it include charging functionality or battery management systems? These seemingly straightforward design choices may introduce additional safety requirements, affect EMC testing, or require compliance with product-specific standards.

Another area that is frequently overlooked is product variants.

Manufacturers rarely develop a single product. More often, they create an entire product family with different housing designs, wireless configurations, regional versions, or performance levels. From an engineering perspective, these differences may appear relatively small. From a regulatory perspective, however, they can significantly influence the certification strategy. Identifying product variants early allows manufacturers to determine which test results can potentially be reused and which configurations require separate evaluations.

Target markets must also be defined as early as possible. Is the product intended only for the European Union, or will it also be marketed in the United States, Canada, Japan, Australia, the United Kingdom, or other international markets? This decision has a direct impact on regulatory planning from the very beginning. Certification requirements vary considerably around the world, and global market access should never become an afterthought once CE compliance has already been completed.

Future product evolution should also be considered during this stage. Many products receive firmware updates, new hardware revisions, additional wireless functionality, or expanded software features throughout their lifecycle. Understanding how these future changes may affect regulatory compliance helps manufacturers design products that remain easier to maintain and certify over time.

In practice, the information required for a complete compliance assessment is rarely available in one place. Engineering teams understand the technical design. Product managers define the intended functionality. Sales teams identify target markets, while project managers oversee development timelines. Only by bringing all of this information together can a complete regulatory picture emerge.

This is exactly why every assessment within ScopeRight begins with a structured product analysis. Rather than immediately suggesting standards or testing activities, the platform first guides manufacturers through the collection of all compliance-relevant product information. This creates transparency from the very beginning and establishes a reliable foundation for every subsequent step—from identifying applicable regulations and performing compliance scoping to planning testing activities and preparing for global market access.

Only after the product has been fully understood can the next critical question be answered:

Which regulatory requirements actually apply?

3. Identifying Regulatory Requirements and Standards

How do you determine which regulatory requirements apply to a product?

Once the product has been fully understood, the next critical step is identifying the applicable regulatory requirements.

Many manufacturers begin by asking, “Which standard applies to our product?” While this seems like a logical starting point, it is often the wrong question. Standards represent only one part of the regulatory framework. Before selecting individual standards, manufacturers must first determine which legal requirements actually apply to the product.

Depending on the product’s intended purpose, integrated technologies, and target markets, different directives, regulations, and national requirements may apply. A simple electronic device is subject to a different regulatory framework than a wireless product, a medical device, or industrial equipment. Once products are introduced into international markets, country-specific regulations further increase the complexity.

Only after this regulatory foundation has been established can the appropriate harmonized standards, technical specifications, or testing procedures be identified.

It is equally important to understand the role that standards actually play.

Many manufacturers assume that standards are legal requirements. In reality, standards describe recognized technical methods for demonstrating compliance with the essential requirements of applicable regulations or directives. Following harmonized standards provides a well-established path toward demonstrating conformity, but standards themselves are only one component of a much broader compliance process.

Selecting the correct standards depends on numerous factors. Even seemingly minor design changes can introduce additional standards or entirely different testing requirements. A new wireless interface, a modified power architecture, or a different product classification may significantly change the applicable regulatory framework. There is rarely a universal answer to the question, “Which standard applies to our product?” The correct answer can only be determined after evaluating the complete set of product characteristics.

Another important consideration is that regulatory requirements are constantly evolving.

New standards are published, existing editions are revised, transition periods expire, and regulatory authorities introduce new requirements. Manufacturers who rely on outdated information risk planning certification projects based on requirements that are no longer valid.

This is particularly important for products with long development cycles. It is not uncommon for twelve to twenty-four months to pass between the initial product concept and market launch. During that time, applicable standards may change, regulatory deadlines may expire, or entirely new legislation may come into force. If these developments are discovered only shortly before certification, engineering work may need to be revisited, testing plans revised, or additional evaluations performed.

For this reason, monitoring regulatory changes should never be treated as a one-time activity. It should be considered an ongoing part of every product’s lifecycle.

This is one of the reasons we developed the ScopeRight Standards Database. Instead of searching through multiple sources, manufacturers have access to a centralized knowledge base covering applicable standards, regulatory developments, and ongoing updates. The objective is not simply to provide information, but to help companies stay informed as regulatory requirements evolve throughout the lifetime of their products.

Of course, even the most comprehensive standards database cannot determine compliance on its own. It provides the necessary regulatory information, but identifying the requirements that actually apply to a specific product always depends on a structured assessment of the product itself, its intended use, integrated technologies, and target markets.

Once the applicable regulations and standards have been identified, the next question naturally follows.

Knowing which requirements apply is only the beginning.

The real challenge is determining which tests, documentation, calculations, and evidence are actually required to demonstrate compliance.

This is where Compliance Scoping becomes the most important step of the entire compliance process.

4. Compliance Scoping – The Most Important Step of the Entire Project

How do you know which tests are actually required?

Once the applicable regulatory requirements and standards have been identified, the next critical question arises:

Which tests are actually necessary?

This is where uncertainty begins for many manufacturers.

A common approach is to contact several testing laboratories and request quotations. More often than not, the responses differ significantly. One laboratory recommends additional testing, another considers it unnecessary. Some quotations cover only laboratory testing, while others include certification activities, technical assessments, or additional engineering support. As a result, manufacturers are often left wondering which scope is actually required.

In most cases, these differences do not mean that one laboratory is right and another is wrong.

The real issue is that the product has not yet been fully defined from a regulatory perspective.

Without complete information about the product, its technologies, intended use, and target markets, assumptions must be made. Different assumptions naturally lead to different testing strategies, different quotations, and different project expectations.

This is precisely why we consider Compliance Scoping to be the single most important phase of the entire compliance process.

Compliance Scoping is the structured process of determining the complete regulatory scope of a product before any testing begins. Its purpose is to translate regulatory requirements into a clear and practical certification plan. It is not simply about identifying applicable standards—it is about determining exactly what evidence must be generated to demonstrate compliance.

A comprehensive compliance scope answers questions such as:

• Which laboratory tests are required?
• Which tests are not required?
• Which technical assessments must be performed?
• Which documentation needs to be prepared?
• Are calculations or risk assessments required?
• How many test samples will be needed?
• How long is the certification project likely to take?
• What additional requirements arise when the product will be marketed internationally?

Only after these questions have been answered does the true scope of a certification project become visible.

In our experience, this is also the stage where the majority of project costs are determined. An incomplete or inaccurate compliance scope frequently leads to additional testing being identified halfway through the project. Laboratory schedules must be revised, engineering changes become necessary, project budgets increase, and product launches are delayed.

A structured compliance scope creates transparency for everyone involved.

Manufacturers gain a realistic understanding of the work ahead. Testing laboratories receive complete and consistent project information. Quotations become easier to compare because they are based on the same assumptions, and the likelihood of unexpected testing requirements is significantly reduced.

This philosophy led us to develop the ScopeRight Compliance Scoping Tool.

Instead of presenting manufacturers with lengthy checklists or overwhelming collections of standards, the platform guides users through a structured assessment of every compliance-relevant product characteristic. It evaluates factors such as product functionality, integrated wireless technologies, power architecture, intended markets, and many other technical details that influence regulatory requirements.

Based on this information, ScopeRight generates a structured overview of the expected compliance scope, including applicable regulations, anticipated testing activities, and the overall certification effort. Manufacturers gain valuable regulatory clarity long before the first laboratory is contacted, allowing them to prepare projects with greater confidence and accuracy.

The objective is not to replace testing laboratories or regulatory experts.

Instead, the platform helps manufacturers enter discussions with laboratories fully prepared. When both parties work from the same regulatory foundation, certification projects become more predictable, communication becomes more efficient, and the risk of costly misunderstandings is greatly reduced.

For this reason, Compliance Scoping should never be viewed as a simple administrative task. It is the stage where the direction of the entire project is established. The better the preparation, the more predictable the timeline, budget, and certification process become.

Once the complete regulatory scope has been defined, attention can shift to the next challenge.

Knowing what must be tested is only part of the process.

The next question is equally important:

How do you transform that information into an efficient testing and certification strategy?

5. Developing an Effective Testing Strategy

How do you turn a compliance scope into a successful certification project?

Once the regulatory scope of a product has been defined, the focus shifts from identifying requirements to planning the certification project itself. Many manufacturers assume that the most difficult part is already behind them. After all, the applicable regulations are known, the relevant standards have been identified, and the required testing activities have been determined.

In reality, however, the success of a certification project depends largely on the testing strategy.

A testing strategy is much more than a list of required laboratory tests. It defines when testing should take place, in which order, under which conditions, and how each activity supports the overall certification plan. A well-developed strategy considers technical dependencies, engineering milestones, test sample availability, laboratory scheduling, and future international approvals. Its purpose is to ensure that every testing activity contributes efficiently to the final objective while avoiding unnecessary duplication of work.

This becomes particularly important for today’s connected electronic products. A single device may require EMC testing, radio performance measurements, electrical safety evaluations, RF exposure assessments, cybersecurity considerations, and additional country-specific approval activities. When these workstreams are planned independently, certification projects often become fragmented, resulting in duplicated effort, unnecessary costs, and avoidable delays.

Selecting the right testing laboratory is another key element of an effective strategy.

Although cost is naturally an important consideration, it should never be the only deciding factor. Laboratories differ significantly in their technical capabilities, accreditations, regulatory experience, available equipment, certification partnerships, and scheduling flexibility. A laboratory that is ideal for one project may not be the best choice for another. The decision should always be based on the specific technical and regulatory requirements of the product rather than on price alone.

A realistic project schedule is equally important.

One of the most common planning mistakes is overestimating the time spent inside the laboratory while underestimating the preparation required beforehand. Before a product can be tested, engineering teams typically need to finalize hardware revisions, freeze software versions, prepare technical documentation, manufacture representative test samples, and complete internal design reviews. Delays during these preparation stages frequently have a much greater impact on project timelines than the laboratory testing itself.

The availability of suitable test samples should also be considered early in the planning process. Certification projects are often postponed because prototype hardware changes shortly before testing or because production-representative samples are not available when laboratory time has already been reserved. Close coordination between engineering teams, project managers, and testing laboratories significantly reduces these risks.

For manufacturers planning international product launches, the testing strategy should extend beyond the initial certification. Decisions made during the first certification project often determine how efficiently approvals can later be obtained in additional countries. Identifying opportunities to reuse existing test reports, anticipating country-specific requirements, and planning future certifications early can substantially reduce both cost and time when expanding into global markets.

Another frequently overlooked aspect is communication.

Successful certification projects require close collaboration between engineering, product management, quality assurance, regulatory specialists, and testing laboratories. When these stakeholders work with incomplete or inconsistent information, misunderstandings become inevitable. Conflicting assumptions, duplicated work, and unnecessary project delays are often the result.

A structured testing strategy establishes a common foundation for everyone involved. Every stakeholder understands the project objectives, certification roadmap, current status, and next steps. As a result, technical decisions become easier to coordinate, project risks are identified earlier, and certification activities can be managed with far greater confidence.

For this reason, Compliance Scoping should never be viewed as the final planning activity. Instead, it provides the foundation upon which an efficient testing strategy is built. The more thoroughly this planning phase is completed, the more predictable the certification process becomes—from engineering through laboratory testing and ultimately to market approval.

Even the best testing strategy, however, cannot eliminate every technical risk.

The next question therefore becomes:

How can potential compliance issues be identified before they turn into costly failures during accredited laboratory testing?

6. Considering Compliance Throughout Product Development

Why are many compliance issues only discovered when they are the most expensive to fix?

Many manufacturers still treat compliance as the final step of product development. The product is designed, a prototype is built, and only then is it sent to a testing laboratory. If problems are identified during certification, engineering teams begin investigating the root cause and implementing corrective actions.

While this approach may seem reasonable, it often creates exactly the delays and costs that companies are trying to avoid.

The later regulatory requirements are considered during product development, the more expensive design changes become. A modification that might have required only a few hours during the concept phase can result in weeks of engineering work, new tooling, additional prototypes, or even a complete product redesign once development is nearly complete.

For this reason, compliance should not be viewed as a final verification step. It should be integrated into product development from the very beginning.

Many of the engineering decisions made during the early design stages have a direct impact on the certification process. Selecting a wireless module, for example, affects far more than wireless functionality. It influences radio testing requirements, antenna evaluations, RF exposure assessments, and future international approvals. Likewise, decisions involving power architecture, clock frequencies, PCB layout, grounding concepts, and enclosure design all influence how a product will perform during EMC and safety testing.

Mechanical design also plays a much greater role than many engineers initially expect. Material selection, cable routing, connector placement, shielding techniques, and component positioning can significantly affect a product’s electromagnetic behavior. Design changes that appear minor from a mechanical perspective may produce measurable differences during compliance testing.

As modern products become increasingly sophisticated, these interactions continue to grow in complexity. Today’s electronic devices often combine multiple wireless technologies, various power systems, displays, sensors, charging functions, and cloud-connected software services within a single product. Each of these technologies introduces its own regulatory considerations, while interactions between them can create additional compliance challenges that should be identified early in the development process.

Software has become equally important.

Firmware updates no longer affect only product functionality. They can also influence regulatory compliance. Changes to transmission parameters, power management, communication protocols, cybersecurity features, or radio behavior may impact existing certifications and require additional regulatory evaluation. Manufacturers should therefore consider from the outset how future software updates will be controlled, documented, and assessed throughout the product’s lifecycle.

Another critical success factor is collaboration across departments.

Engineering, product management, purchasing, quality assurance, and regulatory teams often work toward different objectives. Engineering focuses on innovation, project management concentrates on schedules and budgets, while compliance is frequently consulted only after major design decisions have already been made.

The most successful manufacturers take a different approach.

They integrate regulatory considerations directly into their product development process. New technologies are evaluated not only for technical performance but also for their regulatory impact. As a result, products are designed with compliance in mind from the beginning, making certification projects significantly more predictable and reducing the likelihood of costly redesigns later.

This is exactly where ScopeRight provides value. By helping manufacturers identify regulatory implications during the earliest stages of development, the platform gives engineering teams greater visibility into how technical decisions may affect future certification activities. Instead of discovering compliance issues during laboratory testing, potential risks can be identified, evaluated, and addressed while the product is still being designed.

This proactive approach reduces technical risk while providing greater confidence throughout the entire project. Engineering decisions become better informed, certification planning becomes more predictable, and unnecessary development iterations can often be avoided.

Even with careful planning and well-informed engineering decisions, however, no product is entirely free from technical risk.

Before entering an accredited certification program, one important question remains:

Can potential compliance issues be identified under realistic test conditions before formal laboratory testing begins?

7. Pre-Compliance – Identifying Problems Before They Become Expensive

Why should the laboratory be the first place where a product is tested?

Even with careful engineering and a well-planned compliance strategy, one important fact remains:

Until a product has been evaluated under realistic test conditions, its compliance performance is largely based on assumptions.

Many manufacturers encounter the same situation. Product development is complete, the technical documentation has been prepared, laboratory testing has been scheduled, and the market launch is already planned. Only once formal certification testing begins do unexpected issues emerge. Emissions exceed the permitted limits, radio performance does not meet expectations, or certain components behave differently under laboratory conditions than they did during development.

At this stage, even relatively small technical changes can become expensive.

The engineering effort required to resolve the issue is only part of the problem. Laboratory schedules must be rearranged, additional engineering resources become necessary, and product launches are often postponed by weeks. Repeat testing introduces additional costs, while project timelines become increasingly difficult to predict.

Many of these situations can be avoided through Pre-Compliance testing.

Pre-Compliance is not intended to replace accredited certification testing. Its purpose is to identify potential technical issues before they affect the formal certification process. It allows manufacturers to evaluate their products under conditions that closely resemble those of an accredited laboratory while design changes can still be implemented quickly and cost-effectively.

This approach is particularly valuable for EMC performance. Relatively small improvements to PCB layout, grounding concepts, shielding, cable routing, or power distribution can significantly influence the final test results. Discovering these opportunities before formal certification often saves considerably more time and effort than correcting them after a failed compliance test.

Wireless products benefit just as much from early technical evaluation. Antenna performance, transmitter characteristics, coexistence between multiple radio technologies, and RF exposure considerations can all be reviewed before entering the official certification process. This gives engineering teams the opportunity to optimize product performance without every modification triggering another formal certification test.

For this reason, Pre-Compliance should not be viewed as an additional expense.

It should be viewed as an investment in the success of the entire certification project.

The objective is not to achieve perfect results before formal testing. The objective is to significantly reduce the likelihood of unexpected failures once the product enters an accredited laboratory.

This philosophy is reflected in ScopeRight Premium.

As part of the Premium package, customers receive half a day of Pre-Compliance testing at our partner laboratory. The purpose is not to sell additional laboratory services or extend the certification process unnecessarily. Instead, it gives manufacturers the opportunity to evaluate their products under realistic test conditions, validate critical design decisions, and resolve potential issues before formal certification begins.

In our experience, this early evaluation often delivers significant value. Potential issues are identified while engineering changes remain manageable. Development teams gain greater confidence in their designs, project schedules become more predictable, and the transition into accredited certification testing is considerably smoother.

Of course, even a successful Pre-Compliance evaluation does not replace official certification.

Eventually, every product must enter an accredited laboratory and demonstrate compliance with the applicable regulatory requirements.

The next question is therefore straightforward:

What actually happens during accredited testing, and how can manufacturers prepare for it as effectively as possible?

8. Accredited Testing

What actually happens during accredited testing?

For many manufacturers, the day their product arrives at a testing laboratory represents the culmination of months—or even years—of development. Engineering decisions have been made, documentation has been prepared, prototypes have been built, and the regulatory scope has been clearly defined. The product is now expected to demonstrate that it complies with all applicable regulatory requirements.

Despite this preparation, accredited testing is still viewed by many companies as the most uncertain phase of the certification process.

Not because the test procedures themselves are unknown, but because many manufacturers are unsure what actually happens inside the laboratory and how they can prepare for the process most effectively.

A common misconception is that accredited testing simply involves connecting a product to test equipment and recording a series of measurements. In reality, every evaluation follows internationally recognized standards, documented procedures, and strictly controlled methodologies. The laboratory is not assessing whether a product has been engineered well or poorly. Its responsibility is to objectively determine whether the product demonstrates compliance with the applicable regulatory requirements.

For that reason, successful laboratory testing begins long before the product enters the test chamber.

The laboratory depends on complete and accurate technical information. This includes technical documentation, descriptions of operating modes, software and firmware versions, product configurations, supported accessories, and details about any product variants that may influence the evaluation. The more complete this information is, the more efficiently the testing process can be performed.

Providing representative test samples is equally important.

The products submitted for testing should reflect the final production version as closely as possible. Last-minute hardware modifications, unfinished firmware, or differences between submitted samples and the intended production design frequently result in additional engineering discussions, repeated testing, or unnecessary project delays.

Depending on the applicable regulations and standards, the product may undergo a variety of evaluations. These can include EMC testing, radio performance measurements, electrical safety assessments, RF exposure evaluations, or other product-specific investigations. While the individual procedures vary from one product to another, the objective always remains the same: to demonstrate, through objective evidence, that the product complies with the relevant regulatory requirements.

If a product does not achieve the expected results during testing, this should not automatically be viewed as a failed project.

Laboratory measurements provide valuable engineering information. They help identify where unexpected behavior occurs and allow development teams to understand the technical reasons behind those results. The speed with which these issues can be resolved often depends less on the measurements themselves and far more on how thoroughly the project was prepared beforehand.

In our experience, the greatest delays during certification are rarely caused by laboratory testing.

Much more frequently, projects are slowed by incomplete documentation, missing product information, inconsistent software versions, or design changes introduced shortly before testing begins. These issues often require additional clarification, updated documentation, or repeat evaluations—all of which consume valuable time.

This is why thorough preparation is one of the most effective ways to reduce certification risk.

Accredited testing should not be viewed as an obstacle or a final hurdle. It is the formal confirmation of the engineering work that has already been completed. Manufacturers who understand the regulatory requirements early, prepare their products carefully, and follow a structured certification strategy typically approach laboratory testing with significantly greater confidence and predictability.

Completing the laboratory evaluation, however, does not conclude the compliance process.

Successful test results alone are not sufficient to demonstrate conformity.

Every test must be supported by complete and well-structured technical documentation. That documentation ultimately demonstrates how compliance was achieved and becomes an essential part of every successful market approval.

9. Technical Documentation

Why is technical documentation just as important as laboratory testing?

When manufacturers think about certification, laboratory testing naturally receives most of the attention. Test reports, measurements, and certificates are often seen as the final proof that a product complies with regulatory requirements.

In reality, however, successful compliance depends on much more than passing laboratory tests.

Every compliance assessment must be supported by technical documentation that demonstrates why a product complies, how compliance was evaluated, and which evidence supports that conclusion.

Without proper documentation, even a successfully tested product may fail to meet its regulatory obligations.

Technical documentation is much more than a collection of files created shortly before market launch. It is the structured record of every regulatory decision made throughout the product’s development. It explains how the product was designed, which requirements apply, how compliance was demonstrated, and how future modifications can be assessed.

The exact contents of a technical file depend on the applicable legislation and the product itself. Nevertheless, most technical documentation includes a combination of product descriptions, design information, circuit diagrams, bills of materials, software information where applicable, risk assessments, laboratory test reports, user documentation, labeling information, and the Declaration of Conformity.

These documents should not exist independently from one another.

Together, they create the regulatory story of the product.

For example, a laboratory test report confirms that specific testing was successfully completed. The technical documentation explains why those tests were selected, how the product configuration was defined, and how the results support the applicable regulatory requirements. The Declaration of Conformity ultimately references this documentation as the manufacturer’s formal statement that the product complies with all relevant legislation.

One of the most common mistakes is treating documentation as an administrative task performed at the end of the project.

In practice, this often results in missing information, inconsistent product descriptions, outdated drawings, incomplete software records, or documentation that no longer matches the final product configuration. Correcting these issues shortly before market launch is frequently far more time-consuming than maintaining accurate documentation throughout development.

Documentation also plays an essential role long after certification has been completed.

Products continue to evolve throughout their lifecycle. Hardware revisions are introduced, firmware is updated, components become obsolete, and new market opportunities emerge. Every change raises an important regulatory question:

Does this modification affect the product’s compliance?

Without complete technical documentation, answering that question becomes significantly more difficult. Engineering teams may struggle to understand previous certification decisions, while regulatory assessments become slower and more uncertain.

Well-maintained documentation provides the opposite benefit.

It allows manufacturers to evaluate design changes efficiently, determine whether additional testing is required, support market surveillance requests, and prepare future certifications with significantly less effort. Rather than being a regulatory obligation, technical documentation becomes a valuable engineering resource throughout the product’s entire lifecycle.

For this reason, documentation should never be viewed as paperwork created for regulatory authorities.

It is the central record that connects engineering, testing, certification, and future product maintenance.

At ScopeRight, we believe documentation should be structured from the beginning—not assembled under time pressure just before certification. Throughout the platform, regulatory information is organized in a way that helps manufacturers build a complete understanding of their products and certification projects, making it easier to maintain consistency across technical decisions, compliance assessments, and future product updates.

Once testing has been completed and the technical documentation is in place, manufacturers are often ready to place their products on the European market.

For many companies, however, that is only the beginning.

How do you take a product beyond CE marking and prepare it for successful market access around the world?

10. From CE Marking to Global Market Access

Is CE marking enough to sell a product worldwide?

For many manufacturers, obtaining the CE marking represents the successful completion of their compliance project. The product meets the applicable European requirements, the technical documentation has been completed, and everything is in place to launch the product within the European Union.

For companies with global ambitions, however, CE marking is often only the beginning.

Every country has its own regulatory framework. While some markets recognize European test reports to a certain extent, others require national certifications, additional testing, product registrations, or approvals issued by local authorities. This is especially true for wireless products, where regulations governing frequency bands, transmission power, labeling requirements, and local representation can differ significantly from one country to another.

Many manufacturers underestimate this complexity.

A common scenario is that a product is initially developed only for the European market. Once it has been successfully launched, new business opportunities arise in countries such as the United States, Canada, Australia, Japan, South Korea, or the Middle East. International approvals then become urgent business requirements, even though many of the necessary regulatory decisions could have been considered much earlier during product development.

For this reason, a successful global market access strategy should not begin after CE marking has been achieved.

It should begin while the product is still being developed.

One of the most important questions is:

Which existing compliance evidence can be reused for other markets?

Many laboratory test reports can support certification activities in additional countries. However, this does not automatically mean that a product can be placed on every international market without further action. Depending on the country, manufacturers may need additional testing, national certifications, local documentation, product registrations, or approvals issued by domestic regulatory authorities. Some countries also require local representatives who are legally responsible for regulatory communication within that market.

Administrative procedures vary just as much as the technical requirements.

Some authorities provide fully digital approval systems, while others still require physical documentation or cooperation with local certification bodies. Processing times, certificate validity periods, renewal procedures, and application requirements differ considerably from one country to another.

For manufacturers, this leads to one important conclusion:

Global market access should be planned strategically—not managed country by country as new business opportunities arise.

Companies that identify their target markets early can align testing activities, technical documentation, and certification projects accordingly. Existing test reports can often be leveraged more effectively, duplicate work can be minimized, and international product launches can be completed significantly faster.

This is exactly why we developed the ScopeRight Global Radio Approvals (GRA) Module.

The GRA Module helps manufacturers plan international radio approvals by providing structured regulatory information for more than 200 countries and territories. It includes information such as national approval requirements, responsible regulatory authorities, local representative obligations, certificate validity periods, renewal processes, and country-specific regulatory considerations for wireless products.

Our objective is not to make international approvals appear simpler than they really are.

Our objective is to make them transparent.

By giving manufacturers access to structured regulatory information at an early stage, they can understand what each market requires, identify potential challenges before projects begin, and develop a global certification strategy that supports long-term business growth rather than reacting to regulatory obstacles one country at a time.

For companies planning international expansion, this approach transforms Global Market Access from a series of disconnected certification projects into a structured part of overall product strategy.

Obtaining regulatory approvals, however, does not mean a manufacturer’s responsibilities have come to an end.

Products continue to evolve. Firmware is updated, hardware components are replaced, standards are revised, and new regulations enter into force.

The final question therefore becomes:

How do manufacturers ensure that their products remain compliant long after they have been placed on the market?

11. Maintaining Compliance Throughout the Product Lifecycle

Why does compliance continue after a product has entered the market?

Many manufacturers view certification as the finish line of a development project.

Once the product has passed laboratory testing, the technical documentation has been completed, and the required approvals have been obtained, it is easy to assume that the compliance process is finished.

In reality, however, regulatory compliance continues for as long as the product remains on the market.

Modern electronic products rarely remain unchanged. Firmware is updated, hardware components become obsolete, suppliers change, new product variants are introduced, and additional features are added throughout the product’s lifecycle. At the same time, regulatory requirements continue to evolve. New standards are published, transition periods expire, and market surveillance authorities increasingly monitor products already available on the market.

Every technical modification raises an important question:

Does this change affect the product’s regulatory compliance?

The answer is not always obvious.

Some changes have little or no regulatory impact. Others may require additional engineering assessments, partial testing, updated documentation, or even a completely new conformity assessment. Replacing a passive component may have no measurable effect, while changing a radio module, antenna, enclosure, power supply, or firmware controlling wireless functionality could significantly influence the product’s compliance status.

Determining the regulatory impact of a design change requires an understanding of both the product and the applicable legislation.

For this reason, change management should always include a regulatory review—not only an engineering review. Compliance should become part of every design modification process, allowing potential issues to be identified before products are manufactured or released to customers.

Manufacturers must also monitor changes that originate outside their own organization.

Standards are revised regularly. Existing harmonized standards may be replaced by newer editions, transition periods eventually expire, and regulatory authorities publish updated guidance or introduce new legal requirements. Companies that fail to monitor these developments risk placing products on the market based on outdated assumptions.

Market surveillance represents another important aspect of post-market compliance.

Authorities may request technical documentation, Declarations of Conformity, laboratory reports, risk assessments, or additional information to demonstrate that a product continues to comply with the applicable legislation. Manufacturers should therefore ensure that all documentation remains complete, accurate, and readily accessible throughout the product’s commercial lifetime.

Effective compliance management is therefore not a one-time activity.

It is an ongoing process that combines engineering, quality management, regulatory monitoring, documentation control, and product lifecycle management into a single, structured workflow.

At ScopeRight, this long-term perspective has shaped the way we built the platform. Compliance information should not disappear after certification is complete. It should remain available throughout the entire product lifecycle, helping manufacturers evaluate design changes, understand evolving regulatory requirements, maintain consistent documentation, and prepare future certifications more efficiently.

Manufacturers that integrate compliance into everyday product development are typically able to react much faster to technical changes, regulatory updates, and new business opportunities. Instead of repeatedly rebuilding regulatory knowledge for each project, they create a continuously growing foundation that supports every future product.

Ultimately, successful compliance is not defined by a single certificate.

It is defined by an organization’s ability to develop compliant products consistently, adapt confidently to change, and bring new innovations to market with predictable regulatory outcomes.

This philosophy is exactly what inspired the creation of ScopeRight.

So what does a modern, structured compliance ecosystem look like—and how can manufacturers transform compliance from a regulatory obligation into a strategic advantage?

12. The Compliance Ecosystem

How does compliance become a competitive advantage instead of a regulatory obligation?

In many organizations, compliance is still viewed as a necessary hurdle. Regulatory requirements seem to appear only shortly before product launch, testing has to be organized under tight deadlines, and technical documentation is completed at the last minute. As a result, compliance is often perceived simply as a cost of doing business—something that must be completed before a product can be sold.

The most successful manufacturers take a different approach.

They integrate regulatory requirements into product development from the very beginning and treat compliance as an essential part of their engineering strategy. This enables better decisions, earlier risk identification, and far more predictable certification projects.

That philosophy is exactly why ScopeRight was created.

It all started with a simple observation:

The greatest uncertainty does not exist inside the laboratory.

It exists long before a product ever reaches one.

There are countless experts in laboratory testing, certification, and regulatory standards. Yet many manufacturers still lack a structured way to understand which regulatory requirements actually apply to their products while they are still being designed.

That is the gap we set out to close.

ScopeRight is not intended to replace testing laboratories, certification bodies, or regulatory consultants. On the contrary—they remain essential partners throughout the certification process. Our objective is to help manufacturers prepare for those collaborations by giving them a clear understanding of their regulatory obligations before quotations are requested, projects are planned, or testing begins.

This vision has evolved into a connected compliance ecosystem.

The Compliance Scoping Tools help manufacturers identify applicable legislation, relevant standards, and required testing activities at the very beginning of a project.

The Standards Database provides a centralized overview of regulatory standards while helping teams stay informed about updates and changes that may affect existing or future products.

The Knowledge Database brings together practical regulatory knowledge, explains technical concepts, and supports engineers with everyday compliance questions.

The ScopeRight Wizards offer a growing collection of free tools that simplify common regulatory tasks, such as RF exposure evaluations and preliminary compliance assessments.

For companies planning international product launches, the Global Radio Approvals (GRA) Module provides structured regulatory information for more than 200 countries and territories, helping manufacturers develop efficient global approval strategies before entering new markets.

The platform is complemented by practical regulatory support. Depending on the project, we assist manufacturers with certification preparation, regulatory reviews, technical guidance, or complete project management through to successful market approval.

Every component of the platform serves the same purpose:

To make compliance understandable.

Not by oversimplifying regulations, but by bringing structure, transparency, and planning to an area that is often perceived as unnecessarily complex.

Manufacturers should always be able to answer a few fundamental questions:

• Which regulations apply?
• Why do they apply?
• What evidence is required?
• Where are the regulatory risks?
• Which decisions will influence the certification process?

The answers to these questions often determine whether a certification project progresses smoothly or becomes delayed by unexpected technical and regulatory challenges.

Compliance therefore becomes much more than a legal requirement.

It becomes an integral part of effective product development.

Organizations that consider regulatory requirements from the earliest design stages reduce project risks, improve engineering efficiency, accelerate market entry, and build a stronger foundation for international growth.

That is exactly why ScopeRight was founded.

Not to replace the certification process.

But to help manufacturers understand it from the very beginning.

Conclusion

Regulatory compliance is not a single activity performed at the end of product development.

It begins with the very first product concept, influences every important engineering decision, and continues long after a product has entered the market. From defining the product and identifying applicable legislation, to compliance scoping, testing strategy, product development, pre-compliance evaluations, accredited laboratory testing, technical documentation, global market access, and ongoing change management, every stage forms part of one continuous process.

The earlier regulatory requirements are understood, the more predictable product development becomes.

Manufacturers can avoid costly design changes, prepare testing more efficiently, reduce certification risks, and bring products to both domestic and international markets faster.

This is how we see the future of modern compliance.

Not as an isolated regulatory function, but as an integral part of successful product development.

We hope this guide helps you approach future compliance projects with greater structure, identify potential risks earlier, and navigate regulatory requirements with greater confidence.

Because ultimately, compliance is not just about obtaining certificates.

It is about bringing innovative products to market safely, efficiently, and successfully.