Every artifact a federal-construction firm needs in its CMMC evidence binder. Organized by the CMMC 2.0 practice domains, sequenced for annual self-attestation at Level 1 and C3PAO assessment readiness at Level 2.
What federal-construction firms actually need in their CMMC evidence binder
The Cybersecurity Maturity Model Certification 2.0 final rule went into effect in late 2024. The DoD phase-in started in 2025. By now, DoD solicitations under DFARS 252.204-7021 are naming required CMMC levels, and federal-construction primes are asking their subs to prove compliance before subcontract award. The question every federal-construction firm is asking their IT lead or compliance officer is: what exactly do we need to have documented?
The CMMC framework answers that question at a practice level. 17 practices for Level 1, 110 practices for Level 2 under NIST SP 800-171 r3. What it doesn’t do is give you a binder organization guide. It tells you what to implement; it doesn’t tell you what to put in the folder you hand to the C3PAO assessor or the prime’s contracting officer when they ask for your evidence package.
That’s the gap this checklist fills. The 18 artifact categories below are what a federal-construction firm actually needs in its CMMC documentation binder. Whether you’re a subcontractor doing an annual Level 1 self-attestation through the SPRS portal, or a prime or large sub going through a Level 2 third-party C3PAO assessment. Some categories are required for both levels; some apply only at Level 2. Each category is marked accordingly.
Here’s the practical reality: the artifacts you need to collect are mostly things your firm should already have. A password policy, an incident response procedure, a list of the systems that touch project data, training records for field personnel. What most construction firms don’t have is those things in one place, organized, current, and formatted in a way that an assessor can review. A CMMC binder is not a cybersecurity program. It’s evidence that your cybersecurity program exists and works.
The False Claims Act exposure added by the 2025 CMMC final rule makes this documentation requirement concrete. A senior official at your firm will sign the SPRS self-attestation affirming that all 17 Level 1 practices are implemented. That signature is a legal certification. The binder is the evidence behind it.
Who this checklist is for
- Federal-construction subcontractors building the evidence package behind their annual Level 1 SPRS self-attestation
- 8(a) federal subs on DoD set-aside contracts preparing for prime CMMC verification requests
- Federal-construction primes building a Level 2 evidence binder for C3PAO assessment
- Compliance officers organizing and maintaining the CMMC documentation between annual attestation cycles
- IT leads at construction firms who need a structured artifact collection list to work from
If you haven’t completed your CMMC Level 1 self-assessment yet, work through the CMMC Level 1 self-assessment checklist (construction) first. This binder checklist assumes the self-assessment is done. It’s the documentation that goes behind it.
The 18 artifact categories the binder must contain
The binder checklist covers 18 artifact categories organized by CMMC 2.0 domain. Collect each, tab it, and verify currency before the attestation:
- SPRS self-assessment confirmation and signed attestation letter (L1 + L2). The printed confirmation from the SPRS portal showing your submitted NIST SP 800-171 self-assessment score and submission date, plus the signed attestation letter from the senior official who submitted it. This is the centerpiece of the Level 1 binder. Without the SPRS confirmation, the binder doesn’t prove the attestation was made. Tab 1.
- System Security Plan (SSP) or equivalent IT policy document (L1 + L2). A written description of the systems in scope for CMMC. Every device, cloud platform, network, and application that touches FCI or CUI. At Level 1, a 2–3 page summary document covering your firm’s IT environment is sufficient. At Level 2, the SSP must map each of the 110 NIST SP 800-171 controls to a system component and describe how it’s implemented.
- Network diagram showing CUI/FCI data flows (L2; recommended at L1). A diagram showing how project data flows through the firm’s systems. From receipt through storage to transmission. At Level 2, this diagram is required as part of the SSP. At Level 1, assessors and primes increasingly ask for it. A one-page Visio or hand-drawn schematic is sufficient.
- Access control policy and user access list (L1 + L2). Written policy governing who has access to systems containing FCI or CUI (Level 1 practices AC.L1-3.1.1 and AC.L1-3.1.2). The access list shows which users have access to which systems, with job-role justification. At Level 2, the policy must also cover privileged access, remote access, and access revocation on personnel departure. Review and update the access list at minimum quarterly.
- Password policy and configuration screenshots (L1 + L2). The written password policy governing minimum length, complexity, and rotation for all systems containing FCI or CUI (Level 1 practices IA.L1-3.5.1 + IA.L1-3.5.2). Screenshots from each system’s password configuration settings proving enforcement. Common systems requiring screenshot evidence: Active Directory or Azure AD, Procore admin settings, Microsoft 365 admin center, corporate email.
- Multi-factor authentication configuration evidence (L1 + L2). Screenshots from each system’s MFA configuration showing MFA is enforced for all users with access to FCI or CUI. At Level 1, SMS-based MFA is acceptable. At Level 2, NIST SP 800-171 r3 practice 3.5.3 requires MFA for remote access and privileged access; phishing-resistant MFA (FIDO2 / hardware tokens) is strongly recommended for C3PAO assessment. System-by-system screenshots, date-stamped.
- Patching and vulnerability management records (L1 + L2). A log of OS and software patches applied to in-scope devices for the past 12 months (Level 1 practice SI.L1-3.14.1). For each device: device name, OS version, patch date, and the patch batch applied. A monthly patching cadence with a log entry per device per month is the construction-firm standard. At Level 2, the log must also include vulnerability scan results and remediation timelines.
- Endpoint protection enrollment records (L1 + L2). Evidence that antivirus and endpoint protection is installed and active on all in-scope devices (Level 1 practices SI.L1-3.14.2 + SI.L1-3.14.4). Enrollment reports from the endpoint protection platform showing device name, enrollment date, last scan date, and current protection status. Export from the admin console quarterly.
- Media sanitization policy and disposal log (L1 + L2). Written policy governing how devices are sanitized or destroyed at end of life (Level 1 practice MP.L1-3.8.3). Disposal log showing each device disposal event: device description, serial number, sanitization method (NIST 800-88 wipe or physical destruction), disposal date, and the name of the person who performed it. Construction firms frequently miss this.
- Physical access controls and visitor log (L1 + L2). Evidence that physical access to areas where FCI is stored or accessed is controlled (Level 1 practices PE.L1-3.10.1 through PE.L1-3.10.5). In a construction context: the jobsite trailer sign-in log showing visitor escort practice, photos of locked file cabinets where printed drawings are stored, and a written policy describing physical access control for the office and IT closets.
- Training records for personnel with FCI/CUI access (L1 + L2). Documentation that personnel with access to FCI or CUI received CMMC awareness training (Level 1 practice AT.L1-3.2.1 equivalent). Training records must include: employee name, training date, training content (course name or description), and completion confirmation. At Level 2, practice 3.2.1 requires documented training at hire and annually thereafter.
- Incident response plan and incident log (L1 + L2). A written incident response plan describing how the firm detects, contains, and reports cyber incidents. The incident log records any incidents that occurred in the past 12 months. Under DFARS 252.204-7012, any cyber incident affecting DoD-related systems must be reported to the contracting agency within 72 hours. The incident log proves reporting compliance.
- Configuration baseline documentation (L2 only). At Level 2, NIST SP 800-171 r3 practice 3.4.1 requires a baseline configuration for each system type in scope. A configuration baseline is a documented, approved set of settings for a system type (e.g., “standard field iPad configuration” showing OS version, installed apps, MFA status, encryption enabled, screen lock timeout). Construction firms typically have 3–5 system types.
- Risk assessment documentation (L2 only). NIST SP 800-171 r3 practice 3.11.1 requires a periodic risk assessment. An analysis of the threats and vulnerabilities affecting systems that contain CUI. At Level 2, the risk assessment must be documented, reviewed annually, and updated when the firm’s IT environment materially changes.
- Audit log configuration and retention evidence (L2 only). NIST SP 800-171 r3 practice 3.3.1 requires audit logging of access events on systems containing CUI. Configuration evidence showing audit logging is enabled on each in-scope system. Log retention policy, typically 90 days live, 12 months archived, must be documented and the retention configuration must match the policy.
- Supply chain / vendor assessment documentation for cloud platforms (L2 only). NIST SP 800-171 r3 requires supply chain risk management for systems handling CUI. For each cloud platform in scope (Procore, Microsoft 365, Autodesk Construction Cloud, Google Workspace), collect evidence that the platform meets CMMC L2 compliance requirements: the platform’s FedRAMP authorization letter or CMMC L2 certification.
- Plan of Action and Milestones (POA&M) for any open gaps (L1 + L2). A POA&M documents CMMC practices that are not yet fully implemented, with a description of the gap, the planned remediation, the responsible owner, and the target completion date. At Level 1, a POA&M demonstrates responsible governance and is increasingly expected by primes. At Level 2, open POA&M items are reviewed by the C3PAO.
- C3PAO assessment letter or SPRS verification screenshot (as applicable). The culminating artifact: either the C3PAO final assessment letter (Level 2 certified firms) or a screenshot of the SPRS portal showing the self-assessment submission (Level 1 firms). This is the artifact the prime’s contracting officer requests when verifying sub CMMC compliance. Keep this current. Level 1 attestations require annual renewal; Level 2 certifications are valid for 3 years.
How to build and maintain the CMMC binder
Work through the 18 categories in order. For each:
- Mark
- Collected (artifact is in the binder, current, and dated),
- Gap (artifact is missing or outdated), or
- L2 Only (skip if building a Level 1 binder).
- Any Gap item gets an owner and a 30-day deadline. Do not sign the SPRS attestation while a Gap is open. The attestation is a legal certification.
- Review the binder quarterly and update artifacts whose evidence is more than 12 months old (patching logs, training records, access lists, SPRS confirmation).
- At each annual self-attestation cycle, run the full 18-category review, update the senior official’s signed attestation letter, and re-submit to SPRS.
Stop scrambling to assemble CMMC evidence on demand
The 18 artifact categories above take a compliance officer 3–4 days to collect and organize on the first run. They take 2–3 hours per quarter to maintain. The problem most construction firms have is the first run happens 3 days before the prime’s contracting officer requests the evidence package. Contracts Connected’s compliance dashboard keeps every CMMC artifact indexed by category, flags stale evidence before it expires, and generates a submission-ready binder package on demand, so the 3-day scramble becomes a 30-minute export.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about CMMC documentation
What is a CMMC documentation binder?
A CMMC documentation binder is the organized collection of evidence artifacts that proves your cybersecurity practices are implemented. It’s what an assessor reviews during a Level 2 C3PAO assessment and what a prime’s contracting officer requests when verifying your CMMC compliance at Level 1. The binder doesn’t make you compliant. Implementing the practices makes you compliant. The binder proves it.
Does Level 1 actually require a physical binder?
No: “binder” is shorthand for organized documentation, whether physical or digital. Most firms maintain a shared folder or a compliance platform with tabs corresponding to each evidence category. The key requirements are: the artifacts are current, they’re organized so they can be found and reviewed quickly, and they cover every practice at the level you’re attesting to. A 3-ring binder works; a SharePoint folder works; a compliance platform works. What doesn’t work is scattered evidence across five systems that takes a day to reconstruct on request.
How often do the artifacts need to be updated?
Annual minimum for most artifacts (matching the Level 1 attestation cycle). More frequently for time-sensitive evidence: patching logs should be monthly, access lists should be reviewed quarterly and updated on personnel changes, incident logs should be continuous. The key discipline is: don’t let artifacts go stale between attestation cycles. An expired training record or a patching log with a 14-month gap is an immediate gap finding.
What’s the difference between Level 1 and Level 2 documentation requirements?
Level 1 covers 17 practices aligned with FAR 52.204-21 and is documented through a self-assessment in SPRS. The evidence requirement is proportional. A written IT policy, patching logs, training records, and physical access controls. Level 2 covers 110 practices from NIST SP 800-171 r3 and is assessed by an authorized C3PAO assessor. The evidence requirement is substantially more formal. A full SSP, network diagrams, configuration baselines, audit logs, risk assessments, and supply chain documentation. Categories 13–16 in this checklist are Level 2-only for that reason.
Can we share a CMMC binder across multiple projects?
The binder covers your firm’s IT environment, not individual projects. One binder covers all DoD work across your portfolio as long as the scope of in-scope systems is the same. If a new project requires handling CUI on a system not previously in scope (a new cloud platform, a new site trailer server), that system needs to be added to the SSP and the binder before CUI is placed on it. The CMMC program is firm-level, not project-level.
What happens if a C3PAO finds gaps during a Level 2 assessment?
The C3PAO will issue findings against specific NIST SP 800-171 r3 practices. Minor findings with a clear remediation path may be conditionally accepted with a POA&M. Significant findings, missing practices with no plan, or a score below the DoD minimum threshold, result in a conditional or failed assessment. A failed assessment means no Level 2 certification until remediation is complete and a re-assessment is conducted. Building the binder before the assessment (not during it) is the difference between a conditional pass and a failed assessment.