scope:

CONDO policy applies to all Contractors including all Subcontractors and their personnel who are deployed outside the British Isles to provide commercial services to deployed operations and exercises under a range of discrete contracts. CONDO deployments may be pre-planned to meet both routine and surge requirements or may be ad-hoc responses to urgent operational requirements (UORs). UK or Third Country Nationals (TCNs) may deploy into the OA, from the UK or from an alternative location; additionally there may be other contractors/subcontractors who deploy direct from within the OA. In principle, the processes outlined in this Defence Standard will be used for all types of deployments irrespective of whether CONDO Personnel deploy from the UK or abroad. This will also include Surge and UOR deployments. In the event that a Contract Sponsor (CS) has a Surge or UOR requirement these should in the first instance be discussed with the Permanent Joint Head Quarters (PJHQ) for Joint Operations and the Front Line Commands (FLC) for Single Service Operations in order that the appropriate priority may be afforded to the deployment. Where exceptional operational circumstances require changes to normal processes these exceptions will be agreed by the MOD and Contractor on a case by case basis.

There may on occasion be no need to relocate geographically CONDO Personnel in order to deploy resources for a CONDO task or contract. Therefore, whenever referenced in this Defence Standard, the term 'deploy' is used for all CONDO Personnel within the OA, and includes the term 'operate' which may be used by the MOD to refer to those CONDO Personnel who are already located within an OA. Whichever is the case, the relevant approvals processes apply and must be completed in accordance with this Standard.

The following MOD staffs have responsibilities for CONDO policy, processes and procedures consistent with JSP 567.

a) ACDS (Log Ops), Director of Defence Logistics Policy (D Def Log Pol) has responsibility for CONDO Policy and its future development. The lead desk for CONDO Policy development is D Def Log Pol SO1 Force Policy.

b) PJHQ, Assistant Chief of Staff (ACOS) J1/J4 Personnel and Logistics has responsibility for developing internal CONDO joint operating processes and procedures in consultation with ACDS (Log Ops) and the FLCs. Where appropriate, this responsibility may be delegated to logistics staffs within the Joint Force Logistic Component (JFLogC) or the National Component Headquarters.

c) FLCs have responsibility for developing internal CONDO operating processes and procedures for single service deployments in consultation with the PJHQ and the CONDO Mounting Cell (CMC).

d) The CMC is responsible for the administration of all CONDO applications on behalf of the PJHQ and FLCs and the archiving of all pertinent data. It will hold the most recent set of Operation Specific Information (OSI) produced and maintained by the PJHQ for Joint Operations and FLCs for Single Service Operations.

e) The Contract Sponsor (CS) is responsible for the CONDO deployment and operational interface between the contractor and the MOD. All applications for deployment are to be staffed by the CS in the first instance and then through the CMC for approval by the PJHQ or FLC as appropriate. The CS will appoint an In Theatre Sponsor (ITS) for all CONDO deployments. The ITS will provide the deployed CONDO interface between the MOD and contractors for the C

A diagram illustrating the CONDO contract execution process can be found in the Guideline For Industry (GFI) associated with DEFCON 697.