PR for a Defense Company: Where Publicity Meets Export Control

A company preparing an export filing is already used to identifying its product against the definitions in Law 549-IV “On State Control over International Transfers of Goods of Military Purpose and Dual-Use.” The same definitions apply to public content — a press release, a case study, a webinar, a LinkedIn post — because the law doesn’t distinguish by format. What matters is the content, not the container.

The practical consequence for a team preparing outward-facing communication: “can we publish this” is the same question a company already asks itself during product identification for state export control — the same statutory categories, just applied to a piece of text instead of a piece of hardware, ahead of the same registration and permit process a producer already runs before it can transfer anything across a border.

In practice, a team preparing communication works with four categories of information. The first two are usually safe to publish without a separate sign-off; the second two aren’t, because they overlap the definitions above.

Content built on the first two categories can almost always ship without delay. Content that touches the third or fourth needs the same check as the paperwork for registering as a subject of international transfers — and, as the procedure itself shows, that check is faster when it runs before publication, not after a question from a journalist or a partner.

The discipline that protects a company from over-disclosure in the export sense protects it in another spot too — when public material gets checked against what a company shows during due diligence. The six domains an investor scores a company against are laid out in the due-diligence checklist: if a page names a parameter, a volume or a partner that isn’t in the company’s internal documents, or the reverse, that’s a discrepancy a reviewer flags as its own line item, not something that gets waved through.

It works the other way too: a company that can’t be verified against any outside source reads as more risk to an investor or buyer, not less. It’s the same underlying skepticism behind one of the five objections foreign capital raises about Ukrainian defense-tech. So the question a team actually has to answer is which information a given piece carries, and that is settled draft by draft rather than by a standing policy on whether to speak publicly at all.

1. 1Check the technical description against the definition of technical datain Article 1. If the draft carries a parameter, a drawing or a code fragment, that’s a subject of identification, not a line for marketing.
2. 2Write in classes, not numbers — task type, product category, target market, without exact thresholds for range, power or mass.
3. 3Check whether the draft narrows the field to an identifiable case — a specific unit, a delivery location, a date — even when no name is used directly.
4. 4Send the draft to whoever runs product identification for export control, not only to the person responsible for marketing.
5. 5Keep a log of what’s already public, so the next piece doesn’t disclose a detail the previous one deliberately left out.