Skip to content
Assyro AI
Assyro AI
Module 1
1.17
Letter

How to prepare postmarketing requirement and commitment correspondence

Tie each request or update to the correct obligation, study, milestone and agency record.

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

How do you prepare correspondence about an FDA postmarketing study?

Identify the exact PMR or PMC, its original and subsequent agency records, study identifiers and milestones. State the specific action requested, supporting progress evidence and current status. Distinguish completion of study work, submission of its report and FDA’s determination of fulfillment or release. Preserve the original schedule when explaining FDA status categories; a revised forecast alone does not erase a delay.

Before you begin

Correspondence about an actual postmarketing requirement (PMR) or commitment (PMC). PMRs have a statutory/regulatory basis; PMCs are agreed studies not required by such authority. Reporting duties and agency decisions still need product-specific verification.

What you will prepare: A study-specific communication with the original obligation, evidence of current status and a clearly bounded requested action.

Sections covered in this guide (3)

Recover the original requirement or commitment

Obtain the approval or postapproval letter, exact wording, identifier, study/protocol references and milestones, including later agency changes. Distinguish PMR from PMC using the actual basis rather than an old spreadsheet label. Public databases can assist reconciliation but are not a substitute for the product correspondence and may omit proprietary commitments.

Write for one defined decision

State whether you are submitting a protocol, proposing a milestone change, reporting a problem, providing a report or requesting a status determination. Link the requested action to the relevant identifier. Give the original and currently agreed schedule, actual progress, supporting evidence and the implications of a change. If several obligations are discussed, separate their facts and requested actions; one completed study does not automatically satisfy another.

Use status language that the evidence supports

Distinguish study completion, report submission and FDA determination that an obligation is fulfilled or released. Do not mark an obligation closed merely because a final report was uploaded. A request to change a date is not an accepted extension. Reconcile the correspondence with the applicable annual status-report process and any separate reporting requirements; this guide does not replace them.

Fictional example: enrollment delay

Recruitment is behind plan and the sponsor proposes a later completion date. Explain actual enrollment, causes, mitigation, evidence for the revised forecast and the precise requested milestone change. Preserve the existing obligation until its status changes through the applicable process. If the original letter is missing, recover it before describing a date as agreed or a study as voluntary.

Keep the obligation, the forecast and the agency disposition separate

Create one working record for each requirement or commitment before drafting the letter. A study can support more than one question, and an application can contain several obligations. Neither relationship means that completing one automatically closes the others.

Keep the obligation, the forecast and the agency disposition separate
RecordEvidence to retainDrafting consequence
Obligation identityActual PMR/PMC number, application and exact agency wordingDo not use a database row position as the identifier
Regulatory basisOriginal letter and any subsequent agency changesDistinguish a requirement from an agreed commitment
Study relationshipProtocol, versions, cohorts and reports linked to the obligationExplain what part of the obligation the submitted artifact addresses
ScheduleOriginal milestone, agency correspondence and current forecastKeep changes visible rather than overwriting the original dates
ProgressActual study activity, analysis and report status with cutoffSupport the reason for delay or claimed milestone completion
Requested decisionExact change or disposition sought, rationale and attachmentsA request remains a request until the applicable process establishes its state
Reporting relationshipRelevant status-report and prior submission referencesCorrespondence does not automatically replace other reporting duties

FDA's public FAQ distinguishes pending, ongoing, delayed, terminated and submitted as open categories, and fulfilled or released as closed categories. In that framework, “submitted” means the final report has reached FDA but the applicant has not received written fulfillment or release notification. Do not map a successful upload directly to a closed obligation.

The FAQ defines delay against the original schedule, assessing each phase in its own right. Preserve that baseline even when the team develops a new operational forecast or requests a milestone change. Explain the actual phase, its dates and any agency correspondence; a rewritten internal schedule cannot make historical performance on time. A delay in one phase need not persist as the status if the study gets back on its original schedule in the next phase.

Fictional status exercise: final-report submission was originally scheduled for June, but analysis runs late and the team forecasts September. In August, the tracker labels the study “on time” because September has not arrived. Correct the narrative to show the original milestone, actual delay, revised forecast, mitigation and requested action. After the report is submitted, use the appropriate submitted state until the agency disposition supports closure; neither the forecast nor the upload is a fulfillment decision.

Use public data as a cross-check. FDA notes that database updates can lag and that commitments containing proprietary information, such as some chemistry/manufacturing work, are excluded. Absence from the public database therefore does not establish absence of an obligation. Recover the actual letter when identifiers or dates conflict.

For an enrollment problem, provide the relevant progress evidence and a justified plan rather than a generic request for more time. If the proposal changes a population, endpoint or study design, explain how the revised work would still address the obligation. Use the REMS assessment guide only for that distinct assessment task; a REMS metric and a postmarketing study commitment are not interchangeable merely because both concern safety.

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 a PMR the same as a PMC?

FDA distinguishes a PMR required under a statute or regulation from a PMC the sponsor agreed to conduct without that requirement. Establish the actual agency record and basis; older documents sometimes used commitment more broadly. Do not classify the obligation solely from an inherited spreadsheet abbreviation.

Does final-report submission mean the obligation is fulfilled?

No. FDA’s FAQ distinguishes submitted from fulfilled or released. A submitted final report remains in an open status until the applicable written agency disposition establishes closure. Preserve evidence of the submission and the later decision separately rather than closing the obligation when the file uploads.

Can a revised forecast remove delayed status against the original schedule?

Not simply by replacing the dates in an internal tracker. FDA’s FAQ defines delay against the original schedule and considers each phase separately. Explain actual progress, the original milestone, the revised forecast and relevant agency correspondence. A requested change is not proof of an accepted extension or historical timeliness.

Does absence from FDA’s public database prove that no commitment exists?

No. FDA identifies proprietary commitments that are excluded from the public database and notes that updates may lag. Use the database to reconcile, then verify the original and subsequent product correspondence. A missing public row or blank field is not evidence that the sponsor has no obligation.

Sources and revisions

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

FDA resource

FDA: Postmarketing Requirements and Commitments ↗

Live FDA introduction and definitions checked September 22, 2026. Distinguishes required studies from agreed commitments; actual product letters determine obligations.

FDA resource

FDA: Postmarketing Requirements and Commitments FAQ ↗

Questions 10, 12, 17 and 20; live page reopened October 6, 2026. Read original-schedule delay, submitted versus closed status, missing public fields and update lag. Product letters remain controlling for the actual obligation.

Technical specification · placement only

FDA eCTD v4.0 comprehensive hierarchy ↗

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

Talk with Assyro about your next document