Risk Management Plans (RMPs) sit at the heart of post-market safety oversight for medicines. Yet despite being well established within regulatory frameworks, they continue to appear regularly in inspection findings.

For many organisations, the challenge is not the existence of an RMP. Most companies have them in place. The difficulty arises in maintaining them, implementing the commitments they contain, and ensuring updates occur in step with evolving safety knowledge.

Inspection experience across the sector suggests that many deficiencies stem from breakdowns in coordination rather than gaps in knowledge. RMP readiness therefore depends less on documentation alone and more on how effectively pharmacovigilance and regulatory affairs work together across the lifecycle of a product.

For organisations operating in the Australian regulatory environment, strengthening this collaboration has become essential to maintaining Good Pharmacovigilance Practice (GVP) compliance.

Why RMP readiness matters

An RMP describes how a sponsor will monitor and manage the risks associated with a therapeutic product after it enters the market. It outlines the safety profile of the medicine, identifies known and potential risks, and specifies the pharmacovigilance and risk minimisation activities required to manage those risks.

These plans are particularly important because the evidence generated during clinical development does not fully reflect how a medicine will perform in real-world use. Clinical trials involve controlled conditions and defined patient populations. Once a product is used in broader clinical practice, new safety signals may emerge.

The RMP framework ensures there is a structured process for identifying, assessing and mitigating these risks as more information becomes available.

For higher-risk medicines and biologicals, the Therapeutic Goods Administration (TGA) requires an RMP as part of the registration process. Once approved, the plan forms part of the product’s regulatory conditions and must be maintained throughout its lifecycle.

In practice, this means the RMP is not a static document. It evolves alongside the product as new safety information emerges, indications change, or additional pharmacovigilance activities are introduced.

Where organisations encounter difficulties

Inspection findings across the industry reveal two consistent areas of concern.

The first relates to delays in submitting updated RMPs or Australian-specific annexes following safety changes. When global RMP updates occur, or when safety information leads to changes in risk minimisation measures, the Australian documentation must be updated accordingly. In some cases, organisations fail to reflect these changes locally in a timely manner, creating a misalignment between what is occurring operationally and what regulators have formally approved.

The second area concerns the implementation of RMP commitments. These commitments may include additional pharmacovigilance activities, educational programmes for healthcare professionals, patient monitoring initiatives or post-authorisation studies. Inspections sometimes identify cases where these activities have not been implemented as described, where monitoring schedules have not been followed, or where documentation supporting the activities is incomplete.

Often these issues arise because organisations lack a clear system for tracking commitments across the lifecycle of a product. Without structured oversight, obligations can easily become fragmented across multiple teams.

The role of the Australian-specific annex

While many organisations rely on global or European RMPs as the foundation for their safety management strategies, the Australian regulatory framework requires additional local context.

The Australian-specific annex (ASA) accompanies the core RMP and addresses factors relevant to the Australian market. This includes differences in the safety profile within the local population, variations in risk minimisation measures, and differences between international product information and the Australian Product Information (PI).

Importantly, the ASA also identifies the responsible person for pharmacovigilance oversight in Australia, typically the Qualified Person for Pharmacovigilance (QPPV). This requirement reinforces the expectation that local affiliates maintain active oversight of the RMP, even when global teams are responsible for developing the core document.

RMPs as living documents

One of the most common misconceptions about RMPs is that they are completed at the time of product approval. In reality, regulators expect them to evolve continuously as the safety profile of the medicine develops.

Updates may be triggered by a range of events, including:

• identification of new safety signals• changes to product information• new clinical or post-marketing data• changes to pharmacovigilance activities• regulatory updates in other jurisdictions.

Sponsors are expected to monitor these developments and determine whether an update to the RMP or ASA is required. Maintaining this oversight requires structured processes and clear lines of responsibility within the organisation.

The collaboration challenge

Because RMPs involve both safety monitoring and regulatory submissions, they sit directly at the interface between pharmacovigilance and regulatory affairs.

Regulatory teams typically manage communications with the TGA and oversee formal submissions. Pharmacovigilance teams are often responsible for coordinating risk management strategies, monitoring safety data and ensuring commitments are implemented.

While this division of responsibilities is logical, it also creates a potential gap. If responsibilities are not clearly defined, teams may assume another function is responsible for initiating updates or monitoring commitments.

This ambiguity can lead to delays, missed deadlines or incomplete implementation of risk minimisation measures.

In organisations where RMP management works well, regulatory and pharmacovigilance teams operate as partners rather than separate functions. Regular communication, shared planning and clear accountability ensure that safety insights translate quickly into regulatory action.

Building organisational readiness

Organisations seeking to strengthen their RMP readiness typically focus on three core areas: people, processes and systems.

People

Clear ownership is fundamental. Every organisation should define who is responsible for initiating updates, preparing documentation, monitoring commitments and maintaining communication with regulators.

Training also plays an important role. Risk minimisation activities often involve teams beyond pharmacovigilance and regulatory affairs, including medical affairs, commercial teams and medical information specialists. Ensuring these teams understand the regulatory importance of RMP commitments helps embed compliance across the organisation.

Processes

Documented procedures should outline how RMP updates are triggered and managed. These processes should include clear mechanisms for identifying when safety changes require updates, how global changes are communicated to local affiliates, and how timelines for submission are monitored.

Processes should also address deviations. If a commitment cannot be met within the agreed timeframe, organisations must be able to document the reason, assess the impact and communicate appropriately with regulators.

Well-defined procedures create consistency and ensure organisations can demonstrate compliance during inspections.

Systems

Tracking commitments across multiple products and teams can be complex. Effective organisations rely on systems or structured trackers to monitor deadlines, commitments and supporting documentation.

These tools help ensure that pharmacovigilance activities, educational programmes, studies and reporting obligations remain visible throughout the lifecycle of the product.

They also provide a valuable audit trail during regulatory inspections.

Learning from the regulatory environment

RMP readiness is not achieved in isolation. Regulatory expectations evolve, and organisations must stay informed about emerging inspection trends and compliance risks.

Inspection reports, regulatory guidance and professional forums provide valuable insights into the areas where regulators are focusing their attention. Engagement with industry networks also helps organisations learn from the experiences of peers facing similar challenges.

For professionals working across pharmacovigilance, regulatory affairs and clinical development, these conversations contribute to a stronger culture of compliance and shared learning.

A shared responsibility

Ultimately, RMP readiness reflects the maturity of an organisation’s safety governance.

Effective risk management requires pharmacovigilance specialists, regulatory professionals and operational teams to work together with a shared understanding of their responsibilities. When communication is strong and processes are clear, RMPs become more than regulatory documents. They become practical tools that guide ongoing safety monitoring and protect patients in real-world clinical use.

For organisations operating in today’s complex regulatory environment, strengthening the partnership between pharmacovigilance and regulatory affairs is one of the most important steps in achieving that goal.