Failing a CMMC assessment sounds like a buzzer at the end of a game. For small businesses that sell to the DoD (or to primes), it can feel the same way because CMMC shows up where it hurts most: contract awards, onboarding, and option years.
Here’s the part that surprises people. “Fail” doesn’t look the same at Level 1 and Level 2. At Level 1, the problem is usually that I can’t honestly self-attest yet, so I shouldn’t claim I meet the requirement. At Level 2, the problem is that I don’t earn certification (or I only get a short conditional window with strict limits).
The good news: failing is a business risk, but it’s also fixable. What matters is what I do next.
What it means to fail a CMMC assessment (Level 1 vs Level 2)

When I say “I failed,” I’m really talking about one of two situations.
At CMMC Level 1, there isn’t a third-party pass/fail event. Level 1 is an annual self-assessment tied to basic safeguarding for Federal Contract Information (FCI). Failing, in practice, means I can’t truthfully say I meet all required practices right now, or I can’t support that claim with evidence if someone asks.
At CMMC Level 2, the stakes rise because Level 2 aligns to the 110 practices of NIST SP 800-171 for Controlled Unclassified Information (CUI). Depending on the contract, Level 2 may be self-assessed (in some cases) or it may require a third-party assessment by a C3PAO. In the third-party world, “fail” becomes real: no certification, or a conditional outcome with a hard deadline.
A key point that keeps me grounded: assessors don’t award me contracts. Contracting teams and program offices set the required level for a solicitation, then they check my status at award time. If I don’t meet the requirement on paper when it counts, I can do everything else right and still lose.
For the official program overview, I point people to the DoD’s own About CMMC page. It helps set expectations before spending money or scheduling an assessment.
Level 1 self-assessment: failing means I can’t honestly attest (and that blocks awards)
Level 1 is simple on purpose, but it’s not optional. If I can’t honestly attest that all Level 1 practices are met, I’m not “ready,” even if my IT feels decent day to day.
In real life, Level 1 failure shows up like this:
- I discover gaps during my internal review (no MFA on every access path, weak account reviews, missing basic policies).
- A prime asks for proof of my status and my story doesn’t match my evidence.
- A DoD review later finds my self-attestation was wrong.
The risk here isn’t just embarrassment. A false attestation can create contract problems and legal exposure. I don’t need to panic, but I do need to treat accuracy like money in the bank. If my controls aren’t met, I fix them, document them, then update what I report.
Level 2 third-party assessment: failing means no certification, or a short POA&M clock if I qualify
If I’m going through a Level 2 third-party assessment, “fail cmmc assessment” has a clear meaning: I don’t receive Level 2 certification.
Outcomes usually fall into three buckets:
Pass: All practices are met, and I earn certification.
Conditional (with a POA&M): I’m close enough to qualify for a limited window to finish small items. The common rule of thumb is I need a high score (often discussed as at least 88 out of 110) and only certain lower-impact items can go on a POA&M.
Fail: I’m below the threshold, I have gaps that cannot be deferred, or my documentation is incomplete enough that the assessor can’t verify what I’m doing.
If I get conditional status, the clock matters. POA&M items have a hard 180-day deadline to close, or that conditional status can expire. If you want a plain explanation of which controls tend to be blocked from POA&Ms, this breakdown is helpful: CMMC Level 2 POA&M restrictions.
What happens next after I fail: reports, POA&Ms, and contract impact
Failing doesn’t mean I shut down. It means my cybersecurity gaps become visible and measurable, and that changes how buyers and primes treat my bids.
First, there’s documentation. Then there’s business impact.
How findings are documented (gap list, SSP updates, and POA&M rules)
At Level 1, my “report” is mostly internal. I track which practices aren’t met, assign owners, and keep evidence that shows the fix is real. Level 1 still needs proof, even when no one is visiting my office.
At Level 2 with a C3PAO, documentation becomes formal. I should expect to see:
- A list of practices marked MET or NOT MET
- Notes about what evidence was reviewed (screenshots, logs, tickets, policy statements)
- An updated SSP expectation (my System Security Plan has to match reality)
- If allowed, a POA&M tied to specific gaps, with clear ownership and dates
A good POA&M is not “we’ll fix this later.” It’s more like a repair receipt: what broke, who’s fixing it, the steps, the due date, and what proof closes it. This guide is a solid reference when I’m building that plan: what to include in your POA&M.
One more practical detail: a C3PAO can identify gaps, but they can’t consult me through remediation. That separation protects the process, but it means I need a plan before the assessor walks in.
Contract eligibility and flowdown: why a failed result can knock me out of bids fast
This is where the pain shows up. If a solicitation requires a certain CMMC level, and I can’t show the right status at award, my proposal may be rejected as non-responsive. Even if I’m the best technical fit, I’m still out.
Here are common business outcomes I see after a failure:
Award delays: I’m asked to re-compete later, or the prime shifts work away while I fix my status.
Lost options or follow-on risk: If my status drops during performance, it can trigger reporting duties and put future work at risk.
Supply chain squeeze: Primes often ask for proof before onboarding a subcontractor. If I can’t show it, they may choose a less risky vendor.
This hits small businesses in very specific ways. If my CUI scope is messy, like CUI living in a broad Microsoft 365 tenant without clear boundaries, assessment evidence gets harder. If my MSP has been “helping” but not documenting, I might be doing the work without being able to prove it.
If I want a real-world view of what companies do after an unsuccessful assessment, this is worth reading: What Happens After an Unsuccessful CMMC Assessment.
How I recover fast: remediation steps, timelines, reassessment prep, and a next-steps checklist
When I fail, my goal is speed with control. I don’t want random fixes. I want the shortest path back to eligibility.
My remediation plan and realistic timelines (Level 1 vs Level 2)
Here’s the approach I use with small teams:
Triage first: I sort findings into “must-fix to qualify” versus “can improve after.”
Assign owners: Every gap has a name next to it, not a committee.
Update the paper: Policies and the SSP must match what’s actually happening.
Harden the systems: MFA, access control, patching, device baselines, backups, logging.
Prove it: Tickets, screenshots, audit logs, training records, and change notes.
Timelines depend on how deep the gaps go:
- Level 1: Often 1 to 6 months if I’m close and my environment is small.
- Level 2: Often 3 to 18 months, especially if CUI scope is large or identity and logging need work.
- If I received conditional Level 2, the 180-day POA&M deadline becomes my schedule, not my preference.
For POA&M guardrails and common mistakes, I also like this summary: CMMC POA&Ms guidelines and limitations.
How I prepare for reassessment (and avoid failing the same way twice)
I treat reassessment prep like a fire drill. If my staff can’t “show me” the evidence fast, I’m not ready.
What helps most:
- A mock assessment with someone who wasn’t involved in the build
- Tight scope, especially where CUI lives in Microsoft 365
- Short, repeatable processes (joiner/mover/leaver, account reviews, patch cycles)
- Staff coaching on where evidence is stored and how to explain it
- Scheduling assessor time early, because calendars fill up
FAQs and next steps checklist
Can I keep performing on an existing contract?
Sometimes, yes, but it depends on contract terms and clauses. I also plan for status-change reporting requirements during performance.
Can I bid while I fix issues?
If the solicitation requires a certification status I don’t have, bidding may be pointless. If it only requires a self-assessment score, I still need my score and evidence to be honest.
What if I miss the 180-day POA&M deadline?
I should expect my conditional status to expire, which puts me back in the “not eligible” bucket for contracts requiring that level.
Can my MSP help?
Yes, as long as they can implement controls, document changes, and support evidence collection. “We handle IT” isn’t evidence by itself.
What do primes want to see?
Clear proof of status, clean scope boundaries, and confidence that I won’t create a compliance problem for the team.
Checklist I follow after I fail a CMMC assessment:
- Collect the assessment results and confirm the failed practices
- Confirm CUI scope (systems, users, locations, cloud tenants)
- Update the SSP so it matches reality
- Build or refine the POA&M with owners, dates, and proof targets
- Fix the must-pass items first (access, MFA, logging, backups)
- Gather evidence as I go (tickets, screenshots, logs, training)
- Update my SPRS entry if I’m in a self-assessment path
- Book reassessment or closeout assessment early
- Confirm contract and subcontract flowdown requirements
- Communicate a clear remediation timeline to my prime
Conclusion
If I fail cmmc assessment requirements, the real penalty is simple: I’m not counted as meeting the level for awards that require it. Level 1 usually fails quietly through an honest self-attestation that I can’t make yet. Level 2 fails loudly because third-party certification is pass, fail, or conditional with a strict 180-day POA&M clock.
I don’t treat failure as a dead end. I treat it like a failed inspection sticker, fix what’s broken, document it, then re-test. If you want help scoping where CUI actually lives, closing the gaps, and building evidence that holds up under review, I can help you get back to an award-ready position.
Discover more from Guide to Technology
Subscribe to get the latest posts sent to your email.
