Additional Use Cases
Executive Summary
This gap analysis maps solicitation_text.docx requirements (Sections L and M submission instructions; Sections D–I contract requirements; Attachment A SOW summary and security/records obligations) to the content provided in input_proposal.docx. Requirements were extracted as discrete, testable obligations (e.g., “submit X by Y time”, “provide plan within N days”, “comply with clause Z”) and evaluated for evidence in the proposal text. Coverage status is categorized as Covered, Partially Covered, or Gap depending on whether the proposal (a) explicitly commits and/or provides the required artifact, (b) commits but omits key parameters, formats, recipients, deadlines, or flowdowns, or (c) does not address the requirement. Special attention is given to preliminary screening factors (license), proposal formatting/submission instructions (page limit, file size, email destination, Excel requirement), HUBZone set-aside and limitations on subcontracting, construction administration controls (QC, safety, schedule, outages), and DHS/FEMA security, CUI/PII handling, and training requirements. Risks reflect likely evaluation/award impacts (non-responsiveness, proposal rejection, access denial, compliance exposure) and operational impacts during performance (stop work, outages, security incidents). Recommendations focus on adding explicit compliance matrices, required attachments, and clause-specific implementation statements to strengthen alignment without altering solicitation terms.
Score Breakdown
Net Score
67%
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
61%
5.8% recoverable
Estimated from 24 status signals across 3 published compliance tables.
Evaluation Readiness
65%
5.2% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Evidence
65%
5.2% recoverable
No dedicated published table was available, so the overall findings estimate is used.
Requirement Coverage
61
reqs
Covered: 59% (36)
Partially Covered: 20% (12)
Missing: 21% (13)
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
0
0
Medium
0
0
0
Low
0
1
0
What Would Improve My Score
Add a solicitation compliance matrix (Section-by-section L/M/H/F/E mapping) with references to proposal sections/attachments
+5.5% possible
Details
Owner
Proposal team
Requirement
Sections L & M; H/F/E; Attachment A
Solicitation Source
Sections L & M; H/F/E; Attachment A
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable Additions)
Finding
Reduces evaluator effort; lowers risk of 'missing item' determination
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add a solicitation compliance matrix (Section-by-section L/M/H/F/E mapping) with references to proposal sections/attachments
Add explicit proposal submission compliance statement
+4.4% possible
Details
Owner
Proposal team
Requirement
L.12(f)-(g)
Solicitation Source
L.12(f)-(g)
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable Additions)
Finding
Reduces administrative rejection risk
Completion Standard
Update the proposal so this recommendation is directly evidenced: Add explicit proposal submission compliance statement
Explicitly state offer acceptance period (≥60 days)
+3.3% possible
Details
Owner
Proposal team
Requirement
L.10
Solicitation Source
L.10
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable Additions)
Finding
Avoids nonconformance
Completion Standard
Update the proposal so this recommendation is directly evidenced: Explicitly state offer acceptance period (≥60 days)
Include explicit HUBZone eligibility affirmation and limitations on subcontracting execution approach
+2.2% possible
Details
Owner
Proposal team
Requirement
52.219-3; 52.219-14; 52.236-1
Solicitation Source
52.219-3; 52.219-14; 52.236-1
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable Additions)
Finding
Strengthens set-aside eligibility confidence
Completion Standard
Update the proposal so this recommendation is directly evidenced: Include explicit HUBZone eligibility affirmation and limitations on subcontracting execution approach
Address bid bond requirement directly
+1.5% possible
Details
Owner
Proposal team
Requirement
L.12(a)
Solicitation Source
L.12(a)
Proposal Evidence
See the published use-case finding and supporting evidence.
Source Tables
Recommendations to Enhance Alignment (Actionable Additions)
Finding
Prevents non-responsiveness
Completion Standard
Update the proposal so this recommendation is directly evidenced: Address bid bond requirement directly
Requirements
75%
Details
Estimated from 38 status signals across 5 published requirements tables.
Compliance
61%
Details
Estimated from 24 status signals across 3 published compliance tables.
Evaluation Readiness
65%
Details
No dedicated published table was available, so the overall findings estimate is used.
Strategy
65%
Details
No dedicated published table was available, so the overall findings estimate is used.
Evidence
65%
Details
No dedicated published table was available, so the overall findings estimate is used.
Management
65%
Details
No dedicated published table was available, so the overall findings estimate is used.
Past Performance
90%
Details
Estimated from 1 status signal across 1 published past performance table.
Risk
58%
Details
Estimated from 28 status signals across 1 published risk table.
Production
52%
Details
Estimated from 10 status signals across 1 published production table.
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.
Document Meta & Inferred Context
Technical Factor Alignment (Section M.1 Factor 1)
Quality Control (Section E.3) Detailed Requirement Mapping
Safety & Occupational Health (H.4 / FAR 52.236-13)
Schedule / Performance Requirements (Section F)
Compliance
Required documents, instructions, forms, certifications, and package checks.
Preliminary Screening Factor Compliance (Responsiveness Gate)
Section L Submission & Format Requirements (Compliance Mapping)
Price/Commercial & Contract Administration Requirements
Past Performance
Past performance relevance, proof, and outcome support.
Past Performance & References (Section M.1 Factor 2)
Risk
Risk register findings, assumptions, exceptions, and deviations.
Key Gaps & Risks Register (Exhaustive Highlights)
Production
Final package readiness, attachments, and production cleanup.
Security / Access / CUI-PII Handling & Training (Sections H.9, H.18–H.23; HSAR 3052.204-72/-71/-73; Attachment A T.2/T.3)
Recovery
Prioritized fixes, clarification candidates, and recovery actions.
Recommendations to Enhance Alignment (Actionable Additions)
Riftur’s Impact
Riftur’s results show this submission is strongest where it makes explicit, evaluable commitments on execution controls such as the three-phase QC approach, safety plan timing, outage coordination lead time, and a CPM schedule commitment. The same review isolates a smaller set of administrative and clause-driven gaps that carry disproportionate award risk, including a missing bid bond signal, an unstated 60-day (or greater) offer acceptance period, and absent confirmation of the required submission mechanics like the specific email destination, PDF-only delivery, and the 25MB/no-.zip/.exe constraint. It also highlights incomplete offer-form commitments around signed representations and certifications and an eligibility ambiguity where HUBZone status is not explicitly affirmed despite set-aside dependence. On the security side, Riftur surfaces higher-impact compliance blockers such as missing Privacy training commitments for PII/SPII handling, conditional but unaddressed IT security plan/accreditation requirements, and partial HSAR CUI incident-response specifics like subcontractor flowdowns and evidence/retention obligations. These items drive evaluability, eligibility, and access authorization in ways that narrative refinements cannot offset, because they determine whether the Government can accept, verify, and legally rely on the offer. The insights also clarify where risk is concentrated versus where the submission is already aligned, reducing the chance that reviewers spend time polishing low-impact prose while acceptance-critical elements remain uncertain.
© 2025 Riftur — All Rights Reserved