Rev5 Class D to 20x: RFC-0036 Proposes a Class C Step

A Rev5 Class D certification does not answer every question about a move to 20x Class D. RFC-0036 proposes a progression through 20x Class C, with a general six-month condition, a special exemption route and a distinct Phase 4 pilot note.

For a team considering a Rev5 Class D to FedRAMP 20x Class C transition, those differences belong in the planning discussion before anyone estimates a Class D completion date. As checked on October 26, 2026, RFC-0036 still presents FRC-CLD-PCD as proposed language for the Class D Cloud-Hosted pilot work.

Read the proposed routes separately

Proposed FRC-CLD-PCD uses MUST for providers seeking 20x Class D: maintain a 20x Class C certification without corrective action for at least six months, or receive a special exemption from FedRAMP to apply directly because of an urgent critical need. The proposal says such exemptions may include services prioritized by the FedRAMP Board and limited pilots. RFC-0036, Progressive Certification to Class D

The pilot note does not say a pilot Class C certification satisfies the prerequisite. It also does not settle every question about participation, corrective-action circumstances or selection. Use the wording as a specific planning condition, not a selection promise.

Preserve the Rev5 distinction without assuming concurrent paths

The RFC says providers with Rev5 Class D would not be expected to give up that certification, while transitions to 20x Class D would still be expected to pass through 20x Class C first. It anticipates that many offerings would seek to maintain Rev5 Class D after obtaining 20x Class D. That is proposed transition context, not an announcement that Rev5 Class D is retiring.

Keep certification type, path and class explicit. The existing FRC-CSO-POP rule prohibits seeking both Rev5 Program Certification and 20x Program Certification for the same offering. Its note does not prevent seeking and maintaining Rev5 Agency Certification with 20x Program Certification, but strongly discourages that combination because of added complexity and confusion. The proposal's retention expectation is not blanket permission for concurrent Program certifications.

Build a planning comparison from actual records

As an editorial practice, put the following facts beside each proposed scenario:

• The offering's current certification type, path and class.
• Whether its 20x Class C status is full non-pilot or pilot.
• The certification history and any corrective-action information relevant to the scenario.
• Any actual FedRAMP exemption, separated from unresolved questions about one.
• The source and date of the proposal language used in the plan.

This is a working comparison, not a new application form. If a fact is unclear, assign an owner to resolve it instead of filling the gap with an assumed route. In particular, do not treat the pilot's six-month exception as evidence that any current corrective-action situation is acceptable.

Keep the sequencing question separate from architecture and agency involvement. The hosting dependency proposal addresses the former; the Phase 4 agency participation article addresses the latter.

Before committing to a transition plan, recheck the current proposal, applicable certification rules and actual pilot participation information. A useful plan shows which route is being considered and which facts still need resolution; it does not convert a proposed prerequisite into an enrollment or delivery promise.