Skip to content
Assyro AI
Assyro AI
Module 1
1.16
Guide

How to prepare an FDA risk-management plan outside REMS

Define the safety question, planned activity and evaluation method without turning every risk-management document into a REMS.

By Assyro
Published
Article updated FDA · eCTD v4.0 placement
On this page

How do you write a US risk-management plan that is not a REMS?

Define the actual safety question and product context, then connect each evidence gap to a feasible activity, data source, analysis and decision. Distinguish detecting or characterizing a risk from reducing it, and distinguish a signal from established causality. Verify any product-specific FDA requirements separately. An EU risk-management plan or a Module 1 heading does not itself establish the content or status of a US REMS.

Before you begin

Preparation of non-REMS risk-management material where relevant to the FDA submission. An EU RMP is not automatically the US document, and the presence of 1.16 does not establish a REMS obligation.

What you will prepare: A risk-to-action plan with explicit purpose, evidence, owners, evaluation methods and unresolved safety questions.

Sections covered in this guide (2)

Identify the actual risk-management task

Start with the identified safety concern, product, population and lifecycle stage. Determine whether the document describes pharmacovigilance, a specific risk-minimization activity or an FDA-required REMS. Retrieve relevant agency correspondence. Do not infer “no REMS needed” merely because no REMS document is present, and do not relabel a foreign risk-management plan as a US REMS.

Connect each activity to an answerable question

For each concern, identify the evidence, what remains unknown, the proposed activity, data source, responsible owner and how findings will be assessed. Distinguish a signal from an established causal risk. Routine reporting, additional observational research and targeted mitigation serve different purposes. The March 2005 guidance provides pharmacovigilance concepts; product-specific requirements and contemporary methods still need appropriate assessment.

Use a risk-to-action working table

Use a risk-to-action working table
ConcernCurrent evidence and uncertaintyActivityDecision/outputOwner and review point
Fictional safety signalCases identified; causality unresolvedDefined case review or justified studyCharacterize the signal and decide next stepsNamed safety function; actual planned review

Add feasibility, limitations and dependencies. Avoid a vague promise to “monitor closely.” Define what records will be examined, how duplicates and missing information will be handled, and what would trigger reassessment. A low spontaneous-report count cannot by itself establish a low incidence.

Fictional example: a new population changes the plan

A program expands to a population poorly represented in existing safety evidence. Reassess the question, available data and proposed activity rather than copying the old monitoring paragraph. If the exposure denominator is unavailable, say so and avoid an unsupported incidence estimate. If FDA subsequently requires a REMS, establish that separate program and its actual requirements instead of merely changing this document’s title.

Choose the activity from the question it can answer

Begin with a short safety specification: the concern, supporting observations, relevant population, what remains unknown and why that uncertainty matters. Then ask what evidence would change the next decision. More activity is not automatically more informative; a large dataset with the wrong population or no usable exposure denominator may not answer the question.

Choose the activity from the question it can answer
QuestionPossible activity to assessNecessary design inputLimitation to preserve
Are reported cases sufficiently documented and distinct?Case review and targeted follow-upCase definition, chronology, duplicate handling and missing fieldsReporting does not itself establish causality
How often does the event occur among exposed people?A justified epidemiologic studyDefined population, ascertainment, exposure and time at riskSpontaneous reports divided by sales are not a reliable incidence estimate
Which factors may explain an association?Appropriate comparative investigationComparator, confounding assessment and data feasibilityAn unadjusted difference may reflect population or use differences
Do intended users understand a risk communication?A designed and reviewed surveySampling frame, instrument, interpretation and nonresponse approachKnowledge does not by itself establish behavior
Is the activity generating useful evidence?Scheduled review against the questionDeliverable, responsible owner and reassessment criteriaA completed report is not proof that the uncertainty was resolved

These are planning options, not instructions that every product needs every activity. FDA's March 2005 pharmacovigilance guidance discusses escalation beyond routine reporting when warranted by the product's safety concerns and evidence gaps. Its historical terminology and examples should not be converted into a new universal REMS requirement or a substitute for the current reporting framework.

Fictional data exercise: an internal dashboard divides 12 spontaneous case reports by an estimate of units shipped and labels the result “patient incidence.” The numerator may contain duplicate reports and incomplete ascertainment, while shipped units are neither distinct exposed people nor person-time. Preserve the case information, correct the measure's description and decide whether a suitable data source can answer the incidence question. A smaller reporting ratio than last quarter does not establish that the risk fell.

For each selected activity, specify the accountable scientific and operational owners, access to data, anticipated limitations, deliverable and review point. Describe how important findings enter the applicable safety assessment and reporting process. Do not make scheduled plan review a waiting point for a time-sensitive obligation, or change reporting frequency without assessing the actual requirements.

Keep risk characterization and risk minimization connected but distinct. Finding out why an event occurs and implementing a control against it may need different evidence and owners. If FDA requires a REMS, move to the REMS preparation guide and its actual program requirements. A particular postmarketing study obligation also needs its own identity, basis and milestone record.

Your preparation checklist

0/3 checked

Use this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.

Frequently asked questions

Is every US risk-management plan a REMS?

No. Pharmacovigilance, additional research and risk-minimization activities can have different purposes and regulatory bases. Establish the actual FDA correspondence and product context. Neither the phrase risk management nor the existence of Module 1.16 proves that a REMS is required or that an existing document constitutes one.

Can spontaneous reports divided by sales be called an incidence rate?

Not without a defensible numerator, exposed population and relevant time basis. Spontaneous reporting has ascertainment and reporting limitations, and sales may be only an exposure surrogate. FDA’s pharmacovigilance guidance distinguishes reporting rates from incidence and cautions against interpreting reporting-rate comparisons as actual comparative risk.

Does a safety signal establish that the drug caused the event?

No. A signal warrants an appropriate evaluation of the evidence, chronology, alternative explanations and relevant data. Preserve the distinction between the observation and the causal assessment. The plan should identify how uncertainty will be investigated rather than rewriting a possible association as an established product risk.

Can an EU risk-management plan simply be renamed for the US submission?

Do not assume that another jurisdiction’s structure or obligations establish the US task. Identify the FDA question, applicable product requirements and relevant evidence, then prepare the appropriate US document. Retain the provenance of shared scientific information and assess each jurisdiction’s program requirements separately.

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Guidance

FDA: Format and Content of a REMS Document ↗

January 2023 final guidance; III.A–F and IV. Distinguishes REMS document, materials and supporting document. Checked September 22, 2026.

Guidance

FDA: Good Pharmacovigilance Practices and Pharmacoepidemiologic Assessment ↗

March 2005 final; sections III–VII. January 2025 production header is not a new substantive guidance revision. Scope excludes blood/blood components. Checked September 22, 2026.

Technical specification · placement only

FDA eCTD v4.0 comprehensive hierarchy ↗

Version 2.2, February 2025. Section 1.16. A heading identifies placement, not mandatory applicability.

Talk with Assyro about your next document