Skip to content

SPRS Scoring

SPRS scoring works out a Supplier Performance Risk System score from the implementation status and evidence you enter. It uses the DoD Assessment Methodology, version 1.2.1, and the 110 requirements of NIST SP 800-171 Rev 2.

During the pilot the compliance tools are switched off for customer accounts. See how pass-through works.

  • The score starts at 110.
  • Each requirement not met subtracts its weight from the methodology: 5, 3 or 1 point. A requirement is subtracted once. A requirement that is not assessed counts as not met, because the methodology scores an incomplete roll-out as not implemented.
  • Two requirements allow partial credit. 3.5.3 costs 3 if multi-factor authentication covers only remote and privileged users, and 5 if there is none. 3.13.11 costs 3 if encryption is used but is not FIPS-validated, and 5 if there is none. No other requirement has partial credit. Partial credit is assessor-only: the platform’s own “partially met” evidence status never earns it. An assessor can record it explicitly.
  • 3.12.4 (the system security plan) has no point value. Without a plan the assessment cannot be completed, so the readiness check does not pass.
  • The lowest possible score is -203.
  • The only threshold in regulation is 88. A score is labeled “Meets 88” or “Below 88”, with the points to 88 shown.
  • A plan of action and milestones (POA&M) does not make a requirement implemented. Two POA&M facts do change the score, both described under the limits below.

On 2026-10-14 all 110 weights were checked against Annex A of the methodology, by hand and by a parse of the PDF, with no differences. A test fails if a weight changes.

There is one scorer. Every score it produces comes with its working, which reads “110 - 5 x a - 3 x b - 1 x c = score”: the start of 110, each deduction with its weight and reason, the total, the -203 floor, the methodology name and version, the NIST revision, and the date the score is valid until (three years).

  • The working shows under the score on the CMMC page, on the last snapshot, and on the roll-up and vendor snapshot tiles.
  • The affirmation draft carries a section, “2a. How the score was reached”, so the official who reviews it sees the working.

Some views count requirements met instead of scoring them. Those carry the label “Count-based estimate, not an SPRS score” and no tier. A count is not a score.

Treat a figure as an SPRS score from this tool only if the working is shown with it.

The score is your submission material. GovConHouse never submits it. You submit your score in SPRS yourself, with your own credentials, and your organization’s senior official affirms it.

The submit route in the platform is switched off. It returns a 503 that says submission is disabled and that nothing was sent. Nothing the platform shows you is a SPRS record. See Shared Responsibility.

  • 3.12.2 and the POA&M. The methodology says that if you have no POA&M for requirements you have not implemented, 3.12.2 is assessed as not implemented. The platform applies this rule. When your company has no POA&M item that is open or in progress and at least one other requirement is unmet, 3.12.2 is also counted as not implemented, 3 points, and the working says “3.12.2 deducted: no POA&M on file”. Proposed, resolved, accepted-risk and false-positive items do not count as a plan on file.
  • Temporary deficiencies. The methodology treats a temporary deficiency with a POA&M as implemented. The platform does this only when your POA&M item for the requirement is open or in progress, is flagged as a temporary deficiency, carries a system security plan reference, and is for a requirement that may sit on a POA&M at all. 3.12.2 and the 5-point requirements that cannot be on a POA&M are never lifted. Each lift is listed in the working, so a missing deduction always has a reason.
  • Not applicable. The methodology lets you leave a requirement out of the deductions in two cases: the capability is not permitted, or the DoD CIO has adjudicated the requirement as not applicable or equally effective. For the first case the platform follows Annex A, which names five requirements: 3.1.12, 3.1.13, 3.1.16, 3.1.17 and 3.1.18 (remote access, wireless access and mobile devices). A requirement whose assessment objectives you recorded as not applicable in the requirement workbook is left out of the deductions only if it is one of those five. Any other requirement marked not applicable is still deducted, because the platform has no field for a DoD CIO adjudication. Use the exemption only where you do not permit the capability.
  • Basic assessment. Assessments recorded in the platform are Basic (self) assessments with low confidence, as the methodology describes for a self-assessment.

The methodology scores the 110 requirements of Rev 2 only. DoD had published no Rev 3 methodology as of 2026-10-14, so there is no Rev 3 SPRS score, and the platform does not make one.

The “Rev 3 readiness” tab is a view, not a score. It is labeled “Not an SPRS score”. It shows:

  • The 97 active NIST SP 800-171 Rev 3 requirements.
  • For each, the Rev 2 requirements that cite at least one of the same NIST SP 800-53 base controls. This is a starting point, not NIST’s crosswalk. 85 of the 97 link. The other 12 have no Rev 2 counterpart and say “no data”.
  • The status of the linked Rev 2 requirements, from your own evidence. A Rev 3 requirement is never shown as met.
  • How many organization-defined parameters each requirement’s text contains. You set those values. GovConHouse holds none.

If the account has no evidence, the view says so instead of showing numbers.

Try this in the platform