National Inter-Agency
Coordination at the
Strategic Level

Duration: 1 minute — opening

Good morning. Thank you for the invitation. It is a privilege to address such a distinguished audience — the breadth of the Philippine maritime security community in one room.

The agenda has been adjusted, and we now have two complementary sessions before lunch instead of one. This first session — sixty minutes — is the strategic level. We will look at the national decision-making process: the political and governance machinery that lets a whole-of-government response actually function when a large-scale maritime crisis hits.

After the coffee break, in the second session, we will move down to the operational level: how the agencies in this room then translate that strategic frame into joint operations on the water.

This is not an academic lecture. These are practical observations from European inter-agency coordination — what works, what doesn't, and what we wish we had known earlier. I will be drawing on recurrent observations from European maritime programmes, which I think will resonate with much of what you face here.

Let's start with the question that frames everything: why is strategic-level coordination at sea so difficult, and what does it actually take to make whole-of-government work?

Duration: 4–5 minutes

Let me start with what defines a large-scale maritime crisis — because the word matters. A grounded fishing boat, a routine fisheries inspection, a normal SAR — these are not strategic problems. They are managed at the operational and tactical level by the agency on watch.

What we are talking about today is the kind of event that has five dimensions at once. A hijacked tanker carrying CBRN cargo. A cyberattack disabling vessel-traffic systems in a major port. A maritime terrorist attack on critical infrastructure. A mass-rescue event in disputed waters with foreign nationals on board.

Look at the right side of this slide. Every one of these incidents simultaneously triggers a military response, a law-enforcement investigation, a safety operation, a diplomatic demarche, and an economic impact. They are not sequential — they are concurrent.

This is the structural reason why no single agency can own the response. The Navy can deal with dimension 1. Coast Guard with dimensions 2 and 3. DFA with dimension 4. The economic ministries and port authority with dimension 5. Each agency holds a piece. Nobody holds all of them.

So the strategic question of this session is not whether you should coordinate — that's self-evident. The strategic question is: who decides how, and on whose authority? Because in the middle of a fast-moving crisis, the time to debate jurisdiction is exactly the time you do not have.

That decision-making architecture — the national one — is what we will spend the next hour examining.

Duration: 5–6 minutes

If you allow me to be direct: in every maritime nation I have worked with — in Europe, in Africa, in the Indo-Pacific — strategic-level coordination fails in the same five ways.

And the most important point I want you to take from this slide is this: the obstacles are not technical. They are organisational, cultural and political. We will look at technology later, but if you only fix technology you will get nothing.

One — information silos. Every administration eventually builds its own fusion centre. Each one watches the same waters, produces parallel reports, and nobody assembles the complete picture. This pattern is widely documented across European maritime administrations — each ministry tends to develop its own fusion cells.

Two — information as power. This is the cultural barrier — and it is the hardest. In many administrations, sensitive information is treated as a source of internal influence. To share it feels like giving up an advantage. Agencies end up competing rather than cooperating, even when they serve the same national interest.

Three — unclear mandates. Overlapping legal authorities. Who has the lead in territorial waters versus the EEZ? Who handles a vessel that is simultaneously a customs case and a counter-terrorism case? When that is not pre-decided, every crisis begins with a jurisdiction debate — and you waste the first hour you don't have.

Four — paper versus practice. The organisational chart looks fine. There are MoUs. There is a doctrine. But in practice coordination depends on whether two specific officers happen to know each other. One rotates — it collapses.

Five — political will that fades. After a crisis, a reform is announced at the highest level. Three years later it has quietly drifted because no minister is asking about it. Without a sustained, visible top-level mandate, coordination decays back to silos.

Does any of this sound familiar? I suspect much of it does. These failures are universal. The good news is that the remedies are also universal — and that is what the rest of this session is about.

Duration: 5–6 minutes

If you take only one idea from this session, take this one: trust is infrastructure.

It is not soft. It is not a question of personal goodwill. It is the load-bearing layer of everything else — and it has to be built deliberately, the way you build a road or a port.

Look at the pyramid on the right. Read it from the bottom up.

Layer I — political will. A clear, top-level interministerial mandate. In France, that is the SG Mer — the Secretariat General for the Sea, attached directly to the Prime Minister. Whatever you call the equivalent here, it must exist, and it must be held by someone with the political weight to compel ministries to cooperate. Without that, nothing above it stands.

Layer II — a common classification framework. A “sensitive-but-shareable” tier — the equivalent of the Anglo-Saxon Law Enforcement Sensitive marking. This is the practical mechanism that lets information actually move. Without it, every agency hides behind classification walls and you get nothing.

Layer III — liaison officers and joint strategic meetings. Permanent embedded officers across agencies. People whose job description is to bridge two organisations. Plus regular interministerial meetings at the strategic level — not crisis-driven, scheduled.

Layer IV — integrated processes. Each agency's information-handling cycle has the joint coordination cell inside it, not appended to the outside. This is what makes coordination survive personnel rotation.

And only then — Layer V — you get the outcome. Shared maritime awareness. The reason you set up the whole thing.

Most countries try to start at Layer III or IV — build the cells, name the liaison officers — and skip the political layer. That always fails. The pyramid only stands on its base.

Now — what does that political base actually look like?

Duration: 6–7 minutes

“Whole-of-government” is one of the most over-used phrases in security policy. So before we go further, let me give you a working definition that I have seen actually deliver results.

Whole-of-government rests on three concrete commitments. If any one of them is missing, the other two will not save you.

First — a named interministerial body that sits above the line agencies, not next to them. In France, that is the SG Mer, the Secretariat General for the Sea, attached to the Prime Minister. In the UK, the National Maritime Information Centre architecture sits under Cabinet Office. In your context, the National Maritime Council can play exactly this role — but only if it is genuinely above the agencies, with a chair whose authority none of them can simply override.

Why must it be above? Because a peer cannot arbitrate between peers. If your interministerial chair is the head of one of the agencies, that agency will always be suspected of using the chair to push its own agenda. And it will be right to be suspected, because that is human.

Second — a pre-decided lead agency matrix. A document, signed at the highest level, that fixes for every scenario type and every maritime zone: which agency leads, which support, which is informed. CBRN at sea — who leads? Cyber attack on a vessel — who leads? Mass-rescue with foreign nationals on board — who leads?

This sounds bureaucratic. It is, in fact, the single most important crisis-readiness asset a country can have. Because in the middle of an event, you do not have an hour to negotiate jurisdiction. You are looking up the matrix, executing the playbook, and arguing about it later in the post-mortem.

Third — a doctrine that is refreshed, not engraved. A recurring finding across European reviews: the legal frame for many maritime coordination cells still dates back to the early 2000s. Twenty-plus years ago. The threats have changed completely — cyber, drones, hybrid maritime warfare — but the doctrine has barely moved. So a formal review every two or three years, signed at the top, that re-tests the scenarios and updates the matrix.

Three commitments. If your country can honestly point to all three, you have whole-of-government. If you can only point to one or two, what you have is an aspiration.

Duration: 6–7 minutes

This is the architectural slide. Read it as a blueprint, not as a chart.

At the top — strategic level — one national maritime authority. Single chair, single signature on directives. In France: the SG Mer. In your context: whatever body you choose to anchor at the level of the President or the National Security Council.

Below it — operational level — a single national operational coordination centre. Not a committee. A standing centre, staffed permanently, that drives the inter-agency network. We will spend the second session on what this centre actually does.

Below that — local cells in each maritime region. Per facade, per zone. They feed incidents up; they receive direction back down.

Now — the five principles on the right.

Principle A. A single authority. The temptation is always to make this a committee of agency heads — everyone has a vote, everyone is happy. It does not work. A peer cannot arbitrate between peers. You need someone whose mandate is to coordinate, not to defend an agency's interests.

Principle B — and this is the one most often missed. Bidirectional flow. European reviews consistently find this: the link between the strategic level and the cells works far better bottom-up than top-down — incidents are reported upward, but few clear directives, priorities or intelligence cues come back down. Result: cells improvise, work styles diverge, and the strategic level never closes the loop.

Principle C. The operational centre must animate the network. It must drive thematic meetings, set priorities, push intelligence outward to the cells. If it just forwards reports upward to ministers, it is a mailbox — and a mailbox is not coordination.

Principle D. Generic coordination does not exist. CBRN at sea has its own pattern. Cyber on a vessel has its own pattern. Trafficking has its own. Set up thematic working groups — standing, with a permanent secretary — for each priority threat.

Principle E. Measured. Evaluated. Renewed. Clear KPIs at strategic level — not output metrics like “number of meetings held”, but outcome metrics: time-to-decision, fraction of incidents handled inter-agency, lessons captured per exercise. And an honest annual debrief, signed by the political authority — not by the agencies grading themselves.

Duration: 5–6 minutes

I want to land one very practical strategic decision. Inside the architecture we just looked at, there must be one document — one signed instruction at the highest national level — that says four specific things.

One: objectives. The platform exists to deliver shared awareness. Not intelligence production. This distinction is critical and we will return to it. The moment a coordination platform starts producing its own intelligence, the civilian agencies pull back, the police pull back, and the platform dies.

Two: scope. The instruction must list what kinds of information move through the platform — and it must explicitly invite over-sharing rather than under-sharing. The default assumption in most administrations is “don't share unless required”. The strategic instruction must flip that default to “share unless prohibited”.

Three: operating rules. Standardised inter-agency procedures. And critically — this is the box on the right — a specific maritime classification tier.

Most national classification frameworks have only two functional levels for sensitive material: classified — which is hard to share — and unclassified — which is fine to share but contains nothing useful. That gap is fatal. You need a middle tier: sensitive-but-shareable, with clear handling rules and an audit trail.

The Anglo-Saxon Law Enforcement Sensitive marking is a pragmatic model widely cited in European debates. It is sharable across cooperating agencies, including industry partners under NDA, with reversible access and logging.

Without that middle tier, your beautiful coordination platform is empty. With it, information actually moves.

Four: priorities by maritime zone. Trafficking patterns differ between Sulu Sea and the Luzon Strait. Critical-infrastructure protection in Manila Bay is a different problem from environmental risk in Palawan. The instruction should fix priorities and escalation thresholds per facade, not generically.

One signed national instruction. Four sections. Updated every two or three years. That is what makes the architecture above it executable.

Duration: 5 minutes

One last strategic dimension before I show you the pitfalls. Whole-of-government is necessary, but it is not sufficient.

Here is an inconvenient fact that any honest assessment surfaces: most maritime data is not owned by you. It is owned by private actors. Vessel positions are reported by shipowners. Cargo manifests come from agents. Port operations data is held by terminal operators. Cyber telemetry on vessels is collected by maritime service providers. AIS feeds at scale are commercial. Even local human intelligence — weak signals about something off-pattern — lives with the local fishers and the community.

If your inter-agency platform sits inside the government walls and never speaks to industry, you are missing most of the picture.

European practice points to a clear architectural answer: a single national maritime liaison centre that the industry can talk to — the MICA Centre in Brest is one well-known example. The principle: industry will not maintain twenty bilateral channels with twenty agencies. They need one door.

That single point of access works only if it is built on three guarantees:

One: Pre-signed NDAs and data-sharing protocols. Industry will not improvise legal terms during a crisis.

Two: Strict confidentiality of the data they share — in writing, with consequences if breached. Otherwise commercially sensitive information will not flow.

Three: two-way value. If industry only ever receives demands and never receives anything back — warnings, threat assessments, coordinated alerts — the relationship dies. The exchange must be commercially worthwhile to the partner.

Strategically, the recommendation is straightforward: designate one centre as the official industry-facing maritime hub, sign the protocols, and build the relationship deliberately. Don't wait for a crisis to introduce yourselves.

Duration: 4–5 minutes

I want to give you the warning slide. These are the six pitfalls repeatedly observed across European inter-agency programmes. Each one will sound deceptively simple. None of them is.

One — duplicating information centres. The most common reform path: minister announces a new fusion cell. Six months later, every other agency announces theirs. You end up with five centres watching the same waters with five slightly different versions of the truth. The strategic question is not how many cells. It is how many versions of the truth — and the answer must be one.

Two — confusing coordination with intelligence. This is the most subtle and the most dangerous. The moment a coordination hub starts producing its own classified intelligence assessments, two things happen: the police and customs view it as competing with their own intel chains, and they pull back. And the civilian partners — industry, port authorities — see it as an intelligence service and refuse to talk to it. The hub must coordinate. It must not produce intelligence. European practice is unambiguous on this: a coordination cell is not, and must never become, an intelligence body.

Three — no common procedures. Each cell improvises. The crisis arrives at 3 AM, the duty officer has no playbook, and decisions are made by whoever happens to answer the phone first.

Four — personal-relationship dependency. Coordination works because Captain X and Colonel Y trust each other. Captain X retires. The relationship dies overnight. Coordination must outlive any individual.

Five — information flows only upward. The most-reported pitfall across European reviews. Cells report incidents up to the strategic level — but nothing comes back. No directives, no priorities, no inter-cell sharing. The strategic level becomes a black hole. We saw this in the architecture slide.

Six — no shared classification. We discussed this. Without a sensitive-but-shareable tier, the platform is decorative.

If your national reform avoids these six, you are already ahead of most countries I have worked with.

Duration: 4 minutes — close + bridge

Let me close this first session with the five things the strategic level cannot delegate. None of these can be solved by the agencies on their own. They must be owned at political level — or they will not happen.

One. Designate a single empowered authority. If your national maritime governance is a committee of agency heads voting by consensus, you do not have whole-of-government — you have whole-of-meeting. The chair must sit above the agencies.

Two. Sign one national doctrine instruction. Mission, scope, classification, lead-agency matrix. One document. Signed at the top. Many national maritime frameworks across Europe still date from the early 2000s and are overdue for renewal — this is a recurrent failure pattern. Build the document, sign it, and put a renewal date on it.

Three. Build trust as infrastructure, from the top. Trust is not a training programme. It is a political signal: the highest authority shows, repeatedly and visibly, that this matters. Plus the mechanisms — classification tier, liaison officers, joint meetings — that survive personnel rotation.

Four. Guarantee bidirectional flow. Information must come back down. If the strategic level only receives reports and never sends back guidance, priorities or intelligence, the cells stop reporting. Close the loop, deliberately and on a schedule.

Five. Open one door to the maritime industry. Whole-of-society starts with a single point of access for shipowners, ports and operators. With NDAs, two-way value, and confidentiality in writing.

Five strategic decisions. None of them technical. All of them indispensable.

The bridge. After the coffee break, we move from the strategic frame to the operational reality. The architecture we just built is necessary — but the agencies in this room then have to make it work day by day. How does the strategic frame translate into joint operations on the water? That is the question for Session 1B.

Thank you. I will take any quick questions on the strategic level now — we will go deeper into the operational mechanics after the break.