Connectivity Is Not Enough: Why Indigenous Broadband Governance Is Moving Toward Consent, Local Operations and Co-Ownership
Original Chinese title: 網路接到了，控制權也該一起到嗎？加拿大原住民族寬頻正從「被接上」走向同意、自營與共同持有
Canada’s 2026 Broadband Fund rules place written Indigenous community consent, technical training, community benefits and co-ownership closer to the center of infrastructure design. The deeper question is who chooses sites, maintains systems, governs data and assets, and retains control after a subsidy ends.
鄭淑禎
鄭淑禎 | Full-time Assistant Professor, Shih Chien University | Focuses on industrial transformation, agricultural value chains, local economies and the application of technology.
Having a Signal Is Only the First Question; the Second Is Who Decides How the Network Lives On
Remote-area broadband policy is often measured through coverage, download speed, upload speed and household availability. Those indicators matter because telehealth, online education, government services, disaster information and ordinary work all depend on basic connectivity. For an Indigenous community, however, a tower appearing on a coverage map does not by itself answer who controls a network that is becoming essential public infrastructure.
The next layer of questions concerns governance. Who chooses where infrastructure is placed, who can demand repairs, who owns equipment, who is allowed to inspect operational data, who selects vendors, and who bears responsibility after construction funding is exhausted? Those questions determine whether connectivity creates durable local capacity or merely deepens dependence on a distant provider.
Canada’s CRTC 2026 Broadband Fund call contains an important shift. Projects affecting Indigenous communities are expected to obtain written evidence of community consent before final approval, and the program framework also encourages Indigenous employment, technical training, community benefit and forms of co-investment or co-ownership. The policy direction is moving from “build a network for a remote community” toward “give the community a stronger role in designing, holding and operating the network.”
Why Written Consent Matters More Than Routine Consultation
Many infrastructure projects hold public meetings or information sessions, but procedural consultation is not the same as governance authority. If the route, technology, supplier and operating model are already fixed before residents are invited to comment, participation may reduce conflict without giving the community any real ability to alter the project.
The CRTC guidance requires applicants serving or building in Indigenous communities to provide evidence of consent from community representatives before final approval. The form of that consent can reflect the community’s own processes, including a formal resolution, agreement, memorandum or meeting record. That matters because an external agency should not unilaterally define the only legitimate way a community can express collective consent.
Written consent is still only a starting point. Meaningful consent requires enough information and time to understand maintenance costs, backhaul capacity, spectrum constraints, security risks, long-term contracts, equipment replacement and what happens if the service model changes. A signature attached to a short engineering presentation does not automatically produce an informed or sustainable decision.
After the Tower Is Built, the Most Expensive Problems Often Begin in Later Years
Remote networks can be difficult to maintain because snow, wildfire, heavy rain, power failures, cable cuts, satellite backhaul problems and shortages of replacement parts can all produce longer outages than in urban areas. When a specialized technician must travel hundreds of kilometers, travel costs and restoration time become part of service inequality.
That is why local technical training is not a minor benefit. If community staff can diagnose power systems, routers, antennas, backup links and common equipment failures, they may be able to restore essential service or provide useful diagnostics before an outside contractor arrives. Local capability turns maintenance knowledge into part of the infrastructure itself.
Digital equity should therefore include restoration time as well as advertised speed. Two communities can both be listed as having a 50/10 Mbps service while experiencing radically different realities if one outage is repaired in two hours and another lasts three days. Mean time to repair is a public-service fairness indicator when health, education and emergency response all depend on the same connection.
Co-Ownership Is Not Symbolic; It Shapes Who Decides the Next Upgrade
Policy interest in co-investment and co-ownership has a practical reason. If every asset belongs to an outside telecommunications company, the community may be the principal user yet still have little authority over upgrade schedules, service priorities, pricing or equipment replacement. Shared ownership can create a formal seat in decisions about assets, operations and long-term planning.
But co-ownership is not automatically empowerment. It can also transfer debt, depreciation, legal liability and maintenance obligations. If a community contributes capital without receiving technical information, system access or meaningful voting power, risk has been decentralized while control remains elsewhere.
A sound co-ownership agreement should therefore specify rights and responsibilities in operational terms: who holds the equipment inventory, who has administrative access, who can view network status, who chooses suppliers, who authorizes upgrades, and how major outages or cybersecurity incidents are jointly managed. Ownership becomes meaningful when it changes decisions, not merely when a community name appears on a contract.
Once a Network Exists, It Creates Another Asset: Data
Connectivity generates operational data such as device logs, traffic statistics, location information, usage periods, service demand and platform records. These data can improve reliability and capacity planning, but they can also be used for surveillance, commercial analysis or policy decisions that affect a community without its participation.
This is where broadband infrastructure intersects with Indigenous data sovereignty. The First Nations Information Governance Centre’s OCAP® principles—Ownership, Control, Access and Possession—show why data governance cannot be reduced to individual privacy notices. Collective data can shape how a community is represented, funded, researched and governed.
A community-governed broadband project therefore needs data clauses alongside engineering and asset clauses. The agreement should ask what operational data are retained, how long they remain stored, whether a supplier can reuse them, whether third-party cloud services are involved, whether the community can obtain its own service statistics, and whether researchers need separate permission before turning network-use data into research material.
Network Quality Should Be Defined by Community Needs, Not Only by a Speed Test
Urban consumers often judge a connection with a speed test, but remote public services may depend on different characteristics. A clinic may require stable upload capacity and low latency for video consultation. A school may need many simultaneous users. Emergency services may need backup power and redundant links. Cultural documentation may require reliable upload of large media files.
Service quality should therefore be derived from actual community priorities rather than a single nationwide download target. A network can look fast at midnight and still fail during the day when a school and clinic are active at the same time. An attractive average can hide the hours when essential services are effectively unavailable.
Co-design begins by identifying the services that must not fail and then translating those needs into engineering requirements. Clinics, schools, emergency centers, administrative offices, community broadcasting and cultural-data facilities may require different priority levels, backup power and capacity. Local knowledge becomes an engineering input when it can change these design choices before construction is finalized.
Taiwan Should Borrow the Governance Questions, Not Copy the Canadian System
Taiwan has different terrain, telecommunications markets, law and community-governance arrangements, so the CRTC model cannot simply be transplanted. The useful lesson lies in the questions it makes visible. Does a remote-area broadband subsidy stop at coverage, or does it also require local maintenance capability and skills transfer? Are fiber, microwave, mobile and satellite backup choices shaped by the communities that will depend on them?
Data governance is another question that has to be localized. Who controls service statistics and public-service platform data? What outage standard is acceptable when one network supports telehealth, education and emergency information at the same time? Should remote Indigenous communities have restoration commitments that reflect higher consequences of prolonged disconnection?
These are not cultural decorations added after an engineering project is complete. They are questions of public-service equity. The purpose of comparison is to expose design choices that may otherwise remain invisible, then test which choices make sense under Taiwan’s own legal, geographic, economic and community conditions.
The Two-Eyed Seeing Entry Point Is Whether Community Knowledge Can Change the Engineering Drawing
Technology projects often survey residents after construction, but post-hoc satisfaction measurement is not Two-Eyed Seeing. A genuinely two-way knowledge process allows different knowledge holders to alter the problem definition before the engineering drawing is fixed. Community knowledge must be able to change technical decisions, and technical evidence must also be able to test and refine local assumptions.
Residents may know which ridge experiences the strongest seasonal winds, which road becomes inaccessible during heavy rain, where people gather during power failures, which households rely most heavily on telehealth, and where mobile dead zones create real safety risks. Engineers contribute knowledge about spectrum, antenna height, backhaul, backup power, cybersecurity and capacity constraints. Neither perspective is useful if it is invited only after the other has already made every consequential decision.
The practical test of Two-Eyed Seeing is whether the exchange changes site selection, backup requirements, service priorities and data-governance rules. When engineering measurements can revise a local judgment and local experience can revise the engineering plan, the project becomes a shared design process rather than a technical system decorated with community consultation.
From the “Last Mile” to Control Over the Last Mile
Remote broadband policy has long spoken about the “last mile,” as though the problem were solved once the final segment of cable, wireless backhaul or satellite service reaches a community. The 2026 Canadian framework is notable because it points toward a more difficult question: who controls that last mile after the construction phase ends?
If connectivity arrives while maintenance, pricing, equipment, data and upgrades remain entirely controlled from elsewhere, dependence can increase even as coverage improves. If the same project develops local technical capacity, requires meaningful consent, creates a real role in ownership and establishes data-governance rights, connectivity can become part of long-term community capability.
The next generation of Indigenous digital policy should therefore ask more than how many households are covered. When service fails, who can repair it? When quality deteriorates, who has standing to demand improvement? When operational data are reused, who decides? When the next upgrade is planned, who has a seat at the table? Those answers determine whether a network remains an external service or becomes public infrastructure that a community can meaningfully govern.
Sources
AI use and content-safety disclosure
This English translation was prepared with AI assistance for organization, drafting and language editing. Human editorial review remains responsible for viewpoint, factual verification and publication.