Estimated, Not Simulated
The journey times behind ALTO were drawn from a spreadsheet of international averages — not from a model of the actual corridor. What that distinction means, and who set the target.
A government record released under the Access to Information Act shows that, of the journey times prepared for the project, only the slowest case was produced by an actual simulation of the railway. That case was a 110 mph (177 km/h) train — a roughly four-hour Toronto–Montréal trip. Every faster time, including those near the speeds ALTO now markets, came from a spreadsheet that applied average speeds borrowed from intercity railways in other countries.
The technical memorandum describes those faster figures, in its own words, as “for information and comparison purposes.” And the email chain attached to it records the most senior Transport Canada official on the file directing that the times not assume Toronto speeds above 160 mph (257 km/h), because a higher figure was “not the intent of the Government.” The journey time, in other words, was managed as a policy and cost target — not derived as an engineering result.
What the document is
The release (A-2025-00333) was obtained under the Access to Information Act and provided to the Initiative. It consists of an email chain dated August 30 to September 4, 2023 among Transport Canada and Via HFR / Via TGF officials and their technical advisers, together with the attached memorandum “VIA HFR-TGF Journey Times.” It dates from the procurement period, when the project was still a high-frequency rail (HFR) programme under Transport Canada’s lead, before the February 2025 announcement re-scoped it as high-speed rail at 300 km/h.
The memorandum is the engineering note that sits beneath the project’s headline travel times. It is explicit about how those times were calculated — and it used two very different methods for two different parts of the answer.
Two ways to get a journey time
A train’s journey time is the single number a project like this is sold on — “Toronto to Montréal in X hours.” There are two fundamentally different ways to produce that number, and they are not equally reliable.
A simulation builds a digital twin of the real railway and “drives” a train along it. The software knows the actual track: every curve that forces the train to slow, every hill, every station stop, where the signals are, how fast the specific train accelerates and brakes, and whether other trains — including freight — are in the way. It runs the trip second by second on that line and reports how long it genuinely takes. The memorandum names the tool used for this: RailSys, drawing on the JPO’s 2021 Rail Operational Summary Report. It is the railway equivalent of a flight simulator, or of a mapping app with live traffic.
A spreadsheet estimate does something far cruder: it takes the distance, assumes an average speed borrowed from how fast trains run in other countries, and divides one by the other. It never looks at this corridor’s actual geometry, terrain, urban approaches, or shared freight track. The memorandum is candid that its faster figures are of this kind — an “estimated calculation based on the maximum permissible speed,” provided “for information and comparison purposes.”
| Simulation — the RailSys tool | Spreadsheet estimate |
|---|---|
| Drives the actual route. Models every curve, gradient, station stop, signal and conflicting train on the real Toronto–Québec line, second by second. | Distance ÷ an assumed average speed. Takes the route length and an average operating speed benchmarked to comparable intercity rail abroad, and divides. |
| Knows the corridor. A curve too tight for high speed shows up as a slower section; a freight train ahead shows up as lost minutes. Constraints surface before construction, not after. | Blind to the corridor. Cannot see this line’s curves, hills, city approaches or freight sharing. The memorandum labels its outputs indicative only. |
| What ALTO simulated. Only the 110 mph (177 km/h) base case — roughly a four-hour Toronto–Montréal trip. | What ALTO estimated. Every faster time, including the 160 and 186 mph figures (257 and 300 km/h) closest to the marketed speeds. |
The difference is the difference between “we modelled it and it works” and “we estimated it from comparables.” The first is a tested result for this railway. The second is an educated guess that a later, detailed study would have to confirm.
The only simulated number is the slow one
The memorandum’s own tables make the gap plain. The single time it produced by simulation — the 110 mph (177 km/h) base case — is roughly 3:59 to 4:19 for Toronto–Montréal. The faster times on the same page, for a 186 mph (300 km/h) or 160 mph (257 km/h) train, run from about 2:40 to 3:10. But those faster figures are the spreadsheet ones. The four-hour trip is the only number anyone actually drove through the model. The under-three-hour trips that make high-speed rail attractive were never simulated for this corridor.
This matters because the public ALTO project is now built on 300 km/h (186 mph) running. Even the “calculated” 186 mph (300 km/h) times in this 2023 record trace back to the spreadsheet, not the simulator — and the simulator was only ever pointed at the slow case.
A second problem: not the door-to-door time
There is a second issue with these numbers, separate from how they were produced. Every figure here — simulated or estimated — is a train-in-motion time, measured platform to platform. It is not the door-to-door time that decides whether a traveller picks rail over flying, and door-to-door time depends on something ALTO has not settled: where the stations are. With downtown stations at both ends the corridor is competitive; with the suburban or peri-urban stations most consistent with the project’s cost structure, the advantage over air narrows or disappears. A separate academic submission to the consultation went further, noting that ALTO’s published times do not appear to even include the time for a stop in Ottawa — so the in-motion figures may be understated before the door-to-door question is reached. We treat that in full in The Station Location Problem and The Last Mile; the point here is narrower — the headline time is an estimate, and even taken at face value it is not the number that matters.
The journey time as a government decision
The instruction to hold the journey times down did not come from a technician. The email chain records that when a Toronto figure was put forward assuming sustained speeds above 160 mph (257 km/h), a Transport Canada official objected that it “assumes a full journey time from Toronto at speed greater than 160, which is not the intent of the Government,” and explained that the intent was to have bidders identify the segments with the lowest marginal cost for higher speed. The exchange closes on September 4, 2023 with the project director’s note: “No change to journey time agreed by Vincent.”
That official is Vincent Robitaille. According to Transport Canada’s own published biography, Robitaille has served as Assistant Deputy Minister – High Frequency Rail since December 2021 — the month the project’s governance passed to a Transport Canada–led integrated team — and he leads that team. His background before the role was in commercial policy and financing, not rail engineering: from 2018 to 2021 he was Director General of Transport Canada’s Centre of Excellence on Strategic Investments, working on the commercial elements and alternative financing of major transportation investments, and before that he led the public-private-partnership procurement of the new Champlain Bridge Corridor in Montréal. His credentials are financial and project-management designations (CFA, PMP, Certified Director, and an MBA). Transport Canada
Why the background is relevant, not incidental
This is an observation of record, not of motive. The person defining the journey-time ceiling as the Government’s intent — and steering bidders toward “the lowest marginal cost” rather than the fastest trip — is the project’s most senior Transport Canada official, whose professional expertise is procurement and project financing. It is consistent with a journey time being treated as a commercial and cost target to be managed, rather than an engineering output to be measured. The released record shows the target being set; it does not require any inference about why.
The same official, now selling the fast times
In a public podcast interview in December 2025, Robitaille — by then leading the project for Transport Canada — described the corridor to a general audience in precisely the terms the 2023 record could not support with simulation: Montréal reachable in well under current rail times, a city you could reach for a day trip and return the same evening, trains “every half an hour,” the corridor as “commuting distance.” Those are the fast, frequent-service figures — the ones drawn from the spreadsheet.
The internal record from 2023 shows the same official holding the specification below those speeds — directing that journey times not assume sustained running above 160 mph (257 km/h), because faster was “not the intent of the Government” — and relying on benchmarked estimates for anything quicker. The public pitch and the internal caution are two years apart and point in opposite directions. The travel times now used to sell the project are of the kind the same official described internally, in 2023, as indicative.
A promise, or an estimate?
When a government tells the public “this train will get you there in X hours,” people reasonably assume engineers modelled the actual route and confirmed it. This record shows that, for the fast times, they did not. They did the back-of-an-envelope version — distance against speeds observed in other countries — and said so internally. A spreadsheet estimate is a hope; a simulation is the closest thing to a tested promise. The faster ALTO travels in its marketing, the further it gets from the only journey time anyone actually ran.
One caveat, stated plainly so the point is not overdrawn. The memorandum does say these estimates were always meant to be refined through later design and operational modelling by the eventual private partner. So the fair claim is not that the numbers were invented. It is that the detailed validation was deferred, and that as of this 2023 record the project’s faster journey times — including those near what is marketed today — had no corridor-specific engineering behind them, only benchmarked estimates. No simulation of high-speed running on the Toronto–Québec line appears anywhere in the released record.