What Is the ITU BR IFIC, and Why Every Satellite Operator Should Track It
If you work anywhere near satellite frequency coordination, you've run into the acronym "BR IFIC." It sounds bureaucratic because it is โ but understanding what's actually inside it is one of the most useful things a spectrum engineer can do before filing a new network.
What BR IFIC stands for
BR IFIC is short for the Bureau's International Frequency Information Circular, published by the Radiocommunication Bureau (BR) of the ITU โ the United Nations agency that manages the international radio-frequency spectrum and satellite orbital slots. Every satellite network filing submitted to the ITU, from the earliest advance publication to a final notification, eventually shows up in this circular. It's the public record of "who has told the ITU they intend to use which frequencies, where."
Why it's published, in plain terms
The ITU's whole coordination system runs on a simple idea: before you can claim protected use of a frequency band and orbital position, everyone else who might be affected needs a chance to know about it and raise concerns. The BR IFIC is how that notice happens. Once a filing appears in it, the clock effectively starts on coordination timelines, comment periods, and โ for many notification types โ the operator's claim of priority in the international registry.
For an operator, this cuts two ways:
- Your own filing needs to appear correctly and on time, because your priority date and coordination obligations flow from it.
- Everyone else's filings are potential interference sources โ or potential parties you'll need to coordinate with โ the moment they're published.
How often it's published
The BR IFIC has historically been published on a weekly basis, though the Bureau's exact cadence and the split between different notification types (API, CR/C, notification, etc.) can shift over time โ it's worth checking the ITU's own publication schedule for the current arrangement rather than assuming a fixed weekly date. What matters operationally is that it's frequent: a network that could conflict with yours can appear with very little warning.
What's actually inside a BR IFIC filing
Each entry is a structured technical record โ administration, satellite name, orbital position (for GSO) or orbital parameters (for NGSO), frequency bands and bandwidths per beam, polarization, EIRP, antenna gain, and a handful of other RF and orbital parameters, all captured in a standardized database format (the "SNS" format used by the ITU's own SpaceCap software). It's precise, but it's also dense โ a single satellite filing can span dozens of frequency assignments across multiple beams, spread across several administrative notice types.
The practical problem this creates
Manually scanning new BR IFIC entries against your own network's frequency plan โ every time a new circular is published โ is exactly the kind of repetitive, detail-heavy task that's easy to get wrong under time pressure. Missing an overlapping filing doesn't just cost you an afternoon of double-checking; it can mean walking into a coordination discussion unprepared, or missing a comment window entirely.
This is the specific problem a first-pass interference screening tool is built to solve: instead of reading through raw filings by hand, you compare your satellite's frequency plan against the full BR IFIC history (and every new publication going forward) automatically, and get back only the entries that actually overlap in frequency.
Screen your filing against the full BR IFIC history
SatCoo checks a satellite's frequency plan against 10 years of BR IFIC publications โ and keeps checking automatically as new circulars come out โ so you see potential interferers without reading through raw filings by hand.
Run a free screening โ