Additional Use Cases
Executive Summary
This gap analysis maps solicitation_text.docx requirements (SF1449/RFQ instructions, PWS performance requirements, and administrative/contract clauses) to evidence in input_proposal.docx. Requirements were decomposed into discrete, auditable statements (e.g., subparagraphs in PWS 1.1.x, 1.6.x, 1.7.x and Attachment 02 sections 1–3) and then assessed for coverage in the proposal volumes. Coverage statuses use four labels: Covered (explicitly addressed), Partially Covered (addressed but missing a required detail, condition, metric, or artifact), Gap (not addressed), and Not Applicable/Not Provided in Extract (requirement exists but cannot be validated from provided draft text, often because a referenced attachment/form is required). Risks were assigned qualitatively based on impact to eligibility (e.g., submission compliance), award evaluation (technical/past performance), and post-award performance/compliance (e.g., security, OPSEC, QA/QC). Recommendations focus on adding explicit commitments, artifacts (plans, SOPs, evidence), and traceable cross-references to the PWS and Attachment L/M instructions to increase evaluability and reduce ambiguity. Packaging-only gaps (fonts/page limits/PDF) are excluded from remediation per instructions, but submission-structure requirements that affect compliance are included.
Score Breakdown
Net Score
69%
Top Score Constraints
These are the three stage-level categories costing the most recoverable score percentage. The percentage estimates how much the score could improve if that constraint were fully resolved.
Compliance
64%
5.4% recoverable
Estimated from 29 status signals across 4 published compliance tables.
Evaluation Readiness
66%
5.1% recoverable
Estimated from 0 status signals across 1 published evaluation readiness table.
Evidence
66%
5.1% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Requirement Coverage
57
reqs
Covered: 53% (30)
Partially Covered: 37% (21)
Missing: 11% (6)
Unclear: 0% (0)
Risk Heatmap
Shows how many Risk Register findings fall into each severity and likelihood combination. Likelihood means the estimated chance that the issue will affect evaluation, submission acceptance, or delivery if it is not fixed.
Likelihood
Severity
Low
Medium
High
High
0
4
0
Medium
1
5
0
Low
0
0
0
What Would Improve My Score
Add a dedicated 'PWS Compliance Matrix' (table) cross-walking each PWS 1.1.1–1.1.3 subtask and deliverable to the curriculum agenda and facility features, including explicit track dimensions (2500ft/50ft and 250x250 area) and cone-layout compliance statements.
+5.5% possible
Details
Owner
Proposal team
Requirement
PWS 1.1; PWS 1.1.3.4–1.1.3.6; Evaluation Factors §2.1
Solicitation Source
PWS 1.1; PWS 1.1.3.4–1.1.3.6; Evaluation Factors §2.1
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, non-timeline)
Finding
Add a dedicated 'PWS Compliance Matrix' (table) cross-walking each PWS 1.1.1–1.1.3 subtask and deliverable to the curriculum agenda and facility features, including explicit track dimensions (2500ft/50ft and 250x250 area) and cone-layout compliance statements.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add a dedicated 'PWS Compliance Matrix' (table) cross-walking each PWS 1.1.1–1.1.3 subtask and deliverable to the curriculum agenda and facility features, including explicit track dimensions (2500ft/50ft and 250x250 area) and cone-layout compliance statements.
Replace conditional language ('where dedicated vehicles and track dimensions allow') with firm compliance statements or clearly stated alternatives subject to COR/KO approval.
+4.4% possible
Details
Owner
Proposal team
Requirement
PWS 1.1.3.4–1.1.3.9
Solicitation Source
PWS 1.1.3.4–1.1.3.9
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, non-timeline)
Finding
Replace conditional language ('where dedicated vehicles and track dimensions allow') with firm compliance statements or clearly stated alternatives subject to COR/KO approval.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Replace conditional language ('where dedicated vehicles and track dimensions allow') with firm compliance statements or clearly stated alternatives subject to COR/KO approval.
Add a 'CUI/Cyber/DFARS 7012 Compliance' subsection: confirm whether any CUI/CDI handled; NIST 800-171 compliance; SPRS status; incident reporting process; subcontractor/service-provider flowdowns.
+3.3% possible
Details
Owner
Proposal team
Requirement
PWS 1.7.5; DFARS 252.204-7012; 252.204-7008
Solicitation Source
PWS 1.7.5; DFARS 252.204-7012; 252.204-7008
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, non-timeline)
Finding
Add a 'CUI/Cyber/DFARS 7012 Compliance' subsection: confirm whether any CUI/CDI handled; NIST 800-171 compliance; SPRS status; incident reporting process; subcontractor/service-provider flowdowns.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add a 'CUI/Cyber/DFARS 7012 Compliance' subsection: confirm whether any CUI/CDI handled; NIST 800-171 compliance; SPRS status; incident reporting process; subcontractor/service-provider flowdowns.
Add Security/Access compliance statements: background checks, PIV, badging, contractor identification to public, and facility/equipment securing each work period.
+2.2% possible
Details
Owner
Proposal team
Requirement
PWS 1.7.1; PWS 1.6.8; PWS 1.7.6
Solicitation Source
PWS 1.7.1; PWS 1.6.8; PWS 1.7.6
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, non-timeline)
Finding
Add Security/Access compliance statements: background checks, PIV, badging, contractor identification to public, and facility/equipment securing each work period.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add Security/Access compliance statements: background checks, PIV, badging, contractor identification to public, and facility/equipment securing each work period.
Add iWATCH/Suspicious Activity Reporting training commitment and how completion will be recorded and reported to COR.
+1.5% possible
Details
Owner
Proposal team
Requirement
PWS 1.7.2
Solicitation Source
PWS 1.7.2
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable, non-timeline)
Finding
Add iWATCH/Suspicious Activity Reporting training commitment and how completion will be recorded and reported to COR.
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add iWATCH/Suspicious Activity Reporting training commitment and how completion will be recorded and reported to COR.
Requirements
80%
Details
Estimated from 28 status signals across 1 published requirements table.
Compliance
64%
Details
Estimated from 29 status signals across 4 published compliance tables.
Evaluation Readiness
66%
Details
Estimated from 0 status signals across 1 published evaluation readiness table.
Strategy
66%
Details
No dedicated published table was available, so the overall findings estimate is used.
Evidence
66%
Details
No dedicated published table was available, so the overall findings estimate is used.
Management
59%
Details
Estimated from 11 status signals across 1 published management table.
Past Performance
90%
Details
Estimated from 3 status signals across 1 published past performance table.
Risk
52%
Details
Estimated from 22 status signals across 1 published risk table.
Production
66%
Details
No dedicated published table was available, so the overall findings estimate is used.
Score Equation
Details
The overall score is a weighted average of stage-level proposal categories. Detailed tables are rolled up into Requirements, Compliance, Evaluation Readiness, Strategy, Evidence, Management, Past Performance, Risk, and Production so the summary reflects the full report without duplicating overlapping findings. Each category receives a 0-100 score, that score is weighted by proposal impact, and the weighted results are added and rounded to the final score. The largest weighted influence currently comes from Requirements, Compliance, Evaluation Readiness. Top Score Constraints are the weighted categories with the largest recoverable point loss.
Scoring Caveats
Requirements
Authoritative requirement inventory and taxonomy.
PWS Training Objectives & Curriculum Traceability (PWS 1.1)
Compliance
Required documents, instructions, forms, certifications, and package checks.
Metadata & Submission Compliance Snapshot
Security, CUI, OPSEC, and Physical Security Requirements (PWS 1.7)
Contractor-Furnished Items / Facilities / EMS (PWS 3.1–3.2)
WAWF Invoicing & DoDAAC Routing Compliance (DFARS 252.232-7006)
Evaluation Readiness
Evaluator-facing readiness, criteria traceability, and issue severity.
Evaluation Factor Alignment (Attachment 03)
Management
Management approach, staffing, roles, and execution ownership.
Operational/Management Requirements (PWS 1.3–1.6)
Past Performance
Past performance relevance, proof, and outcome support.
Past Performance Volume Compliance (Attachment 02 §3.2)
Risk
Risk register findings, assumptions, exceptions, and deviations.
Key Gaps & Risks Register (Industry-standard risk table)
Recovery
Prioritized fixes, clarification candidates, and recovery actions.
Recommendations to Enhance Alignment (Actionable, non-timeline)
Riftur’s Impact
Riftur’s findings show that the submission is strongest where it provides direct, concrete alignment to the training progression, facility proximity, and medical support, which supports technical evaluability. It also revealed several high-leverage compliance gaps that are more determinative than narrative refinements, including missing commitments for background checks/PIV handling and FPCON-driven access changes, iWATCH training, and OPSEC program/training requirements. The analysis flagged partial coverage of CUI and DFARS cyber obligations, with no explicit NIST 800-171 posture, SPRS status, SSP/POA&M position, or incident reporting workflow, which affects auditability and can raise eligibility questions. It surfaced conditional language around minimum track dimensions and dedicated areas for required maneuvers, creating an evaluability blocker because the Government cannot confirm the required minima will be met as written. It identified incomplete offer-form evidence, where the pricing volume is asserted to rely on a completed form but the populated SLIN pricing and signature blocks are not verifiable in the draft, which can undermine price evaluation and acceptance. Finally, it highlighted absent or partial administrative commitments such as deadline/method compliance, OCI notification, contractor badging/identification, and post-award meeting attendance, clarifying where responsiveness risk is concentrated even when the technical approach is otherwise aligned.
© 2025 Riftur — All Rights Reserved