CONDO is a set of enabling functions, processes, requirements and assurance checks in support of an effect for which Defence has deemed it appropriate to contract. The nature of the effect contracted for and the supporting elements of contract management are beyond the scope of this standard. CONDO is focussed upon the enablement and appropriate generation of a Deployed capability to meet a specified task.

CONDO policy applies globally to all Contractors, including all Subcontractors in support of the MOD on Operations outside of the UK in an Operational Area (OA) or an area or PJOB designated by PJHQ. In line with current commercial policy, DEFCON 697 will be applied to all contractors who Deploy into an OA or an area or PJOB designated by the PJHQ. It should be noted that it may not be appropriate or possible to impose the full requirements of DEFCON 697 on suppliers indigenous to an OA or an area or PJOB designated by PJHQ. In such circumstances narrative clauses governing indigenous contractors and their employees should be drafted in conjunction with commercial and legal advice and agreed with the Contractor.

CONDO Deployments may be pre-planned to meet both routine and surge requirements or may be ad-hoc responses to UORs. UK Nationals (UKN) or Third Country Nationals (TCNs) may Deploy, from the UK or from an alternative location. Additionally, there may be other Contractors and Subcontractors who Deploy direct from within the region. In principle, the processes outlined in this 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 Requirement Sponsor has a Surge or UOR these should in the first instance be discussed with the PJHQ for Joint Operations and the relevant Commands for Single Service Operations in order that the appropriate priority may be afforded to the Deployment.

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 standard, the term 'Deploy' is used for all CONDO Personnel delivering contracted effects and includes the term ‘operate' which may be used by the MOD to refer to those CONDO personnel who are already located within a country to which MOD assets are Deployed. 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 requirements consistent with JSP 567:

a. ACDS (Log Ops), Head of Defence Logistics Policy (Hd Def Log Pol) has responsibility for CONDO policy, its future development and the linkage of CONDO policy to the development of the Whole Force Concept (WSF). The lead desk for CONDO policy development is 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 Commands. Where appropriate, this responsibility may be delegated to logistic staffs within the Joint Force Logistic Component (JFLogC) or the National Component Headquarters.

c. The DSCOM CONDO Mounting Cell (CMC) has the responsibility for developing internal CONDO operating processes and procedures for Joint Operations on behalf of PJHQ and in support of Commands in employing their internal CONDO operating processes and procedures for single Service Deployments. The DSCOM CMC is responsible for the administration of all CONDO applications on behalf of the PJHQ and Commands (Cmds) and the archiving of all pertinent data. It will hold the most recent set of Operational Specific Information (OSI) produced and maintained by PJHQ for Joint Operations and Cmds for single Service Operations.