Common use of Information to be shared Clause in Contracts

Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) there is an open breach on HO systems and the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b)where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to safeguarding concerns. provide details of minors who have been categorised as missing children or children from a family group who are (or believed to be) immigration offenders and have an open breach on Home Office systems where the conditions in 15.1 are met. The details supplied will be extracted from HO Casework Information Database (CID) by the HOand will include:  Surname  Middle Name (if known)  Forename  Address  Post Code  Gender (if known)  Date of Birth  Nationality  CID PER ID  Details of offence being committed.  Evidence, concerns and/or reasons that the well-being of the child is in question 15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records. 15.2.3 The DfE will extract the information required for this exchange from records held on the National Pupil database which is managed by Cap Gemini on behalf of DfE under contract as data processors for the DfE. The data will be shared on a monthly basis and the number of records to be shared is in the region of xxx in any given month. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE . Commented ]: DfE Colleagues Volumes and frequency TBC by Home Office 15.2.4 Data willmay also shared on an- ad-hoc basis as set out in section 15.4.4 below Commented ]: DfE Colleagues- do we need to future proof by referencing either that it is currently managed by , or the possibility it could be managed by another body? 15.2.5 The DfE will extract the information required for this exchange from records held on the Census collections which is managed by Cap Gemini on behalfheld by of DfE under contract as data processors for the DfE

Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) there is an open breach on HO systems and the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b)where b) where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to safeguarding concerns. provide details of minors who have been categorised as missing children or children from a family group who are (or believed to be) immigration offenders and have an open breach on Home Office systems where the conditions in 15.1 are metconcerns over their wellbeing. The details supplied will be extracted from the HO Casework Information Database (CID) by the HOand and will include:  • Surname  • Middle Name (if known)  • Forename  • Address  • Post Code  • Gender (if known)  • Date of Birth  Nationality  • CID PER ID  Details of offence being committed.  Evidence, concerns and/or reasons that the well-being of the child is in questionID 15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records. 15.2.3 The DfE will extract the information required for this exchange from records held on the National Pupil database which is managed by Cap Gemini on behalf of DfE under contract as data processors for the DfE. The data will be shared on a monthly basis and the basis. The number of records to be shared is for the checking process will be in the region of xxx 1500 in any given month. In exceptional circumstances (for example where there are concerns over the wellbeing of children) the HO may include up to 50 records that will be identified in this monthly feed to be checked manually with DfE. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE . Commented ]: DfE Colleagues Volumes and frequency TBC by Home Office DfE. 15.2.4 Data willmay may also be shared on an- an ad-hoc basis as set out in section 15.4.4 below Commented ]: DfE Colleagues- do we need to future proof by referencing either that it is currently managed by , or the possibility it could be managed by another body?below. 15.2.5 The DfE will extract the information required for this exchange from records held on the Census collections which is managed held by Cap Gemini on behalfheld by of DfE. 15.2.6 DfE under contract as data processors will return the following pupil/ child and school(s) information (the “DfE Return Information”): • Surname • Forename • Middle name • (If held) Former surname • (If held) Preferred surname ▪ Multiple or sole addresses (for the DfElast 3 to 5 years where held)l ▪ House number/ name, street name and town/ city ▪ Post code ▪ Relevant census collection date for this record • Multiple or sole school information to include for all ▪ School number ▪ School name ▪ School post code ▪ Earliest known pupil date at school ▪ Latest known pupil date at school ▪ Adopted From Care Flag On review, HO and DfE will assess the DfE Return Information and consider any reasonable adjustments to this information.

Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) there is an open breach on HO systems and the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b)where b) where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to safeguarding concerns. provide details of minors who have been categorised as missing children or children from a family group who are (or believed to be) immigration offenders and have an open breach on Home Office systems where the conditions in 15.1 are metconcerns over their wellbeing. The details supplied will be extracted from the HO Casework Information Database (CID) by the HOand and will include:  Surname  Middle Name (if known)  Forename  Address  Post Code  Gender (if known)  Date of Birth  Nationality  CID PER ID  Details of offence being committed.  Evidence, concerns and/or reasons that the well-being of the child is in questionID 15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records. 15.2.3 The DfE will extract the information required for this exchange from records held on the National Pupil database which is managed by Cap Gemini on behalf of DfE under contract as data processors for the DfE. The data will be shared on a monthly basis and the basis. The number of records to be shared is for the checking process will be in the region of xxx 1500 in any given month. In exceptional circumstances (for example where there are concerns over the wellbeing of children) the HO may include up to 50 records that will be identified in this monthly feed to be checked manually with DfE. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE . Commented ]: DfE Colleagues Volumes and frequency TBC by Home Office DfE. 15.2.4 Data willmay may also be shared on an- an ad-hoc basis as set out in section 15.4.4 below Commented ]: DfE Colleagues- do we need to future proof by referencing either that it is currently managed by , or the possibility it could be managed by another body?below. 15.2.5 The DfE will extract the information required for this exchange from records held on the Census collections which is managed held by Cap Gemini on behalfheld by of DfE. 15.2.6 DfE under contract as data processors will return the following pupil/ child and school(s) information (the “DfE Return Information”):  Surname  Forename  Middle name  (If held) Former surname  (If held) Preferred surname  Multiple or sole addresses (for the DfElast 3 to 5 years where held)l  House number/ name, street name and town/ city  Post code  Relevant census collection date for this record  Multiple or sole school information to include for all  School number  School name  School post code  Earliest known pupil date at school  Latest known pupil date at school  Adopted From Care Flag On review, HO and DfE will assess the DfE Return Information and consider any reasonable adjustments to this information.

Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) there is an open breach on HO systems and the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b)where or b) where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to safeguarding concerns. provide details of minors who have been categorised as missing children or children from a family group who are (or believed to be) immigration offenders and have an open breach on Home Office systems where the conditions in 15.1 are metconcerns over their wellbeing. The details supplied will be extracted from the HO Casework Information Database (CID) by the HOand and will include:  • Surname  • Middle Name (if known)  • Forename  • Address  • Post Code  • Gender (if known)  • Date of Birth  • Nationality  • CID PER ID  Details of offence being committed.  Evidence, concerns and/or reasons that the well-being of the child is in questionID 15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records. 15.2.3 The DfE will extract the information required for this exchange from records held on the National Pupil database which is managed by Cap Gemini on behalf of DfE under contract as data processors for the DfE. The data will be shared on a monthly basis and the basis. The number of records to be shared is for the checking process will be in the region of xxx 1500 in any given month. In exceptional circumstances (for example where there are concerns over the wellbeing of children) the HO may include up to 50 records that will be identified in this monthly feed to be checked manually with DfE. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE . Commented ]: DfE Colleagues Volumes and frequency TBC by Home Office DfE. 15.2.4 Data willmay may also be shared on an- an ad-hoc basis as set out in section 15.4.4 below Commented ]: DfE Colleagues- do we need to future proof by referencing either that it is currently managed by , or the possibility it could be managed by another body?below. 15.2.5 The DfE will extract the information required for this exchange from records held on the Census collections which is managed held by Cap Gemini on behalfheld by of DfE. 15.2.6 DfE under contract as data processors will return the following pupil/ child and school(s) information (the “DfE Return Information”): • Surname • Forename • Middle name • (If held) Former surname • (If held) Preferred surname ▪ Multiple or sole addresses (for the DfElast 3 to 5 years where held)l ▪ House number/ name, street name and town/ city ▪ Post code ▪ Relevant census collection date for this record • Multiple or sole school information to include for all ▪ School number ▪ School name ▪ School post code ▪ Earliest known pupil date at school ▪ Latest known pupil date at school ▪ Adopted From Care Flag ▪ (Once collected) Nationality On review, HO and DfE will assess the DfE Return Information and consider any reasonable adjustments to this information.

Information to be shared. 15.2.1 The HO will share with DfE to meet the objectives in 15.1.1 where a) there is an open breach on HO systems and the HO suspects that an immigration offence has been committed under Section 24 or 24A of the Immigration Act 1971 or Section 35 of Asylum and Immigration (Treatment of Claimants) Act or b)where or b) where the child in question is an unaccompanied minor and XX has lost contact with the child giving rise to safeguarding concerns. provide details of minors who have been categorised as missing children or children from a family group who are (or believed to be) immigration offenders and have an open breach on Home Office systems where the conditions in 15.1 are metconcerns over their wellbeing. The details supplied will be extracted from the HO Casework Information Database (CID) by the HOand and will include:  Surname  Middle Name (if known)  Forename  Address  Post Code  Gender (if known)  Date of Birth  Nationality  CID PER ID  Details of offence being committed.  Evidence, concerns and/or reasons that the well-being of the child is in questionID 15.2.2 The DfE will match this information against records and then in response provide the HO with information relating to those individuals that matched DfE records. 15.2.3 The DfE will extract the information required for this exchange from records held on the National Pupil database which is managed by Cap Gemini on behalf of DfE under contract as data processors for the DfE. The data will be shared on a monthly basis and the basis. The number of records to be shared is for the checking process will be in the region of xxx 1500 in any given month. In exceptional circumstances (for example where there are concerns over the wellbeing of children) the HO may include up to 50 records that will be identified in this monthly feed to be checked manually with DfE. Any significant fluctuations in volumes will be notified to DfE in advance and with prior agreement with DfE . Commented ]: DfE Colleagues Volumes and frequency TBC by Home Office DfE. 15.2.4 Data willmay may also be shared on an- an ad-hoc basis as set out in section 15.4.4 below Commented ]: DfE Colleagues- do we need to future proof by referencing either that it is currently managed by , or the possibility it could be managed by another body?below. 15.2.5 The DfE will extract the information required for this exchange from records held on the Census collections which is managed held by Cap Gemini on behalfheld by of DfE. 15.2.6 DfE under contract as data processors will return the following pupil/ child and school(s) information (the “DfE Return Information”):  Surname  Forename  Middle name  (If held) Former surname  (If held) Preferred surname  Multiple or sole addresses (for the DfElast 3 to 5 years where held)l  House number/ name, street name and town/ city  Post code  Relevant census collection date for this record  Multiple or sole school information to include for all  School number  School name  School post code  Earliest known pupil date at school  Latest known pupil date at school  Adopted From Care Flag  (Once collected) Nationality On review, HO and DfE will assess the DfE Return Information and consider any reasonable adjustments to this information.