Most people outside the function have a vague idea of what regulatory affairs does. They know it involves submissions, agencies and approvals. What is less clear is how RA actually works inside a company: where it sits, who it talks to, how it makes decisions, and why it sometimes slows things down in ways that frustrate everyone else.
This article looks at the internal mechanics. Not the theory of what regulatory affairs is supposed to do, but how it functions in practice within a pharmaceutical organisation. For a broader overview of the discipline, the article on what is regulatory affairs in pharma is a good starting point. For a breakdown of the specific roles and career paths, see pharmaceutical regulatory affairs: roles, responsibilities and career paths.
Where regulatory affairs sits in a pharma organisation
Reporting lines: who does RA answer to?
There is no universal answer. In some companies, regulatory affairs reports directly to the CEO or to a Chief Scientific Officer. In others it sits under R&D, under Medical Affairs, or under a broader Chief Medical Officer structure. The reporting line matters because it signals how the organisation views the function: as a scientific discipline, a compliance function, or a strategic asset.
Where RA reports into R&D, the focus tends to be on development support and pathway strategy. Where it reports into a compliance or quality structure, the emphasis shifts toward procedural rigour and inspection readiness. Neither model is inherently better, but the differences in culture and priority are real.
Centralised vs decentralised models
How a company distributes its regulatory function across geographies is one of the more consequential organisational decisions it makes.
Global RA vs local affiliates
In a centralised model, a global RA team based at headquarters handles all major submissions and agency interactions. Local affiliates may have small regulatory teams, but they work within the strategy and dossiers produced centrally. This ensures consistency but can create distance from local regulatory environments and national competent authorities.
In a decentralised model, regional or country-level teams have more autonomy. They manage local submissions, handle interactions with national agencies and adapt global strategies to local requirements. The trade-off is coordination complexity and the risk of inconsistency across markets.
Regional hubs and their role
Many large pharmaceutical companies operate regional hubs as a middle ground. A European hub, typically based in a country with strong regulatory infrastructure such as Germany, the Netherlands or the UK, coordinates submissions and agency interactions across EU member states. Similar hubs exist for the US, Japan and increasingly for markets in Asia-Pacific and Latin America.
Hubs allow a degree of regional expertise without fully fragmenting the function. They also act as the practical interface between global strategy and local execution.
How regulatory affairs interacts with other functions
This is where a lot of the real work happens, and also where a lot of the friction originates.
RA and Research & Development
The relationship between RA and R&D is the most consequential one in the organisation. Regulatory affairs professionals are involved from early development: advising on preclinical study designs, identifying applicable guidelines, helping shape the Target Product Profile. The earlier RA is involved, the fewer expensive corrections are needed later.
In practice, the quality of this relationship varies considerably. In organisations where RA is seen as a partner in development, the collaboration tends to be early and iterative. Where RA is treated as a checkpoint at the end of a development stage, problems accumulate until they cannot be ignored.
RA and Clinical Operations
Clinical operations run the trials. Regulatory affairs makes sure those trials can run, and that the data they generate will support a marketing authorisation. This means RA prepares and submits Clinical Trial Applications and INDs, manages responses to agency questions, and reviews protocols and informed consent documents for regulatory compliance.
The relationship is close and often time-pressured. Trial start-up timelines depend on submission timelines, and submission timelines depend on the quality of the documents that clinical operations and the broader team provide.
RA and Medical Affairs
Medical affairs manages the relationship between the company and the medical community after approval. Regulatory affairs determines what can actually be said about the product, in what context, and to whom. Label claims, approved indications, risk minimisation measures: all of these constrain what medical affairs can do.
This makes the relationship important but also occasionally tense. Medical affairs teams sometimes want to communicate data that goes beyond the approved label. RA has to be clear about what is and is not permissible, and that conversation is not always easy.
RA and Quality Assurance
Quality and regulatory affairs share a common interest in compliance, but from different angles. Quality assurance focuses on internal systems: manufacturing processes, batch release, quality management systems, CAPA management. Regulatory affairs focuses on the external interface: what the agencies require and how the company demonstrates it meets those requirements.
The two functions have to work closely on manufacturing change management, where any change to an approved process may require a regulatory submission. They also collaborate on preparation for regulatory inspections, where agency assessors examine both the quality systems and the regulatory documentation.
RA and Commercial teams
The tension between regulatory affairs and commercial teams is a recurring feature of pharmaceutical organisations. Commercial teams want fast approvals, broad label claims and maximum market flexibility. Regulatory affairs operates within the constraints of what the data supports and what agencies will accept.
This does not have to be adversarial. When RA is involved early in portfolio and launch planning, commercial teams understand the regulatory parameters better and can plan around them more realistically. The problems tend to arise when commercial timelines are set without regulatory input, and RA is then expected to compress months of work into weeks.
Regulatory affairs across the company’s product portfolio
Managing a pipeline product vs a marketed product
The regulatory work for a product in development and the regulatory work for a marketed product are quite different in character.
Pipeline products require strategic thinking about development pathways, clinical trial design and marketing authorisation strategy. The decisions made here are largely forward-looking: what data do we need, in what format, for which agencies, by when.
Marketed products require continuous management: variations, renewals, periodic safety reports, labelling updates, post-approval commitments. The work is more operational and more predictable in its rhythms, but it is also non-negotiable. Failing to submit a PSUR on time or to implement a required label change has direct regulatory consequences.
Priority-setting: how RA allocates resources internally
Regulatory affairs teams are almost always working with limited resources relative to the demands on them. Priority-setting is therefore a constant exercise. Which submissions get the most senior attention? Which markets are handled first? Which variation can wait?
These decisions are rarely made by RA alone. They involve R&D leadership, commercial teams and executive management. But RA has to be able to articulate the regulatory implications of different priority choices clearly enough that decision-makers understand what they are trading off.
When the portfolio grows: acquisitions, licensing and partnerships
Acquisitions and in-licensing deals bring new products into the portfolio, often with existing regulatory histories that need to be assessed and integrated. This means reviewing dossiers prepared by other companies, understanding approval conditions in multiple markets, and sometimes inheriting post-approval commitments or outstanding issues with agencies.
Licensing partnerships introduce another layer of complexity: who holds the marketing authorisation, who is responsible for submissions in which markets, how are regulatory costs and timelines shared. These questions need regulatory input at the deal stage, not after the contract is signed.
Regulatory processes inside a pharma company
Internal governance and regulatory review boards
Most pharmaceutical companies of any significant size have internal governance structures for regulatory decisions. These typically include a regulatory review board or equivalent body that approves submission strategies, reviews draft dossiers before submission and manages significant agency interactions.
These governance processes exist for good reasons: regulatory submissions are expensive to prepare and consequential if they go wrong. But they also add time, and managing internal governance alongside external agency timelines is a coordination challenge that RA teams navigate constantly.
Document management and regulatory information systems
The volume of regulatory documentation generated over a product’s lifecycle is substantial. Managing it requires dedicated systems.
eCTD publishing and submission management tools
Electronic Common Technical Document publishing tools manage the compilation and formatting of submissions for electronic filing with agencies. These are specialised systems, and the people who work with them develop a specific technical expertise that is not widely understood outside the function.
Regulatory tracking and intelligence platforms
Separate from document management, regulatory intelligence platforms track the global regulatory environment: new agency guidelines, consultation papers, changes to submission requirements, emerging legislation. Companies use these tools to monitor developments that could affect their pipeline or their marketed products, and to feed that information into development and post-approval planning.
Change control and its regulatory dimension
Change control is primarily a quality process, but it has a direct regulatory dimension. Any change to a manufacturing process, a formulation, a specification or a facility that is described in an approved dossier may require a regulatory submission before it can be implemented. The regulatory assessment of a proposed change determines whether prior agency approval is needed or whether the change can be handled through annual reporting or notification.
Getting this wrong has real consequences. Implementing a change that required prior approval without submitting it first is a serious GMP compliance issue. RA teams work closely with quality and manufacturing to ensure that proposed changes are assessed correctly before any decision is made on implementation timing.
Common friction points and how companies address them
Timeline pressure from development teams
Development teams work to ambitious timelines. Regulatory submissions take as long as they take, and no amount of pressure changes what an agency needs to see in a dossier. The friction this creates is real, and it is one of the most consistent sources of tension in pharmaceutical organisations.
Companies that manage this well tend to involve RA early, build regulatory milestones into development timelines from the start, and treat regulatory requirements as fixed parameters rather than variables to be negotiated away. Companies that manage it less well find themselves repeatedly surprised by the time it actually takes.
Regulatory risk appetite across functions
Different parts of a pharmaceutical organisation have different tolerances for regulatory risk. Commercial teams, under pressure to launch, may be willing to accept more uncertainty than RA is comfortable with. Development teams may want to proceed with a regulatory strategy that RA considers insufficiently robust.
These conversations happen regularly, and they are not always easy. RA professionals have to be able to articulate risk clearly, without being paralysed by it and without understating it to avoid conflict.
Knowledge gaps between RA and non-regulatory colleagues
One of the less-discussed challenges in pharmaceutical organisations is the gap in regulatory knowledge between RA and the functions it works with. Project managers, scientists, commercial leads: many of them have limited understanding of what regulatory submissions involve, what agencies actually look for, and why certain things simply cannot be done faster.
Bridging this gap is partly a training issue and partly a communication issue. RA teams that invest in sharing regulatory knowledge with their colleagues, through briefings, internal training or simply clearer communication, tend to work more effectively with the rest of the organisation. LS Academy offers regulatory affairs training programmes designed specifically for pharmaceutical and medical device professionals who need to strengthen this understanding, whether they work in RA or in functions that interact with it.
FAQ
There is no single standard model, but large pharmaceutical companies usually organise RA around a combination of geography (global, regional and local teams), product or therapeutic area, and function (regulatory operations, regulatory strategy, regulatory intelligence). The precise structure depends on the company’s size, pipeline, and the markets it operates in.
Global regulatory affairs manages the overarching submission strategy, prepares core dossiers and handles interactions with major agencies such as the EMA and FDA. Local regulatory affairs teams, based in specific countries or regions, adapt global strategies for national markets, manage submissions to national competent authorities and handle local agency relationships. In practice the boundary between the two varies by company.
Regulatory submissions require complete, high-quality data packages that meet specific agency requirements. Agencies do not compress their review timelines because a company is in a hurry. What looks like a delay from outside the function is often the time required to prepare a submission properly, or the result of agency review processes that cannot be shortened. Early RA involvement in development planning typically reduces, rather than increases, overall timeline.
Beyond obtaining the marketing authorisation, RA manages the conditions attached to the approval, oversees labelling finalisation, handles any pre-launch regulatory requirements and coordinates the transfer of regulatory responsibilities to the commercial organisation. In many companies, RA also reviews promotional and medical education materials to ensure they comply with the approved label.