Compliance Studio: From Regulatory Context to Market Entry and Continuous Compliance
Regulatory work is rarely a single task.
A product may already be established in one market while the team is assessing entry into another. Existing applicability decisions may be spread across spreadsheets, documents and individual expertise. New developments may affect decisions that were made months or years ago.
Compliance Studio brings these activities together around one central construct: the Regulatory Position.
A Regulatory Position is the documented regulatory context for a specific product or organisation in a specific market. It brings together the product’s characteristics, the regulatory requirements that may apply, the team’s applicability decisions and rationales, and the regulatory developments that may require those decisions to be reviewed over time.
This is how it works in practice
One environment for products, markets and regulatory decisions
Compliance Studio provides a shared environment for maintaining Regulatory Positions across a product portfolio and selected markets.
A single Product Profile can be used to create multiple Regulatory Positions. The same product can therefore have one position for the European Union, another for the United States, and further positions as the organisation enters new markets. Each position remains specific to its market while staying connected to the underlying product context.
For this example, we will follow Aurevia Connect, a connected patient-monitoring system already established in the European Union. The manufacturer is now considering entry into the United States.
Start with the product (or company), not with a generic list of regulations
A Regulatory Position begins by defining the product context.
For Aurevia Connect, that includes its medical-device status, connected functionality, software component, wireless technology, battery, processing of personal data and other characteristics that may affect its regulatory environment.
This matters because regulatory relevance is rarely determined by product category alone. A connected medical device may be affected by medical-device requirements, but also by obligations relating to data protection, cybersecurity, radio equipment, batteries, environmental requirements and market surveillance.
Compliance Studio helps users identify and document the product attributes that define this context. The resulting Regulatory Position gives the team, and the Studio Agent, a defined basis for further work.
Establish and maintain the position in existing markets
Aurevia Connect is already marketed in the European Union. The immediate task is therefore not simply to identify new regulations. It is to establish a clear and maintainable view of the regulatory decisions that already support the product’s EU position.
Compliance Studio creates a Regulations Register for the selected product and market. Each record can be assessed as applicable, not applicable or requiring further review. The rationale for each decision remains connected to the regulatory record.
The EU register for Aurevia Connect includes its primary medical-device framework alongside other potentially relevant requirements, including GDPR, market surveillance, radio equipment, batteries, packaging and environmental obligations.
This is important because a defensible Regulatory Position is not a list of regulations. It is a structured record of why each requirement has been considered relevant, irrelevant or unresolved for a specific product and market.
For organisations with existing spreadsheets, applicable lists and supporting documentation, Hoodin offers a complimentary migration service during onboarding. Existing work is transferred into Compliance Studio and used as the starting point for review. The purpose is not to discard established regulatory knowledge, but to bring it into a structure that can be maintained and governed over time.
Keep the position current as regulations change
Establishing a Regulatory Position is only the starting point. Regulations, guidance, expectations and related regulatory developments continue to change. The relevant question is not simply what has changed. It is whether the change affects a specific product, market or regulatory decision.
Regulatory Signals continuously identifies developments that may be relevant to a Regulatory Position. Signals are linked to the affected regulatory context and can be reviewed directly within the workspace.
In this example, a development relating to the EU Batteries Regulation is connected to Aurevia Connect and its established EU position. The signal is classified as potentially affecting scope, documentation and internal processes.
The user can then discuss the development with Studio Agent in the context of the product, market and specific regulatory record. The Agent identifies practical review actions and clarifies what additional information is needed, while leaving the final regulatory judgement with qualified professionals.
This turns monitoring from a separate stream of news into a maintained regulatory decision process.
Use the same product context to explore a new market
The same Product Profile can then be used to create a Regulatory Position for a new market.
For Aurevia Connect, the manufacturer selects the United States as the next market under consideration.
Compliance Studio introduces the relevant market context and creates a new Regulatory Position without requiring the team to define the product from the beginning again.
The product remains the same. The regulatory environment does not.
Use the same product context to explore a new market
For the United States, Compliance Studio proposes potentially applicable regulatory records based on Aurevia Connect’s product context and the selected market.
Each proposal includes a rationale explaining why it may create obligations for the product. The regulatory team can review the proposal, adjust it, add it to the register, dismiss it or flag it for further assessment.
This creates a structured basis for market-entry planning. It also makes uncertainty visible. Some questions can be assessed from the available context. Others require further product information, regulatory research or professional judgement.
That distinction is essential. Compliance Studio supports the work of Regulatory Affairs. It does not replace regulatory accountability.
Turn regulatory context into practical market-entry work
Once the US Regulatory Position has been established, Studio Agent can use that context to support more specific work.
For example, the team can ask for a preliminary FDA market-entry pathway assessment. Rather than giving an unqualified answer, the Agent distinguishes between:
What can be determined from the existing Regulatory Position
What information still needs to be confirmed
Which issues require regulatory judgement
Which practical actions and submission-readiness artefacts should be prepared next
For Aurevia Connect, this can include assessment of plausible FDA pathways, evaluation of whether an appropriate predicate may exist, clarification of intended use and claims, and preparation of a structured decision flow for the team’s further review.
The result is not a final regulatory determination. It is a documented and context-aware working basis that helps the team move from an initial market question to a defined set of decisions, activities and evidence needs.
One product. Multiple markets. A position that stays alive.
Compliance Studio is designed for the full regulatory lifecycle. It helps teams establish a position where the product is already marketed, maintain that position as the regulatory environment changes, and use the same structured product context to assess new markets and plan the work required to enter them.
The outcome is a clearer and more defensible way to work with regulatory requirements across products and markets.
Not another isolated spreadsheet. Not another generic AI chat. A maintained Regulatory Position that connects product context, regulatory requirements, team decisions, ongoing change and practical regulatory work.
Compliance Studio Foundations
Join our in-depth training session for current and future users of Compliance Studio.
We will demonstrate how to establish and maintain a Regulatory Position, work with the Regulations Register, assess Regulatory Signals and use Studio Agent for practical regulatory work.
Tuesday , 15 September, 16:00–16:45 CET
