Hello Meta
We’d love to partner with you to build the next generation of mobility in The Bay and PNW.
The Bay. The Sound. Better Together.
Our Launch Plan
From award to first day of service, every line accounted for.
This is the master launch plan TransWest Team Members run for every new program, shown against Meta's commuter and intercampus service as we understand it from the RFP, the Statement of Work, and bidder Q&A. The sequencing and dependency logic are real. The counts and dates are illustrative and get rebuilt once award scope, the yard split, and a first day of service are set.
Meta has not set an award or start date, the scope can land on one region or both, and central dispatch can stay with the operator or return to Meta. Week zero is a relative anchor rather than a date. What is stable here is the sequence: what has to happen, in what order, and what each line waits on. Paddle counts, headcount, and yard assignments get filled in after final scoping.
Every yard runs the same plan on the same clock.
Meta's four Bay Area yards are Meta-leased and stay where they are. The Pacific Northwest yard is ours to source. Each yard gets its own Location Manager, its own readiness check, and its own day one command post.
People are the critical path, not the fleet.
Meta supplies the vehicles, the spares, and the Bay Area yards, so there is nothing to order and no build slot to wait on. The longest line runs from contract execution to the last driver qualified and trained under our program. Whatever the final scope, three consequences hold.
Incumbent drivers first, then three training waves.
Driver headcount follows the final paddle count and extra board, so the cohorts below are shaped to roughly 200 drivers across five yards and get resized once award scope settles. What does not move is the order: the people who already know Meta's riders, routes, and stops hear from us first, and open-market hiring fills only the seats that remain. Every driver, transitioning or new, meets the same qualification standard and completes our training before a first paddle.
Our most recent enterprise launch, by the numbers.
The plan is not theoretical. Here is how it played out on a 260 Team Member enterprise commuter program in the Puget Sound region: 115 days from notification of award to first day of service.
How to read this plan. Timing is shown in weeks relative to first day of service. Hover over any line to see its window and what it depends on; lines highlighted in green are its upstream dependencies. The sequencing here is not decorative. It is the same dependency logic our launch team manages task by task, so nothing is discovered late and day one feels effortless for Meta's riders. Requirements shown reflect Meta's RFP, Statement of Work, and compiled bidder Q&A. Confirmed award scope, the yard split, and a required first day of service are what turn this into a plan we can commit to.
Enjoy the Ride