Getting a QHP application through review is not a single event. Submission opens a back-and-forth with CMS and, depending on your exchange model, your state DOI. That cycle, not the submission itself, is the actual work of getting certified. Teams that manage the cycle deliberately are better positioned to respond quickly, protect deadlines and prevent one correction from creating inconsistencies elsewhere.

In this episode of Regulatory Joe, we walk through how the QHP review and certification cycle works and what it means for ACA issuer teams managing plan year filings.

How Does the QHP Review Cycle Actually Work?

Your application doesn’t get reviewed as one document. It gets broken into review areas, like benefits, service area, network adequacy and prescription drug data, and each one moves through review on its own clock.

That’s why review results arrive in stages rather than as one final report. Each review area is evaluated separately and may reach resolution at a different point in the cycle.

Each review area either clears or comes back needing more from you. Your state calls that finding an objection. CMS calls the equivalent finding a deficiency. From there, the process moves in rounds. The issuer responds, the reviewer evaluates the correction and a new result either clears the review area or identifies additional work. The cycle continues until all required corrections are resolved.

For FFE and SBE-FP filings, teams need to track federal QHP review separately from state approval and certification responsibilities. CMS reviews the application against federal certification requirements, while the state may be reviewing rates, forms, binders and other state-specific requirements. Progress in MPMS does not necessarily mean the related state filing is resolved, and state approval does not automatically close the federal review.

Full SBE states manage QHP certification through their own state-defined processes rather than the standard federal MPMS review used for FFE certification. Issuers still need to confirm how responsibilities are divided among the state marketplace, DOI and any other reviewing entities, because a full SBE does not necessarily mean one system or one reviewer.

How to Handle a QHP Correction from Deadline to Resolution

How a correction gets resolved depends almost entirely on one thing: where you are relative to the final submission deadline.

Before the applicable final submission deadline, issuers can generally revise and resubmit application data through the regular submission process without a post-deadline data change request. That is the most flexible window, which is why teams should resolve as many findings as possible before it closes.

After the applicable deadline, the correction path depends on who identified the issue, the stage of review and the issuer’s exchange model. Changes to QHP application data generally require a formal data change request or an authorized correction window before the update can take effect. For SBE-FP filings, issuers work through the state rather than submitting the request directly to CMS.

For most requested QHP template changes, CMS also requires a Change Analysis Report showing what changed from the previously submitted version, with certain exceptions such as the Network Adequacy Template.

Where you actually file the fix depends on your exchange model:

Exchange Model	General Correction Path	What the Issuer Must Confirm
Federally Facilitated Exchange (FFE)	Federal QHP application corrections are generally submitted through MPMS. Related state filings may also need to be updated.	Whether the change affects corresponding rate, form, binder or state-approved data.
State-Based Exchange on the Federal Platform (SBE-FP)	Corrections may require coordination across state filing systems and the federal platform. The state may control part of the transfer or resubmission process.	Which party submits or transfers the revised data and whether state or federal approval is required first.
Full State-Based Exchange (SBE)	Corrections follow the marketplace’s state-defined certification process rather than the standard FFE MPMS route.	Which state system, reviewer and approval path apply to the affected filing component.

A correction only counts once your data matches everywhere it needs to, not just in the system where you fixed it. Update your QHP application without also aligning your state-approved filing, and the gap just moves instead of closing.

Unresolved inconsistencies can create a separate compliance concern and may require additional correction, regulator follow-up or other action depending on the nature and timing of the discrepancy.

6 Tips for Filing Teams on Managing the QHP Review Cycle

• Prioritize findings by deadline and downstream impact. Resolve corrections that affect multiple templates, systems or approvals before isolated issues.
• Track federal and state status separately. Use distinct fields for CMS review, DOI disposition, marketplace certification and any required data transfer.
• Track the root cause behind each objection, not just the fix. Whether it traces back to a PBM or vendor, an internal process or a plan design choice determines who should own it and whether it shows up again next cycle.
• Confirm the correction route before changing data. Identify the submission system, approval authority and required documentation for the specific state and review stage.
• Reconcile every affected record after resubmission. Verify that MPMS, SERFF and approved source documents reflect the same final information.
• Preserve the full correction history. Record the finding, response, revised file, approval and final resolution by review area.

QHP review is a cycle of findings, responses, resubmissions and reconciliation across federal and state processes. The teams that manage it well maintain a complete, defensible filing record, understand who controls every next step and verify that the final approved data is consistent everywhere it appears.

Watch the full episode for more of Joe’s insights on the QHP review and certification cycle.

Getting a QHP application through review is not a single event. Submission opens a back-and-forth with CMS and, depending on your exchange model, your state DOI. That cycle, not the submission itself, is the actual work of getting certified. Teams that manage the cycle deliberately are better positioned to respond quickly, protect deadlines and prevent one correction from creating inconsistencies elsewhere.

In this episode of Regulatory Joe, we walk through how the QHP review and certification cycle works and what it means for ACA issuer teams managing plan year filings.

How Does the QHP Review Cycle Actually Work?

Your application doesn’t get reviewed as one document. It gets broken into review areas, like benefits, service area, network adequacy and prescription drug data, and each one moves through review on its own clock.

That’s why review results arrive in stages rather than as one final report. Each review area is evaluated separately and may reach resolution at a different point in the cycle.

Each review area either clears or comes back needing more from you. Your state calls that finding an objection. CMS calls the equivalent finding a deficiency. From there, the process moves in rounds. The issuer responds, the reviewer evaluates the correction and a new result either clears the review area or identifies additional work. The cycle continues until all required corrections are resolved.

For FFE and SBE-FP filings, teams need to track federal QHP review separately from state approval and certification responsibilities. CMS reviews the application against federal certification requirements, while the state may be reviewing rates, forms, binders and other state-specific requirements. Progress in MPMS does not necessarily mean the related state filing is resolved, and state approval does not automatically close the federal review.

Full SBE states manage QHP certification through their own state-defined processes rather than the standard federal MPMS review used for FFE certification. Issuers still need to confirm how responsibilities are divided among the state marketplace, DOI and any other reviewing entities, because a full SBE does not necessarily mean one system or one reviewer.

How to Handle a QHP Correction from Deadline to Resolution

How a correction gets resolved depends almost entirely on one thing: where you are relative to the final submission deadline.

Before the applicable final submission deadline, issuers can generally revise and resubmit application data through the regular submission process without a post-deadline data change request. That is the most flexible window, which is why teams should resolve as many findings as possible before it closes.

After the applicable deadline, the correction path depends on who identified the issue, the stage of review and the issuer’s exchange model. Changes to QHP application data generally require a formal data change request or an authorized correction window before the update can take effect. For SBE-FP filings, issuers work through the state rather than submitting the request directly to CMS.

For most requested QHP template changes, CMS also requires a Change Analysis Report showing what changed from the previously submitted version, with certain exceptions such as the Network Adequacy Template.

Where you actually file the fix depends on your exchange model:

Exchange Model	General Correction Path	What the Issuer Must Confirm
Federally Facilitated Exchange (FFE)	Federal QHP application corrections are generally submitted through MPMS. Related state filings may also need to be updated.	Whether the change affects corresponding rate, form, binder or state-approved data.
State-Based Exchange on the Federal Platform (SBE-FP)	Corrections may require coordination across state filing systems and the federal platform. The state may control part of the transfer or resubmission process.	Which party submits or transfers the revised data and whether state or federal approval is required first.
Full State-Based Exchange (SBE)	Corrections follow the marketplace’s state-defined certification process rather than the standard FFE MPMS route.	Which state system, reviewer and approval path apply to the affected filing component.

A correction only counts once your data matches everywhere it needs to, not just in the system where you fixed it. Update your QHP application without also aligning your state-approved filing, and the gap just moves instead of closing.

Unresolved inconsistencies can create a separate compliance concern and may require additional correction, regulator follow-up or other action depending on the nature and timing of the discrepancy.

6 Tips for Filing Teams on Managing the QHP Review Cycle

• Prioritize findings by deadline and downstream impact. Resolve corrections that affect multiple templates, systems or approvals before isolated issues.
• Track federal and state status separately. Use distinct fields for CMS review, DOI disposition, marketplace certification and any required data transfer.
• Track the root cause behind each objection, not just the fix. Whether it traces back to a PBM or vendor, an internal process or a plan design choice determines who should own it and whether it shows up again next cycle.
• Confirm the correction route before changing data. Identify the submission system, approval authority and required documentation for the specific state and review stage.
• Reconcile every affected record after resubmission. Verify that MPMS, SERFF and approved source documents reflect the same final information.
• Preserve the full correction history. Record the finding, response, revised file, approval and final resolution by review area.

QHP review is a cycle of findings, responses, resubmissions and reconciliation across federal and state processes. The teams that manage it well maintain a complete, defensible filing record, understand who controls every next step and verify that the final approved data is consistent everywhere it appears.

Watch the full episode for more of Joe’s insights on the QHP review and certification cycle.