Tag: Billy Bishop

  • One shows its work

    How Public Feedback Gets Counted
    One Shows Its Work. One Doesn’t.

    Two federal consultations were each asked the same plain question under access–to–information law: how did you analyse what the public told you? One answered in full. The other withheld it.

    The short version

    Public consultations produce thousands of comments that someone has to read, sort, and summarise into “what we heard.” So a fair accountability question is how that sorting is done. Transport Canada, asked that question about the Billy Bishop airport consultation, disclosed its method in full — the software it used, the written instructions given to it, even the program code. ALTO, asked the same question about its rail–corridor consultation, withheld the tool, the categories, and the instructions. And when asked for the actual tally of what people said, ALTO produced no record at all.

    The same question, asked of both

    Both access requests asked, in nearly identical words, for three things: the name of the software, tool, or model used to sort and classify the public’s responses; the list of categories or codes applied to them; and any written rules or prompts given to that tool.12 It is about as basic as transparency questions get — not what people said, but how their words were organised and counted.

    The two consultations differ in scale and format: one was largely email–based, the other a larger multi–channel process with open houses, a questionnaire, and an interactive map. But the access question put to each was the same.

    Transport Canada showed its work

    In response to a request about the Billy Bishop Toronto City Airport consultation, Transport Canada released its analysis method in full, with no exemption applied to it.1 It named two tools, used in sequence: an in–house routine that strips personal information from each email before any analysis — and the full source code of that program was released — and, for the categorisation itself, “Claude, a general–purpose large language model,” used to identify recurring themes, tally supportive submissions, and estimate how many emails were part of coordinated form–letter campaigns.

    It went further. Transport Canada released the written prompts its analyst gave the tool, and the standing rules the work operated under — among them that published counts in a category can never be quietly revised downward, that the count of supportive submissions rises only after each one is individually reviewed and confirmed, and that no figures are to be fabricated.1 Whatever one makes of using software to help read public comment, the method is on the public record, and can be checked.

    ALTO withheld it

    ALTO was asked the same thing about its Corridor Study Area consultation: name the tool behind the “semantic clustering” and “multi–label classification” it describes in its own What We Heard Report, and share the category list and the instructions.2 ALTO released a board–level slide deck, but withheld the tool, the classification scheme, and the prompts, citing the exemptions for advice and for accounts of deliberations — sections 21(1)(a) and 21(1)(b) of the Act.

    A companion request asked for the tabulation itself: how many submissions fell under each theme, and how many were for or against. That record, ALTO replied, does not exist — “no responsive records were identified.”3 So the method is withheld, and the counted result is said not to exist.

    Why this matters

    A consultation is only as trustworthy as the method that turns raw comments into a summary of “what we heard.” When one federal institution can show its tools, its code, and its counting rules for exactly this task, it is hard to see how the same information becomes advice or deliberation when another institution is asked about the same kind of work. And if no record tabulates what people said, then the public is entitled to ask on what basis it is told its feedback is helping to shape the project at all.

    Questions worth asking

    • If Transport Canada can name the software it used to analyse consultation feedback, and release the prompts and the code, why can’t ALTO?
    • Where is the record showing how many people raised each concern — and how many were for and against?
    • What rules govern how ALTO counts support and opposition in its consultation, and who checks them?

    This is not about which tool is better, or whether software should help read public feedback — it plainly can. It is about whether the public can see how its own words were sorted and counted. One federal consultation showed its work. The people living along the rail corridor are entitled to the same.

    Sources

    1. 1Transport Canada, access request A–2026–00271, released under the Access to Information Act (Billy Bishop Toronto City Airport consultation). The analysis–methodology response names the tools used, including an in–house anonymization macro (source code at Annex 1) and “Claude, a general–purpose large language model,” and sets out the analyst prompts and counting rules. Download the release package (PDF).
    2. 2ALTO (VIA HFR – VIA TGF Inc.), access request A–2026–0016, released in part under the Access to Information Act (methodology and classification scheme for the Corridor Study Area consultation). The tool name, classification taxonomy, and prompts were withheld under sections 21(1)(a) and 21(1)(b). Download the released record (PDF).
    3. 3ALTO (VIA HFR – VIA TGF Inc.), access request A–2026–0017, released under the Access to Information Act (tabulations and participation figures). For the tabulation of feedback by theme and direction of view, ALTO identified no responsive records. On file.
    ALTO HSR Citizen Research Initiative Independent, non-partisan research on the proposed Toronto–Québec City high-speed rail corridor citizenresearch.ca
  • A deal that lost its other half

    The Billy Bishop Reversal
    A Deal That Lost Its Other Half

    Reporting says Ontario agreed to go along with ALTO in exchange for the Billy Bishop airport expansion. Ottawa has now pulled back from the airport — so if that account is right, what is holding up the province’s side?

    The short version

    A newspaper report describes an informal trade behind the scenes: the province would support the ALTO high-speed rail line, and in return Ottawa would let Billy Bishop airport expand. Ottawa has now pulled back from the airport. If the report is right, the reason Ontario was cooperating with ALTO has just disappeared — and that matters for every community along the route.

    What the reporting says

    In late July 2026, the Toronto Star reported that Ottawa’s decision to drop the Billy Bishop airport expansion was tied to a behind-the-scenes understanding: the province would go along with ALTO, and in exchange the airport expansion would proceed. One source put it plainly — “It’s Billy Bishop for Alto, that was always the understanding.”1 The paper reported the Premier and Prime Minister had even shaken hands on it. It also noted that the high-speed line — a 300 km/h train cutting through farmland in rural Ontario — has always been a hard sell to the province’s own members whose ridings it crosses.

    A private handshake can’t be independently confirmed, and the account rests on unnamed sources. But it was reported in detail, and it fits how difficult the corridor has been for the province to defend.

    What changed

    Ottawa has now pulled back from the airport expansion. In his July 24 statement, the Minister of Transport said the government’s focus is now only on the already-approved safety work, that Toronto voices would shape any future plans, and that it would not pursue anything that harms treasured public spaces, raises noise, damages the environment, or blocks housing — the effects opponents of the expansion had raised.2 The government cited more than 87,000 public responses;2 the Toronto Star reported that about 87 per cent were opposed.1 Some call the decision a cancellation, others a pause1 — but either way, the province is left holding, at best, a promise that has been put on hold. Whatever it was reportedly getting in return for supporting ALTO is, for now, gone.

    Why this matters for the corridor

    ALTO’s Ontario stretch can’t be built by the federal government on its own. It needs the province and local municipalities to cooperate on the hard, unglamorous parts: assembling land, approving where the line crosses roads, relocating utilities, and separating the tracks from local traffic. If that cooperation was really a trade — support given in exchange for the airport — then taking the airport away removes the reason for the support. That uncertainty lands squarely on the towns, farms, and landowners in the train’s path, who still don’t know whether or how the project moves ahead.

    One standard, for everyone

    Ottawa reconsidered the airport by listening: it counted the public responses, weighed the opposition, and set conditions rather than pressing ahead. Yet the same July 24 statement reaffirmed ALTO as part of the government’s integrated plan for the Greater Toronto Area, alongside the Pearson expansion.2 One waterfront project was reshaped by public feedback; the far larger rail project was restated in the same document without reference to any. Communities along the ALTO route raised their objections too, through the project’s own consultation, which closed on 24 April 2026. No comparable count of responses received, or of concerns raised, has been published for that consultation. If 87,000 responses were enough to change course on one waterfront project, the people who live along a much larger one are entitled to know how their objections are being weighed.

    Questions worth asking

    • Does Ontario still support ALTO now that the thing it was reportedly promised is off the table?
    • If the province’s support was tied to the airport, what is it tied to now?
    • Will the communities along the corridor get the same fair hearing that stopped the airport expansion?

    None of this is about one political party. Unease with ALTO crosses party lines. The Star reports the line has been a hard sell to the province’s own members whose ridings it crosses. This is a straightforward question of accountability: if the reported understanding was what it appeared to be, one public decision has knocked a leg out from under another, and the people in the corridor’s path deserve to know where that leaves them.

    How to read this page

    The trade described here is reported by the Toronto Star on unnamed sources. Neither government has confirmed it, and this page does not treat it as established. Everything that follows from it is written conditionally, because that is all the evidence supports.

    Everything else is quoted from the two named sources below and can be checked there: the Minister’s 24 July statement and its conditions, the figure of more than 87,000 responses, the reported 87 per cent opposition, and the reaffirmation of ALTO in the same statement. Where something has not been published, this page says so rather than inferring it, and makes no claim about anyone’s motives.

    Sources

    1. 1Robert Benzie, Ryan Tumilty and Mark Ramzy, “‘Disappointed’ Doug Ford spoke privately with Mark Carney after decision blocking Billy Bishop expansion,” Toronto Star, July 27, 2026.
    2. 2Hon. Steven MacKinnon, Minister of Transport, Statement on Billy Bishop Toronto City Airport, July 24, 2026.
    ALTO HSR Citizen Research Initiative Independent, non-partisan research on the proposed Toronto–Québec City high-speed rail corridor citizenresearch.ca