What’s Happening

One of the recent ITU regulatory mechanisms receiving attention is the waiver process for bringing into use (BIU) or deployment milestones for NGSO constellations. A prominent case is the decision by the ITU Radio Regulations Board to grant Rivada Space Networks a waiver from the requirement that 10 percent of its constellation be placed into orbit in a given year, conditional on evidence of manufacturing, funding, and launch contracts. PR Newswire+2SpaceNews+2

These waiver decisions occur when an operator shows that meeting a particular deployment or operational requirement is infeasible under existing constraints, but that the intent and underlying capabilities are credible. The waiver does not change the treaty provisions, but grants relief under specific, documented conditions.

Another related mechanism is the risk of losing frequency assignments if BIU or deployment milestones are not met. ITU requires that once spectrum or orbital rights are granted, they must be “brought into use” within a specified time window, or risk lapse or cancellation. Historically, many filings were made opportunistically, long in advance, but delays in manufacturing, launch or deployment often meant operators miss those BIU-based deadlines.

Why It Matters

If SmallSat or CubeSat operators do not meet BIU or deployment milestones, they risk losing spectrum rights globally under the ITU treaty framework. For a constellation, this can mean the loss of frequency assignment or orbital coordination protections, which then undermines commercial viability or international operations. The waiver process is not guaranteed and requires detailed evidence of ability to deliver—not just intent. Financial commitment, launch contract proofs, and demonstrable deployment capability are commonly evaluated. Missing BIU deadlines without such evidence can jeopardize mission planning and funding.

Moreover, operators must build in contingency for delay risks: manufacturing delays, payload test failures, launch delays, or regulatory review delays. Because the ITU is international, missing BIU milestones can have knock-on effects in multiple nations, especially where administrations require consistency with ITU filings for national licensing or spectrum coordination.

Implications for SmallSat / CubeSat Operators

Operators should treat BIU milestones as hard deadlines rather than optional targets. Constellation filing strategies need to include backup launch arrangements or payload spares so that at least a minimum number of satellites are in orbit when required. Also, technical readiness — including spectrum performance, orbital tracking, antenna performance — must match filings before deployment.

Similarly, when seeking waivers, applicants need rigorous documentation: proofs of funding, manufacturing contracts, validated launch manifest, orbital plans, and evidence that coordination issues are addressed. If waivers are granted, they often come with conditions or reporting obligations which must be met to maintain the waiver and spectrum assignment.

SmallSat teams must also consider that frequency assignments or orbital rights acquired without subsequent BIU may reduce valuation, restrict opportunities for future filings, or dissuade investors or launch partners who see BIU compliance as part of risk assessment.

Deep Dive Scenarios

Scenario: A SmallSat Internet provider applying for global service rights
Such a provider files for large NGSO spectrum rights early. If they cannot place a minimum number of satellites by the BIU deadline, they may lose the right to claim protection from interference under the ITU treaty. To guard against this, they may need to deploy a minimal “pathfinder” sub-constellation early, or document alternate deployment paths.

Scenario: A University / Research consortium building CubeSats over several years
A multi-year research program may file early for frequency assignments or coordinate orbital slots but intend to launch in phases. Without careful alignment with BIU requirements, early filings may lapse or require renegotiation. The institution may need to plan for interim flights or leverage waiver mechanisms.

Checklist for SmallSat / CubeSat Operators

• Verify the BIU or deployment milestone requirements attached to your ITU filings; ensure your mission schedule can meet them.
• Document manufacturing, launch contracts, funding status well ahead of BIU deadlines.
• Maintain transparency and readiness for waiver submissions, including technical readiness and coordination status.
• Monitor risk factors that could delay deployment (launch provider risks, payload delays, regulatory holdups) and plan mitigations.
• Track recent precedent decisions (e.g., Rivada waiver) to understand what evidence the ITU deems acceptable.