The Bell tower file, from start to finish: what the process required, what happened, and what it taught us

Between March and July 2026, Ormstown went through its first federal telecommunications consultation — a 36-metre Bell Mobilité tower proposed on municipal land near Route 138. Council authorized the lease by a unanimous recorded vote on July 6. This article consolidates the Observer's coverage into a single record: what the rules required, what was done well, where the documents show gaps, and what residents can take from it for next time.

Why this file mattered

This was never only about one tower. Cellular coverage in the Haut-Saint-Laurent is a real need, and many residents want it improved. The Observer's interest has been narrower: when a telecommunications company and a municipality carry out a public consultation, do residents get the information and the time the rules promise them? That question matters whatever one thinks of the tower, because the same process will govern the next tower, and the next.

The framework, in plain language

Telecommunications are federal jurisdiction. Before Bell can build an antenna system, it must follow Innovation, Science and Economic Development Canada's procedure CPC-2-0-03: notify residents within a prescribed radius, run a written public consultation of at least 30 days, respond to questions, and show that alternatives to a new structure were considered. The municipality plays two distinct roles in such a file: as the property owner — here, the land is municipal — and as the land-use authority whose review of the consultation ISED relies on before approving construction.

Ormstown has no municipal protocol for telecom consultations, a fact noted in Bell's own consultation brochure. That is not unusual for a municipality of 4,300, and it is one of the constructive takeaways below.

The timeline

What the record shows was done well

Fairness requires saying this clearly, and specifically.

The municipality asked Bell to hold a public information session it was not obliged to hold, and the full council attended it. The written consultation ran longer than the federal minimum. On July 6, at the mayor's initiative, the lease was put to a full recorded vote, each member's position stated publicly — when it could have passed on consent. Residents' written questions were read into the record and answered.

And council did not sign the lease early, though it could have. The authority existed from March 2: Resolution 26-03-074 mandated the director general to negotiate and sign. By the mayor's account on July 6, the municipality considered signing with an exit clause, its notary advised against it, and it waited until the consultation had concluded. Council held that authority for four months and chose not to use it. That was a choice, and it was the prudent one.

Where the record shows gaps

Five matters, each documented in the sources listed below, remain part of the factual record. The Observer presents them as questions the file leaves open, because that is what they are.

1. The height as first described

The tower was described to council on March 2 as "une trentaine de mètres." Bell's engineering plan specifies 36 metres — a monopole carrying 12 antennas. The figure reached residents through Bell's own notification materials rather than through a municipal correction. How did the description presented to council come to differ from the plan?

2. The lot number

Public documents in this file have carried three different cadastral numbers for the site. The June 2 notice cited lot 6 065 438. The published July 6 agenda cited lot 6 065 482. Bell's engineering plan, its notices to residents, and Resolution 26-03-074 — as well as the resolution as read aloud on July 6 — cite lot 6 065 483. The Observer has verified through the Québec cadastral registry that these are distinct parcels. In all likelihood these are clerical errors; but the lease will be filed at the land registry, where precision is the entire point. The Observer will verify the number recorded in the official minutes and in the registered lease.

3. The zoning designation

The Observer's reading of Règlement 148-2023 places the site in Zone P-15, where the listed uses do not include telecommunications infrastructure. Because telecommunications are federal, a federal undertaking can proceed regardless of local zoning — the mayor made this point on July 6, noting the municipality's role in the file is that of property owner. That is broadly correct as a matter of law. The open question is narrower: in its consultation role, how did the municipality evaluate the project against its own planning framework, and where is that evaluation recorded? The Observer put the zone-designation question to the municipality in writing and has not received a substantive answer.

4. The consultation's closing date, and the disclosure record

Bell's June 19 letter to the Observer stated that the reply period would close on July 10. On June 26 — fourteen days before that date, and one day after receiving the Observer's reply — Bell notified ISED that the consultation was closed. The municipality, for its part, relied on the dates in the May 20 Gleaner notice, which Bell extended in practice to June 26. Asked about the discrepancy on July 6, the mayor answered that the dates he relies on are those in the published notice. By the end of the file, three closing dates had been in play — the newspaper date, the letter date, and the date on which Bell decided it was finished — and no two parties were working from the same one. Which date governed, and what became of comments the proponent had invited up to July 10?

Separately, the alternatives analysis that CPC-2-0-03 requires — rooftops, the municipal water tower, other structures — was referenced at the June 10 session but has not been made public, and Bell's June 19 letter declined to provide the list of alternative sites or the criteria on which they were set aside, describing this as commercially confidential. The Observer's assessment of each disclosure obligation, and the full correspondence, are published and linked below. The question of whether the process met the federal requirements now rests with ISED, the body responsible for answering it.

5. The rent, and what was already public

At the June 10 session, the annual rent was described as confidential information that should not have been released. The figure had been public since March 2: Resolution 26-03-074 states an initial annual rent of $10,000, increased annually, over a term of five years plus six five-year renewal options. The resolution was adopted unanimously, published on ormstown.ca, and the session was broadcast on the municipality's YouTube channel. Residents seeking the rent for their own municipal land could find it in their council's own published record. The remaining terms of the lease are not public; on July 6, the mayor directed those seeking them to the access-to-information process, noting that some provisions are legally protected.

The municipality's position

The mayor has addressed this file publicly at greater length than any other this year, and his position deserves to be presented fully. In his account: the municipality's hands are largely tied — telecommunications are federal, and had the tower been proposed on private land, the town could only have submitted written comments like any citizen. As owner, it negotiated a lease; as a council, it weighed residents' reservations against a coverage need it considers pressing. The consultation exceeded the federal minimum, and the information session was held at the municipality's own request. On the ecological question raised by a resident, council concluded in caucus that legal compliance rests with the promoter and that the site — a clearing already hosting a pumping station, ringed by mature trees — showed no indication of particular ecological risk.

[Right of reply: on July 16, 2026, the Observer transmitted the factual points in this article to the municipality, through its legal counsel, with an invitation to respond. Any response received will be incorporated into this article and noted here.]

What residents can take from this

Two practical outcomes are worth pursuing, and neither requires an adversarial posture.

A municipal telecom consultation protocol. Many Québec municipalities have adopted their own antenna-siting protocols under ISED's framework, setting local expectations for notification, documentation, and timelines before the next proposal arrives. Ormstown now has first-hand experience of where the default federal process leaves residents guessing — starting with the question of when, exactly, a consultation ends. Adopting a protocol would turn this file's lessons into policy, and it is squarely within council's power.

Clear separation of roles. When a municipality is simultaneously the landowner, the lease beneficiary, and the authority whose review of the consultation ISED relies on, residents benefit from seeing those roles handled distinctly and documented — who evaluated what, wearing which hat, on what record. A protocol can address this too.

The lease is authorized. The tower, pending ISED's process, is likely coming — and with it, coverage many residents genuinely need. What remains open is whether the next consultation, on whatever subject, reaches more than a handful of people, and whether the paper record it produces is one everyone can rely on: one lot number, one closing date, one version of the facts, available to all.

Sources and the complete record

This article consolidates and supersedes the Observer's running coverage of this file. Corrections made along the way are reflected here — including the antenna count (12, not the 18 first reported) and the attribution of one statement in the June 10 transcript. Questions or corrections: ormstownobserver@gmail.com