Skip to content
← Back to blog

DBE set-aside pulse: Wasco County Transportation System Plan (TSP) Update pre-solicitation (ODOT)

Mar 06, 2026Taylor NguyenCapture Strategy Analyst3 min readset aside pulse
DBETransportation planningTSP updateODOTOregonBuysPre-solicitation
Opportunity snapshot
Pre-Solicitation Notice - Wasco County TSP Update (TGM 4B-24)
Department of Transportation7304310 - Planning | 6442 - TGM-ODOTSet-aside: DBE
Posted
Due
2026-07-31T16:00:00+00:00

Executive takeaway

ODOT has posted a pre-solicitation notice for a forthcoming mini-RFP to TLUP ’21 vendors (Transportation System Planning discipline) to update Wasco County’s Transportation System Plan (last updated in 2009). The eventual work is positioned as a multimodal, 20-year planning assessment that also considers intelligent transportation systems (ITS) and planning consistency requirements—while explicitly noting the reality of declining transportation funding. This posting is not the solicitation; proposals submitted now will be rejected.

What the buyer is trying to do

The anticipated contract action is intended to produce an updated Transportation System Plan for Wasco County that reflects population growth and economic development since 2009 and the resulting demands across user groups and modes. The update is expected to assess priorities for a 20-year planning horizon, with emphasis on freight movement, commuter patterns to/from neighboring communities, and multimodal needs (including cycling), while maintaining alignment with federal and state transportation planning requirements.

What work is implied (bullets)

  • Update Wasco County’s existing Transportation System Plan (current plan last updated in 2009).
  • Assess transportation system priorities for a 20-year planning period.
  • Address multimodal transportation needs (the notice references agricultural users, freight, residential/commercial development, industrial activity, tourists, and cycling).
  • Consider key freight routes and commuter travel patterns to/from neighboring communities.
  • Incorporate intelligent transportation systems (ITS) to enhance traffic safety and efficient movement of freight and system users.
  • Ensure consistency with federal and state transportation planning requirements.
  • Develop priorities in the context of declining federal, state, and local transportation funding.

Who should bid / who should pass (bullets)

  • Should bid: DBE firms that are already eligible to compete as TLUP ’21 vendors under the Transportation System Planning discipline (as the notice states the mini-RFP will be released to that vendor pool).
  • Should bid: Planning teams with demonstrated multimodal transportation planning capability (including freight and cycling considerations) and the ability to address ITS integration in planning.
  • Should pass (or reassess): Firms not on the TLUP ’21 vendor list for the Transportation System Planning discipline (unless there is a pathway to participate via teaming/subconsulting—verify in attachments and eventual RFP).
  • Should pass (for now): Anyone planning to submit a proposal in response to this pre-solicitation notice; the notice says such submissions will be rejected.

Response package checklist (bullets; if unknown say “verify in attachments”)

  • Confirm the mini-RFP will be limited to TLUP ’21 vendors under the Transportation System Planning discipline (verify in attachments).
  • Review the pre-solicitation notice details in the attachments (the posting directs bidders to the Attachments tab).
  • Capture a compliance matrix for: multimodal coverage, 20-year planning horizon, ITS considerations, and federal/state planning consistency (verify specific deliverables and submission requirements in attachments and the future mini-RFP).
  • Internal “no-bid” gate: confirm you are not submitting anything until the mini-RFP is issued.
  • Document questions/assumptions to validate once the mini-RFP is released (scope changes are explicitly possible).

Pricing & strategy notes (how to research pricing; do not invent pricing numbers)

This notice does not provide a solicitation package or pricing structure. Treat this as a lead time window to prepare a defensible cost approach once the mini-RFP drops.

  • Start by reviewing any scope cues in the attachments (e.g., required meetings, engagement expectations, analysis components, and deliverables)—then map those to labor categories and hours.
  • Build a workplan-based estimate aligned to the notice’s themes: multimodal planning, freight/commuter considerations, ITS integration, and compliance with federal/state planning requirements.
  • Benchmark your pricing using recent, comparable transportation system planning updates you’ve delivered (or supported) and adjust for anticipated stakeholder/agency review cycles once known (verify in the eventual mini-RFP).
  • Plan for scenario-based pricing options (e.g., base update plus optional enhancements) only if the mini-RFP allows alternates—verify in attachments/final solicitation.

Subcontracting / teaming ideas (bullets)

  • Team with a partner strong in ITS planning concepts (the notice explicitly calls out ITS to enhance safety and efficient movement).
  • Add a freight-focused planning subconsultant to address key freight routes and movement needs referenced in the synopsis.
  • Include multimodal specialists who can credibly cover cycling and other non-auto modes mentioned in the notice.
  • If you’re not a TLUP ’21 prime, explore subconsulting roles with an eligible TLUP ’21 Transportation System Planning vendor (verify eligibility constraints in the mini-RFP).

Risks & watch-outs (bullets)

  • This is not an RFP/RFI; the agency states proposals/offers submitted in response to this notice will be rejected.
  • Information is subject to change; the project may be delayed, cancelled, or revised at any time.
  • Eligibility appears constrained to TLUP ’21 vendors under the Transportation System Planning discipline—confirm your status before investing heavily (verify in attachments).
  • The plan must address all modes and incorporate ITS, which can expand scope if not tightly defined in the mini-RFP—watch for ambiguous requirements once released.
  • The synopsis flags declining transportation funding; expect prioritization tradeoffs and be ready to justify recommendations under constrained funding assumptions.

Related opportunities

How to act on this

  1. Open the BidPulsar notice and review the Attachments tab referenced in the posting.
  2. Validate TLUP ’21 Transportation System Planning eligibility and DBE positioning before committing capture resources (verify in attachments and the eventual mini-RFP).
  3. Pre-build a compliant outline: multimodal priorities, freight/commuter considerations, ITS integration, and federal/state planning consistency—then refine when the mini-RFP is issued.
  4. Identify teaming gaps now (ITS, freight, multimodal) so you can move quickly when ODOT releases the mini-RFP.

Need help deciding whether to bid—or building the response package fast once the mini-RFP drops? Federal Bid Partners LLC can support capture planning, compliance mapping, and proposal development strategy.

Source notice (BidPulsar): Wasco County TSP Update pre-solicitation

Related posts