TransLink put its new Compass fare payment system out for bid this year, and the numbers are worth sitting with. The request for proposals, which closed to bidders on March 20, 2026, is asking a single vendor to design, implement, operate, and maintain an account-based fare system for Metro Vancouver: replacing more than 400 SkyTrain and SeaBus gates, thousands of bus readers, and the card itself, which still stores fare data locally the way it did when Compass launched in the early 2010s. The published cost has climbed from an early estimate of roughly $220 million to $507 million, spread across a budget line that runs from 2025 through 2031.
That jump is the kind of number that makes headlines, and it should get scrutiny. But if you’ve spent any time inside a public infrastructure procurement, a rising estimate between initial business case and RFP close isn’t automatically evidence of mismanagement. It’s often evidence that the scope got more honest. Early estimates for a program like this tend to price the visible pieces: gates, readers, a card. What’s harder to price up front is the account-based back end, the integration work with BC Transit’s Umo system so a single credential works across regional operators, the digital wallet and rewards infrastructure riders will expect, and the multi-year operate-and-maintain tail that a design-build-only contract wouldn’t even touch. Whether $507 million holds up depends entirely on how well that scope was locked down before contracts get signed, not on the fact that it’s bigger than the number from a few years ago.
Which is where the comparison to Boston is instructive. The MBTA’s AFC 2.0 program, its own account-based fare overhaul with Cubic, has gone from a $723 million contract to roughly $935 million, a jump driven less by scope creep and more by structure: it was the MBTA’s first major public-private partnership of this kind, the agency shifted mid-program from an all-at-once cutover to a phased rollout after realizing the original sequencing was too risky, and it ended up paying $35 million upfront to Cubic, a departure from the no-down-payment structure it had originally negotiated. Agency staff have said publicly that they looked at New York, Chicago, and Vancouver specifically to understand what went wrong elsewhere before finalizing their own approach. That’s the right instinct. The lesson from Boston isn’t “avoid PPP-style delivery” or “phase everything from day one.” It’s that the contract structure, the payment schedule, and the rollout sequencing all need to be negotiated with the same rigor as the technical requirements, and that agencies without a track record in a given delivery model should expect to pay a premium for that inexperience, whether in dollars or in schedule.
For TransLink, that means the interesting part of this program isn’t the RFP itself. It’s what happens in the eighteen months after a vendor is selected, when the contract has to translate “design, implement, operate, and maintain” into a payment schedule that doesn’t front-load risk onto the agency, a phased cutover plan that keeps 1.3 million daily boardings moving while readers get swapped out corridor by corridor, and a governance structure that can actually coordinate with BC Transit on the Umo integration without either side treating it as an afterthought. Bundling design, build, and long-term operations into one contract is a defensible choice. It gives the agency a single point of accountability instead of a finger-pointing exercise between an integrator and an operations contractor. But it also means the RFP evaluation criteria have to weight a bidder’s operational track record as heavily as its technical proposal. The vendor selected here is the one who answers the phone in 2029 when a gate goes down during rush hour, not just the one who installs it in 2028.
The account-based ticketing shift itself is well understood at this point across the industry. What’s less talked about, and what actually determines whether a program like this lands on budget, is the unglamorous work: how the RFP structures payment milestones against delivery, how much contingency gets built in for financing costs on a seven-year build-out, and whether the agency has the internal capacity to manage a vendor relationship of this size rather than just the contract that created it. That’s the part of transit payment modernization that doesn’t show up in a press release about tap-to-pay, and it’s the part worth watching as TransLink moves from RFP to contract award.
If you’re inside one of these programs right now, on either the agency or vendor side, I’d genuinely like to compare notes on how the payment-and-risk structuring is going. It’s the part of this work that’s hardest to get right and easiest to underestimate.
High Street Consulting 
Leave a comment