The landscape in one paragraph
Coordination is the process that converts a filed satellite network into one that can actually operate with protection: the negotiation, network by network, through which your system and those filed ahead of you agree how to share the same frequencies without destroying each other. Formally it is a procedure between administrations under Article 9 of the ITU Radio Regulations; practically it is conducted by operators’ engineers and regulatory staff, in meeting rooms and spreadsheets, over years. Two facts frame everything. First, coordination is where the real content of your spectrum rights is written: the register records that you may operate, but the coordination agreements determine how — at what power, in which geometries, with what constraints. Second, the procedure has no judge: the ITU identifies who you must talk to and records the outcome, but nobody can compel agreement, which makes coordination a diplomatic campaign with engineering as its language — and preparation, patience and creativity as its decisive weapons.
Step 0 — Design for coordinability, before you file
Your coordination burden is fixed largely on the day your filing’s technical envelope is drafted, so the discipline starts pre-filing. Three choices dominate. Band selection: the congestion of the band you choose determines the length of the queue you must negotiate through — a fact that should sit beside link budgets in the trade-off analysis, because a two-year coordination in a quieter band can be worth more than theoretical capacity in a saturated one. Power discipline: filings drafted with maximal power and coverage “to preserve flexibility” maximise the number of networks you technically affect, and therefore the number of counterparties who can say no; a tighter envelope buys a shorter campaign. Realistic geometry: for GSO, your orbital position relative to neighbours; for NGSO, your constellation’s altitude and inclination relative to systems you will repeatedly align with. File what you will fly, sized to what you can defend, and the campaign shrinks before it begins.
Step 1 — Read your own publication like an adversary would
When the ITU’s Radiocommunication Bureau publishes your coordination request in the fortnightly BR IFIC, it comes with the crucial annexe: the identification of the administrations and satellite networks with which coordination is required — triggered by criteria such as overlap within the coordination arc for GSO networks, or the interference-potential thresholds of the Regulations’ appendices. This list is your campaign map, and the first professional act is to triage it, because the entries are radically unequal.
Sort every identified network into three piles. Real and operating: systems with satellites in orbit and services running — these can genuinely block you, and their agreements are worth the most. Real and coming: filings backed by funded programmes with plausible deadlines — future neighbours, worth early goodwill. Paper: filings that will predictably lapse at their bringing-into-use deadlines, held by speculators or abandoned programmes. The paper pile is often the largest, and distinguishing it is the highest-value analysis in the whole exercise: agreements conceded to networks that will never fly are operational freedom given away for nothing, while time spent chasing their holders is schedule burnt. Assess each filing’s deadline, its holder’s credibility, its administration’s track record — and calibrate your effort accordingly.
Step 2 — Work the four-month window, in both directions
The procedure’s first hard clock: administrations identified in a coordination request must lodge their disagreement or comments within four months of publication, and silence has consequences — a counterparty that fails to respond in time can lose its right to be taken into account. This cuts both ways, and both matter.
Defensively, it means the fortnightly circular is not optional reading. Every BR IFIC may contain new filings that affect your networks, and your four-month clock to protect your position starts at publication, not at discovery. A standing review of each circular against your portfolio — the single most important recurring task in spectrum operations — is what keeps later-comers from slipping past your protection. Offensively, it means your own publication will draw a wave of responses within four months, defining who has formally entered your campaign; log them, acknowledge them, and use the response pattern itself as intelligence about who is paying attention and who is not.
Step 3 — Build the technical case before the first meeting
Coordination meetings are won in the preparation. Before contacting any counterparty, your engineers should have run the interference analysis both ways: what your network does to theirs, what theirs does to yours, under the standard methods — carrier-to-interference ratios and the ΔT/T thresholds of the Regulations for GSO cases, equivalent power flux-density compliance towards GSO systems for NGSO constellations, and time-domain simulation of in-line events for NGSO-to-NGSO. Commercial tools exist for all of this, and for a first campaign, engaging a specialist consultancy for the modelling is money that buys credibility: arriving with a rigorous analysis marks you as a serious counterparty and reframes the meeting from posturing to problem-solving.
The preparation should conclude in a negotiating brief per counterparty: where the genuine conflicts are (usually a small subset of the identified overlap), which operational scenarios actually matter to you, what you can concede cheaply, and what you must hold. Know your own red lines quantitatively — the power, the geometries, the band segments without which your business case fails — before someone else proposes them away.
Step 4 — Run the campaign
With the map triaged and the analysis built, coordination becomes a managed portfolio of bilateral negotiations, and the craft lies in a few practices the veterans all share.
Prioritise by blocking power, not list order. Open early with the operating incumbents who can genuinely constrain you and whose agreement unlocks financing confidence; let the paper pile age towards its deadlines.
Use the industry’s rhythms. Coordination runs on meetings, and the community economises by clustering them: the margins of ITU meetings, WRC preparatory sessions and industry conferences are where multiple counterparties can be progressed in one trip. Relationships compound — the engineer across the table this year will be across it for decades, which is why the field prizes reasonableness and long memory in equal measure.
Trade in the standard currencies. Agreements are assembled from a known toolkit: frequency segmentation (you take this sub-band here, they take that one there), geographic separation (coverage carve-outs, service-area limits), power and off-axis emission limits, polarisation isolation, orbital-separation commitments, and — increasingly, between constellations — operational rules for the geometries where systems align. Creativity in packaging these is what closes hard cases; a concession worthless to your business but valuable to theirs is the best money in the room.
Paper everything, precisely. Coordination agreements are typically confidential operator-to-operator documents, later reflected in what the administrations record. Draft them with transaction-grade care: they bind for the life of the systems, they surface in every future due diligence, and ambiguity in them is deferred conflict. Where you and a counterparty share many networks, consider the umbrella agreement — one framework covering the fleets — which the major operators use to keep their mutual coordination wholesale rather than retail.
Keep the register in sync. Progress must flow back through your administration to the ITU at the procedure’s gates; a campaign won in meetings but unrecorded in Geneva protects nothing.
Step 5 — The NGSO specifics
Constellation operators inherit two extra disciplines. Towards GSO networks, protection is largely rule-based rather than negotiated — compliance with the applicable power flux-density limits, demonstrated by validated software — though the recent divergence between ITU limits and national regimes (the United States has replaced the treaty framework domestically) means the compliance target now varies by market, a fragmentation your regulatory team must track jurisdiction by jurisdiction. Between NGSO systems, the problem is the in-line event — the moments when two constellations and an earth station align — and the practice, where negotiation fails, has converged on variants of splitting the affected spectrum for the duration of the event. Some national regimes make such sharing a default rule among their licensees; internationally it remains a matter for good-faith agreement, which makes early operational-coordination arrangements with the handful of constellations you will constantly intersect a first-class asset rather than an afterthought.
Step 6 — When agreement cannot be reached
Some counterparties will be unreasonable, absent or hostile, and the Regulations anticipate this without solving it. Understand the endgame options before you need them.
You may, after demonstrating sustained good-faith efforts, request that your assignments be recorded despite the incomplete coordination — the Regulations allow notification where the required agreement could not be obtained, with the assignment recorded on the basis that you must not cause harmful interference to, and cannot claim protection from, the specific networks concerned. Operating “at risk” in this way is common and often commercially rational — particularly against paper networks — but it is a calculated exposure: if the counterparty’s system materialises and interference arises, you carry the obligation to resolve it. The Radiocommunication Board exists as a further recourse for procedural disputes, and administrations can escalate diplomatically; what does not exist is compulsory arbitration with binding technical outcomes. The regime’s honest description is negotiated coexistence backed by mutual deterrence — your future filings will meet their comments, and theirs yours — which is precisely why reputation is a balance-sheet item in this field.
Ongoing: coordination never ends
The campaign that precedes launch is only the acute phase. Every subsequent BR IFIC can bring new filings behind you — where you now hold the senior position and others must seek your agreement; guard that seniority with the same four-month discipline you once feared in others. Fleet changes, replacement satellites and modified parameters reopen coordination questions. And the agreements themselves require management: a register of every commitment, its triggers and its counterparty contacts, owned by a named person, is the difference between institutional memory and rediscovering your own constraints during an interference event.
Timeline, budget and the five mistakes
Expect a serious GSO coordination campaign to run one to three years against real counterparties, and NGSO campaigns to be continuous; budget for specialist engineering tools or consultancy, for travel to the industry’s meeting cycle, and for legal review of agreement drafting. The recurring failures, one last time: treating the identified list as homogeneous instead of triaging paper from steel; missing four-month windows on other people’s filings while perfecting your own; arriving at meetings with positions instead of analysis; conceding operational freedom to networks that were never going to fly; and leaving agreements half-documented — the cheapest possible way to purchase a dispute with a counterparty who will outlast your job, your financing round, and quite possibly your satellite.