The Conversion Deficit
Role
Diagnoses where institutional value is lost between signal and outcome.
Digital diplomacy is usually encountered through what can be seen: ministry and mission websites, public statements, campaigns, social channels, leadership communication, public-diplomacy activity, consular information, media engagement, and visible use of digital or AI-supported tools.
The public sees the output. Institutional performance depends on the system beneath it.
Read the iceberg
The iceberg is not an organisational chart. The functions may sit across existing units, mission networks, national services, regional hubs, and external partnerships. The visual shows that visible activity depends on capabilities that are often difficult to observe from outside.
A ministry can have strong public channels and weak out-of-hours authority. It can have an advanced AI strategy and no tested fallback when the provider is unavailable. It can have experienced diplomats and no route through which their local interpretation reaches the decision-maker.
Visibility is evidence of activity. Readiness requires evidence of connection.
Role
Diagnoses where institutional value is lost between signal and outcome.
Role
Describes what must exist somewhere in the institutional system.
Role
Explains how the capabilities work together before, during, and after pressure.
The Readiness Assessment, Retained Authority Test, maturity language, implementation models, and Field Kit are applications or modules within this architecture rather than separate conceptual systems.
Foreign-policy intent and institutional authority
A written mandate connecting foreign-policy intent to digital diplomacy activity.
Named ownership, decision rights and escalation paths across headquarters and missions.
Structured skills, professional practice and career pathways for digital and AI-era work.
Embassies and consulates operate as capable nodes, not passive channels.
The institution can turn signals into interpretation, not only reports.
Coherent action under time pressure across HQ, missions and functions.
Technology, data and AI serve institutional judgment under proportionate safeguards.
Experience becomes doctrine, not folklore.
The live eight-domain layered capability architecture: foreign-policy intent and institutional authority enter at the top, four capability layers convert them, and institutional outcomes are read at the base.
Domain 1
Does the ministry have a shared institutional purpose for digital diplomacy, with clear ownership, boundaries, principles, and connection to foreign-policy priorities?
Digital activity can grow through separate initiatives. A communications team develops channels. A cyber unit expands international engagement. A policy team examines AI governance. A mission experiments with public diplomacy. A technology function introduces an analytical tool.
Each initiative may be useful. Without a shared mandate, the institution may remain uncertain about how the activities connect, which outcomes matter, where responsibility sits, and how competing priorities should be resolved.
Mandate defines purpose and responsibility. Doctrine guides behaviour: common principles, operating assumptions, headquarters–mission relationships, evidence expectations, authority, technology boundaries, response principles, and learning requirements.
The document format matters less than whether officials understand how the guidance applies to their work.
Domain 2
Can the ministry recognise meaningful change, preserve evidence, and establish what is known before a signal shapes institutional action?
Signals arrive through missions, contacts, official statements, media, public platforms, consular enquiries, cybersecurity alerts, partner governments, civil society, local communities, monitoring systems, and AI-supported tools.
Capability involves more than observing digital activity. It combines public information with diplomatic relationships, local knowledge, technical evidence, institutional records, and trusted external expertise.
The institution should be able to preserve original material, distinguish independent confirmation from repeated circulation, record uncertainty, and identify when specialist technical or intelligence support is required.
Domain 3
Can the ministry turn evidence into diplomatic meaning and decide what deserves institutional attention?
Verified information still requires interpretation. The ministry must understand why the development matters, which interests and audiences are affected, what local history shapes the reaction, which trajectories are plausible, and what remains uncertain.
Interpretation is distributed. Missions, regional desks, security teams, consular functions, communications, legal advisers, and leadership may see different dimensions. Capability lies in combining those views without removing genuine disagreement.
Prioritisation governs attention. It should distinguish visibility, urgency, consequence, reversibility, citizen or staff impact, political sensitivity, and the risk of response or non-response.
Domain 4
Can the right issue reach the right level of authority in time, with a clear decision request and a reconstructable evidence base?
Authority includes who may decide, who must be consulted, what can be delegated, which actions require senior or political approval, who acts when the normal authority is unavailable, and who may challenge or stop a technology-supported process.
Escalation should connect the issue with the authority, resources, or cross-government reach required for action. It should distinguish awareness, consultation, coordination, clearance, and decision.
The institution needs enough delegation to operate under pressure and enough oversight to protect legitimacy, security, coherence, and accountability.
Domain 5
Can headquarters and missions combine national direction with local knowledge, discretion, and implementation capacity?
Missions possess language, context, relationships, early warning, direct exposure to public and citizen concerns, and knowledge of local operating conditions. Headquarters possesses policy, political authority, cross-network visibility, legal and security support, and common standards.
Capability depends on reliable two-way movement. Missions provide signals, verification, interpretation, relationships, and implementation evidence. Headquarters provides national direction, specialist support, decision authority, wider coordination, and learning across the network.
The domain should preserve local adaptation and constructive disagreement rather than treating alignment as uniformity.
Domain 6
Can the ministry implement a proportionate response, sustain essential functions, adapt as evidence changes, and recover after disruption?
A response may combine public communication, private diplomatic engagement, consular guidance, security measures, platform engagement, technical action, partner coordination, exposure, attribution, operational adjustment, or strategic restraint.
Response begins with purpose: protect citizens, correct a claim, reassure an audience, preserve diplomatic space, prevent escalation, expose manipulation, protect official identity, maintain service delivery, or engage a partner privately.
Continuity asks whether critical work can continue when a person, account, system, provider, or connection becomes unavailable. It includes substitutes, fallback channels, exportable records, local arrangements, and recovery.
Domain 7
Can the ministry benefit from digital and AI-supported systems while preserving identity, evidence, accountability, continuity, exit capacity, and human authority?
AI, data, institutional identity, and vendor dependency converge inside real diplomatic workflows. An assistant may process institutional data through external infrastructure, generate material carrying official identity, influence a briefing, and become embedded in a process partly controlled by a provider.
The ministry should define approved, restricted, and prohibited uses; risk and consequence levels; data boundaries; source and uncertainty requirements; human review; monitoring; accountability; and the authority to challenge or stop use.
Governance should follow the complete use case rather than the tool alone.
Domain 8
Can the ministry convert experience into changed doctrine, skills, workflows, systems, relationships, and future behaviour?
An institution can manage a difficult incident successfully and remain no better prepared for the next one.
Learning begins with an accurate record: chronology, original evidence, assessments, uncertainty, decisions, authority, actions, effects, workarounds, points of friction, and successful adaptations.
The realistic objective is not to capture professional judgment completely. It is to reduce avoidable relearning and repeated failure. A review becomes institutional learning when specific changes are owned, implemented, and tested.
What it examines
What institutional responsibility and foreign-policy outcome does the capability support?
What it examines
Who is accountable, and who acts when the normal owner is unavailable?
What it examines
Which workflows, standards, authority, skills, and tools allow it to function?
What it examines
Can the capability operate across the relevant headquarters, missions, partners, and time zones?
What it examines
What demonstrates use, testing, correction, continuity, and improvement?
A strategy, policy, team, tool, or programme can provide an important foundation. The capability becomes operational when it is understood, owned, resourced, connected to workflows, available across the relevant network, used in practice, reviewed, and improved.
The framework does not require one ministry to copy another. The domains may sit across existing structures. A small state may rely on central services and regional networks. A large ministry may distribute functions across several directorates. The essential requirement is that the responsibility remains visible and governable.
The complete framework can appear demanding, especially for ministries with limited staff and resources. Capability-building can begin with a focused baseline.
This is not full institutional maturity. It is a dependable starting point.
The capability is asserted in strategy, mandate or public commitment, but nothing further is visible.
Does it exist anywhere other than in a statement of intent?
The capability is written into protocols, roles, guidance or budget lines.
Is the capability described in documents that are not yet used?
The capability is applied in routine practice across the relevant units and missions.
Do HQ and missions work from the same operating assumptions in daily practice?
The capability has been exercised under pressure, in a drill or in a real incident.
Has it held when conditions were adversarial rather than planned?
The capability is reviewed after use and changed on the evidence produced.
Is the capability demonstrably stronger after each pressure event?
Stated → Documented → Used → Tested → Improved
Five evidence conditions — Stated, Documented, Used, Tested, Improved — read against the evidence available for each domain. No composite score or public ranking is produced.
The central proposition
The Capability Framework explains what must exist somewhere in the system. It does not decide where every function must sit or assume that a framework can replace people, authority, infrastructure, or professional judgment.
Source IDs follow the Technical and Evidence Annex citation map. Conceptual models developed by Diplomats.Digital are analytical propositions, not externally validated standards.
Cited in this section as S19 in the Technical and Evidence Annex citation map.
Cited in this section as S21 in the Technical and Evidence Annex citation map.
Cited in this section as S22 in the Technical and Evidence Annex citation map.
Cited in this section as S23 in the Technical and Evidence Annex citation map.
Cited in this section as S24 in the Technical and Evidence Annex citation map.
Cited in this section as S25 in the Technical and Evidence Annex citation map.
Cited in this section as S26 in the Technical and Evidence Annex citation map.
Cited in this section as S27 in the Technical and Evidence Annex citation map.
Cited in this section as S28 in the Technical and Evidence Annex citation map.
Cited in this section as S29 in the Technical and Evidence Annex citation map.
Cited in this section as S30 in the Technical and Evidence Annex citation map.
Cited in this section as S35 in the Technical and Evidence Annex citation map.
Cited in this section as S36 in the Technical and Evidence Annex citation map.
Cited in this section as S37 in the Technical and Evidence Annex citation map.
Cited in this section as S38 in the Technical and Evidence Annex citation map.
Source status: Citation records and publication links were checked for Edition 1.0 at publication. Subsequent corrections are recorded through the version history.
Suggested citation
Diplomats.Digital (2026). State of Digital Diplomacy 2026: From Communication to Capability. Edition 1.0. Section: The Digital Diplomacy Capability Framework.