For most small and mid-size defense contractors, plan on 9 to 18 months from the first gap assessment to a CMMC Level 2 certificate recorded in SPRS. Remediation is the long pole — typically 6 to 12 months. The C3PAO assessment itself is 1 to 3 weeks of fieldwork, but scheduling one can add 1 to 3 months, and any POA&M items must close within 180 days. The certificate is then valid for three years.
The timeline, phase by phase
These are typical ranges from our engagements, not guarantees. Your scope, starting point, and vendor dependencies move every number.
| Phase | Typical duration | What’s happening |
|---|---|---|
| 1. Scoping | 2–4 weeks | Identify where CUI enters, lives, moves, and leaves. Decide enclave vs. enterprise. Inventory people, systems, and external service providers (MSP, cloud, ESP). |
| 2. Gap assessment | 3–6 weeks | Assess all 110 requirements against their assessment objectives (NIST SP 800-171A). Produce a SPRS score and a prioritized remediation list. |
| 3. Remediation | 3–12 months | Fix technical gaps (MFA, FIPS-validated encryption, logging, configuration baselines) and build the process gaps (incident response, access reviews, training, change control). |
| 4. Documentation & evidence | 2–3 months, in parallel | Write the System Security Plan, policies, and procedures; collect artifacts that prove each objective is met and has been operating. |
| 5. Mock assessment | 2–4 weeks | A dry run against 800-171A, ideally by someone who didn’t do the remediation. Fix what fails. |
| 6. C3PAO scheduling | 1–3 months lead time | Select a C3PAO from the Cyber AB marketplace, agree scope and dates, submit pre-assessment materials. |
| 7. Assessment | 1–3 weeks | Readiness review, evidence examination, interviews, and testing. Daily out-briefs; preliminary results at the end. |
| 8. Results & POA&M closeout | 0–180 days | Final status (or Conditional status) posted. Any POA&M items must be closed and verified by a closeout assessment within 180 days. |
Add the midpoints and you land around 12 months. A well-scoped enclave at an organization with an executive sponsor and an MSP that already understands 800-171 can do it in 6 to 9. A sprawling enterprise scope with legacy systems and documentation debt will take 18 or more.
Why remediation is the long pole
Most of the 110 requirements aren’t hard individually. Three things make the aggregate slow:
- FIPS-validated cryptography (SC.L2-3.13.11). Not “we use encryption” — the module must be on the NIST CMVP list in the validated configuration. Replacing non-compliant VPNs, backup tools, or storage can take a quarter on its own.
- MFA everywhere CUI is (IA.L2-3.5.3). Network access by privileged and non-privileged users, plus local access for privileged users. Legacy applications and shop-floor equipment are where this stalls.
- Evidence of operation. An assessor wants to see access reviews that happened, logs that were reviewed, training that was completed, incidents that were handled. Processes you turn on in month 10 have no history in month 11. Start the operational controls early, even before the technical ones are finished.
What stretches the timeline
- Enterprise scope when an enclave would do. Every laptop, printer, and SaaS tool in scope is one more thing to secure and evidence.
- External service providers that aren’t ready. If your MSP or cloud provider handles CUI, their controls are in your assessment. Get their shared-responsibility matrix and FedRAMP (or equivalent) status in month one, not month ten.
- No named owner. Programs that are “IT’s project” slip. Programs with an executive sponsor who clears budget and decisions weekly don’t.
- Documentation debt. Writing an SSP from zero is 100+ hours. Writing one while the environment keeps changing is more.
- C3PAO scheduling. While Phase 2 is suspended, no phase date is driving demand for assessments. If a prime or a solicitation asks for a voluntary C3PAO assessment, book it once your evidence is ready; if the Department sets a new phase date, expect scheduling pressure to return.
What shortens it
- A tight, honest CUI enclave (often Microsoft GCC High or an equivalent) with a small user population.
- An existing, accurate NIST SP 800-171 self-assessment score in SPRS — you’re starting at phase 3, not phase 1.
- Policies and procedures that already match how people work, so “documentation” is editing, not inventing.
- Running the mock assessment with someone independent of the remediation team, so the real assessment holds no surprises.
What the Phase 2 suspension changes (and what it doesn’t)
Phase 2 of the rollout — Level 2 (C3PAO) certification as a condition of award in new solicitations — was scheduled for November 10, 2026. On July 13, 2026 the Department CIO suspended it, along with Phases 3 and 4, and stood up a CMMC Reform Task Force; Class Deviation 2026-O0025 Revision 3 (September 3, 2026) put the pause into the contracting clause. The Task Force’s recommendations went to the CIO in mid-September and hadn’t been published as of mid-November 2026.
Three things did not change:
- The 110 requirements are a contract obligation today. DFARS 252.204-7012 has required NIST SP 800-171 since 2017, and your SPRS score and annual affirmation are still live. Nothing about the suspension lowers the bar — it only pauses the third-party sign-off.
- Self-assessments can still be required. Contracting officers may include Level 1 (Self) or Level 2 (Self) in solicitations now. A false self-assessment is a False Claims Act problem regardless of what happens to Phase 2.
- The rule’s end date stands. 32 CFR Part 170 still names November 10, 2028 for full implementation, and that date wasn’t moved by the deviation.
So the timeline above is still the timeline. What the suspension buys you is the C3PAO scheduling pressure — not the remediation. Primes are already asking for Level 2 readiness evidence from subcontractors, and a voluntary C3PAO assessment remains valid and recordable. If you’re mid-remediation, keep going; if you were about to book an assessor, you can choose to finish clean first and book when the Task Force outcome is public.
After the certificate
A Level 2 (C3PAO) certificate is valid for three years. Each year a senior official affirms in SPRS that you still meet all 110 requirements. Significant changes to the assessed environment can require a reassessment sooner. Budget for maintaining the program — access reviews, log review, training, vulnerability remediation — as a recurring operating cost, because the annual affirmation is a legal statement that it’s all still happening.
