Every export authorization this business holds, laid out as a board of hex tiles — one tile per destination country. The colour of a tile is the state of that country's licenses, the chip in the middle counts the live authorizations, and clicking a tile opens the detail: what each line covers, who the end-user is, how much of the authorized value is drawn down, when it lapses, and which conditions ride on it. Under that sits the EAR layer: each line's pathway (BIS license, License Exception, no license required, or ITAR), the reasons for control and Commerce Country Chart columns behind it, and a check of whether the pathway on file matches what the regulations ask for. The calendar under the board turns all of that into a work queue.
portfolio as of — · EAR reference as of — · screen a new item →
tile state — click to filter
pathway — click to filter
region
The chip on a tile counts the authorizations that can actually carry a shipment today. The pips under the number show how far the most drawn-down of those licenses has run: one pip is barely touched, five is nearly exhausted. A tile with no live authorization carries a marker instead — a circled arrow for an application still out, a dash for nothing on file, and a cross for a restricted destination. An amber dot in the corner means a condition falls due soon, and a red one means a condition is already overdue. The three harbours mark the AUKUS partners, where much defence trade moves under the §126.7 exemption rather than a license. Pathway colours are used in the matrix and the list: green for a BIS license, blue for a License Exception, sand for a no-license-required record and gold for an ITAR authorization.
ear-controls.json; it does not see end-user lists, end-use facts, 'is informed'
letters or the fine print of an ECCN, all of which can change the answer. Dates are measured
against the portfolio date above rather than today's date, so the demo stays readable over
time. Screening an item for classification is a separate step — see the
Export License Screener, which reads this same file to tell
you whether what you are screening is already covered. Edit export-licenses.json
to change the board and ear-controls.json to change the reference layer.