Riftur

Additional Use Cases

Public use case

DoD Life Support Services RFQ Compliance Gap Analysis

Solicitation

CAV Life Support AT OCTC Boise

Industry

NAICS 56 – Administrative and Support and Waste Management and Remediation Services

Executive Summary

This gap analysis maps explicit requirements and instructions contained in solicitation_text.docx (the baseline RFQ/contract terms and incorporated provisions/clauses) to statements made in input_proposal.docx (the vendor’s quotation narrative). Requirements were extracted across the solicitation’s (1) schedule/CLIN and performance parameters, (2) inspection/acceptance and delivery schedule, (3) evaluation and submission instructions (including quotation validity), (4) invoicing/WAWF routing and payment method, and (5) required representations/certifications referenced in the addenda and DFARS provisions included in full text. Each requirement is assessed for evidence of coverage in the quotation narrative and marked as Covered, Partially Covered, or Gap based on whether the quotation provides specific, auditable commitments aligned to the solicitation’s wording. Special attention is given to items that are common causes of nonresponsiveness in RFQs (mandatory certifications/representations, SAM status, SF 1449 completion, and WAWF compliance). The solicitation references a PWS attachment that is not provided in the input; therefore, PWS task-level compliance can only be assessed at a high level (the quotation’s claim of compliance), and all PWS-specific service details are flagged as “Not Verifiable from provided text.” Risks are scored qualitatively based on potential for quotation rejection, payment delays, or post-award performance disputes due to insufficient specificity or missing certifications.

Score Breakdown

Review output

Net Score

59%

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.

Requirements

59%

8.2% recoverable

No dedicated published table was available, so the overall findings estimate is used.

Compliance

58%

6.3% recoverable

Estimated from 8 status signals across 1 published compliance table.

Evidence

59%

6.2% recoverable

No dedicated published table was available, so the overall findings estimate is used.

Requirement Coverage

5

reqs

Covered: 60% (3)

Partially Covered: 40% (2)

Missing: 0% (0)

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

2

0

Medium

1

1

0

Low

0

0

0

What Would Improve My Score

REC-1

+5.5% possible

Details

Owner

Proposal team

Requirement

Addendum to 52.212-1 §4; FAR 52.203-2; FAR 52.209-2; DFARS 252.204-7016/7017

Solicitation Source

Addendum to 52.212-1 §4; FAR 52.203-2; FAR 52.209-2; DFARS 252.204-7016/7017

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No timelines)

Finding

Reduces nonresponsiveness risk and strengthens compliance evaluation.

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-1

REC-2

+4.4% possible

Details

Owner

Proposal team

Requirement

Inspection/Acceptance instructions; Addendum to Evaluation §1(c)-(d); PWS attachment reference

Solicitation Source

Inspection/Acceptance instructions; Addendum to Evaluation §1(c)-(d); PWS attachment reference

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No timelines)

Finding

Improves technical scoring by making “reasonable assurance” auditable.

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-2

REC-3

+3.3% possible

Details

Owner

Proposal team

Requirement

Technical factor (reasonable assurance) and performance risk management

Solicitation Source

Technical factor (reasonable assurance) and performance risk management

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No timelines)

Finding

Strengthens feasibility and reduces evaluator uncertainty.

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-3

REC-4

+2.2% possible

Details

Owner

Proposal team

Requirement

DFARS 252.232-7006(c)-(f)

Solicitation Source

DFARS 252.232-7006(c)-(f)

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No timelines)

Finding

Reduces invoicing/payment friction and speeds acceptance/payment.

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-4

REC-5

+1.5% possible

Details

Owner

Proposal team

Requirement

SF 1449 note; Addendum to Evaluation §4; Addendum to 52.212-1

Solicitation Source

SF 1449 note; Addendum to Evaluation §4; Addendum to 52.212-1

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No timelines)

Finding

Improves evaluator speed and minimizes administrative omissions.

Completion Standard

Update the proposal so this recommendation is directly evidenced: REC-5

Requirements

59%

Details

No dedicated published table was available, so the overall findings estimate is used.

Compliance

58%

Details

Estimated from 8 status signals across 1 published compliance table.

Evaluation Readiness

62%

Details

Estimated from 17 status signals across 1 published evaluation readiness table.

Strategy

59%

Details

No dedicated published table was available, so the overall findings estimate is used.

Evidence

59%

Details

No dedicated published table was available, so the overall findings estimate is used.

Management

59%

Details

No dedicated published table was available, so the overall findings estimate is used.

Past Performance

59%

Details

No dedicated published table was available, so the overall findings estimate is used.

Risk

60%

Details

Estimated from 27 status signals across 3 published risk tables.

Production

54%

Details

Estimated from 9 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

  • Scores reflect the published solicitation and proposal content available to this review.
  • Categories without a dedicated source table use the average of the available status signals.

Intake

Source basis, solicitation structure, and review setup.

1 tables

Document Meta-Data & Context Extract

8 rows
Fieldsolicitation_text.docxinput_proposal.docxNotes / Gap Implication

Solicitation/Contract Form

SF 1449 (REV. 11/2021); RFQ indicated

References SF 1449 and blocks to complete

Aligned; ensure executed SF 1449 actually included in submission package (not verifiable from narrative).

Solicitation Number

W9124X26QA008

Cites W9124X26QA008

Covered.

CLIN / Line Item

0001: 221 CAV FY26 AT LIFE SUPPORT; 1 Job; FFP

Offers CLIN 0001 as FFP 1 Job

Covered.

PSC / NAICS

PSC W085; NAICS 562991

States PSC W085 and NAICS 562991

Covered.

Place of Performance / Inspect-Accept

OCTC, 33400 S Orchard Access Road, Boise, ID 83716; Inspect/Accept = Both; DoDAAC W65KUH

States same address; references “both” inspection/acceptance and DoDAAC W65KUH

Covered.

Period of Performance

27 May 2026 to 09 Jun 2026; 14 calendar days; daily

States same dates; 14-calendar-day daily performance

Covered.

PWS Attachment

Attachment: “PWS 221 CAV AT FY26 Life Support”, dated 31 Mar 2026

References attached PWS dated 31 Mar 2026

High dependency; service/task details not verifiable without PWS content.

Evaluation Factors

Timeliness, Price, Technical, Compliance; Past performance not required but may be checked; award to lowest priced meeting requirements; quote valid ≥ 15 days

Acknowledges technical/compliance emphasis; states validity ≥ 15 days; states award to lowest-priced meeting requirements

Covered for acknowledgment; does not provide evidence of timeliness (submission by due date) within narrative.

Compliance

Required documents, instructions, forms, certifications, and package checks.

1 tables

Invoicing, WAWF, and Payment Instruction Compliance Mapping (DFARS 252.232-7006 / -7003 / FAR 52.232-33)

5 rows
Requirement IDRequirement (solicitation_text.docx)Evidence in input_proposal.docxCoverage StatusGap/Risk Notes

INV-1

Electronic invoicing via WAWF; contractor must be registered to use WAWF and have SAM E-Biz POC (252.232-7006(c))

States will submit invoices through WAWF; states SAM active; does not explicitly state WAWF registration status

Partially Covered

Add explicit statement that OSS is registered in WAWF and identifies WAWF administrator/E-Biz POC alignment.

INV-2

Use document type for fixed price services without shipment: Invoice 2-in-1 (252.232-7006(f)(1)(ii)(B))

States will use “Invoice 2-in-1”

Covered

No gap.

INV-3

Use Routing Data Table entries: Pay Official HQ0670; Issue By W9124X; Admin W9124X; Service Approver/Acceptor W65KUH (252.232-7006(f)(3))

Lists routing information and DoDAACs as stated

Covered

No gap.

INV-4

WAWF POCs for invoicing issues: helpdesk then Gina Putt, SFC Robert Glass, Mr. Andrew Simbeck (252.232-7006(g))

States will coordinate with WAWF acceptor identified if issues arise; does not cite names

Partially Covered

Not required, but including the named POCs improves realism and reduces onboarding friction.

INV-5

Payment by EFT via SAM (FAR 52.232-33)

States accepts EFT via SAM as required by FAR 52.232-33

Covered

No gap.

Evaluation Readiness

Evaluator-facing readiness, criteria traceability, and issue severity.

1 tables

Requirement-to-Quotation Coverage Matrix (Submission, Admin, and Evaluation Requirements)

10 rows
Requirement IDRequirement (solicitation_text.docx)Evidence in input_proposal.docxCoverage StatusGap/Risk Notes

SUB-1

Offeror must follow all instructions; meet all solicitation requirements incl. terms/conditions, reps/certs, and technical requirements (Addendum to 52.212-1 §1)

States will provide in strict accordance with PWS and all terms/conditions incl. FAR/DFARS requirements; includes multiple compliance statements

Partially Covered

General commitment is present, but solicitation requires inclusion of specific certifications (e.g., 52.209-2, 252.204-7016/7017) as part of the offer; narrative does not include completed check-box representations.

SUB-2

SAM registration must be active at time of submission; must remain active prior to award, during performance, through final payment (Addendum to 52.212-1 §§2-3; 52.204-7; 52.204-13 maintenance)

States registered/active in SAM and will maintain active registration through final payment; cites FAR 52.204-13

Covered

Verify UEI/CAGE and SAM record snapshot included if required by local practice (not stated in RFQ text provided).

SUB-3

Include certifications in: 52.209-2; 52.219-28 (unless in SAM for NAICS 562991); 252.204-7016; 252.204-7017 (unless 7016 indicates “does not provide”) (Addendum to 52.212-1 §4)

States includes required certifications associated with FAR 52.209-2 and DFARS 252.204-7016/7017; states SAM reps current; represents will not provide covered telecom; implies 7017 not needed if 7016 = does not provide

Partially Covered

Narrative asserts inclusion, but does not reproduce the completed representations (check marks/answers). If the actual completed provisions are missing from the submission, quotation may be deemed nonresponsive.

SUB-4

Complete SF 1449 Blocks 12, 17, 23, 24, and 30 (SF 1449 note)

States SF 1449 completed incl. Blocks 12, 17, 23, 24, 30; executed by authorized signatory

Partially Covered

Narrative claims compliance; cannot verify blocks are actually completed and accurate (e.g., pricing fields, remittance, signature/date).

EVAL-1

Quotation must be valid for at least 15 days after solicitation close date (Addendum to Evaluation §4)

States quotation will remain valid for at least 15 days

Covered

Consider stating an explicit expiration date/time to eliminate ambiguity.

EVAL-2

Award without discussions; Government may hold discussions (Addendum to Evaluation §2)

States understands Government may award without discussions; provided complete quotation

Covered

No gap.

EVAL-3

Technical: Government must have reasonable assurance proposed facility is capable of meeting PWS (Addendum to Evaluation §1(c))

Provides approach, daily battle rhythm, QC, onsite supervisor, logs, corrective action, surge capacity

Partially Covered

Uses strong narrative but does not describe “facility” capabilities (e.g., yards, staging location, disposal points) or provide evidence (equipment lists, staffing numbers, prior similar work) that typically supports “reasonable assurance.”

EVAL-4

Compliance with solicitation and PWS requirements; noncompliance may result in nonresponsive (Addendum to Evaluation §1(d))

Multiple statements of compliance; references clauses and WAWF instructions

Partially Covered

Compliance is asserted; missing itemized crosswalk to PWS and clause-by-clause acknowledgement could reduce confidence.

EVAL-5

Past performance not required; Government may check (Addendum to Evaluation §1(e))

States past performance not required; will provide references upon request

Covered

No gap.

SUB-5

Timeliness: quote received by closing date/time or may not be considered (Addendum to Evaluation §1(a))

No explicit statement of submission timing

Gap

Normally handled operationally, but adding a statement that submission is timely (or including a transmittal email timestamp) reduces administrative risk.

Risk

Risk register findings, assumptions, exceptions, and deviations.

3 tables

Clause/Provision Acknowledgement & Representation Coverage (High Risk of Nonresponsiveness if Missing Attachments)

13 rows
Clause/ProvisionIncluded in solicitation_text.docxQuotation Evidence in input_proposal.docxCoverage StatusRisk if Not Actually Included/Executed

FAR 52.212-1 (Instructions) + Addendum

Yes (by reference) with addenda narrative requiring specific certs

Acknowledges; states compliance and that required certs included

Partially Covered

Medium: if required cert forms are absent, CO may find quote nonresponsive.

FAR 52.212-2 (Evaluation) + Addendum

Yes (full text) + addendum

Addresses technical/compliance/price basis; validity 15 days; award without discussions

Covered

Low.

FAR 52.204-7 / 52.204-13 (SAM registration/maintenance)

Yes

States active SAM and will maintain through final payment; cites 52.204-13

Covered

Low.

FAR 52.222-41 (SCLS) and wage determination compliance

Yes

Commits to compliance with 52.222-41 and DOL WD; recordkeeping/postings

Covered

Low.

FAR 52.222-42 (Statement of Equivalent Rates) informational

Yes (full text informational statement)

Acknowledges as informational; will ensure pay practices compliant with WD

Covered

Low.

FAR 52.222-62 (Paid Sick Leave EO 13706)

Yes

Commits to comply

Covered

Low.

DFARS 252.232-7006 (WAWF instructions)

Yes (full text)

Commits to comply; Invoice 2-in-1; routing data included

Covered

Low.

DFARS 252.204-7016 (Covered telecom representation)

Yes (full text)

Represents will not provide covered defense telecom equipment/services

Partially Covered

High: must ensure the actual provision response is completed as required (checkbox/affirmation).

DFARS 252.204-7017 (Additional representation, conditional)

Yes (full text)

States 7016/7017 included and represents will not provide covered telecom

Partially Covered

Medium: If 7016 is “does not provide,” 7017 may not be required; ensure consistency with SAM annual reps.

DFARS 252.239-7009 (Cloud computing representation)

Yes (full text) with [X] does not anticipate cloud computing

States does not anticipate use of cloud computing services

Partially Covered

Medium: Solicitation already marks [X]; but if offeror must also represent, include explicit completed provision response in submission package.

FAR 52.203-2 (Certificate of Independent Price Determination)

Yes (full text)

Not mentioned

Gap

High: if required to be signed/completed and missing, could render quote noncompliant.

FAR 52.209-2 (Inverted Domestic Corporations-Representation)

Yes (full text)

States includes required certifications; does not provide the actual representation responses

Gap

High: add executed representation (is/is not; subsidiary yes/no) if not satisfied via SAM incorporation method specified by CO.

FAR 52.204-19 (Incorporation by Reference of Reps & Certs)

Yes (addendum to contract clauses)

Not explicitly addressed

Gap

Medium: If relying on SAM reps by incorporation, explicitly state compliance with 52.204-19 and confirm SAM reps are current.

Key Gaps, Overlaps, and Ambiguities (Actionable Items)

7 rows
CategoryFinding TypeDescription (Difference/Gaps/Overlap)ImpactRecommended Enhancement to input_proposal.docx

Representations & Certifications

Gap

Solicitation includes full-text provisions requiring explicit representations (e.g., FAR 52.209-2; DFARS 252.204-7016/7017; FAR 52.203-2). Proposal narrative claims inclusion but does not show completed/checked representations.

High (risk of nonresponsiveness/rejection)

Attach completed, signed representations/cert pages (or clearly state that reps/certs are satisfied via SAM/52.204-19 where applicable), and ensure consistency across SAM and attached forms.

PWS Technical Compliance

Gap / Not verifiable

PWS is referenced as attachment; quotation provides approach/QC but not a requirement-by-requirement PWS crosswalk (tasks, frequencies, metrics).

High (technical acceptability risk)

Add a PWS compliance matrix citing each PWS paragraph: task description, frequency, standard, OSS method, and evidence (equipment/staff) supporting compliance.

Technical “Reasonable Assurance” Evidence

Partial

Solicitation emphasizes reasonable assurance facility is capable; proposal lacks concrete resource detail (staffing numbers by labor class, equipment list, sanitation assets, spare parts/consumables quantities, disposal plan).

Medium

Add resource plan: staffing roster (counts, shifts), equipment/vehicle list, consumables plan, waste handling/disposal approach (if applicable), and supervisory coverage schedule.

Timeliness

Gap

Solicitation states late quotes may not be considered; proposal does not explicitly assert timely submission (though typically outside narrative).

Low to Medium

Add a short compliance statement in cover letter: “Submitted on/before due date/time” and reference submission method (email/portal) if known.

WAWF Readiness

Partial

Proposal commits to WAWF but does not confirm WAWF registration or internal billing point-of-contact alignment.

Low to Medium (payment setup delays)

Add explicit statement: registered in WAWF, identify WAWF administrator/contact, and confirm SAM E-Biz POC is current.

Administrative Data Completeness

Gap

Vendor order number is shown as TBD by vendor in schedule; proposal does not address it.

Low

State a vendor order/reference number or confirm it will be provided upon award in WAWF and on invoice.

Clause Acknowledgements

Overlap

Proposal proactively cites many FAR/DFARS clauses (52.212-1/4/5; 52.222-41/42/62; 252.232-7006/7003; 252.204-7016/7017; 252.239-7009).

Positive (alignment)

Retain, but organize into an appendix ‘Compliance’ section with a checklist to improve evaluator readability.

Risk Register (Procurement/Performance/Payment)

4 rows
Risk IDRiskCause (Gap)LikelihoodSeverityMitigation Recommendation

R-1

Quotation deemed nonresponsive

Missing or unverified completion/signature of required representations/certifications (e.g., FAR 52.203-2, FAR 52.209-2, DFARS 252.204-7016/7017) despite narrative assertions

Medium

High

Include executed full-text provision responses and a submission checklist cross-referencing each required provision/attachment.

R-2

Technical acceptability uncertainty

No PWS paragraph-level compliance matrix; limited quantitative resource detail to support “reasonable assurance”

Medium

High

Add PWS crosswalk and resource/equipment plan; include measurable deliverables aligned to PWS metrics.

R-3

Post-award performance dispute over scope/frequency

High-level description of services without explicit listing of tasks and frequencies (dependent on missing PWS detail)

Medium

Medium

Explicitly restate each service category and frequency from PWS in the quotation (where permitted) and confirm included in FFP price.

R-4

Invoice rejection / payment delay

WAWF registration status and internal billing workflow not explicitly confirmed; documentation expectations not specified

Low

Medium

State WAWF registration complete; specify what will be attached to Invoice 2-in-1 (e.g., daily logs/acceptance notes if required by acceptor).

Production

Final package readiness, attachments, and production cleanup.

1 tables

Requirement-to-Quotation Coverage Matrix (Performance, Inspection/Acceptance, and Delivery Schedule)

6 rows
Requirement IDRequirement (solicitation_text.docx)Evidence in input_proposal.docxCoverage StatusGap/Risk Notes

PERF-1

Provide CLIN 0001 life support services in accordance with PWS; services must accord with PWS (Inspection/Acceptance instructions)

States will provide all required life-support services in strict accordance with attached PWS; daily execution per PWS frequency and performance standards

Partially Covered

PWS content not provided; cannot validate that all required service elements, frequencies, and standards are addressed.

PERF-2

Daily performance for 14 calendar days; 1 Job Daily (Delivery schedule)

States daily performance for 14 days; aligns mobilization/demobilization to start 27 May

Covered

No gap.

PERF-3

Service performance site and POC: DoDAAC W65KUH; CPT Elijah Armstrong (Schedule)

Names CPT Elijah Armstrong; commits onsite supervisor interface

Covered

No gap.

PERF-4

Inspection and Acceptance: Both at OCTC address; Government accepts based on PWS (Inspection/Acceptance)

Commits to logs, inspection support, corrective action; references “both” inspection/acceptance

Covered

No gap.

PERF-5

Vendor’s order number: TBD by vendor (Line item detail)

Does not state a vendor order number

Gap

May be optional/administrative, but if SF 1449 requires entry, omission could cause processing friction.

PERF-6

FOB Destination unless otherwise marked (SF 1449)

States price includes transportation; will furnish and deliver

Partially Covered

Does not explicitly state FOB Destination; usually implicit for services, but explicit statement can prevent disputes about incidental delivery costs.

Recovery

Prioritized fixes, clarification candidates, and recovery actions.

1 tables

Recommendations to Enhance Alignment (No timelines)

5 rows
Recommendation IDRecommended Change to input_proposal.docx / Submission PackageMapped Solicitation Driver (solicitation_text.docx)Expected Benefit

REC-1

Add an appendix “Mandatory Reps/Certs Packet” containing completed, signed responses for FAR 52.203-2 and FAR 52.209-2 and completed DFARS 252.204-7016/7017 (or an explicit statement that 7017 is not required due to 7016 “does not provide”).

Addendum to 52.212-1 §4; FAR 52.203-2; FAR 52.209-2; DFARS 252.204-7016/7017

Reduces nonresponsiveness risk and strengthens compliance evaluation.

REC-2

Provide a PWS Compliance Matrix: PWS paragraph/task → frequency/standard → OSS method → evidence/artifact (log, checklist) → responsible role.

Inspection/Acceptance instructions; Addendum to Evaluation §1(c)-(d); PWS attachment reference

Improves technical scoring by making “reasonable assurance” auditable.

REC-3

Add a quantified staffing/equipment plan (counts by labor class and shift; vehicles/equipment; consumables; backup coverage).

Technical factor (reasonable assurance) and performance risk management

Strengthens feasibility and reduces evaluator uncertainty.

REC-4

Add explicit statement: OSS is registered in WAWF; SAM E-Biz POC is current; identify invoicing POC; confirm Invoice 2-in-1 will include any acceptance support docs requested by W65KUH acceptor.

DFARS 252.232-7006(c)-(f)

Reduces invoicing/payment friction and speeds acceptance/payment.

REC-5

Include a one-page “Solicitation Compliance Checklist” confirming completion of SF 1449 blocks, quote validity ≥15 days, SAM active, and all required attachments included in the package.

SF 1449 note; Addendum to Evaluation §4; Addendum to 52.212-1

Improves evaluator speed and minimizes administrative omissions.

Riftur’s Impact

Riftur revealed that this quotation’s primary risk sits in items that determine whether the Government can evaluate and accept the submission at all, not in the overall understanding of the requirement. The analysis showed potential nonresponsiveness drivers where mandatory representations appear required but are not evidenced as completed provision responses, including FAR 52.203-2 and FAR 52.209-2, and where DFARS 252.204-7016/7017 coverage is asserted without auditable checkbox-style answers. It also surfaced incomplete offer-form commitments because completion of key SF 1449 blocks and signatures is claimed rather than verifiable from the provided text, which can undermine eligibility and contract file auditability. Riftur highlighted an evaluability blocker on technical compliance because the PWS is not traceable through a task-level matrix, limiting the Government’s “reasonable assurance” determination even when the narrative is coherent. It further isolated payment and acceptance exposure where WAWF usage is described but WAWF registration status and internal invoicing POC alignment are not confirmed, increasing the chance of invoice rejection or delays. At the same time, Riftur confirmed solid alignment on core schedule facts, CLIN structure, location, and WAWF routing and invoice type, narrowing attention to the few omissions that carry disproportionate compliance and acceptance consequences.

© 2025 Riftur — All Rights Reserved