Skip to content
CMMC12 min readUpdated June 6, 2026

CMMC Guide Hub: Levels, SPRS, POA&Ms, Remediation, and Evidence

A practical CMMC learning hub for contractors that need to understand levels, SPRS, self-assessments, certification assessments, POA&Ms, remediation, evidence, and CUI scope.

Built for
Federal contractors trying to turn CMMC language into a real readiness plan
By the end
Know where CMMC touches bids, systems, evidence, timelines, and post-assessment cleanup.
Cluster map

Keep going inside this topic

All guide clusters →
Field guide

CMMC subtree map

Level 1
DoD says POA&Ms are not permitted for Level 1.
Signal
FCI is involved and the requirement expects basic safeguarding.
Response
Prepare self-assessment habits, annual affirmation, and clean evidence for basic practices.
Level 2
Some Level 2 work requires C3PAO certification rather than self-assessment.
Signal
CUI is involved and the solicitation points to CMMC Level 2.
Response
Map CUI scope, NIST 800-171 requirements, assessment path, SPRS, and evidence ownership.
POA&M and remediation
Conditional status can expire if closeout does not happen in the required window.
Signal
An assessment leaves limited unmet requirements that may be remediated after conditional status.
Response
Track owner, evidence, due date, closeout assessment path, and business impact.
CMMC updates
Do not write CMMC pages like static compliance theater. The program changes.
Signal
Rules, phased implementation, assessment bodies, or DoD guidance changes.
Response
Keep a dated update page so contractors can separate stable concepts from fresh program movement.
Part 1

CMMC belongs in capture, not only IT

CMMC affects which contracts a company can realistically pursue, how teaming is structured, what systems can touch contract data, and how evidence is produced when an assessment arrives.

The most useful CMMC library is not a wall of acronyms. It is a map from bid requirement to data scope, control owner, evidence, assessment path, remediation, and ongoing affirmation.

Part 2

Build the cluster around workflow

The next CMMC pages should be organized by the decisions contractors actually face: Level 1, Level 2, CUI scope, SSP, SPRS, POA&M, remediation, evidence, assessment, affirmations, and DFARS clauses.

That structure gives readers somewhere to go when a solicitation says CMMC, when a subcontractor asks about CUI, or when a customer needs proof before award.

Part 3

Create an updates lane

CMMC needs an updates page for phased implementation, assessment guidance, rule movement, and source changes. That keeps time-sensitive material separate from evergreen explainers.

Recommended next CMMC pages: /guides/cmmc/poam, /guides/cmmc/remediation, /guides/cmmc/sprs, /guides/cmmc/ssp, and /guides/cmmc/updates.
Examples

What this looks like in practice

In actionA manufacturer sees CUI language in a draft RFP

The capture team should not wait until final RFP release to ask where CUI lives. They should identify systems, users, subcontractors, file paths, enclave assumptions, and evidence gaps while the opportunity is still being shaped.

That makes the later bid/no-bid conversation more honest: can the company protect the data, prove the controls, and absorb remediation work on the schedule?

  • Mark CUI touchpoints.
  • Name control owners.
  • Check SPRS status.
  • Build an evidence tracker.

Frequently asked questions

Should CMMC be its own subtree?

Yes. It is too important to live as one article because contractors need separate pages for level, data, evidence, assessment, and remediation decisions.

Should CMMC updates be mixed into the same guide?

No. Keep evergreen concepts stable and use an updates page for program movement, phase timing, and source changes.

What should be built first under CMMC?

Start with SPRS, POA&M, remediation, SSP, and Level 2 because those pages will answer the most urgent contractor questions.