Section 505-1 of the Federal Food, Drug, and Cosmetic Act sets a default timetable for REMS assessments: 18 months, 3 years, and 7 years after approval, unless FDA requires a different frequency. Drug safety teams read that schedule as the REMS lifecycle and plan accordingly — build it, submit the assessments, wait for the next one. That reading misses the provision that actually reshapes a REMS: section 505-1(g), which lets FDA require a modification whenever new safety information or an assessment finding calls for one, on no fixed schedule at all.

What section 505-1 actually sets on a schedule

Three things in section 505-1 are genuinely calendar-driven. The assessment timetable under 505-1(d) defaults to 18 months, 3 years, and 7 years after initial REMS approval, unless the REMS itself specifies a different frequency. Elements to assure safe use (ETASU) under 505-1(f) are imposed when necessary to mitigate a specific serious risk identified in labeling — a determination made at approval, then revisited at each assessment. And the assessment report itself has to say whether the REMS is meeting its goals and whether the burden on the healthcare delivery system remains justified. None of that is where the mechanism for changing the REMS actually lives.

18/36/84 mo.
Default REMS assessment dates under 505-1(d) — unless the REMS specifies otherwise.
505-1(g)
The modification authority — available whenever a safety finding warrants it, not on a schedule.
505-1(g)(4)
Requires an adequate rationale for any added, modified, or removed REMS goal or element.

Why the assessment clock isn't the modification clock

A modification under 505-1(g) can originate two ways, and neither is bound to the assessment timetable. FDA can determine, from an assessment or from safety information that arrives independently of any assessment, that the REMS needs to change to keep the drug's benefits outweighing its risks or to reduce the burden of complying with it — and require the holder to submit a proposed modification in response. Or the holder can propose a modification on its own initiative, at any time, when it identifies a change worth making. A serious adverse event report, a new labeling change, or a postmarketing study finding can trigger the first path on whatever week it surfaces, years before the next scheduled assessment is due.

  • A safety signal outside the assessment window. New adverse event data or a postmarketing study result can prompt FDA to require a modification immediately, independent of where the REMS sits in its 18-month/3-year/7-year cycle.
  • A labeling change that touches the ETASU. If the labeling change narrows or expands the risk the ETASU was built to mitigate, the REMS elements may need to move with it.
  • A holder-initiated modification. A holder can propose loosening or tightening a REMS element on its own timeline, but still needs a rationale under 505-1(g)(4) that will survive FDA review.
  • A shared system change driven by another participant. If your REMS runs on a shared system, a modification another application holder's assessment or safety finding triggers can reach your own ETASU on their clock.
An approved REMS is not dormant between its scheduled assessments. Section 505-1(g) gives FDA a modification lever that operates on the safety finding, not the calendar. Why the assessment schedule isn't the whole picture

The shared system complication for generics

Where the reference listed drug's REMS includes ETASU, ANDA applicants are generally expected to use a REMS comparable to the branded product's — usually through a single, shared system that the reference listed drug holder and its ANDA holders develop and implement jointly. That structure means an ANDA holder does not fully control the modification timeline for its own product's REMS: when FDA requires or approves a change to the shared system, driven by the reference product holder's assessment or by a safety finding, every participant implements it together. An ANDA holder that assumed its own three-year assessment date was the next relevant milestone can find the shared system has already moved. Questions specific to an ANDA's participation in a shared system REMS — including proposed modifications — go to the Office of Bioequivalence in CDER's Office of Generic Drugs, and for generic and ANDA regulatory strategy more broadly, that contact point is worth having mapped before a modification lands rather than after.

A REMS modification-readiness sequence
  1. Separate the assessment calendar from the modification trigger. Track 505-1(d) dates as reporting deadlines, not as the only moments a change can be required.
  2. Build the rationale file before you need it. Keep safety and utilization data current so a 505-1(g)(4) rationale isn't drafted from scratch under deadline pressure.
  3. Map your shared system dependencies. Know who else participates in your shared system REMS and how their modification reaches your ETASU.
  4. Rehearse the submission. Have the proposed REMS document, rationale, and supporting data ready to assemble quickly, not just the strategy for what you'd propose.

REMS programs are common in pain management and CNS drug development, where the ETASU and the labeling it supports are tightly coupled — a coupling that also means a labeling change can pull the REMS with it faster than a team expecting the next scheduled assessment might plan for. Treating a REMS as a documentation obligation that resets every 18 months, 3 years, and 7 years is the assumption that leaves a modification request looking like a surprise instead of a foreseeable event. It is not exotic work to get ahead of: a current rationale file, a clear picture of shared system dependencies, and a submission package that does not have to be built from a standing start once FDA or your own assessment calls for a change.

Frequently asked questions

Does FDA only modify a REMS on the 18-month, 3-year, and 7-year assessment schedule?

No. That schedule, set under section 505-1(d), governs when the application holder must submit an assessment of the REMS — it is not the only occasion for modification. FDA can require a modification under section 505-1(g) whenever new safety information or an assessment finding shows the REMS needs to change, on whatever timeline that finding arrives.

Who has to submit a proposed REMS modification, FDA or the application holder?

The application holder submits the proposed modification, whether FDA required it or the holder initiated it. Section 505-1(g)(4) requires an adequate rationale supporting the addition, modification, or removal of any REMS goal or element — a rationale FDA can reject if it is not sufficiently supported.

How does a REMS modification affect an ANDA holder on a shared system REMS?

A shared system REMS is developed and implemented jointly by the reference listed drug holder and its ANDA holders. When FDA requires or approves a modification to that shared system, every participant implements it on the shared system's timeline — not on the individual ANDA holder's own assessment calendar. Questions about a specific ANDA's REMS modification go to the Office of Bioequivalence in CDER's Office of Generic Drugs.

Sources & further reading

  1. FDA. Risk Evaluation and Mitigation Strategies (REMS): Modifications and Revisions — guidance for industry. fda.gov
  2. FDA. Development of a Shared System REMS — draft guidance for industry. fda.gov
  3. 21 U.S.C. 355-1 — Risk evaluation and mitigation strategies. govinfo.gov

This article is provided for general informational purposes and reflects the regulatory landscape as of August 2026. It is not legal or regulatory advice. Confirm current REMS requirements with FDA or qualified counsel before acting.