Security at a diplomatic mission requires careful coordination of visitors, confidentiality, staffing and communication with public authorities. An embassy building, a consular service area and a diplomatic residence do not necessarily operate in the same way. Specify the service according to each location's legal status and daily activities.
Inviolability does not mean foreign territory
Article 22 of the 1961 Vienna Convention on Diplomatic Relations establishes the inviolability of mission premises and the receiving state's special duty to protect them. This does not turn an embassy into the sovereign territory of the sending state. Consular premises require separate consideration under Article 31 of the 1963 Vienna Convention on Consular Relations; the regimes are not identical in every detail.
A private security contract does not replace these state obligations. Nor does diplomatic status automatically expand an officer's powers. Verify permissions, duty boundaries and mission-approved instructions within the applicable legal framework. Identify who will decide unclear matters before the service starts.
Connect visitor processing to the mission's decision structure
Appointment holders, staff, maintenance contractors and official visitors may require different admission processes. Officers should know whose approval they need, where to direct people and when to contact a mission representative. Checking an appointment is not deciding the substance of a consular application.
Consider waiting areas, accessibility and information during busy periods. Define language requirements for each role rather than assuming every officer is multilingual or a diplomatic protocol specialist. Ask how these requirements will be maintained when staff change.
Respect special arrangements for deliveries
Ordinary parcels and diplomatic consignments should not share an indiscriminate processing routine. The conventions also treat diplomatic and consular bags under distinct provisions. Where a consignment's status is unclear, officers should refer it to an authorised mission representative rather than act independently. A generic search or opening procedure would be inappropriate.
For technical visits, the plan can identify the work order, authorised host, accessible areas and departure record. Specialist screening, dog teams or technical inspections should not be assumed to exist or to be required at every mission. Verify the need, suitability and actual competence of the proposed provider separately.
Apply confidentiality to everyday information sharing
Limit access to visitor information, programmes, shifts and recordings according to duty requirements. Define authorised sharing within the mission, with the provider and with public authorities. Publishing photographs or naming a mission as a reference is not an automatic component of the service.
Incident reports should distinguish observations from assumptions. They should not suggest that officers produce intelligence or can identify every threat in advance. Sample tender documents must also avoid exposing another mission's identity or protective arrangements.
Verify emergency communication and service handover
Agree duties compatible with the mission's emergency plan, a current contact list and responsibility for liaison with authorities. Exercises should follow authorised arrangements; do not assume staff independently undertake tactical or medical interventions. Response or travel times require validation against real project conditions.
During procurement, request the processes for shift handover, instruction changes, record transfer and removal of access rights. This brings diplomatic courtesy, legal limits and daily operations into one understandable service specification.
