Riftur

Additional Use Cases

Public use case

DoDEA Student Transportation Proposal Gap Analysis and Risks

Solicitation

Daily Commute Student Transportation Services for the Ansbach Military Community, Germany

Industry

NAICS 48-49 - Transportation and Warehousing

Executive Summary

This gap analysis maps the explicit requirements and instructions in solicitation_text.docx (RFP + PWS + addenda) to the content provided in input_proposal.docx (proposal narrative). Requirements were extracted across (1) proposal submission/format instructions, (2) Volume structure and attachment completion mandates, (3) PWS operational standards (routes, staffing, vehicles, security, communications, training, incident response), (4) deliverables and invoicing, and (5) key FAR/DFARS compliance items that are explicitly called out in the solicitation as proposal responsibilities. Coverage status is assessed as Covered, Partially Covered, Gap, or Not Evidenced (where the proposal asserts compliance generally but does not provide the specific required artifact, data, or process detail). The Draft Document is generally well-aligned to many PWS operational requirements (communications, delays, route timing, inspections, safe havens, incident reporting, training memo concepts). However, several solicitation “proposal compliance” items are either not addressed or cannot be satisfied by narrative alone (mandatory completion of Attachment 2/3/5/6, NDA Attachment 7 gate, Enclosures 1–5, subcontractor letters, and certain admin submission constraints). The highest-risk gaps are those that the solicitation ties to eligibility/acceptability (Attachment 7 NDA submission, mandatory yellow-cell responses in Attachment 2, Enclosure 3 if teaming, and fully completed Attachment 6) as these can render the proposal Unacceptable regardless of narrative strength.

Score Breakdown

Review output

Net Score

62%

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.

Evaluation Readiness

59%

6.2% recoverable

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

Evidence

59%

6.2% recoverable

Estimated from 0 status signals across 1 published evidence table.

Compliance

62%

5.7% recoverable

Estimated from 34 status signals across 4 published compliance tables.

Requirement Coverage

reqs

Covered: 53% (33)

Partially Covered: 26% (16)

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

Medium

Low

What Would Improve My Score

Convert narrative commitments into the required solicitation artifacts (complete Attachments 2/3/5/6 and Enclosures) and ensure no placeholders remain

+5.5% possible

Details

Owner

Proposal team

Requirement

See mapped source criteria

Solicitation Source

See the published source table

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No Timelines)

Finding

Solicitation evaluates attachments; incomplete artifacts can trigger Unacceptable regardless of narrative quality

Completion Standard

Update the proposal so this recommendation is directly evidenced: Convert narrative commitments into the required solicitation artifacts (complete Attachments 2/3/5/6 and Enclosures) and ensure no placeholders remain

Add a compliance crosswalk appendix mapping each key PWS paragraph to your SOP/process/record (e.g., TE1/TE2/TE3, dispatch logs, training memos)

+4.4% possible

Details

Owner

Proposal team

Requirement

See mapped source criteria

Solicitation Source

See the published source table

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No Timelines)

Finding

Reduces evaluator uncertainty; supports ‘thorough approach’ and lowers perceived risk

Completion Standard

Update the proposal so this recommendation is directly evidenced: Add a compliance crosswalk appendix mapping each key PWS paragraph to your SOP/process/record (e.g., TE1/TE2/TE3, dispatch logs, training memos)

Explicitly address missing driving conduct and stop safety rules: forward curbside door-only, no violent braking, Danger Zone clearance, traffic-flow pattern, release by loading-zone supervisor/COR

+3.3% possible

Details

Owner

Proposal team

Requirement

See mapped source criteria

Solicitation Source

See the published source table

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No Timelines)

Finding

These are explicit PWS standards; omission increases risk of CDRs and safety findings

Completion Standard

Update the proposal so this recommendation is directly evidenced: Explicitly address missing driving conduct and stop safety rules: forward curbside door-only, no violent braking, Danger Zone clearance, traffic-flow pattern, release by loading-zone supervisor/COR

Add explicit mobile device policy: no phone use with students onboard except permitted correspondence; hands-free requirement for duration of run; enforcement mechanisms

+2.2% possible

Details

Owner

Proposal team

Requirement

See mapped source criteria

Solicitation Source

See the published source table

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No Timelines)

Finding

Directly maps to PWS prohibitions and DFARS distracted driving encouragement clause intent

Completion Standard

Update the proposal so this recommendation is directly evidenced: Add explicit mobile device policy: no phone use with students onboard except permitted correspondence; hands-free requirement for duration of run; enforcement mechanisms

Strengthen passenger identification procedures with PWS nuances: adult authorization only via DoWEA bus pass; COR provides adult identity 2 hours prior; student pass-for-other-route logic; misbehavior report triggers

+1.5% possible

Details

Owner

Proposal team

Requirement

See mapped source criteria

Solicitation Source

See the published source table

Proposal Evidence

See the published use-case finding and supporting evidence.

Source Tables

Recommendations to Enhance Alignment (No Timelines)

Finding

Closes security and process gaps; improves compliance with PWS 2.3.1.1.1

Completion Standard

Update the proposal so this recommendation is directly evidenced: Strengthen passenger identification procedures with PWS nuances: adult authorization only via DoWEA bus pass; COR provides adult identity 2 hours prior; student pass-for-other-route logic; misbehavior report triggers

Requirements

74%

Details

Estimated from 33 status signals across 6 published requirements tables.

Compliance

62%

Details

Estimated from 34 status signals across 4 published compliance tables.

Evaluation Readiness

59%

Details

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

Strategy

59%

Details

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

Evidence

59%

Details

Estimated from 0 status signals across 1 published evidence table.

Management

60%

Details

Estimated from 25 status signals across 2 published management tables.

Past Performance

59%

Details

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

Risk

39%

Details

Estimated from 37 status signals across 1 published risk table.

Production

74%

Details

Estimated from 8 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 and Roles

5 rows

Item	solicitation_text.docx	input_proposal.docx
Acquisition/Domain	DoWEA Student Transportation Services (STS) IDIQ FFP; PWS + FAR/DFARS governed RFP	Proposal response for HE1254-26-R-E015
Contract Type	FFP IDIQ; base + options + FAR 52.217-8 extension	Acknowledges FFP; references pricing in Attachment 5
Primary Evaluation Approach	Best Value Tradeoff (FAR 15.101-1); Factors 1–4	Organized into Volumes I–IV narrative sections
Security Marking	CUI / Source Selection header & footer required for all documents	Includes CUI statement repeatedly (header/footer intent acknowledged)
Key Gate/Eligibility	Attachment 7 NDA must be submitted by 27 Mar 2026 to receive route list/map; late/non-submission risks Unacceptable due to inability to complete Attachment 2	Mentions route list Attachment 7(a) generally; does not evidence NDA submission

Requirements

Authoritative requirement inventory and taxonomy.

6 tables

Eligibility / Mandatory Artifact Requirements (Awardability-Critical)

6 rows

Mandatory Item (solicitation_text.docx)	Draft Evidence (input_proposal.docx)	Status	Awardability Risk
Attachment 7 NDA submitted by 27 Mar 2026 to receive Attachment 7(a)/(b); failure may make proposal Unacceptable due to inability to complete Attachment 2	No evidence of NDA submission; proposal references Attachment 7(a) route list but not NDA action	Gap	Critical
Attachment 2 (Volume I Technical Proposal) Excel must be completed; 12 mandatory (yellow) staffing questions + 18 mandatory vehicle questions; blanks treated as non-compliant; failure => Unacceptable per subfactor	Narrative discusses staffing/vehicle approach but does not provide completed Attachment 2 responses/quantities	Gap	Critical
If teaming/subcontracting used: Enclosure 3 Letter of Commitment from each partner; failure => deficiency/Unacceptable for Subfactor 1 and/or 2	Proposal mentions subcontractor alignment generally; does not state whether teaming is used nor include letters	Gap	High (if any teaming is planned)
Attachment 6 Reps & Certs including Enclosures 1–5 required; failure => Unacceptable Factor 4	Narrative states will submit Attachment 6; not included/evidenced	Not Evidenced	Critical (must be included in final package)
Volume II Past Performance: max 3 refs; at least one where prime served as prime or sub; PPQs sent to customers; PPQs returned directly by customer to CO/CS	Narrative states intent to submit; no actual references, no customer POC data, no evidence of PPQ distribution	Not Evidenced	High
Volume III Price: Attachment 5 filled yellow cells for each CLIN/SLIN + FAR 52.217-8 table unit prices; option pricing evaluated	Narrative states will complete; no pricing provided	Not Evidenced	Critical

PWS Objective 1 – Short-Term & Long-Term Adjustments, Communications

5 rows

PWS Requirement	Draft Evidence	Coverage Status	Notes/Gaps
Unscheduled schedule changes: vehicles ready within 2 hours of COR notification at school/inspection point	Explicitly stated	Covered	—
Unscheduled cancellation compensation rules (50% if 6–24 hrs notice; full if <6 hrs)	Draft states will follow PWS compensation logic but no specifics	Partial	Add explicit acknowledgement of the 6-hour/24-hour thresholds and billing approach
Long-term adjustments: implement within 2 business days of COR route change request	Explicitly stated	Covered	—
Equip personnel with reliable mobile two-way intelligible voice comms with local supervisor and DoWEA officials	Explicitly stated	Covered	—
Comms equipment self-contained, portable, self-powered, no vehicle connection; contractor responsible for sustainment and carriers	Explicitly stated incl. devices and sustainment	Covered	—

PWS Objective 2 – Daily Commute Transportation Standards

11 rows

Standard (PWS 2.2.1.x)	Draft Evidence (input_proposal.docx)	Coverage Status	Notes/Gaps
Maintain two-way comms with all personnel during transport	Explicitly stated	Covered	—
Delay >=15 minutes: promptly notify COR; corrective action within 60 minutes if feasible at no cost (force majeure exception by KO)	Explicitly stated (15-min threshold; correct within 60 min; no cost)	Partial	Does not mention KO discretion/force majeure carve-out; add acknowledgement
Drivers not arrive later than scheduled or >10 minutes before scheduled stop time	Explicitly stated	Covered	—
Use only forward curbside door except emergency exit	Not mentioned	Gap	Add explicit operating procedure commitment
No hazardous actions (violent braking/acceleration) to control passengers	Not mentioned	Gap	Add explicit prohibition and training/QC checks
No passenger transfer between vehicles during run unless COR authorized/instructed	Explicitly stated	Covered	—
No backing without adult ground guide when students onboard (except emergency) and in loading zone	Explicitly stated	Covered	—
Disabled/delayed due accident: obtain COR permission before releasing to parents; verify ID before release	Explicitly stated	Covered	—
Passenger compartment inspection after last stop; if child remains, notify CM then COR; transport to COR-designated location	Inspection and escalation stated; transport per COR stated generally	Partial	Add explicit commitment to transport to COR-specified location and immediate notification chain
Lost and found tagging and delivery to COR next business day	Explicitly stated	Covered	—
Misbehavior report using Technical Exhibit 2; submission timing; physical altercation/medical issues reported within 30 minutes	Mentions TE2 form and 30-minute reporting; does not restate specific submission deadlines	Partial	Add: morning run by end of business day; afternoon run by 10:00 next business day

PWS Objective 2 – Inbound/Outbound Standards

3 rows

Requirement	Draft Evidence	Coverage Status	Notes/Gaps
Inbound: wait until school staff takes charge (elem); if staff not present within 5 minutes, notify CM who contacts COR	Explicitly stated	Covered	—
Outbound: buses ready to load 15 minutes before dismissal; no early loading without COR approval	Explicitly stated	Covered	—
Outbound: release Pre-K–2 (as identified) only to parent/caregiver; if not present within 5 minutes, notify CM->COR; take to COR-specified location	Explicitly stated; includes 5-minute rule and COR instruction	Covered	—

PWS Objective 5 – Vehicle Inspection, Readiness, Cleanliness (Coverage)

6 rows

PWS Requirement	Draft Evidence	Coverage Status	Notes/Gaps
Inspect/approve vehicles within 7 days after award effective date and each option start; no transport until COR approved; new vehicles available 48–72 hrs prior	Explicitly stated	Covered	—
Vehicle type restriction: no double-decker/articulated/Blue Bird	Explicitly stated	Covered	—
Daily vehicle safety inspection prior to each run; QCP includes checklist; retain records for life of contract	Draft states daily safety inspections prior to each run; retain records	Partial	Does not explicitly tie to Quality Control Plan content; add explicit QCP alignment
Clean interiors/exterior; air out for smoke-free environment	Explicitly stated	Covered	—
Maintain passenger compartment 65–85°F with H/V/AC; consider idling laws	Explicitly stated with idling mitigation	Covered	—
Replacement buses; emergency replacement onsite within 45 minutes; spares should be previously inspected; if not, COR inspects onsite before use	Draft commits to 45-minute response; maintains spares; notes inspection requirement; proposes interim mitigations	Covered	—

Accident/Incident Response & Reporting (PWS 2.3.4–2.3.6)

5 rows

Requirement	Draft Evidence	Coverage Status	Notes/Gaps
Immediate actions: assess passengers; first aid/CPR; call emergency services	Explicitly stated	Covered	—
Notify COR + District FPO + District Safety Officer + installation security reps; updates at least every 30 minutes	Draft states notify COR and required stakeholders; updates every 30 minutes	Partial	Does not explicitly list all recipients (District FPO, District Safety Officer, installation security rep); add explicit distribution list
Written report by COB next duty day with minimum elements 2.3.5.1–2.3.5.12	Draft lists elements comprehensively	Covered	—
Support investigations; provide personnel/records (inspections, maintenance, training, dispatch logs)	Explicitly stated	Covered	—
Emergency response actions include evacuation and accountability; safe haven direction; unauthorized passenger control	Draft covers safe havens, unauthorized adults, and communications; evacuation/accountability discussed generally	Partial	Add explicit evacuation/accountability procedures and drills linkage

Compliance

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

4 tables

Proposal Instruction & Submission Compliance Matrix (Administrative/Format)

9 rows

Requirement (solicitation_text.docx)	Draft Evidence (input_proposal.docx)	Coverage Status	Gap/Risk
Submit proposal via email to Zlata Dale and Sidnie Miranda; subject line specified	Cover letter includes CO/CS names/emails; does not restate submission mechanics/subject line	Partial	Low risk; but ensure final email package complies exactly
Proposal due NLT 12:00 p.m. EDT 08 Apr 2026	Not stated	Gap	Medium risk if internal team misses deadline; include in internal compliance checklist
Emails over 10MB rejected; replacement within 1 working day if file cannot be opened	Acknowledges virus-free + size limitations; does not mention 10MB or replacement rule	Partial	Low/Medium operational risk; include explicit compliance statement
All documents must include CUI/source selection header & footer	Explicitly acknowledged in cover letter; repeated throughout narrative	Covered	Ensure final rendered documents actually contain header/footer
Admin Cover Letter must include: solicitation #, UEI, address, NCAGE, NAICS, contact name/phone/email	All fields included but placeholders remain ([UEI],[NCAGE],[Address],[Name],[Phone],[Email])	Partial	High risk if placeholders remain at submission
Hold prices firm for 120 calendar days	Explicitly acknowledged	Covered	—
Volume structure required: Admin Cover Letter + Volume I (Attachment 2 Excel) + Volume II (Attachment 3) + Volume III (Attachment 5) + Volume IV (Attachment 6)	Narrative provides sections labeled Volume I–IV but does not evidence completion of required attachments	Partial	High acceptability risk: solicitation requires completion of attachments, not narrative substitutes
No internet links/text boxes to circumvent limits; follow page/word limits	Not addressed	Gap	Low/Medium; add compliance statement and ensure formatting compliance in final files
Documents submitted in separate .pdf or MS Office files	Not addressed	Gap	Low; procedural but must be followed

PWS Objective 3 – Safety & Security Procedures (Key Controls Mapping)

11 rows

Requirement Area	PWS Requirement	Draft Evidence	Coverage Status
Passenger identification	Verify authorized boarding using bus passes or COR passenger lists; special handling if pass for another route; misbehavior report if no pass/not listed; adult authorization only via DoWEA bus pass	Draft says verify passes/lists; refuse unauthorized adults; call police if adult refuses to disembark	Partial	Missing: adult authorization ONLY via DoWEA bus pass (no other ID); 2-hour prior notice from COR; special case: student has pass for another route
Student rider visual identification	Implement procedures to visually identify elementary riders to ensure correct bus	Not addressed	Gap	Add method (e.g., colored tags, route-number lanyards per COR, roster visuals) consistent with PWS
Designated stop compliance	Pick up/discharge only at designated stops/times	Implied via route discipline; not stated explicitly for ‘only designated stops’	Partial	Add explicit statement
Pre-K/Sure Start/K/Special Needs release	Release only to school staff/parents/caregiver; if not present notify dispatcher who contacts COR	Draft covers outbound Pre-K–2 at stops; does not explicitly address Special Needs and dispatcher-notification pathway	Partial	Add explicit coverage for Special Needs and dispatcher role
Hazard stowage of school-related items	Hazardous items stowed in seat behind driver/appropriate area	Not mentioned	Gap	Add explicit procedure
Daily vehicle security inspection procedure + records life of contract; use TE1 checklist; QCP contains checklist	Draft commits to daily documented security inspections using TE1; records life of contract	Covered	—
Suspicious item protocol	Do not touch; evacuate; notify CM; determine police/replacement; notify COR	Draft describes no-touch, evacuate, escalate; mentions IED anomalies	Covered	—
Off-post inspection point timing	Be at inspection location at time prescribed on route sheet	Not mentioned	Gap	Add explicit commitment
Posting route signs	Post route numbers only after pre-run security inspection completed; if no attendant, after driver safety+security inspections	Draft states signage only after security inspection; remove/secure when not in use	Covered	—
Visibility testing	Annual Formal Visibility Test (TE3) yearly	Draft commits to annual testing and program integration	Covered	—
Force protection conditions	Implement alternate routes/schedules; allow inspections; park in secure areas; perform inspections as directed	Draft covers alternate routes/schedules, support inspections, secure parking, comply with direction	Covered	—

Training Requirements (Annual/Refresher/Safety/Security)

8 rows

Requirement (PWS 2.3.3)	Draft Evidence	Coverage Status	Notes/Gaps
Attend government annual security/force protection training; pass exam	Explicitly stated	Covered	—
New hires after annual govt security training: contractor provides interim security training until next annual	Not mentioned	Gap	Add interim training for late hires per PWS 2.3.3.1.1.1
Internal refresher security training: 1 hour in January for all personnel	Draft says refresher training in January; does not specify 1 hour	Partial	Add 1-hour duration and topic parity
Annual safety training 3–4 hours; required topics	Explicitly stated with topic list	Covered	—
CM and Alternate attend annual safety & security training (or training manager may substitute for alternate)	Not mentioned	Gap	Add explicit attendance/substitution rule
Provide draft training materials to COR within 5 days after award effective date or option start for approval	Explicitly stated	Covered	—
Training Memorandum contents + provide to COR within 5 business days of completion or before services begin	Explicitly stated	Covered	—
Participate in school bus safety training/evacuation drills twice per year upon request	Explicitly stated	Covered	—

Cybersecurity / Information Protection Requirements (Solicitation Clauses) – Proposal Coverage

3 rows

Requirement Source	Requirement	Draft Evidence (input_proposal.docx)	Coverage Status	Notes/Risk
DFARS 252.204-7012 / -7020 / -7021 (CMMC)	Maintain required CMMC status for systems processing FCI/CUI; provide CMMC UIDs; annual affirmations; flowdowns	Draft mentions safeguarding CDI and any CMMC requirements generally; no UID/status/level identified	Partial	High if solicitation inserts a specific level (blank in provided text) and if proposal must evidence capability
DFARS 252.204-7018/7016/7017	Prohibit covered telecom; represent disclosures if applicable	Not addressed in narrative; likely handled in Attachment 6 reps	Not Evidenced	Medium; ensure Attachment 6 completed
CUI / Protection of Information (PWS + training topics)	Protect route sheets/passenger lists; remove/secure documents; training includes protection of information	Draft covers securing route signs/docs and treating passenger lists as sensitive	Covered	—

Evidence

Proof support, claim strength, and technical credibility.

1 tables

Key Overlaps / Strength Indicators (Where Draft Exceeds or Strongly Aligns)

5 rows

Area	What solicitation_text.docx requires	What input_proposal.docx provides	Assessment
Operational control and comms	15-min delay notice + 60-min correction; two-way comms; dispatch escalation	Adds structured escalation, scripts, data elements, update cadence; real-time dispatch controls	Potential Strength (if reflected in Attachment 2 responses)
Security inspections and safe havens	TE1 inspections; safe haven list; surveillance reporting	Detailed no-touch IED protocol, surveillance detection training, safe haven selection criteria (15 min cover/concealment)	Strength
Incident reporting content	Minimum elements for written incident report	Draft enumerates comprehensive elements and investigation support	Strength
Fleet resilience	45-min emergency replacement; spares inspected	Dedicated spare readiness posture; rotation through PM; interim student holding mitigations	Strength (ensure consistent with PWS ‘spares should be previously inspected’)
Quality approach to PRS/QASP	High compliance; CDR response within 2 days	Mirrors PRS/QASP logic; commits to 2-business-day CDR response; internal QC emphasis	Strength

Management

Management approach, staffing, roles, and execution ownership.

2 tables

PWS Objective 1 – Program Management & Operations (Requirement Coverage)

10 rows

PWS Requirement (solicitation_text.docx)	Draft Evidence (input_proposal.docx)	Coverage Status	Notes/Gaps
Appoint Primary & Alternate Contract Manager; notify COR in writing within 5 business days of award and prior to replacements	Explicit commitment; within five business days; written notification	Covered	—
CM/Alternate located within 50 miles; attend face-to-face meetings	Explicitly stated	Covered	—
Monitor loading/unloading zones minimum 2 days/week	Explicitly stated	Covered	—
CM/Alternate full authority; primary has program/supervision/transportation management experience	States full authority; does not provide résumé/experience specifics	Partial	Add specific qualifications (years, similar contracts, certifications)
24/7 contact; respond within 30 minutes; arrive within 30 minutes upon initial call	Explicitly stated	Covered	—
Collaborate to develop route schedules/stops/safe havens; COR approval; ridership before task order	States route discipline; safe haven list and COR review	Covered	—
Route elapsed time <=60 minutes unless approved by COR & DTS	Explicitly stated incl. formal request	Covered	—
Arrive at schools AM: no earlier than 30 min/no later than 10 min before bell; PM: no earlier than 30 min and 15 min before dismissal	Draft says arrive within specified windows; also says not >10 min early at stops; mentions 15 min loading readiness before dismissal	Partial	Explicitly restate AM/PM school window constraints exactly as PWS to avoid ambiguity
Do not depart stops before route sheet time unless safety/security/COR approval	Explicitly stated	Covered	—
Extended School Year: provide vehicles for 20 days during summer as requested; dates by mid-May	Not mentioned	Gap	Add ESY capability/assumptions and staffing/fleet readiness

Contractor Personnel Standards (PWS 3.3) – Gaps/Partial Items

9 rows

PWS Requirement	Draft Evidence	Coverage Status	Gap/Risk
Drivers speak/read/write Host Nation language	Not explicitly stated (focus is on licensing)	Gap	Medium: include explicit language qualification assurance
Contract Manager/Alternate English B1 minimum	Not explicitly stated	Gap	Medium
Drivers and attendants free of communicable diseases and impairment (alcohol/drugs)	Not mentioned	Gap	Medium (personnel suitability requirement)
Attire standards; neat/clean; drivers wear nametag/ID badge visible	Draft references attire and professional conduct but not nametag/badge specifics	Partial	Low/Medium
Cell phone restrictions when students onboard; no use except receiving correspondence; drivers not use mobile devices without hands-free	Draft does not address	Gap	Medium/High safety compliance risk
Prohibited behaviors list (abuse, sexual conduct, tobacco/eat/drink, gifts, music, slogans, footwear, etc.)	Draft mentions prohibited behaviors and inappropriate conduct generally but not specific enumerations	Partial	Medium: add explicit policy alignment
Background checks/childcare checks, IRC, LNSP; LOSS markings/requirements; self-report disqualifying info; re-verification every 5 years; DD2981 annual extensions	Draft addresses LNSP and background docs and self-report license events; does not address LOSS, DD2981 renewal, 5-year reverification, IRC specifics, disqualifier list, certified translation	Partial	High: these are detailed compliance expectations in PWS
Criminal offense notification/arrest removal rules	Draft says will notify COR of license suspension etc.; mentions strict prohibitions; does not explicitly commit to immediate notification upon arrest/removal	Partial	High
Do not hire anyone with criminal record to perform under contract	Not explicitly stated	Gap	High

Risk

Risk register findings, assumptions, exceptions, and deviations.

1 tables

Gap & Risk Register (Industry-Standard)

14 rows

ID	Gap	Source Requirement (solicitation_text.docx)	Impact	Likelihood	Severity	Overall Risk	Recommendation
R-01	No evidence of Attachment 7 (NDA) submission to obtain route list/map	52.212-1 Addendum; Attachment 7 instructions	Could be deemed ineligible / unable to complete Attachment 2; proposal may be Unacceptable	Medium	Critical	Critical	Submit signed Attachment 7 NDA per instructions; retain proof of timely submission and receipt
R-02	Attachment 2 (Technical Excel) mandatory yellow-cell responses/quantities not provided	Proposal content/format instructions; Factor 1 evaluation notes	Automatic Unacceptable for Subfactor 1 and/or 2 if blanks/non-compliant	High	Critical	Critical	Complete Attachment 2 with all required quantities and narrative within cell word limits; cross-check no blanks
R-03	Attachment 5 Price spreadsheet not provided; FAR 52.217-8 table unit prices not evidenced	Volume III instructions; price evaluation	Proposal incomplete/unawardable	High	Critical	Critical	Complete Attachment 5 for all CLIN/SLINs and extension table; validate formulas; ensure pricing aligns with staffing/fleet plan
R-04	Attachment 6 Reps & Certs + Enclosures 1–5 not evidenced	Factor 4 instructions and evaluation	Unacceptable Factor 4 (deficiency)	High	Critical	Critical	Submit fully completed Attachment 6 and all required enclosures; include any responsibility documentation (teaming agreement, etc.)
R-05	Invoice requirement (NLT 15th of each month) not addressed	PWS 6.2.7	Potential admin noncompliance; payment delays	Medium	Medium	Medium	Add invoicing process, WAWF readiness, and monthly schedule adherence statement
R-06	Missing explicit operational rules: forward curbside door only; no hazardous braking/acceleration	PWS 2.2.1.1 standards	Safety compliance failures; CDRs; incident exposure	Medium	High	High	Add explicit SOP commitments and training/QC enforcement for these driving conduct requirements
R-07	Danger Zone procedures at stops/loading zones not addressed	PWS 3.2.1–3.2.8	Student injury risk; high severity safety violations	Medium	High	High	Add stop approach/loading/unloading SOPs: danger zone clearance checks, mirror checks, traffic flow pattern adherence, release by supervisor/COR
R-08	Cell phone/mobile device restrictions and hands-free requirement not addressed	PWS 3.2.8 and 3.3.9.9	Safety risk; compliance risk	Medium	High	High	Add policy: no cellular use with students onboard except permitted correspondence; hands-free only; enforce via training and discipline
R-09	Contractor personnel standards gaps (language requirements, impairment/disease-free, ID badges)	PWS 3.3.2–3.3.8	Personnel found noncompliant; removal; performance disruption	Medium	High	High	Add explicit hiring/qualification controls and verification records for language, medical fitness, and ID badge/nametag compliance
R-10	Background check/childcare check details not fully addressed (LOSS marking, translation, 5-year reverification, DD2981 renewals, disqualifier criteria)	PWS 3.3.9.10–3.3.12+	Personnel ineligible; access delays; high mission impact	Medium	Critical	High	Expand compliance narrative and internal process controls for LNSP/IRC/childcare checks, LOSS supervision/marking, translations, reverification cycles, and self-reporting
R-11	ESY (20 summer days) not mentioned	PWS 2.1.2.2.2	Potential inability to meet additional requirement; staffing/fleet not planned	Low/Medium	Medium	Medium	Add explicit ESY readiness statement and resourcing approach
R-12	Passenger identification nuances (adult must have DoWEA bus pass; 2-hour prior identity notice; student pass on other route) missing	PWS 2.3.1.1.1	Security compliance risk; boarding control failures	Medium	High	High	Add explicit rules exactly as PWS and integrate into driver/attendant checklists
R-13	Past performance actual references and PPQ workflow not evidenced	Volume II instructions	Weakened evaluation; potential Neutral; less competitive	High	Medium	High	Prepare Attachment 3 with up to 3 references; ensure at least 1 prime-performed; send PPQs to customers and track direct return to CO/CS
R-14	CMMC/DFARS cybersecurity evidence not provided (UIDs/status)	DFARS 252.204-7021 and related	Responsibility/compliance risk if applicable systems process CUI/FCI	Medium	High	High	Identify in proposal package which systems handle FCI/CUI, required CMMC level, and provide CMMC UID(s)/affirmations as required; flowdown plan

Production

Final package readiness, attachments, and production cleanup.

1 tables

Deliverables & Contract Admin (PWS Section 6) – Coverage

9 rows

Deliverable / Admin Item	PWS Requirement	Draft Evidence	Coverage Status
Personnel List	At award or within 30 days before services begin (option); fields & alpha order; update as changes occur	Draft commits to provide and update; does not list required fields/order	Partial
Vehicle List	At award or within 30 days before services begin; update on changes	Draft commits to provide and update	Covered
Bus Stop Time Report	Within 5 business days upon COR request; record arrive/depart times	Draft commits within 5 business days; describes capability	Covered
Student Ridership Count Report	Up to 3 times/year; 3–5 consecutive days; COR forms	Draft commits to perform upon request; includes 3–5 days up to 3x/year	Covered
Accident/Incident Reports	Per timelines	Covered in incident section	Covered
Student Misbehavior Reports	Submission timing requirements	Mentions use of TE2 and submission; timing not fully specified	Partial
Invoices	Due NLT 15th of each month following services	Not mentioned	Gap
Training Memorandums	Within 5 business days of training completion or before services begin	Covered	Covered
Miscellaneous reports/data available for COR inspection (insurance, maintenance, inspections, licenses, certs, background checks, IRC, QCP, safe haven list)	Draft mentions many items (maintenance, inspections, training, background docs, safe havens) but not insurance/QCP explicitly	Partial

Recovery

Prioritized fixes, clarification candidates, and recovery actions.

1 tables

Recommendations to Enhance Alignment (No Timelines)

13 rows

Recommendation	Applies To	Rationale / Expected Benefit
Convert narrative commitments into the required solicitation artifacts (complete Attachments 2/3/5/6 and Enclosures) and ensure no placeholders remain	input_proposal.docx	Solicitation evaluates attachments; incomplete artifacts can trigger Unacceptable regardless of narrative quality
Add a compliance crosswalk appendix mapping each key PWS paragraph to your SOP/process/record (e.g., TE1/TE2/TE3, dispatch logs, training memos)	input_proposal.docx	Reduces evaluator uncertainty; supports ‘thorough approach’ and lowers perceived risk
Explicitly address missing driving conduct and stop safety rules: forward curbside door-only, no violent braking, Danger Zone clearance, traffic-flow pattern, release by loading-zone supervisor/COR	input_proposal.docx	These are explicit PWS standards; omission increases risk of CDRs and safety findings
Add explicit mobile device policy: no phone use with students onboard except permitted correspondence; hands-free requirement for duration of run; enforcement mechanisms	input_proposal.docx	Directly maps to PWS prohibitions and DFARS distracted driving encouragement clause intent
Strengthen passenger identification procedures with PWS nuances: adult authorization only via DoWEA bus pass; COR provides adult identity 2 hours prior; student pass-for-other-route logic; misbehavior report triggers	input_proposal.docx	Closes security and process gaps; improves compliance with PWS 2.3.1.1.1
Expand personnel compliance controls: language proficiency requirements for drivers/CM; fitness/impairment-free policy; attire and visible ID/nametag; documentation retention	input_proposal.docx	Improves alignment with PWS 3.3 and reduces personnel rejection/removal risk
Enhance background check/LNSP/childcare check governance: translation requirements, IRC, disqualifier criteria awareness, self-reporting arrests, LOSS supervision/marking and supervisor qualifications, 5-year reverification, DD2981 renewals	input_proposal.docx	Addresses high-severity eligibility and child-safety controls; reduces access and suitability disruptions
Add explicit ESY (20-day summer) capability and how it will be resourced without degrading school-year service	input_proposal.docx	Closes a specific scope requirement; improves completeness
For incident reporting, explicitly list all required notification recipients (COR, District Force Protection Officer, District Safety Officer, installation security rep) and embed into your call tree	input_proposal.docx	Aligns with PWS distribution requirements; reduces under-reporting risk
For deliverables, add exact formatting/field commitments for the Personnel List (alpha order + required fields) and Misbehavior Report suspense times	input_proposal.docx	Converts partial coverage into full compliance; improves QASP/PRS performance
Include WAWF readiness and invoicing controls (monthly NLT 15th; Invoice 2-in-1 if used; routing data awareness) in admin section	input_proposal.docx	Aligns with DFARS WAWF clause and PWS invoice suspense; reduces payment friction
If any subcontracting/teaming is contemplated, explicitly declare it and include Enclosure 3 Letters of Commitment + roles/% work/resources + written consent for past performance discussions	input_proposal.docx	Prevents automatic deficiencies and supports responsibility determination
Provide cybersecurity compliance evidence proportionate to use of systems: identify whether any contractor systems will process/store/transmit CUI/FCI; provide required CMMC status/UIDs; describe flowdown approach	input_proposal.docx	Addresses DFARS 252.204-7021 obligations and evaluator responsibility considerations

Riftur’s Impact

Riftur revealed that this draft is strongest where it describes operational control, inspections, communications cadence, and incident reporting content, but weakest where the solicitation demands specific completed artifacts to be eligible and scorable. It highlighted evaluability blockers tied to missing pricing elements in the required price schedule, not-evidenced completion of the technical spreadsheet with mandatory yellow-cell responses, and the absence of a fully completed reps and certs package with required enclosures. It also surfaced an eligibility gate risk around the NDA submission needed to access route data, which directly affects the ability to populate staffing and vehicle quantities in the required format. Where teaming may be involved, Riftur identified incomplete offer-form commitments such as absent letters of commitment, which can trigger deficiencies independent of technical merit. On PWS compliance, it pinpointed rule-level omissions that increase safety and security exposure, including stop danger zone procedures, mobile device restrictions, door-only boarding language, and prohibitions on hazardous driving conduct. These issues are higher leverage than general narrative enhancements because they determine whether the proposal can be accepted, audited, and evaluated under the stated factors, and whether the offeror is treated as compliant and responsible at time of award. By separating aligned controls from missing mandatory submissions and explicit “shall” standards, the output clarifies exactly where acceptance risk is concentrated versus where the approach already supports a lower-risk evaluation.