An Incident Has Occurred. What Should You Do?
Updated: Oct 23
When people ask about export control incidents, they often assume the difficult part is deciding whether something has gone wrong.
Usually it isn't.

Most of the time, somebody already knows something isn't quite right. The difficult part is deciding what to do next.
You've found a shipment that may have moved without the right licence. A customer has suddenly changed the delivery route. Screening has produced a result that nobody can properly explain. A file has appeared somewhere it shouldn't.
Now what?
That's the question that matters. Not next week. Not after a committee meeting. Not after three rounds of emails.
Now.
Start With Facts, Not Opinions
The first thing I learned about incidents is that they have a habit of collecting rumours. Within a few hours, you'll usually have three explanations, four assumptions, and a growing number of people confidently discussing things they don't actually know.
Ignore all of that and work out what happened.
What do you know for certain?
What was shipped?
To whom?
When?
Who approved it?
What records exist?
What evidence supports the concern?
Until you know those things, you're not managing an incident. You're managing speculation.
You don't need every answer immediately, but you do need enough information to understand whether you're looking at a genuine compliance issue or simply a misunderstanding.
Some Problems Need Reporting
Occasionally the facts are clear. A controlled item has been exported without the required authorisation or a licence condition has been breached.
Something has happened that regulators would reasonably expect to know about.
At that point, the discussion changes. The question is no longer whether there is a problem. The question becomes how the organisation deals with it. This is where compliance, legal, and export control specialists need to become involved quickly. Not because they can make the problem disappear, but because they can make sure the organisation responds properly.
One thing worth remembering is that what normally causes damage is not the original mistake, but poor decisions made afterwards.
Some Problems Need Escalation
Not every concern requires external reporting. Some require immediate attention.
A possible diversion concern would fall into that category.
So would credible sanctions concerns, suspicious customer behaviour, unexpected changes to an end-user, or information that suggests goods may not be going where everyone thought they were going.
In situations like these, don't waste time trying to solve everything yourself. Raise it.
Get the right people involved.
Let those responsible for compliance, security, risk, or legal matters look at the evidence and decide how serious the concern really is. I've seen people spend days trying to prove they were right before speaking to anybody. That's usually a mistake.
If something genuinely worries you, say so.
Some Problems Need Fixing Rather Than Reporting
Not every incident ends with a disclosure or a major investigation. Sometimes a weakness is discovered before any shipment leaves the building.
Someone spots a classification error.
A screening step is missed but caught during a review.
A process fails, but the failure is found before it causes any real damage.
Those situations still matter. A control failed for a reason. The sensible response is to understand why, fix it, and make sure the same thing does not happen again next month.
There is little value in treating every internal mistake as a crisis, and there is even less value in pretending it never happened.
If You're Not Sure, Ask
This sounds obvious, but it is surprising how often people avoid it. Many compliance professionals, particularly early in their careers, think they are supposed to know the answer.
They aren't. Nobody knows everything.
Export controls overlap with sanctions, customs, contracts, logistics, engineering, government policy, internal procedures, and a hundred other things. Every experienced practitioner has encountered situations where the answer wasn't immediately obvious.
When that happens, ask.
Ask your Export Control Officer.
Ask your compliance manager.
Ask legal counsel.
Ask somebody with more experience than you.
Five minutes of conversation can save five days of unnecessary activity.
Sometimes the Incident Isn't the Real Problem
Every so often an incident exposes something larger. You investigate one shipment and discover nobody has reviewed licence conditions consistently for years.
You examine one screening failure and find the process depends on a single individual remembering to complete a manual step.
You look into one customer query and realise training hasn't been updated since the regulations changed.
That's when the conversation moves beyond the incident itself. The shipment, document, or transaction may simply have been the thing that exposed a weakness that was already there.
Those discoveries are often uncomfortable, but they're also useful. Problems are always easier to deal with when you've found them yourself rather than having somebody else find them for you.
So What Is the Right Response?
People often hope there is a simple answer. There isn't.
The right response depends on the facts.
Sometimes you report.
Sometimes you escalate.
Sometimes you investigate.
Sometimes you fix a process and move on.
Sometimes you do all four.
The important thing is not to freeze because you're worried about making the wrong decision. Gather the facts. Involve the right people. Use the experience available to you. Then take the next sensible step.
Most incidents are not defined by what went wrong. They are defined by what happened after somebody noticed.





Comments