Skip to main content

FedRAMP 20x: Check Migration-Report Exemptions Before the Inbox Test

Match the offering to the listed exemption, preserve the CR26 qualifier for Class B/C, and read the actual message. Exempt offerings still receive an acknowledgment test.

Written by Boundera Team|November 12, 2026|4 min read

Main question

How should a 20x team check migration-report exemptions before the FY27 Q1 Inbox test?

Before assigning a migration-report task, establish which offering and certification basis the message concerns. For a 20x security lead, the useful question is specific: does this offering match a listed collection exemption, and what response does its actual Security Inbox message request?

The workflow below is our suggested preparation process. It helps preserve the basis for a response without turning an uncertain status into an exemption claim.

Check the collection exemption for the exact offering

FedRAMP's collection guidance, updated November 10 and checked November 12, 2026, lists 20x Class A and 20x Class B and C with the CR26 qualifier among the migration-report collection exemptions. It says offerings outside the migration process will receive a standard Emergency Test requiring acknowledgment. Official collection guidance

Preserve “CR26” when reviewing a Class B or C record. An old pilot label alone is not evidence that an offering matches that qualified exemption. Use our limited-pilot versus full-CR26 claim guide for the separate task of checking certification wording.

Do not convert a collection exemption into a blanket exemption from applicable VDR/VER reporting or Security Inbox duties. The collection page addresses this data call. Keep ongoing operating obligations in their own review.

Build a short owner-and-response record

We suggest preparing one record per offering, with the following information:

Working fieldWhat the team should establish
Offering identityMatch the service name and FedRAMP ID to the record being reviewed.
Current profile and statusRetain the dated source rather than relying on a company-level statement.
Certification basisRecord the evidence supporting the relevant Class A or CR26 Class B/C description.
Collection assessmentIdentify the listed exemption being considered and any unresolved mismatch.
Received messageRetain the actual notification and the requested response.
Action owner and backupAssign who will respond, who will check completion and who covers absence.

These are internal working fields, not a new FedRAMP form. Keep links to the evidence so a backup owner can reconstruct the decision without asking the original reviewer to repeat the research.

For example, imagine a team has a historical pilot announcement but no current evidence establishing the CR26 basis it intends to claim. Record the basis as unresolved. Ask the person responsible for certification records to obtain the missing evidence before declaring the offering exempt. This example does not determine whether that particular offering must submit a migration report.

Treat the forecast dates as planning inputs

The page gives December 1–10, 2026 as the likely send window, with December 3 as the current target. It anticipates a December 17 response deadline at 2 p.m. Eastern and warns that details may change until the test. These are forecasts, not a substitute for the actual notification. Expected timeframes

Use those dates to schedule an internal readiness check and arrange backup coverage. When the message arrives, have the owner read its requested action and deadline, compare it with the preparation record, and update the task. Keep the old planning note available so a changed date is explained rather than silently overwritten.

An automatic reply can be useful evidence of receipt. For this internal workflow, track receipt and completion as separate events so the team can see whether the requested response was actually handled.

Escalate conflicting evidence without ignoring the message

If the received request conflicts with the team's exemption assessment, retain both. Capture the offering identifier, the exact request, the source and date supporting the exemption assessment, and the specific discrepancy. Seek official clarification through the relevant FedRAMP support route while keeping an owner assigned to the message.

Avoid two unsupported shortcuts: silently ignoring the request because an internal sheet says exempt, or announcing that every historical pilot must submit because the evidence is incomplete. The useful next action is to resolve the offering-specific question.

Likewise, a report template or schema that can represent a certification type does not, by itself, establish who must respond to a particular collection. Use the applicability guidance and the received request to make that decision; use format tools for the separate task of preparing information when it is requested.

Rehearse the handoff before the test

Have the backup owner walk through one preparation record. Can they find the current offering evidence, identify the unresolved questions and locate the response owner? Then rehearse handling a message whose requested action differs from the planning note.

Our Security Inbox workflow covers delivery and routing. For this preparation task, finish with an offering-specific record that supports the response you intend to give and clearly identifies any point that still needs clarification.

Frequently asked questions

Which 20x profiles does the collection page list as exempt?

The November 10 guidance lists 20x Class A and Class B/C with the CR26 qualifier. Check the current guidance and the actual offering-specific message.

Does an exemption mean we can ignore the test?

No. The collection page says offerings outside the migration process receive a standard Emergency Test requiring acknowledgment.

Next step

If you want to turn this guidance into an execution plan, the product side handles control mapping, SSP drafting, and evidence collection.

Related articles