Why Do So Many RMPs End Up Copy-Pasted from Old Versions?

Risk Management Plans (RMPs) are among the most important regulatory documents in the life cycle of a medicinal product. They define the known and potential risks, outline missing information, and specify the safety activities designed to monitor, mitigate, and communicate those risks. In theory, each new RMP version should reflect the most current understanding of a product’s safety profile, incorporating new data from post-marketing surveillance, clinical trials, literature, regulatory updates, and evolving benefit-risk evaluations.

But in practice, many RMPs end up being copied, pasted, slightly updated, and then forwarded through cycles of review with almost mechanical repetition. The phenomenon is well-known across the industry: updated RMPs that look remarkably similar to versions written years earlier, sometimes even carrying forward outdated text, legacy assumptions, and inaccuracies.

This raises an obvious question:Why does it happen so frequently?The reasons are deeply rooted in the operational, regulatory, and cultural realities of pharmacovigilance. Understanding these drivers can help organizations improve the quality and relevancy of their RMPs, reduce compliance risk, and streamline the RMP lifecycle.

This article examines the key causes behind copy-pasted RMPs, the implications for regulatory compliance and drug safety, and how modern solutions such as Tesserblu can help break the cycle.

1. The Pressure of Timelines and Workload

Pharmacovigilance teams are consistently under pressure. RMP updates may be triggered by renewal cycles, new indications, new data from Periodic Safety Update Reports, emerging safety signals, or post-authorization commitments. These updates often coincide with other major deliverables such as aggregate reports, signal assessments, or benefit-risk updates.

This environment creates a strong incentive for speed. Team members often rely on the previous version of an RMP because:

• It is the fastest starting point.

• The core structure remains largely the same.

• Many sections are assumed to require only minimal changes.

When submission timelines are aggressive, copying and pasting becomes the default method to keep things moving. The risk, however, is that speed overtakes accuracy and thoroughness.

2. The RMP Template Itself Encourages Repetition

An RMP follows a standardized structure defined by regulators. This structure includes continual repetition of risk descriptions, safety monitoring approaches, pharmacovigilance activities, and risk minimization measures. Because the overall template is stable across updates, teams often assume the content should remain stable too.

The result is that teams treat the document less as a living reflection of safety knowledge and more as a static template to be periodically refreshed.

The structure of the RMP, while necessary to ensure consistency, unintentionally promotes copying forward existing text unless teams actively resist the temptation.

3. Fragmented Data Sources Make Updates Hard

Accurate RMP updates rely on data from many different areas:

• Clinical safety databases

• Post-marketing individual case safety reports

• Literature monitoring

• Registries

• Observational studies

• Signal management systems

• Labeling change history

• Benefit-risk assessments

• Renewals and variations

This information is rarely stored in one place. Instead, it is often distributed across systems, spreadsheets, and team folders. The effort required to gather, interpret, and reconcile all this information can be significant.

When teams lack a single, authoritative source of truth, they tend to default to the last RMP as the most convenient reference. This ease of access makes the copy-paste cycle hard to break.

4. Fear of Creating Errors in New Text

RMPs are high-stakes regulatory documents. A poorly written or inconsistent RMP can lead to:

• Additional requests for clarification from regulators

• Delays in approvals or renewals

• Questions about the robustness of a company’s safety governance

• Escalations or audits

Teams often feel safer copying forward text that has previously passed regulatory review. The logic is simple: if a particular paragraph was approved before, it is less likely to cause issues now.

This conservative approach minimizes perceived risk. However, it also perpetuates outdated language, obsolete assumptions, and legacy inaccuracies.

5. Limited Ownership and Collective Responsibility

RMPs typically involve multiple stakeholders from pharmacovigilance, medical writing, regulatory affairs, clinical development, labeling, biostatistics, and safety epidemiology. With so many contributors, ownership can be diffuse.

When responsibility is shared, no single party may feel accountable for ensuring the document is fully refreshed. Instead, contributors focus on their specific section, often editing only what stands out as clearly outdated.

This collective responsibility without clear ownership reinforces the habit of relying on the previous version as the foundation.

6. Inconsistent Change Management

Effective RMP updates require clear processes for tracking:

• Changes in safety signals

• Updates to known or potential risks

• Adjustments to routine or additional pharmacovigilance activities

• Modifications to risk minimization measures

• Removal of outdated commitments

• Shifts in regulatory expectations

Many organizations lack robust change-control mechanisms for RMP-related inputs. Without structured tracking, teams may overlook how a safety profile has evolved since the last version.

In the absence of an organized catalogue of changes, copying forward text feels safer and easier than rewriting.

7. Insufficient Training on RMP Strategy

Creating a meaningful RMP is not merely a writing exercise. It requires:

• Understanding of risk evaluation methodologies

• Familiarity with regulatory guidance

• Awareness of pharmacovigilance operations

• Ability to align safety data with narrative explanations

• Experience in benefit-risk communication

Many contributors, especially those new to PV or regulatory writing, may lack the strategic background needed to craft fresh, accurate RMP text. Copy-pasting seems like a safe way to avoid making mistakes.

Without adequate training, teams are more likely to perpetuate old content rather than re-evaluating it.

8. The Long Lifecycle of Medicinal Products

Many medicinal products remain on the market for decades. During that time, RMPs may accumulate multiple layers of edits, annotations, and incremental updates. Over the years, this leads to:

• Outdated terminology

• Repetitive structures

• Contradictory statements

• Legacy risks that no longer apply

• Safety activities that have already been completed

• Text added to satisfy previous regulators that is no longer relevant

Cleaning up this accumulated content requires significant time, clarity, and expertise. Many teams choose not to attempt a full rewrite unless absolutely necessary, instead carrying forward historical artifacts.

9. The Consequences of Copy-Pasted RMPs

While copying and pasting is understandable, it can have serious implications:

• Inaccurate or outdated risk descriptions

• Gaps in safety monitoring obligations

• Misalignment with evolving labeling

• Inconsistencies with signal management conclusions

• Reduced credibility with regulators

• Increased inspection findings

• Missed opportunities to adjust risk minimization measures

• Poor internal alignment across functional teams

Ultimately, an RMP that does not reflect the true, current safety profile of a product weakens the foundation of a company’s pharmacovigilance system.

10. How Tesserblu Can Help Break the Cycle

Tesserblu is designed to address exactly these operational, analytical, and strategic challenges. It provides an integrated, structured approach to safety document generation and lifecycle management so that RMPs can be built on current, verified data rather than outdated text.

Below are key ways Tesserblu can help organizations produce higher-quality RMPs without relying on copy-paste.

Centralized Safety Intelligence

Tesserblu aggregates data from across the safety ecosystem, enabling teams to access current information on risks, safety signals, labeling changes, and safety study status. With data unified in one place, teams no longer need to search through disparate sources or rely on the last RMP as the de facto reference.

Dynamic Content Updating

Instead of treating RMPs as static documents, Tesserblu allows sections to update automatically based on validated data inputs. When new safety information emerges, associated RMP elements are flagged or refreshed, ensuring that the document remains accurate and aligned with ongoing safety evaluations.

Structured Templates with Guidance

Tesserblu incorporates regulatory templates, guidance notes, and industry best practices directly into the workflow. This reduces the ambiguity and anxiety that often lead teams to copy approved text from older versions. Writers are supported with context-relevant instruction, reducing the need to rely on legacy content.

Traceability and Change Tracking

The platform provides clear traceability on what has changed between versions, who made the changes, and why. With this transparency, teams gain confidence in updating content rather than cloning previous sections. Reviewers can see the rationale behind updates, which supports more efficient, confident approvals.

Collaboration Management

By managing contributions across safety, medical, regulatory, and quality teams, Tesserblu clarifies ownership and ensures that each section receives appropriate, up-to-date input. Collaboration becomes structured rather than fragmented, reducing the reliance on old content.

Reduction of Manual Workload

By automating repetitive tasks, Tesserblu frees teams to focus on scientific, clinical, and strategic updates. This reduces time pressure, which is one of the biggest drivers of copy-paste behaviors.

Increased Compliance and Inspection Readiness

With consistent, accurate RMPs aligned to current data, organizations reduce the risk of regulatory questions or findings. The system supports continuous inspection readiness through documentation integrity, audit trails, and transparent updates.

Conclusion

Copy-pasted RMPs are not the result of lack of effort but rather the product of operational constraints, outdated workflows, fragmented information, and the inherent complexity of pharmacovigilance documentation. Yet, the consequences of relying on old text can affect compliance, safety decision-making, and regulatory trust.

Breaking the cycle requires a shift from document-centric practices to data-driven, collaborative, and transparent processes. Solutions like Tesserblu empower teams to create RMPs that reflect current knowledge, maintain regulatory accuracy, and evolve with the medicinal product’s safety profile. Book a meeting if you are interested to discuss more.