Objects Overview: (+DfE Data Item Guidance Texts)

This page shows detailed item-level guidance on data items within the Standard Safeguarding Dataset. Right click and open the image in a new browser tab to zoom/magnify/scroll object level detail. Data item id numbers [AAA000A] enable specific item/field referencing.

This is work in progress subject to frequent change; Data objects and item definitions are published here to support iterative development. Diagrams consisdered as conceptual interpretations, not a true relational/representational model

Object/Data item key:

• Existing - Current returned data
• Local - Recorded locally but not currently included in any data collections
• 1aDraft - Suggested new item for SSD
• 1bDraft - Suggested new item for one of the 1b projects
• 1bSpecified - Final specified item for one of the 1b projects
• 1aRemove - Specified item rejected from final spec.
• 1aNotInCMS - Currently exists but commonly outside Social Care CMS. (SSD==Placeholder data)

Note: Colour identifiers on Overview image indicate presence of at least one known change. See below tables for the item level changes/additions with granular colour-coding.

Object name: ssd_cp_plans

Item Ref	Data Item Name	Guidance	Returns	Change Log
CPPL001A	cppl_cp_plan_id	Row identifier for the ssd_cp_plans table	Local
CPPL007A	cppl_referral_id	ID for linking to CIN Referral Episode	Local
CPPL008A	cppl_icpc_id	ID for linking to Initial CP Conference	Local
CPPL002A	cppl_person_id	Person's ID generated in CMS Database	Local
CPPL003A	cppl_cp_plan_start_date	The Start Date of the Child Protection Plan.	CIN, AnnexA, RIIA
CPPL004A	cppl_cp_plan_end_date	The End Date of the Child Protection Plan.	CIN, AnnexA, RIIA
CPPL009A	cppl_cp_plan_initial_category	The category of abuse as assessed when the child protection plan commenced. Code set - Neglect - Physical abuse - Sexual abuse - Emotional abuse - Multiple: [List of relevant categories]	CIN, AnnexA
CPPL011A	cppl_cp_plan_ola	Is this an Other Local Authority Plan? Y/N	Local
CPPL010A	cppl_cp_plan_latest_category	The latest category of abuse recorded on the CP Plan, this may be the same as above. Code set - Neglect - Physical abuse - Sexual abuse - Emotional abuse - Multiple: [List of relevant categories]	CIN, AnnexA

Object name: ssd_cla_placement

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAP001A	clap_cla_placement_id	Row identifier for the ssd_cla_placement table	Local
CLAP003A	clap_cla_placement_start_date	This item records the date that each placement began. Where placements are consecutive, the new placement must start on the same day that the previous placement ended.	SSDA903, AnnexA
CLAP004A	clap_cla_placement_type	This category can be defined, in a broad sense, as indicating where the child is living. Code set A3 - Placed for adoption with parental/guardian consent with current foster carer(s) (S19 Adoption and Children Act 2002) or with a freeing order where parental/guardian consent has been given (S18(1)(a) Adoption Act 1976) A4 - Placed for adoption with parental/guardian consent not with current foster carer(s) (S19 Adoption and Children Act 2002) or with a freeing order where parental/guardian consent has been given (S18(1)(a) Adoption Act 1976) A5 - Placed for adoption with placement order with current foster carer(s) (S21 Adoption and Children Act 2002) or with a freeing order where parental/guardian consent was dispensed with (S18(1)(b) Adoption Act 1976) A6 - Placed for adoption with placement order not with current foster carer(s) (S21 Adoption and Children Act 2002) or with a freeing order where parental/guardian consent was dispensed with (S18(1)(b) of the Adoption Act 1976) H5 - Semi-independent living accommodation not subject to children’s homes regulations K1 - Secure children’s homes K2 - Children’s Homes subject to Children’s Homes Regulations P1 - Placed with own parent(s) or other person(s) with parental responsibility P2 - Independent living e.g. in a flat/ lodgings, bedsit, B&B or with friends, with or without formal support P3 - Residential employment R1 - Residential care home R2 - National Health Service (NHS)/health trust or other establishment providing medical or nursing care R3 - Family centre or mother and baby unit R5 - Young offender institution (YOI) S1 - All residential schools, except where dual-registered as a school and children’s home T0 - All types of temporary move (see paragraphs above for further details) T1 - Temporary periods in hospital T2 - Temporary absences of the child on holiday T3 - Temporary accommodation whilst normal foster carer(s) is/are on holiday T4 - Temporary accommodation of seven days or less, for any reason, not covered by codes T1 to T3 U1 - Foster placement with relative(s) or friend(s) – long term fostering U2 - Fostering placement with relative(s) or friend(s) who is/are also an approved adopter(s) – FFA/ concurrent planning U3 - Fostering placement with relative(s) or friend(s) who is/are not long-term or FFA/ concurrent planning U4 - Foster placement with other foster carer(s) – long term fostering U5 - Foster placement with other foster carer(s) who is/are also an approved adopter(s) – FFA/ concurrent planning U6 - Foster placement with other foster carer(s) – not long term or FFA/ concurrent planning Z1 - Other placements (must be listed on a schedule sent to DfE with annual submission)	SSDA903, AnnexA
CLAP005A	clap_cla_placement_urn	A new requirement was introduced in the collection year 2015 to 2016, to return the unique reference number (URN) where the setting is subject to Ofsted inspections. For children’s homes this would be the URN of the individual home and for foster or adoptive placements this would be the URN of the relevant service or agency providing the placement. For larger providers with multiple settings or branches the precise URN for the particular setting or branch is required. In some cases, it will be valid to provide different information to that registered with Ofsted, for example if a child is placed at the provider but at a different postcode to the main site. This could be the case if a child is residing in a dormitory with a different postcode to the registered site. Here the actual postcode where the child resides should be reported. The URN is in the format SC999999 or 9999999 for newly registered providers. Note that secure training centres may have both a 6-digit education URN and a 7-digit social care URN and it is the 7-digit social care URN which should be returned in the SSDA903. Where local authorities are certain that a provider is not inspected by Ofsted but is inspected by the Care Quality Commission (CQC) or Independent Schools Inspectorate (ISI) then the code ‘XXXXXXX’ should be used. Similarly, the code ‘XXXXXXX’ should be used when the provider is a regional adoption agency. Where placements are of a type or in a setting not inspected by Ofsted, such as placed with parents, then no URN is expected.	SSDA903, AnnexA
CLAP011A	clap_cla_placement_distance	Distance of Placement from Child's home address (miles). When a child’s home postcode is outside of England or not available, or the placement postcode is not available, please use 999.9 for the distance. This includes children from overseas, children whose parents were homeless or children who had no fixed address as they belonged to a traveller family.	SSDA903
CLAP012A	clap_cla_id	System identifier for the whole period of care, encompassing all episodes included within that period of care.	Local
CLAP007A	clap_cla_placement_provider	For each placement, except those children looked-after placed in temporary placements (T0-T4) or other placements (Z1) a placement provider code is required. This will record information on the party providing the placement. Children placed with their own parents do not strictly have a placement provider and should be allocated code PR0, only. Code set PR0 - Parent(s) or other person(s) with parental responsibility PR1 - Own provision (by the local authority) including a regional adoption agency where the child’s responsible local authority is the host authority PR2 - Other local authority provision, including a regional adoption agency where another local authority is the host authority PR3 - Other public provision (for example, a primary care trust) PR4 - Private provision PR5 - Voluntary/third sector provision	SSDA903, AnnexA
CLAP008A	clap_cla_placement_postcode	The postcode of the location where the child is placed.	SSDA903, AnnexA
CLAP009A	clap_cla_placement_end_date	This item records the date that each placement ended. A placement cannot start and end on the same day. Where a child has not left care, a new placement must start on the same day as the previous placement finished.	SSDA903, AnnexA
CLAP010A	clap_cla_placement_change_reason	Reason for placement change. The reason for placement change should be recorded against the episode that is ceasing, not against the new episode starting. Code set CARPL - Change to/Implementation of Care Plan This code would be used where the change of placement is a planned part of the child’s care plan and will be a move to a placement that meets the child’s assessed needs on a temporary or permanent basis. This would include circumstances where a placement change was not expected but becomes necessary. The key factor is that planning takes place and the decision is recorded in the child’s care plan before the change takes place. This would include moves from short to long term foster care or where a child is placed for adoption with the current foster carer. It also includes movements to semi-independence. The nature of the change in plan will be monitored through the placement codes before and after this move. This should not include changes where the foster carer has moved to a new house or where the carer is the same but has changed provider type. CLOSE - Resignation/ closure of provision This code would be used where a child has to be moved because a foster carer decides to resign or the setting closes. This code would be used in a planned move; not in an emergency. The foster carer’s decision to resign may be because their circumstances have changed, for example, the foster carer becomes ill or another change of circumstances means that the foster carer is no longer able to provide a placement for the child. Circumstances may also include where the child’s placement had lasted longer than expected and the foster carer is no longer able to provide a placement for the child. Use of this code would also include where a setting (for example, a children’s home or a fostering service) closes and is therefore no longer a registered provision with Ofsted. ALLEG - Allegation (s47) This code would be used where a child has been removed from placement because of an allegation which is being investigated under s47 (Children Act 1989). This allegation may relate to the carer or another child at the setting. This code should not be used if the allegation has resulted in the setting’s approval (for example, a children’s home or a fostering service) being terminated – in this case, ‘approval removed’ should be used. STAND - Standards of care concern This code would be used where a child has been removed from placement by the responsible authority or provider as a result of concerns about standards of care. This does not mean a child protection investigation (s47) but a formal process followed by the provider. For example, see the National Minimum Standards for Fostering Service 2011, standard. 22. This code can be used for all types of placement such as foster care, residential care. This code should not be used if the setting’s approval is terminated as a result of standards of care concerns – in this case, ‘approval removed’ should be used. CUSTOD - Custody arrangement This code would be used where a child has been admitted into custody. APPRR Approval removed This code would be used where a setting is no longer approved/registered with the appropriate statutory body (such as Ofsted). This code can be used for all types of placement such as foster care, residential care. For example, this code should be used where a foster carer’s approval is terminated by the service following a s47 investigation, a standards of care issue, a complaint or for other reasons that relate to the carers’ conduct. It should also be used where Ofsted take enforcement action resulting in the closure of a residential setting. This code should not be used when a foster carer resigns or a provision is closed voluntarily and they are no longer registered with the relevant statutory body (such as Ofsted). CREQB - Carer(s) requests placement end due to child’s behaviour This code would be used where because of the child’s behaviour the placement has broken down or disrupted, and the carer has asked for the placement to end and the child to be moved to another placement. There may be some planning involved and a short period of time may pass but this is not a planned move. CREQO - Carer(s) requests placement end other than due to child’s behaviour These codes would be used where it was intended that the placement was a short or long term arrangement but has broken down or disrupted and the carer [foster carer, residential unit or connected person] has asked for the child to be moved to another placement. There may be some planning involved and a short period of time may pass but this is not a planned move. CHILD - Child requests placement end This code would be used where it was intended that the placement was a short- or long-term arrangement but has broken down or disrupted and the child has asked to move to another placement. There may be some planning involved and a short period of time may pass but this is not a planned move. LAREQ - Responsible/area authority requests placement end This code would be used where it was intended that the placement was a short- or long-term placement but the responsible authority has decided that the placement no longer meets the child’s needs. There may be some planning involved and a short period of time may pass but this is not a planned move. There will be circumstances where the child is at risk of harm and this would be coded as an allegation or standards of care concern. Where the placement no longer meets a child’s need but there is no immediate risk – this code would be used. PLACE - Change in the status of placement only This code would be used where there is a change of status for the placement, but the child remains with the same carer and there is no change to the care plan. Examples include a foster carer moving to a new house, a foster carer working for a local authority becomes managed by an independent fostering agency, a placement for adoption transferring to a regional adoption agency, or a child in residential accommodation moving under the same provider. Here the ‘reason for new episode’ code will indicate that the child is still living with the same carer. OTHER - Other Any other reason not captured above. Please note that ’Other’ should only be used in exceptional circumstances.	SSDA903
CLAP013A	clap_person_id	Person's ID generated in CMS Database	Local

Object name: ssd_ehcp_assessment

Item Ref	Data Item Name	Guidance	Returns	Change Log
EHCA001A	ehca_ehcp_assessment_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP assessment record unique ID from system or auto-generated as part of export. This module collects information on the decision to issue a plan. Where a decision has been made to issue a plan, the detail about the placement named on the EHC plan should be recorded in Module 4. It is possible that multiple assessments may be recorded for a single person. For example, if it was decided not to issue a plan previously and a new assessment has been agreed following a new request. If a child or young person transfers into the local authority’s area during the assessment process before an EHC plan has been issued there is no right of transfer of decisions made by the originating local authority. Under good practice local authorities may decide to share information but the importing local authority must make its own decisions on whether to assess and whether to issue a plan. Where a person with an existing EHC plan transfers into the local authority’s area (item 5.1) the assessment should be recorded as historical by the importing local authority, even if the EHC plan start date is within the collection year.	1aNotInCMS, RIIA
EHCA002A	ehca_ehcp_request_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP request record unique ID from system or auto-generated as part of export.	1aNotInCMS
EHCA003A	ehca_ehcp_assessment_outcome_date	(currently 'PLACEHOLDER_DATA' pending further development) The assessment outcome date is required where EAM004A is equal to ‘Y’ or ‘N’, either record: -Date on which EHC plan was issued, or -Date on which person was notified of decision not to issue a plan If a decision to issue has been made but no plan has been issued, please leave blank.	1aNotInCMS, SEN2, RIIA, SEN2
EHCA004A	ehca_ehcp_assessment_outcome	(currently 'PLACEHOLDER_DATA' pending further development) Assessment outcome - decision to issue EHC plan: -Y It was decided an EHC plan would be issued -N It was decided an EHC plan would not be issued -A Decision has not yet been made -W Request withdrawn or ceased before decision whether to issue was made -H Historical – Decision to issue was made before the latest collection period If a local authority decides not to issue an EHC plan and this decision is subsequently changed by the local authority for any reason the original assessment outcome and assessment outcome date should not be changed. If the change follows from mediation or tribunal the appropriate mediation and tribunal indicators should be selected for the assessment. W may include where the person moves out of the local authority area, leaves education or training or if the child or young person dies. Where A or W is selected, no further information is required in this or subsequent modules. The 20-week timeliness measure will not apply in cases where a plan has not yet been issued. For an active plan, where the decision to issue was made before the latest collection period (H - Historical) information is still required on the plan itself.	1aNotInCMS, SEN2, RIIA, SEN2
EHCA005A	ehca_ehcp_assessment_exceptions	(currently 'PLACEHOLDER_DATA' pending further development) Assessment 20-week time limit exceptions apply? 1 – Yes, exceptions apply 0 – No, exceptions do not apply	1aNotInCMS, SEN2, RIIA, SEN2

Object name: ssd_sen_need

Item Ref	Data Item Name	Guidance	Returns	Change Log
SENN001A	senn_table_id	(currently 'PLACEHOLDER_DATA' pending further development) SEN need record unique ID from system or auto-generated as part of export.	1aNotInCMS
SENN002A	senn_active_ehcp_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP active plan unique ID from system or auto-generated as part of export.	1aNotInCMS
SENN003A	senn_active_ehcp_need_type	(currently 'PLACEHOLDER_DATA' pending further development) Please record the nature of the person’s special educational need. These options are consistent with those collected within the spring term school census. Where multiple types of need are recorded and ranked, the primary type of need should be ranked 1 under Type of need rank, and if applicable a secondary type of need should be ranked 2. -SPLD Specific learning difficulty -MLD Moderate learning difficulty -SLD Severe learning difficulty -PMLD Profound and multiple learning difficulty -SEMH Social, emotional and mental health -SLCN Speech, language and communication needs -HI Hearing impairment -VI Vision impairment -MSI Multi-sensory impairment -PD Physical disability -ASD Autistic spectrum disorder -OTH Other difficulty	1aNotInCMS, SEN2
SENN004A	senn_active_ehcp_need_rank	(currently 'PLACEHOLDER_DATA' pending further development) If only one type of need is recorded, this should be recorded as rank 1. If multiple types of need are recorded, then the primary type of need should be recorded as rank 1 and the secondary type of need should be recorded as rank 2. Up to two types of need can be recorded.	1aNotInCMS, SEN2

Object name: ssd_cin_visits

Item Ref	Data Item Name	Guidance	Returns	Change Log
CINV001A	cinv_cin_visit_id	Row identifier for the ssd_cin_visits table.	Local
CINV007A	cinv_person_id	Person's ID generated in CMS Database	Local
CINV003A	cinv_cin_visit_date	Date of Visit	Local
CINV004A	cinv_cin_visit_seen	Was the child seen during this visit? Y/N	AnnexA
CINV005A	cinv_cin_visit_seen_alone	Was the child seen alone during this visit? Y/N	Local
CINV006A	cinv_cin_visit_bedroom	Was the child's bedroom seen during this visit? Y/N	Local

Object name: ssd_linked_identifiers

Item Ref	Data Item Name	Guidance	Returns	Change Log
LINK001A	link_table_id	(currently 'PLACEHOLDER_DATA' pending further development) Row identifier for the ssd_linked_identifiers table	1aNotInCMS
LINK002A	link_person_id	(currently 'PLACEHOLDER_DATA' pending further development) Person's ID generated in CMS Database	Local
LINK003A	link_identifier_type	(currently 'PLACEHOLDER_DATA' pending further development) Linked Identifier Type e.g. ['Case Number', 'Unique Pupil Number', NHS Number', 'Home Office Registration', National Insurance Number', 'YOT Number', Court Case Number', RAA ID', 'Incident ID']	1aNotInCMS
LINK004A	link_identifier_value	(currently 'PLACEHOLDER_DATA' pending further development) Identifier value	1aNotInCMS
LINK005A	link_valid_from_date	(currently 'PLACEHOLDER_DATA' pending further development) Date the identifier is known/valid from	1aNotInCMS
LINK006A	link_valid_to_date	(currently 'PLACEHOLDER_DATA' pending further development) Date the identifier ceases to be known/valid	1aNotInCMS

Object name: ssd_cla_immunisations

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAI002A	clai_person_id	Person's ID generated in CMS Database, Row identifier for the ssd_cla_immunisations table	Local
CLAI004A	clai_immunisations_status	Immunisations up to date? Y/N	SSDA903
CLAI005A	clai_immunisations_status_date	Immunisations status last updated	Local

Object name: ssd_cin_episodes

Item Ref	Data Item Name	Guidance	Returns	Change Log
CINE001A	cine_referral_id	Row identifier for the ssd_cin_episodes table	Loca;
CINE002A	cine_person_id	Person's ID generated in CMS Database	Local
CINE003A	cine_referral_date	Date the Referral is effective from	CIN, AnnexA, RIIA
CINE010A	cine_cin_primary_need_code	CIN Primary Need Code. This code indicates the main reason why a child started to receive services. The categories are designed only to identify what kind of pressures are placed on social services. They have no diagnostic value with regard to the children themselves and must not be used to determine what type of service the child should receive. If there is difficulty choosing between two or more categories of need, choose the category that comes highest up in the table, for example, if trying to decide between family in acute stress and family dysfunction, choose family in acute stress. The order of the categories relates to the specificity of the description and not necessarily importance. However, the order is fixed so that there is consistency. The children in need census for 2005 and earlier tried to account for all money spent in a census week. To allow for this, ‘N9’ was created, but as this census is specifically child based, the definition of ‘N9’ from 2005 is not applicable. As in previous years, ‘N9’ can be used if a child is no longer in need and the only service they are receiving is adoption support (on an open case) immediately after they have been in need. Code Set N1 - Abuse or neglect Children in need as a result of, or at risk of, abuse or neglect; also includes children at risk because of domestic violence. N2 - Child’s disability Children and families whose main need for services arises because of their child’s disability, illness or intrinsic condition. N3 - Parental disability or illness Children whose main need for services arises because the capacity of their parent(s) (or carer(s)) to care for them is impaired by the parent(s) (or carer(s)) disability, physical or mental illness, or addictions. N4 - Family in acute stress Children whose needs arise from living in a family that is going through a temporary crisis that diminishes the parental capacity to adequately meet some of the children’s needs. N5 - Family dysfunction Children whose needs primarily arise from living in a family where the parenting capacity is chronically inadequate. N6 - Socially unacceptable behaviour Children and families whose need for services primarily arise out of the child’s behaviour impacting detrimentally on the community. N7 - Low income Children, living in families or independently, whose needs primarily arise from being dependent on an income below the standard state entitlements. N8 - Absent parenting Children whose needs for services arise mainly from having no parents available to provide for them. N9 - Cases other than children in need Children who have been adopted and, although they are no longer a child in need, receive adoption support from children’s social services immediately after adoption. This should not be used where a child receives an adoption payment only. N0 - Not stated Children whose reference data is not completely entered on the system and whose need code is yet to be determined, or the case is a referral that has been closed following assessment.	CIN, AnnexA, RIIA
CINE004A	cine_referral_source_code	Contact Source Code	CIN, AnnexA, RIIA
CINE012A	cine_referral_source_desc	Contact Source Name	Local
CINE005A	cine_referral_outcome_json	Outcome of the Referral. This indicates the outcome of the initial Referral, not the CIN Episode. Combined dictionary/ json type containing the following AS cine_referral_outcome_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { SINGLE_ASSESSMENT_FLAG: "", NFA_FLAG: "", STRATEGY_DISCUSSION_FLAG: "", CLA_REQUEST_FLAG: "", NON_AGENCY_ADOPTION_FLAG: "", PRIVATE_FOSTERING_FLAG: "", CP_TRANSFER_IN_FLAG: "", CP_CONFERENCE_FLAG: "", CARE_LEAVER_FLAG: "", OTHER_OUTCOMES_EXIST_FLAG: "" }	AnnexA, RIIA
CINE011A	cine_referral_nfa	Indicates the outcome of this contact was that there was no further assessment required	CIN, AnnexA, RIIA
CINE006A	cine_close_reason	This is the reason the local authority stops providing services to the child. Code set RC1 - Adopted. RC2 - Died. RC3 - Child arrangements order. RC4 - Special guardianship order. RC5 - Transferred to services of another local authority. RC6 - Transferred to adult social care services. RC7 - Services ceased for any other reason, including child no longer in need. RC8 - Case closed after assessment, no further action. RC9 - Case closed after assessment, referred to early help.	CIN, RIIA
CINE007A	cine_close_date	Date the Referral is effective to, i.e. Case Closure Date	CIN, RIIA
CINE008A	cine_referral_team	Team responsible for completing the initial Referral	AnnexA, RIIA
CINE009A	cine_referral_worker_id	Worker responsible for completing initial Referral	AnnexA, RIIA

Object name: ssd_department

Item Ref	Data Item Name	Guidance	Returns	Change Log
DEPT1001A	dept_team_id	System unique identifier for department|team	Local
DEPT1002A	dept_team_name	Name description for department|team	Local,AnnexA
DEPT1003A	dept_team_parent_id	System identifier for department|team parent	Local
DEPT1004A	dept_team_parent_name	Name description for department|team parent	Local

Object name: ssd_permanence

Item Ref	Data Item Name	Guidance	Returns	Change Log
PERM001A	perm_table_id	Row identifier for the ssd_permanence table	Local
PERM002A	perm_person_id	Person's ID generated in CMS Database	Local
PERM022A	perm_cla_id	System identifier for the whole period of care, encompassing all episodes within that period of care.	Local
PERM003A	perm_adm_decision_date	The date of the decision that the child should be placed for adoption. This is the date on which the local authority formally decides that a child should be placed for adoption, i.e. the date the agency decision maker takes the decision to endorse the proposed adoption plan for the child.	SSDA903, ASGLB
PERM004A	perm_ffa_cp_decision_date	Date of the decision that the child should be placed in a FFA or CP placement with a selected family, if applicable	ASGLB, AnnexA
PERM006A	perm_placement_order_date	The date that a Placement order or Freeing order was granted. This can be ascertained from the date when a child's legal status has changed to E1 (Placement order granted) or D1 (Freeing order granted).	SSDA903, AnnexA, ASGLB
PERM007A	perm_placed_for_adoption_date	The date that the child was placed for adoption with particular prospective adopters.. Or, if the child was placed with their foster carers or were in a FFA/concurrent planning placement, record the date this placement changed from a foster placement to an adoption placement. This is the date that child goes to live with the prospective adopters who will adopt them. It does not mean that the child has been adopted.	SSDA903, AnnexA, ASGLB
PERM008A	perm_matched_date	The date that the child was matched to particular prospective adopters or with dually approved foster carers/adopters for FFA. This is the date on which the local authority formally decides that the child should be placed for adoption with the particular prospective adopters. If the child is adopted by the foster carer or relatives with whom he/she is already placed, the date of decision should be recorded here.	SSDA903, AnnexA, ASGLB
PERM021A	perm_adopted_by_carer_flag	Flag showing if the child was Adopted by their former carer. Y/N	SSDA903, AnnexA
PERM009A	perm_placed_ffa_cp_date	Date the child was placed in a FFA or CP placement.	AnnexA, ASGLB
PERM010A	perm_decision_reversed_date	The date that the local authority formally decides that a child should no longer be placed for adoption	SSDA903, AnnexA, ASGLB
PERM011A	perm_placed_foster_carer_date	(currently 'PLACEHOLDER_DATA' pending further development) Date the child was originally placed with their foster carer(s) (only if the child was adopted by their foster carer(s))	AnnexA, ASGLB
PERM012A	perm_part_of_sibling_group	Is the child a part of a sibling group Code set 0 - No 1 - Yes	ASGLB
PERM013A	perm_siblings_placed_together	Number of children placed, or planned to be placed, for adoption together as sibling group INCLUDING this child	ASGLB
PERM014A	perm_siblings_placed_apart	Number of siblings placed, or planned to be placed, for adoption separately from the child	ASGLB
PERM015A	perm_placement_provider_urn	URN of the placement provider agency	Local
PERM016A	perm_decision_reversed_reason	Reason why the child is no longer considered for adoption Code set RD1 - The child’s needs changed subsequent to the decision RD2 - The Court did not make a placement order RD3 - Prospective adopters could not be found RD4 - Any other reason	SSDA903, AnnexA, ASGLB
PERM017A	perm_permanence_order_date	Date permanence order granted - this is the CLA Placement End Date	AnnexA, ASGLB
PERM018A	perm_permanence_order_type	Type of Permanence order granted - Adoption - Special Guardianship - Child Arrangements Order/ Residence Order	ASGLB
PERM023A	perm_adoption_worker_id	Adoption Social Worker	Local
PERM025A	perm_adopter_sex	The sex of the adopter/s/ prospective adopter/s. Code set F1 - Single Female FF - Female couple M1 - Single Male MF - Male/Female couple MM - Male couple	SSDA903
PERM026A	perm_adopter_legal_status	The Legal Status of the adopter/s/ prospective adopter/s. Code set L0 - Single Adopter L11 - Different gender married couple L12 - Same gender married couple L2 - Civil partnership couple L3 - Different gender unmarried couple L4 - Same gender couple not married or in a civil partnership	SSDA903
PERM027A	perm_number_of_adopters	Number of Adopters/ Prospective Adopters	SSDA903

Object name: ssd_send

Item Ref	Data Item Name	Guidance	Returns	Change Log
SEND001A	send_table_id	(currently 'PLACEHOLDER_DATA' pending further development) Row identifier for the ssd_send table	1aNotInCMS, RIIA
SEND002A	send_upn	(currently 'PLACEHOLDER_DATA' pending further development) The Child's Unique Pupil Number	1aNotInCMS, RIIA, SEN2
SEND003A	send_uln	(currently 'PLACEHOLDER_DATA' pending further development) The young person’s unique learner number (ULN) as used in the Individualised Learner Record.	1aNotInCMS, RIIA, SEN2
SEND004A	send_upn_unknown	(currently 'PLACEHOLDER_DATA' pending further development) Where no identifier is available, please record one of the following options: -UN1 Child is aged under 6 years old and is not yet assigned a UPN -UN2 Child has never attended a state-funded school in England and has not been assigned a UPN -UN3 Child is educated outside of England and has not been assigned a UPN -UN5 Sources collating UPNs reflect discrepancy/ies for the child’s name and/or surname and/or date of birth therefore prevent reliable matching (for example duplicated UPN) -UN8 Person is new to LA and the UPN or ULN is not yet known -UN9 Young person has never attended a state-funded school or further education setting in England and has not been assigned a UPN or ULN -UN10 Request for assessment resulted in no further action before UPN or ULN known	1aNotInCMS, RIIA, SEN2
SEND005A	send_person_id	(currently 'PLACEHOLDER_DATA' pending further development) Person's ID generated in CMS Database	1aNotInCMS, RIIA

Object name: ssd_ehcp_named_plan

Item Ref	Data Item Name	Guidance	Returns	Change Log
EHCN001A	ehcn_named_plan_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP named plan unique ID from system or auto-generated as part of export. This module collects information on the content of the EHC plan, i.e. what is in Section I. It should be completed for all existing active EHC plans. It is possible that multiple plans may be recorded for a single person. For example, if an EHC plan has previously ceased and a further plan has later been issued following a new needs assessment. Changes may occur to this section from one year to the next for the same person, for example where an establishment named on the EHC plan is changed.	1aNotInCMS
EHCN002A	ehcn_ehcp_asmt_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP assessment record unique ID from system or auto-generated as part of export.	1aNotInCMS
EHCN003A	ehcn_named_plan_start_date	(currently 'PLACEHOLDER_DATA' pending further development) Date of current EHC plan.	1aNotInCMS, SEN2
EHCN004A	ehcn_named_plan_ceased_date	(currently 'PLACEHOLDER_DATA' pending further development) Please provide the date the EHC plan ended or the date the EHC plan was transferred to another local authority. Do not record the date of the decision to cease. Local authorities must continue to maintain the EHC plan until the time has passed for bringing an appeal or, when an appeal has been registered, until it has been concluded.	1aNotInCMS, SEN2
EHCN005A	ehcn_named_plan_ceased_reason	(currently 'PLACEHOLDER_DATA' pending further development) Please provide the reason the EHC plan ended from the list below 1 – Reached maximum age (this is the end of the academic year during which the young person turned 25) 2 – Ongoing educational or training needs being met without an EHC plan 3 – Moved on to higher education 4 – Moved on to paid employment, excluding apprenticeships 5 – Transferred to another LA 6 – Young person no longer wishes to engage in education or training 7 – Child or young person has moved outside England 8 – Child or young person deceased 9 – Other	1aNotInCMS, SEN2

Object name: ssd_address

Item Ref	Data Item Name	Guidance	Returns	Change Log
ADDR007A	addr_table_id	Row identifier for the ssd_address table	Local
ADDR001A	addr_address_json	Persons address Combined dictionary/ json type containing the following, AS addr_address_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { ROOM: "", FLOOR: "", FLAT: "", BUILDING: "", HOUSE: "", STREET: "", TOWN: "", UPRN: "", EASTING: "", NORTHING: "" }	Local
ADDR002A	addr_person_id	Person's ID generated in CMS Database	Local
ADDR003A	addr_address_type	Type of Address, e.g. Home/ Placement/ Primary etc.	Local
ADDR004A	addr_address_start_date	Date person started living at the address	Local
ADDR005A	addr_address_end_date	Date person left the address	Local
ADDR006A	addr_address_postcode	Address Postcode, auto-formatted to remove spaces for consistency	SSDA903, AnnexA, SEN2

Object name: ssd_assessment_factors

Item Ref	Data Item Name	Guidance	Returns	Change Log
CINF003A	cinf_table_id	Row identifier for the ssd_assessment_factors table.	Local
CINF001A	cinf_assessment_id	ID for linking to CIN Assessment record	Local
CINF002A	cinf_assessment_factors_json	Record of the factors as understood at the end of the Assessment. Combined dictionary/ json type containing the following AS cinf_assessment_factors_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence -- Opt1: Current implementation as JSON ARRAY [ ] [ "1A", "2B", "3A", ...] -- Opt2: Forward planned implementation as JSON { "1A": "Yes", "2B": "No", "3A": "Yes", ...} Code set 1A/1B/1C - Alcohol misuse by the child/ parent(s) or carer(s)/ another person living in the household. 2A/2B/2C - Drug misuse by the child/ parent(s) or carer(s)/ another person living in the household. 3A/3B/3C - Concerns about the child/ parent(s) or carer(s)/ another person living in the household being the subject of domestic violence. 4A/4B/4C - Concerns about Mental Health of the child/ parent(s) or carer(s)/ another person living in the household. 5A/5B/5C - Concerns about Learning Disability of the Child/ parent(s) or carer(s)/ another person living in the household. 6A/6B/6C - Concerns about Physical Disability/ illness of the Child/ parent(s) or carer(s)/ another person living in the household. 7A - Young carer: concerns child’s health or development may be impaired due to their caring responsibilities. 8B - Privately fostered - overseas children who intend to return 8C - Privately fostered - overseas children who intend to stay 8D - Privately fostered - UK children in educational placements 8E - Privately fostered - UK children making alternative family arrangements 8F - Privately fostered - other 9A - UASC unaccompanied asylum-seeking child 10A - Missing: concerns that the child may be at risk of harm due to going/being missing. 11A - Child sexual exploitation: concerns that the child may be at risk of harm due to child sexual exploitation. 12A - Trafficking: concerns that services may be required or the child may be at risk of harm due to trafficking. 13A - Gangs: concerns that the child may be at risk of harm because of involvement in/with gangs. 14A - Socially unacceptable behaviour: concerns the child may be at risk due to their socially unacceptable behaviour. 15A - Self-harm: concerns that services may be required or due to suspected/actual self-harming child may be at risk of harm. 16A - Abuse or neglect – ‘NEGLECT’: concerns child may be at risk due to neglect. 17A - Abuse or neglect – ‘EMOTIONAL ABUSE’: concerns child may be at risk due to emotional abuse. 18B - Abuse or neglect – ‘PHYSICAL ABUSE’ (child on child): concerns child may be at risk due to physical abuse by another child. 18C - Abuse or neglect – ‘PHYSICAL ABUSE’ (adult on child): concerns child may be at risk due to physical abuse by an adult. 19B - Abuse or neglect – ‘SEXUAL ABUSE’ (child on child): concerns child may be at risk due to sexual abuse by another child. 19C - Abuse or neglect – ‘SEXUAL ABUSE’ (adult on child): concerns child may be at risk due to sexual abuse by an adult. 20 - Other. 21 - No factors identified - no evidence of any of the factors listed above or below and no further action is being taken.F68 22A - Female genital mutilation (FGM) - concerns child may be at risk due to female genital mutilation. 23A - Abuse linked to faith or belief - concerns child may be at risk due to abuse linked to faith or belief. 24A - Child criminal exploitation - concerns child may be at risk of harm due to child criminal exploitation.	CIN

Object name: ssd_disability

Item Ref	Data Item Name	Guidance	Returns	Change Log
DISA001A	disa_person_id	Person's ID generated in CMS Database	Local
DISA003A	disa_table_id	Row identifier for the ssd_disability table	Local
DISA002A	disa_disability_code	The Disability Discrimination Act 2005 (DDA) defines a disabled person as a person with a physical or mental impairment which has a substantial and long-term adverse effect on his/her ability to carry out normal day-to-day activities. The condition must have lasted, or be likely to last at least 12 months in order to be counted as a disability. Code set NONE - ‘NO DISABILITY’ MOB - ‘MOBILITY’ – getting about the house and beyond HAND - ‘HAND FUNCTION’ – holding and touching PC - ‘PERSONAL CARE’ – For example, eating, washing, going to the toilet dressing INC - ‘INCONTINENCE’ – controlling the passage of urine or faeces COMM - ‘COMMUNICATION’ – speaking and/or understanding others LD - ‘LEARNING’ – For example, having special educational needs HEAR - ‘HEARING’ VIS - ‘VISION’ BEH - ‘BEHAVIOUR’ – a condition entailing behavioural difficulties, includes attention deficit hyperactivity disorder (ADHD) CON - ‘CONCIOUSNESS’ – seizures AUT - ‘DIAGNOSED WITH AUTISM OR ASPERGER SYNDROME’ – diagnosed by a qualified medical practitioner as having classical autism or Asperger syndrome. Do not include children who have merely been identified as having an autistic spectrum disorder (ASD), for example by their school. This can be associated with the behaviour and learning categories above. DDA - ‘OTHER DDA’ – one or more of the child’s disabilities under the Disability Discrimination Act 2005 (DDA) does not fall into any of the above categories. Certain conditions are not regarded as impairments for the purposes of the act: • addiction to, or dependency on, alcohol, nicotine, or any other substance (other than as a result of the substance being medically prescribed); • the condition known as seasonal allergic rhinitis (hay fever), except where it aggravates the effect of another condition; • tendency to start fires; • tendency to steal; • tendency to physically or sexually abuse other persons; • exhibitionism; • voyeurism In addition, disfigurements such as tattoos, non-medical body piercing, or something attached through such piercing, are not regarded as having a substantial adverse effect on the person’s ability to carry out normal day-to-day activities. If a child is disabled or becomes disabled at any time during the collection year, record all the relevant disabilities that have affected the child. For example, children may have multiple disabilities in which case more than one category from the below list can be selected. ‘Other DDA’ can also be used in conjunction with any of the other categories. If your MIS does not allow for the identification of individual disabilities, then the code ‘Other DDA’ may be used for all children with a disability. If a child has no disability, do not leave this item blank; use the code ‘NONE’. However, if a child is unborn then the disability item should be left blank.	CIN, AnnexA

Object name: ssd_cla_substance_misuse

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAS001A	clas_substance_misuse_id	Row identifier for the ssd_substance_misuse table	Local
CLAS002A	clas_person_id	Person's ID generated in CMS Database	Local
CLAS003A	clas_substance_misuse_date	Date of substance misuse	SSDA903
CLAS004A	clas_substance_misused	Substance that was being misused	Local
CLAS005A	clas_intervention_received	Did child receive intervention for substance misuse problem?	SSDA903

Object name: ssd_cp_reviews

Item Ref	Data Item Name	Guidance	Returns	Change Log
CPPR001A	cppr_cp_review_id	Row identifier for the ssd_cp_reviews table	Local
CPPR008A	cppr_person_id	Person's ID generated in CMS Database	Local
CPPR002A	cppr_cp_plan_id	ID for linking to the CP Plan	Local
CPPR003A	cppr_cp_review_due	The due date of the review conference.	Local
CPPR004A	cppr_cp_review_date	The actual date on which the Review Conference was held	CIN, AnnexA
CPPR009A	cppr_cp_review_meeting_id	Identifier for the Review CP Conference Meeting	Local
CPPR005A	cppr_cp_review_outcome_continue_cp	Was the outcome of the conference to continue the CP Plan? Y/N	Local
CPPR006A	cppr_cp_review_quorate	Was the conference quorate? The primary principle for determining quoracy is that there should be sufficient agencies or key disciplines present to enable safe decisions to be made in the individual circumstances. Minimum representation is Children's Social Care and at least two other agencies or key disciplines that have had direct contact with the child and family. In a case relating to fabricated or induced illness, it is important to ensure the paediatrician is able to attend.	Local
CPPR007A	cppr_cp_review_participation	(currently 'PLACEHOLDER_DATA' pending further development) The Child/ Young Person's method of participation at review. Code set PN0 - Child aged under 4 at the time of the review PN1 - Child physically attends and speaks for him or herself (Attendance). PN2 - Child physically attends and an advocate speaks on his or her behalf. (Attendance views represented by advocate or Child Protection Adisor (CPA)) PN3 - Child attends and conveys his or her view symbolically (non-verbally) (Attendance symbols) PN4 - Child physically attends but does not speak for him or herself, does not convey his or her view symbolically (non-verbally) and does not ask an advocate to speak for him or her (Attendance without contribution) PN5 - Child does not attend physically but briefs an advocate to speak for him or her (Views represented by advocate or independent reviewing officer (IRO) through texting, written format, phone, audio/video, viewpoint) PN6 - Child does not attend but conveys his or her feelings to the review by a facilitative medium (Texting the chair, written format, phone, audio/video, viewpoint) PN7 - Child does not attend nor are his or her views conveyed to the review	Local

Object name: ssd_contacts

Item Ref	Data Item Name	Guidance	Returns	Change Log
CONT001A	cont_contact_id	Row identifier for the ssd_contacts table	Local
CONT002A	cont_person_id	Person's ID generated in CMS Database	Local
CONT003A	cont_contact_date	Date Contact received into LA	AnnexA, RIIA
CONT004A	cont_contact_source_code	Contact Source Code	AnnexA, RIIA
CONT006A	cont_contact_source_desc	Contact Source Description	Local
CONT005A	cont_contact_outcome_json	Outcome of the Contact. Combined dictionary/ json type containing the following, AS cont_contact_outcome_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { NEW_REFERRAL_FLAG: "", EXISTING_REFERRAL_FLAG: "", CP_ENQUIRY_FLAG: "", NFA_FLAG: "", NON_AGENCY_ADOPTION_FLAG: "", PRIVATE_FOSTERING_FLAG: "", ADVICE_FLAG: "", MISSING_FLAG: "", OLA_CP_FLAG: "", OTHER_OUTCOMES_EXIST_FLAG: "" }	ADCS_SP, RIIA

Object name: ssd_care_leavers

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLEA001A	clea_table_id	Row identifier for the ssd_care_leavers table	Local
CLEA002A	clea_person_id	Person's ID generated in CMS Database	Local
CLEA003A	clea_care_leaver_eligibility	The current Care Leaver Eligibility Status of the Child/ Young Person. Code set Relevant Former Relevant Eligible Qualifying No Current Eligibility A relevant child is: • a young person aged 16 or 17 • is no longer looked-after • before last ceasing to be looked-after, was an ‘eligible child’ (see definition below) OR • a young person aged 16 or 17 • not subject to a care order • detained, or in hospital on their 16th birthday • immediately before being detained or admitted to hospital had been looked-after for at least 13 weeks which began after they reached age 14. A former relevant child is one who is: • aged 18 or above, AND EITHER • has been a relevant child and would be one if he were under 18, OR • immediately before he ceased to be looked-after at age 18, was an eligible child. The definition of eligible children is given below- relevant and former relevant children will have been an eligible child in the past. An eligible child is: • a young person aged 16 or 17 • who is looked-after • and has been looked-after for at least 13 weeks which began after they reached the age of 14 and ended after they reached the age of 16. A qualifying Care Leaver is: • aged between 16 and 25 • who was looked after by children’s services on, or after, their 16th birthday and no longer looked after • and spent less than 13 weeks in care since 14th birthday, i.e. do not fulfill criteria for eligible or relevant child	AnnexA, RIIA
CLEA004A	clea_care_leaver_in_touch	Is the local authority in touch with this young person? Code set YES - Yes - in touch NO - No – not in touch DIED - Died after leaving care REFU - Young person refuses contact NREQ - Young person no longer requires children’s social care services RHOM - Young person returned to live with parents or someone with parental responsibility for a continuous period of 6 months or more	SSDA903, RIIA
CLEA005A	clea_care_leaver_latest_contact	This should be the latest date of PA contact with the young person, it is left blank if the LA is not in touch with the care leaver.	AnnexA, RIIA
CLEA006A	clea_care_leaver_accommodation	The type of accommodation that the young person is living in on or around their 17th, 18th, 19th, 20th or 21st birthday, or the accommodation the young person is living in at the time of their latest contact during the year if they are aged 22-to-25-years-old. Code set B - With parent(s) or relative(s) C - Community home or other form of residential care such as an National Health Service (NHS) establishment D - Semi-independent, transitional accommodation (like a supported hostel, trainer flats); self-contained accommodation with specialist personal assistance support (for example, for young people with disabilities, pregnant young women and single parents); and self-contained accommodation with floating support E - Supported lodgings (accommodation, usually in a family home, where adult(s) in the “host family” provide formal advice and support) G - Gone abroad H - Deported K - Ordinary lodgings, without formal support R - Residence not known S - No fixed abode / homeless T - Foyers and similar supported accommodation which combines the accommodation with opportunities for education, training or employment U - Independent living, for example independent tenancy of flat, house or bedsit, including local authority or housing association tenancy, or accommodation provided by a college or university. Includes flat sharing V - Emergency accommodation (like a night shelter, direct access or emergency hostel) W - Bed and breakfast X - In custody Y - Other accommodation Z - With former foster carer(s) - where the young person has been fostered and on turning 18 continues to remain with the same carer(s) who had fostered them immediately prior to their reaching legal adulthood, and where the plan for their care involves their remaining with this former foster family for the future. This code should not be used for 17-year-old care leavers. If the foster carer is also a relative this code should be used rather than ‘B - with parents or relatives’.	SSDA903, RIIA, AnnexA
CLEA007A	clea_care_leaver_accom_suitable	Is the accommodation considered suitable? Accommodation is to be regarded as suitable if it provides safe, secure and affordable provision for young people. Accommodation that clearly exposes the person to risk of harm or social exclusion by reason of its location or other factors should be coded as ‘unsuitable’. Code set 1 - Accommodation is considered suitable 2 - Accommodation is considered unsuitable	AnnexA, RIIA
CLEA008A	clea_care_leaver_activity	For care leavers aged 17 to 21 years, the young person's main activity status on or around their birthday if the LA was in touch with them, or if the LA was not in touch with them but was certain of their activity on their birthday. For care leavers aged 22 to 25 years, this will be their main activity status at their last contact with the LA. Code set F1 - Young person engaged full time in higher education (for example studies beyond A level) P1 - Young person engaged part time in higher education (for example studies beyond A level) F2 - Young person engaged full time in education other than higher education P2 - Young person engaged part time in education other than higher education F4 - Young person engaged full time in an apprenticeship P4 - Young person engaged part time in an apprenticeship F5 - Young person engaged full time in training or employment (not apprenticeship) P5 - Young person engaged part time in training or employment (not apprenticeship) G4 - Young person not in education, employment or training because of illness or disability G5 - Young person not in education, employment or training: other circumstances G6 - Young person not in education, employment or training due to pregnancy or parenting F3 - (superseded by F4/F5) Young person engaged full time in training or employment P3 - (superseded by F4/F5) Young person engaged part time in training or employment	SSDA903, RIIA, AnnexA
CLEA009A	clea_pathway_plan_review_date	This should be either the date the Pathway plan started, or the latest date the pathway plan was reviewed (if applicable); whichever is the most recent.	AnnexA, RIIA
CLEA010A	clea_care_leaver_personal_advisor	Allocated Personal Advisor for Care Leaver	AnnexA, RIIA
CLEA011A	clea_care_leaver_allocated_team	Allocated Team responsible for Care Leaver	AnnexA, RIIA
CLEA012A	clea_care_leaver_worker_id	Allocated worker responsible for Care Leaver	AnnexA, RIIA

Object name: ssd_cla_visits

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAV001A	clav_cla_visit_id	Row identifier for the ssd_cla_visits table	Local
CLAV007A	clav_cla_id	System identifier for the whole period of care, encompassing all episodes included within that period of care.	Local
CLAV008A	clav_person_id	Person's ID generated in CMS Database	Local
CLAV003A	clav_cla_visit_date	Actual date of Visit	AnnexA
CLAV004A	clav_cla_visit_seen	Was the child seen during this visit? Y/N	Local
CLAV005A	clav_cla_visit_seen_alone	Was the child seen alone during this visit? Y/N	Local

Object name: ssd_professionals

Item Ref	Data Item Name	Guidance	Returns	Change Log
PROF001A	prof_professional_id	System generated worker ID field	Local
PROF010A	prof_staff_id	Staff ID used within reporting. Not all professionals are expected to have a staff_id e.g. External Agency|GP	Local
PROF013A	prof_professional_name	Professional's Name	AnnexA
PROF002A	prof_social_worker_registration_no	This is the child and family social worker Social Work England (SWE) number (formerly HCPC code). For social workers this will start ‘SW’. This data item should be in the format ‘AAnnnnnn’ and is up to 12 digits.	Local
PROF007A	prof_professional_job_title	Professional Job title, e.g. Social Worker, Keyworker, GP etc.	CSCWF, RIIA
PROF008A	prof_professional_caseload	Caseload calculated based on SSD time frame for each worker(using prof_professional_id)	CSCWF, RIIA
PROF012A	prof_professional_department	Professional's team/ organisation	Local
PROF011A	prof_full_time_equivalency	Worker FTE	Local
PROF014A	prof_agency_worker_flag	(currently 'PLACEHOLDER_DATA' pending further development) Y/N flag indicating if worker is an Agency worker	Local

Object name: ssd_missing

Item Ref	Data Item Name	Guidance	Returns	Change Log
MISS001A	miss_table_id	Row identifier for the ssd_missing table	Local
MISS002A	miss_person_id	Person's ID generated in CMS Database	Local
MISS003A	miss_missing_episode_start_date	The missing episode start date. This should be completed for both missing episodes and episodes where the child was away from placement without authorisation. It should be the date the child left his or her normal placement or the date the child was last seen by a responsible adult (whichever was the latest). For this purpose, a responsible adult is either the child’s carer, or a professional directly associated with the child’s welfare or education (like a doctor, school-teacher or social worker). Any UASC that go missing before being accommodated for 24 hours for data collection purposes should still be recorded as missing with a start date as the date in which they left his or her normal placement or the date the child was last seen by a responsible adult (whichever was the latest). For this purpose, a responsible adult is either the child’s carer, or a professional directly associated with the child’s welfare or education (like a doctor, school-teacher, home office official or social worker). Unresolved cases should remain open and until the child’s 18th birthday, at which point the case should be closed using the appropriate reason code. Records must not be closed before this point.	SSDA903, AnnexA
MISS004A	miss_missing_episode_type	Record each episode where a child was ‘missing’ or ‘away from placement without authorisation’ according to the following definitions: • Missing - Missing from care: a looked-after child who is not at their placement or the place they are expected to be (for example school) and their whereabouts is not known • Away - Away from placement without authorisation: a looked-after child whose whereabouts is known but who is not at their placement or place they are expected to be and the carer has concerns or the incident has been notified to the local authority or the police. Any children missing from care or away from placement without authorisation for any length of time should be recorded.	SSDA903, AnnexA
MISS005A	miss_missing_episode_end_date	The missing episode end date. This should be completed for both missing episodes and episodes where the child was away from placement without authorisation. It should be the date that the child was found (where whereabouts are unknown) or the date that the child returned to his/her normal placement (where whereabouts known).	SSDA903, AnnexA
MISS006A	miss_missing_rhi_offered	Records whether the child was offered a Return Interview after their missing episode. Y/N/NA/NULL	AnnexA
MISS007A	miss_missing_rhi_accepted	Records whether the child accepted the Return Interview offered after their missing episode. Y/N/NA/NULL	AnnexA

Object name: ssd_legal_status

Item Ref	Data Item Name	Guidance	Returns	Change Log
LEGA001A	lega_legal_status_id	Row identifier for the ssd_legal_status table	Local
LEGA002A	lega_person_id	Person's ID generated in CMS Database	Local
LEGA003A	lega_legal_status	Legal Status type. If a child is looked-after because it is accommodated, the legal status goes some way to describe (in legal terms at least) why the child is being looked after. There are many legal statuses arising from the Children Act, or the Youth Justice System, to which a child can be subject, but which have no bearing on whether a child is ‘looked-after’ or not. These are included in the SSD extract despite not being rerutned in the SSDA903. These incude statuses for permanence orders, e.g. Special Guardianship and Child Arrangement Orders, as well as Private Fostering and Care Leaver legal stauses, among others.	SSDA903, AnnexA, RIIA
LEGA004A	lega_legal_status_start_date	Start Date of Legal Status	RIIA
LEGA005A	lega_legal_status_end_date	End Date of Legal Status	RIIA

Object name: ssd_s251_finance

Item Ref	Data Item Name	Guidance	Returns	Change Log
S251001A	s251_table_id	(currently 'PLACEHOLDER_DATA' pending further development) Row identifier for the ssd_s251_finance table	1aDraft
S251002A	s251_cla_placement_id	(currently 'PLACEHOLDER_DATA' pending further development) ID for linking to CLA Placement	1aDraft
S251003A	s251_placeholder_1	(currently 'PLACEHOLDER_DATA' pending further development) No guidance available yet	1aDraft
S251004A	s251_placeholder_2	(currently 'PLACEHOLDER_DATA' pending further development) No guidance available yet	1aDraft
S251005A	s251_placeholder_3	(currently 'PLACEHOLDER_DATA' pending further development) No guidance available yet	1aDraft
S251006A	s251_placeholder_4	(currently 'PLACEHOLDER_DATA' pending further development) No guidance available yet	1aDraft

Object name: ssd_person

Item Ref	Data Item Name	Guidance	Returns	Change Log
PERS001A	pers_person_id	Person's ID generated by current CMS Database. This must be a unique ID for each child (no longer than 20 characters) and should be retained from year to year. A person|child ID should not be reused after a period of time, it should be unique to a single child in your local authority. It can include alphabetic and numeric characters. Do not use non-numeric or non-alphabetic characters. If a looked-after child is adopted, and subsequently becomes looked-after again later, they should have two separate unlinked records – one for pre-adoption and one for post-adoption – with two different child identifiers.	SSDA903, CIN, AnnexA, RIIA, SEN2
PERS002A	pers_sex	Person's Sex, as recorded on a birth certificate or in a gender recognition certificate. Code set F - Female M - Male U - Unknown	SSDA903, RIIA, AnnexA, SEN2
PERS003A	pers_gender	A person’s inner concept of self as male, female, neither or a blend of both. Code set 00 - Not known (for example, question has not been asked, answer was refused) 01 - Man / Boy / Male [systems should display the most appropriate value, e.g. Boy for children, Man for adults, Male if preferred] 02 - Woman / Girl / Female [systems should display the most appropriate value, e.g. Girl for children, Woman for adults, Female if preferred] 09 - Prefer to Self-Describe Codes 10 to 99 to be available for local use but to be regarded as subcodes of 9 (Other). Free text field or locally defined codes to be available for recording individual’s identification where ‘Prefer to Self-Describe’ has been chosen. While there are no plans to transfer this data it is envisaged that, if transfer of codes were to be implemented, only code ‘9’ would be transferred rather than codes ‘11’, ‘12’ etc.	CIN, RIIA
PERS004A	pers_ethnicity	Person's Ethnicity. This information must come from the child, or the parent, guardian or carer. Where the ethnicity has not yet been collected, this is recorded as ‘NOBT’ (information not yet obtained). Where a child, parent, guardian or carer declines to provide ethnicity data, code ‘REFU’ (refused) is recorded. Ethnicity should be recorded using one of the DfE main categories shown below, which replicate those used in the school census and the children in need (CIN) return. Code set WBRI - White British WIRI - White Irish WOTH - Any other White background WIRT - Traveller of Irish Heritage WROM - Gypsy/Roma MWBC - White and Black Caribbean MWBA - White and Black African MWAS - White and Asian MOTH - Any other Mixed background AIND - Indian APKN - Pakistani ABAN - Bangladeshi CNHE - Chinese AOTH - Any other Asian background BCRB - Caribbean BAFR - African BOTH - Any other Black background OOTH - Any other ethnic group REFU - Refused NOBT - Information not yet obtained	SSDA903, CIN, AnnexA, RIIA, SEN2
PERS005A	pers_dob	Person's date of birth. Either Date of Birth or Expected Date of Birth should be recorded, but not both. If the exact day of birth is not known: Unknown dates can be a problem for unaccompanied asylum-seeking children, If the day of birth is not known then assume that it was the 15th of the month. Do not use first day of the month as a dummy date of birth.	SSDA903, CIN, AnnexA, RIIA, SEN2
PERS013A	pers_common_child_id	This is a lifetime national identifier allocated from birth, or when a person registers with the NHS for the first time (England, Isle of Man and Wales). Allocated by the PDS, the first nine digits are the identifier and the tenth helps the number test its own validity.	Local
PERS014A	pers_legacy_id	This secondary person identifier follows the same specification as per_person_id and can be used to carry over legacy systems person_ids where maintaining this underpins existing or legacy reporting mechanisms.	Local
PERS007A	pers_upn_unknown	If the UPN is unknown, then one of the codes below should be used. If a child is educated outside England, please use UPN unknown code UN3, unless the child has a UPN from previously attending a school in England. If the child is home educated and has previously attended a mainstream school, please provide the UPN allocated earlier. Code set UN1 - Child looked-after is not of school age and has not yet been assigned a UPN UN2 - Child looked-after has never attended a maintained school in England (for example, some unaccompanied asylum-seeking children (UASC)) UN3 - Child looked-after is educated outside England UN4 - Child is newly looked-after and the UPN is not yet known UN5 - Sources collating UPNs reflect discrepancy(ies) for the child's name and/or surname and/or date of birth therefore preventing reliable matching (for example, duplicated UPNs)	RIIA, CIN, SEN2
PERS008A	pers_send_flag	Flag showing if a person has an EHC plan recorded on the system. Code set Y - Has an EHC Plan N - Does not have an EHC Plan	NEETandparticipation, RIIA
PERS009A	pers_expected_dob	The expected date of birth (due date) is recorded for a child who is unborn at the time of referral. If the child is born before the case is closed, then the actual date of birth should be recorded. If a child is stillborn, or the mother suffers a miscarriage (including a chemical pregnancy) or a phantom pregnancy, or there is a termination of the pregnancy, please record the expected date of birth and leave the date of birth blank. The children in need (CIN) closure date does not need to match the date on the death certificate. The date of death and the final closure date can both be recorded. The reason for CIN closure should be recorded as ‘RC2 died’.	CIN, RIIA
PERS010A	pers_death_date	Date of death, which should be verified from the death certificate.	CIN, RIIA
PERS011A	pers_is_mother	Calculated within the SSD extract based on if a parent-child relationship exists for persons with a sex code other than Male (i.e. Female or Unknown). A child will be classified as a mother even if they do not care for the child themselves (for example, if consent was given for the child to be adopted). Code set N - Child is not a mother Y - Child is a mother	SSDA903, RIIA
PERS012A	pers_nationality	Required for UASC, reported in the ADCS Safeguarding Pressures research.	ADCS_SP, RIIA

Object name: ssd_cp_visits

Item Ref	Data Item Name	Guidance	Returns	Change Log
CPPV007A	cppv_cp_visit_id	Row identifier for the ssd_cp_visits table	Local
CPPV008A	cppv_person_id	Person's ID generated in CMS Database	Local
CPPV001A	cppv_cp_plan_id	ID for linking to the CP Plan	Local
CPPV003A	cppv_cp_visit_date	Actual date of Visit	AnnexA
CPPV004A	cppv_cp_visit_seen	Was the child seen during this visit? Y/N	Local
CPPV005A	cppv_cp_visit_seen_alone	Was the child seen alone during this visit? Y/N	AnnexA
CPPV006A	cppv_cp_visit_bedroom	Was the child's bedroom seen during this visit? Y/N	Local

Object name: ssd_s47_enquiry

Item Ref	Data Item Name	Guidance	Returns	Change Log
S47E001A	s47e_s47_enquiry_id	Row identifier for the ssd_s47_enquiry table.	Local
S47E010A	s47e_referral_id	ID for linking to CIN Referral Episode	Local
S47E002A	s47e_person_id	Person's ID generated in CMS Database	Local
S47E004A	s47e_s47_start_date	Date of the strategy discussion at which the Section 47 Enquiries were initiated.	CIN, RIIA, AnnexA
S47E005A	s47e_s47_end_date	The actual date on which the S47 Enquiry is completed and authorised.	RIIA, AnnexA
S47E006A	s47e_s47_nfa	Standalone field showing whether or not the S47 Enquiry resulted in No Further Action.	AnnexA
S47E007A	s47e_s47_outcome_json	Outcome of the Section 47 Enquiry. Combined dictionary/ json type containing the following, AS s47e_s47_outcome_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { NFA_FLAG: "", LEGAL_ACTION_FLAG: "", PROV_OF_SERVICES_FLAG: "", PROV_OF_SB_CARE_FLAG: "", CP_CONFERENCE_FLAG: "", NFA_CONTINUE_SINGLE_FLAG: "", MONITOR_FLAG: "", OTHER_OUTCOMES_EXIST_FLAG: "", TOTAL_NO_OF_OUTCOMES: , OUTCOME_COMMENTS: "" }	Local
S47E008A	s47e_s47_completed_by_worker_id	Section 47 Enquiry completed by Worker	Local
S47E009A	s47e_s47_completed_by_team	Section 47 Enquiry completed by Team	Local

Object name: ssd_involvements

Item Ref	Data Item Name	Guidance	Returns	Change Log
INVO005A	invo_involvements_id	Row identifier for the ssd_involvements table	Local
INVO006A	invo_professional_id	ID for linking to ssd_professionals table	Local
INVO007A	invo_professional_role_id	Role of the professional/ team working with the child/ young person	Local
INVO009A	invo_professional_team	Name of the Team working with the child/ young person	AnnexA
INVO002A	invo_involvement_start_date	Start Date for team/ worker involvement	RIIA
INVO003A	invo_involvement_end_date	End Date for team/ worker involvement	RIIA
INVO004A	invo_worker_change_reason	Reason for change of Social Worker Code set MANAGE - Managing Caseloads FCONTA - First contact or re-referral LEFTRL - Previous social worker left role ORGRST - New social worker assigned following organisational restructure TSPROC - New social worker assigned following child transfer due to standard process ABSENC - Absence cover or return from absence CHCHAN - Child requested change from previous social worker PCCHAN - Parent/carer requested change from previous social worker SWDIED - Previous Social Worker died OTHERS - Other reason	RIIA
INVO011A	invo_person_id	Person's ID generated in CMS Database	Local
INVO010A	invo_referral_id	ID for linking to CIN Referral Episode	Local

Object name: ssd_version_log

Item Ref	Data Item Name	Guidance	Returns	Change Log
VERS1001A	version_number	SSD ADMIN only table/field
VERS1002A	release_date	SSD ADMIN only table/field
VERS1003A	description	SSD ADMIN only table/field
VERS1004A	is_current	SSD ADMIN only table/field
VERS1005A	created_at	SSD ADMIN only table/field
VERS1006A	created_by	SSD ADMIN only table/field
VERS1007A	impact_description	SSD ADMIN only table/field

Object name: ssd_cin_plans

Item Ref	Data Item Name	Guidance	Returns	Change Log
CINP001A	cinp_cin_plan_id	Row identifier for the ssd_cin_plans table.	RIIA
CINP007A	cinp_referral_id	ID for linking to CIN Referral Episode	Local
CINP002A	cinp_person_id	Person's ID generated in CMS Database	Local
CINP003A	cinp_cin_plan_start_date	Start Date of CIN Plan A CIN plan should be developed where the outcome of an assessment is that a local authority children’s social care should provide services. The CIN plan sets out which organisations and agencies will provide which services to the child and family. The plan should also set clear measurable outcomes for the child and expectations for the parent(s) or carer(s). More information on CIN plans is provided in ‘Working together to safeguard children’. A child can have one, more than one or no CIN plan(s) – but can only have one at a time. CIN plans do not include other plans such as leaving care support or adoption support.	CIN, RIIA, AnnexA
CINP004A	cinp_cin_plan_end_date	End Date of CIN Plan A CIN plan should be developed where the outcome of an assessment is that a local authority children’s social care should provide services. The CIN plan sets out which organisations and agencies will provide which services to the child and family. The plan should also set clear measurable outcomes for the child and expectations for the parent(s) or carer(s). More information on CIN plans is provided in ‘Working together to safeguard children’. A CIN plan should be recorded as ended when the period of the CIN plan ends. This may be because the child becomes the subject of a child protection plan; the child becomes looked after; or the child ceases receiving support from children’s social services (due to no longer needing support, being stepped down to early help, or reaching adulthood). A child can have one, more than one or no CIN plan(s) – but can only have one at a time. CIN plans do not include other plans such as leaving care support or adoption support.	RIIA, CIN, AnnexA
CINP005A	cinp_cin_plan_team	Team responsible for CIN Plan	AnnexA, RIIA
CINP006A	cinp_cin_plan_worker_id	Worker responsible for CIN Plan	AnnexA, RIIA

Object name: ssd_cla_convictions

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAC001A	clac_cla_conviction_id	Row identifier for the ssd_cla_convictions table	Local
CLAC002A	clac_person_id	Person's ID generated in CMS Database	Local
CLAC003A	clac_cla_conviction_date	Date of Offence	SSDA903
CLAC004A	clac_cla_conviction_offence	Details of offence committed.	Local

Object name: ssd_mother

Item Ref	Data Item Name	Guidance	Returns	Change Log
MOTH004A	moth_table_id	Row identifier for the ssd_mother table	Local
MOTH002A	moth_person_id	Person's ID generated in CMS Database	Local
MOTH001A	moth_childs_person_id	The unique identifier of the mother's child.	Local
MOTH003A	moth_childs_dob	The SSD will include all children for each mother. This information is only currently collected in the SSDA903 (CLA) return where the DOB of the mother's first child is required.	SSDA903, AnnexA

Object name: ssd_cla_previous_permanence

Item Ref	Data Item Name	Guidance	Returns	Change Log
LAPP001A	lapp_table_id	Row identifier for the ssd_previous_permanence table	Local
LAPP002A	lapp_person_id	Person's ID generated in CMS Database	Local
LAPP003A	lapp_previous_permanence_order_date	Date of the previous permanence order, if known. In line with the SSDA903 guidance, if the exact date is unknown, the month and year are recorded in the form zz/MM/YYYY, using zz as the day, for example for May 2020 with the exact date being unknown enter zz/05/2020. If the month is unknown, the year is recorded in the form zz/zz/YYYY, for example, where the year of 2021 only is known enter zz/zz/2021. If no information is known about the date of the order, the date is recorded as zz/zz/zzzz.	SSDA903
LAPP004A	lapp_previous_permanence_option	This should be completed for all children who start to be looked-after. Information is collected for children who previously ceased to be looked-after due to the granting of an adoption order, a special guardianship order, residence order (until 22 April 2014) or a child arrangement order. Code set P1 - Adoption P2 - Special guardianship order (SGO) P3 - Residence order (RO) or child arrangements order (CAO) which sets out with whom the child is to live. P4 - Unknown Z1 - Child has not previously had a permanence option P4 should be used when it is not known to the local authority whether the child had a previous permanence option. This information can be updated if information comes to light at any stage in an episode of care. Do not include any adoptions/SGO/ROs/CAOs previously granted where the child was not previously looked-after.	SSDA903
LAPP005A	lapp_previous_permanence_la	The name of the local authority who arranged the previous permanence option.	SSDA903

Object name: ssd_initial_cp_conference

Item Ref	Data Item Name	Guidance	Returns	Change Log
ICPC001A	icpc_icpc_id	Row identifier for the ssd_initial_cp_conference table	Local
ICPC009A	icpc_icpc_meeting_id	Identifier for the Initial CP Conference Meeting	Local
ICPC002A	icpc_s47_enquiry_id	ID for linking to Section 47 Enquiry	RIIA
ICPC010A	icpc_person_id	Person's ID generated in CMS Database	Local
ICPC011A	icpc_cp_plan_id	CP Plan ID for ICPC's resulting in a CP Plan	RIIA, AnnexA
ICPC012A	icpc_referral_id	ID for linking to CIN Referral Episode	Local
ICPC003A	icpc_icpc_transfer_in	Is this is a transfer in ICPC? Y/N	RIIA, AnnexA
ICPC004A	icpc_icpc_target_date	The date that is 15 working days after the strategy discussion at which section 47 enquiries were initiated.	CIN
ICPC005A	icpc_icpc_date	The date on which the initial child protection conference took place.	CIN, RIIA, AnnexA
ICPC013A	icpc_icpc_outcome_cp_flag	Standalone field showing whether or not the ICPC resulted in a CP Plan	AnnexA
ICPC006A	icpc_icpc_outcome_json	Outcome of the Initial CP Conference. Combined dictionary/ json type containing the following, AS icpc_icpc_outcome_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { NFA_FLAG: "", REFERRAL_TO_OTHER_AGENCY_FLAG: "", SINGLE_ASSESSMENT_FLAG: "", PROV_OF_SERVICES_FLAG: "", CP_FLAG: "", OTHER_OUTCOMES_EXIST_FLAG: "", TOTAL_NO_OF_OUTCOMES: , COMMENTS: "" }	AnnexA, RIIA
ICPC007A	icpc_icpc_team	Team responsible for organising ICPC	AnnexA, RIIA
ICPC008A	icpc_icpc_worker_id	Worker who organised the ICPC	AnnexA, RIIA

Object name: ssd_cla_episodes

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAE001A	clae_cla_episode_id	Row identifier for the ssd_cla_episodes table	RIIA
CLAE002A	clae_person_id	Person's ID generated in CMS Database	Local
CLAE003A	clae_cla_episode_start_date	The date that CLA Episode began.	SSDA903, RIIA, AnnexA
CLAE004A	clae_cla_episode_start_reason	Code Set S - Started to be looked after L - Change of legal status only P - Change of placement and carer(s) only T - Change of placement (but same carer(s)) only B - Change of legal status and placement and carer(s) at the same time U - Change of legal status and change of placement (but same carer(s)) at the same time Use Code S where a child is starting to be looked-after for the first time, or had previously ceased to be looked-after, and is now starting to be looked-after again. Also use code S when recording agreements to provide short-term placements (legal status V4), and for individual breaks under such an agreement, if these are being recorded separately (legal status V3). Use Code L where there is a change of legal status, but the placement does not change. By ‘legal status’ we mean the legal status underlying the fact that the child is looked-after. Use Code P where there is a change of placement and carer, but the legal status does not change. This would include the following scenarios: • Move from one foster carer to another foster carer (for example, U3 to another U3 placement type code). • Move from a foster carer to a children’s home (for example, U3 to K2 placement types). In both scenarios there has been a change of carer. When a child is living independently, a new episode should be created each time they move, and code P should be used. Use Code T where there is a change of placement, but the child remains with the same carer and the legal status does not change. This would include the following scenarios: • Child moves to a new house with current foster carer (either inside or outside of local authority boundary). • Child remains with same carer or within same setting but either the URN of the setting changes or the provider type changes (for example, a foster carer moves from an IFA to the local authority provider, or a placement for adoption transferring to a regional adoption agency, or an unregulated independent or semi independent setting registering with Ofsted). In both scenarios, the child has remained with the same carer, but for some other reason, a new placement is required on the SSDA903. Use Code B where both legal status and placement change, with a change of carer, on the same day. The two changes do not need to be simultaneous or consequent one upon the other. The code simply reflects that there was a change in carer and a change in legal status, for whatever reason, on the same day. Use Code U where both legal status and placement change on the same day, but the child remains with the same carer. The two changes do not need to be simultaneous or consequent one upon the other. The code simply reflects that there was a change in placement and a change in legal status, for whatever reason, on the same day.	SSDA903, RIIA
CLAE009A	clae_cla_primary_need_code	Category of need (CIN) codes record the main reason why a child is being provided with services. This provides a further insight as to why a particular child is being looked-after. Use the category of need code most relevant at the time the current period of being looked-after began. The category of need code relates to the reason the child originally became looked-after and should remain the same throughout their period of care. Code set N1 - Abuse or neglect Child in need as a result of, or at risk of, abuse or neglect. N2 - Child’s disability Child and their family whose main need for children’s social care services arises out of the child’s disabilities, illness or intrinsic condition N3 - Parental illness or disability Child whose main need for children’s social care services arises because the capacity of their parent(s) or carer(s) to care for them is impaired by disability, illness, mental illness, or addictions N4 - Family in acute stress Child whose needs arise from living in a family going through a temporary crisis such that parenting capacity is diminished and some of the children’s needs are not being adequately met N5 - Family dysfunction Child whose needs arise mainly out of their living with a family where the parenting capacity is chronically inadequate N6 - Socially unacceptable behaviour Child and family whose need for children’s social care services arises primarily out of their behaviour impacting detrimentally on the community N7 - Low income Child, either living in a family or independently, whose need for children’s social care services arises mainly from being dependent on an income below the standard state entitlements N8 - Absent parenting Child whose need for children’s social care services arises mainly from having no parent(s) available to provide for them. A child whose parent(s) decide it is in the best interest for the child to be adopted would be included in this category	SSDA903, AnnexA, RIIA
CLAE005A	clae_cla_episode_ceased	This item records the date that each episode ended. An episode cannot start and end on the same day. Where a child has not left care, a new episode must start on the same day as the previous episode finished. When a child ceases to be looked-after because of adoption (reason episode ceased codes of E11 or E12), the date episode ceased is the date the court makes the adoption order. When a child ceases to be looked-after because he/she dies whilst being looked-after (reason episode ceased code E2), the date episode ceased must be the same as the date of death as recorded on the death certificate.	SSDA903, AnnexA, RIIA
CLAE006A	clae_cla_episode_ceased_reason	When an episode has ended and a further episode, in the same period of care, has started, use the code, X1. All other ‘reason episode ceased’ codes record the circumstances when a child ceases to be looked-after. If a child ceases to be looked-after because he/she has turned 18, this can already be deduced from his/her date of birth. Therefore, the appropriate code below should be used to capture the destination of the young person. X1 - Episode ceases, and new episode begins on same day, for any reason E11 - Adopted - application for an adoption order unopposed E12 - Adopted – consent dispensed with by the court E2 - Died E3 - Care taken over by another local authority in the UK E4A - Returned home to live with parent(s), relative(s), or other person(s) with parental responsibility as part of the care planning process (not under a special guardianship order or residence order/ child arrangement order). E4B - Returned home to live with parent(s), relative(s), or other person(s) with parental responsibility which was not part of the current care planning process (not under a special guardianship order or residence order or (from 22 April 2014) a child arrangement order). E13 - Left care to live with parent(s), relative(s), or other person(s) with no parental responsibility. E41 - Residence order/ child arrangement order which sets out with whom the child is to live) granted E45 - Special guardianship order made to former foster carer(s), who was/are a relative(s) or friend(s) E46 - Special guardianship order made to former foster carer(s), other than relative(s) or friend(s) E47 - Special guardianship order made to carer(s), other than former foster carer(s), who was/are a relative(s) or friend(s) E48 - Special guardianship order made to carer(s), other than former foster carer(s), other than relative(s) or friend(s) E5 - Moved into independent living arrangement and no longer looked-after: supportive accommodation providing formalised advice/support arrangements (such as most hostels, young men’s Christian association, foyers, staying close and care leavers projects). Includes both children leaving care before and at age 18 E6 - Moved into independent living arrangement and no longer looked-after: accommodation providing no formalised advice/support arrangements (such as bedsit, own flat, living with friend(s)). Includes both children leaving care before and at age 18 E7 - Transferred to residential care funded by adult social care services E9 - Sentenced to custody E14 - Accommodation on remand ended E15 - Age assessment determined child is aged 18 or over and E5, E6 and E7 do not apply, such as an unaccompanied asylum-seeking child (UASC) whose age has been disputed E16 - Child moved abroad E17 - Aged 18 (or over) and remained with current carers (inc under staying put arrangements) E8 - Period of being looked-after ceased for any other reason (where none of the other reasons apply) Further detail on when some of the codes should be used is provided below: E4A - Relates to a planned move where the child returns home as part of their agreed care plan. This return home has been discussed as part of the care planning process and happens within a planned timeframe. E4B - Relates to an unplanned move - includes instances where the child’s return home is immediate (for example, within 24 hours) and has not been discussed as part of the care planning process or does not occur within the planned timeframe. This would include instances where a child under a voluntary arrangement is removed from care by their parents and this was not agreed as part of the care planning process. E13 - Left care to live with parents, relatives, or other person with no parental responsibility – this code should be used if the child left care to live with parents, relatives or another person, but this person did not have parental responsibility. E14 - Accommodation on remand ended – this code should be used if a child was remanded to youth detention accommodation and has stopped their episode of care because they are no longer remanded. E15 - Age assessment determined child is aged 18 or over and E5, E6 and E7 do not apply, for example, an unaccompanied asylum seeking child whose age has been disputed – this code should be used if the episode of care ended because the age was disputed, an assessment revealed the child was 18 or over and the young person was not transferred to residential care and did not move into independent living arrangements. E16 - Moved abroad – use this code if the child left care because they moved to another country, including when a child is deported. E17 - Aged 18 (or over) and remained with current carers (inc under staying put arrangements) – use this code whenever the young person has ceased care and remains with their former carers, irrespective of placement type. Young people in foster care who are ‘staying put’ are only a subset of this group. E8 - Period of being looked-after ceased for any other reason – this code should never be used purely because a child has reached the age of 18 as this can already be deduced from his/her date of birth. It should only be used when none of the alternative destinations listed are appropriate. E8 should also be used when a child turns 18 and continues to be missing. If a looked-after child is sentenced to custody and placed in a secure children’s home, secure training centre or young offenders’ institution, their status in that setting depends on the legislative framework under which the custodial sentence is applied. If the child is subject to a Care Order (Section 31 Children Act 1989) then they remain looked-after regardless of being sentenced to custody. If the child is accommodated in care by a voluntary agreement under Section 20 of the Children Act 1989, then they cease to be looked-after when they are admitted to custody.	SSDA903, AnnexA, RIIA
CLAE010A	clae_cla_id	System identifier for the whole period of care, encompassing all episodes included within that period of care.	Local
CLAE011A	clae_referral_id	ID for linking to CIN Referral Episode	Local
CLAE013A	clae_cla_placement_id	ID for linking to CLA Placement record	Local
CLAE014A	clae_entered_care_date	Start Date of the current Looked After period.	SSD903
CLAE012A	clae_cla_last_iro_contact_date	Date of Last IRO Visit/ Contact to the Child	AnnexA

Object name: ssd_sdq_scores

Item Ref	Data Item Name	Guidance	Returns	Change Log
CSDQ001A	csdq_table_id	Row identifier for the ssd_sdq_scores table	Local
CSDQ002A	csdq_person_id	Person's ID generated in CMS Database	Local
CSDQ003A	csdq_sdq_completed_date	Date of completion of Strength and Difficulties Questionnaire (SDQ)	Local
CSDQ004A	csdq_sdq_reason	(currently 'PLACEHOLDER_DATA' pending further development) If it is not possible to collect the SDQ score for a looked-after child, then a reason should be recorded using the codes below. Code set SDQ1 - No form returned as child was aged under 4 or over 16 at date of latest assessment SDQ2 - Carer(s) refused to complete and return questionnaire SDQ3 - Not possible to complete the questionnaire due to severity of the child’s disability SDQ4 - Other SDQ5 - Child or young person refuses to allow a strengths and difficulties questionnaire (SDQ) to be completed	SSDA903
CSDQ005A	csdq_sdq_score	A single score (0–40), or a reason for the score not being returned is required for each child looked-after continuously for at least 12 months aged 4–16 on the date of the last assessment.	SSDA903

Object name: ssd_family

Item Ref	Data Item Name	Guidance	Returns	Change Log
FAMI003A	fami_table_id	Row identifier for the ssd_family table	Local
FAMI001A	fami_family_id	For linking to adoptive family or Family-level interventions e.g. Early Help	ASGLB, AnnexA
FAMI002A	fami_person_id	Person's ID generated in CMS Database	Local

Object name: ssd_cin_assessments

Item Ref	Data Item Name	Guidance	Returns	Change Log
CINA001A	cina_assessment_id	Row identifier for the ssd_cin_assessments table.	CIN, RIIA
CINA002A	cina_person_id	Person's ID generated in CMS Database	Local
CINA010A	cina_referral_id	ID for linking to CIN Referral Episode	Local
CINA003A	cina_assessment_start_date	This is the actual start date of the continuous assessment.	CIN, RIIA
CINA004A	cina_assessment_child_seen	Was the child seen during the Assessment process?	AnnexA, RIIA
CINA005A	cina_assessment_auth_date	This is the date the assessment is completed and authorised. An assessment is deemed to be completed once the social worker has informed, in writing, all the relevant agencies and the family of their decisions and if the child is a child in need, of the plan for providing support/ or once the assessment has been discussed with the child’s family (or carers) and the team manager has viewed and authorised the assessment.	CIN, RIIA, AnnexA
CINA006A	cina_assessment_outcome_json	Outcome of the single assessment. Combined dictionary/ json type containing the following AS cina_assessment_outcome_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { NFA_FLAG: "", NFA_S47_END_FLAG: "", STRATEGY_DISCUSSION_FLAG: "", CLA_REQUEST_FLAG: "", PRIVATE_FOSTERING_FLAG: "", LEGAL_ACTION_FLAG: "", PROV_OF_SERVICES_FLAG: "", PROV_OF_SB_CARE_FLAG: "", SPECIALIST_ASSESSMENT_FLAG: "", REFERRAL_TO_OTHER_AGENCY_FLAG: "", OTHER_ACTIONS_FLAG: "", OTHER_OUTCOMES_EXIST_FLAG: "", TOTAL_NO_OF_OUTCOMES: , COMMENTS: "" }	AnnexA, RIIA
CINA009A	cina_assessment_outcome_nfa	Standalone field showing whether or not the Assessment resulted in No Further Action.	CIN, RIIA, AnnexA
CINA007A	cina_assessment_team	Team responsible for completing the Assessment	AnnexA, RIIA
CINA008A	cina_assessment_worker_id	Worker responsible for completing the Assessment	AnnexA, RIIA

Object name: ssd_cla_health

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAH001A	clah_health_check_id	Row identifier for the ssd_cla_health table	Local
CLAH002A	clah_person_id	Person's ID generated in CMS Database	Local
CLAH003A	clah_health_check_type	Health Check/ Assessment Type e.g. Health Assessment, Dental Check	SSDA903, AnnexA
CLAH004A	clah_health_check_date	Date of Health Check/ Assessment	SSDA903, AnnexA
CLAH005A	clah_health_check_status	Status of Health Check Code set Planned Refused Cancelled Completed	SSDA903, AnnexA

Object name: ssd_voice_of_child

Item Ref	Data Item Name	Guidance	Returns	Change Log
VOCH007A	voch_table_id	(currently 'PLACEHOLDER_DATA' pending further development) Row identifier for the ssd_voice_of_child table	1bDraft
VOCH001A	voch_person_id	(currently 'PLACEHOLDER_DATA' pending further development) Person's ID generated in CMS Database	Local
VOCH002A	voch_explained_worries	(currently 'PLACEHOLDER_DATA' pending further development) Child answer from questionnaire	1bDraft	release: In review|pending change_id: SSD-0023 change_source: 1bDraft versions_count: 1 impact_title: None type: New Feature
VOCH003A	voch_story_help_understand	(currently 'PLACEHOLDER_DATA' pending further development) Child answer from questionnaire	1bDraft	release: In review|pending change_id: SSD-0024 change_source: 1bDraft versions_count: 1 impact_title: None type: New Feature
VOCH004A	voch_agree_worker	(currently 'PLACEHOLDER_DATA' pending further development) Child answer from questionnaire	1bDraft	release: In review|pending change_id: SSD-0025 change_source: 1bDraft versions_count: 1 impact_title: None type: New Feature
VOCH005A	voch_plan_safe	(currently 'PLACEHOLDER_DATA' pending further development) Child answer from questionnaire	1bDraft	release: In review|pending change_id: SSD-0026 change_source: 1bDraft versions_count: 1 impact_title: None type: New Feature
VOCH006A	voch_tablet_help_explain	(currently 'PLACEHOLDER_DATA' pending further development) Child answer from questionnaire	1bDraft	release: In review|pending change_id: SSD-0027 change_source: 1bDraft versions_count: 1 impact_title: None type: New Feature

Object name: ssd_immigration_status

Item Ref	Data Item Name	Guidance	Returns	Change Log
IMMI001A	immi_person_id	Person's ID generated in CMS Database	Local
IMMI005A	immi_immigration_status_id	Row identifier for the ssd_immigration_status table	Local
IMMI002A	immi_immigration_status	Immigration Status e.g. Unaccompanied Asylum Seeking Child	SSDA903, RIIA, AnnexA
IMMI003A	immi_immigration_status_start_date	Start Date of Immigration Status	RIIA
IMMI004A	immi_immigration_status_end_date	End Date of Immigration Status	SSDA903, RIIA

Object name: ssd_ehcp_active_plans

Item Ref	Data Item Name	Guidance	Returns	Change Log
EHCP001A	ehcp_active_ehcp_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP active plan unique ID from system or auto-generated as part of export.	1aNotInCMS
EHCP002A	ehcp_ehcp_request_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP request record unique ID from system or auto-generated as part of export.	1aNotInCMS
EHCP003A	ehcp_active_ehcp_last_review_date	(currently 'PLACEHOLDER_DATA' pending further development) Please enter the date when the local authority wrote to the parent or young person with the notification of the decision as to whether to retain, cease or amend the plan following the annual review meeting. Note that this date will not be the same as the date of the review meeting.	1aNotInCMS, SEN2

Object name: ssd_cla_care_plan

Item Ref	Data Item Name	Guidance	Returns	Change Log
LACP001A	lacp_table_id	Row identifier for the ssd_cla_care_plan table	Local
LACP007A	lacp_person_id	Person's ID generated in CMS Database	Local
LACP004A	lacp_cla_care_plan_start_date	Date the care plan was effective from	Local
LACP005A	lacp_cla_care_plan_end_date	Date the care plan was effective to	Local
LACP003A	lacp_cla_care_plan_json	The current permanence plan for the child. Combined dictionary/ json type containing the following, REMAINSUP - Remaining with birth family supported by shared care/short term breaks RETURN1M - Return to birth family within one month RETURN6M - Return to birth family within six months RETURNEV - Eventual return to birth family (record number of months below) LTRELFR - Long term placement with relatives/friends LTFOST18 - Long term placement with foster carers (intended to last until 18, no return home envisaged) RESPLMT - Residential placement until independence SUPPLIV - Supported living in the community (with a view to independence) ADOPTION - Adoption OTHERPLN - Other Plan Where the child does not have a permanence plan agreed (such as recently entered care) please leave blank. More than one box might be ticked if parallel planning is being pursued AS lacp_cla_care_plan_json --------------------------------------- -- SSD standard - all keys in structure regardless of data presence { REMAINSUP: "", RETURN1M: "", RETURN6M: "", RETURNEV: "", LTRELFR: "", LTFOST18: "", RESPLMT: "", SUPPLIV: "", ADOPTION: "", OTHERPLN: "" }	AnnexA

Object name: ssd_cla_reviews

Item Ref	Data Item Name	Guidance	Returns	Change Log
CLAR001A	clar_cla_review_id	Row identifier for the ssd_cla_reviews table	Local
CLAR011A	clar_cla_id	System identifier for the whole period of care, encompassing all episodes included within that period of care.	Local
CLAR003A	clar_cla_review_due_date	Date the CLA review was due	Local
CLAR004A	clar_cla_review_date	Actual date of the Review conference	SSDA903, AnnexA
CLAR012A	clar_cla_review_cancelled	Flag showing if the review was Cancelled. Y/N	Local
CLAR007A	clar_cla_review_participation	The Child/ Young Person's method of participation in each review. PN0 - Child aged under 4 at the time of the review PN1 - Child physically attends and speaks for him or herself (Attendance). PN2 - Child physically attends and an advocate speaks on his or her behalf. (Attendance views represented by advocate or Independent Reviewing Officer (IRO)) PN3 - Child attends and conveys his or her view symbolically (non-verbally) (Attendance symbols) PN4 - Child physically attends but does not speak for him or herself, does not convey his or her view symbolically (non-verbally) and does not ask an advocate to speak for him or her (Attendance without contribution) PN5 - Child does not attend physically but briefs an advocate to speak for him or her (Views represented by advocate or independent reviewing officer (IRO) through texting, written format, phone, audio/video, viewpoint) PN6 - Child does not attend but conveys his or her feelings to the review by a facilitative medium (Texting the chair, written format, phone, audio/video, viewpoint) PN7 - Child does not attend nor are his or her views conveyed to the review	SSDA903

Object name: ssd_early_help_episodes

Item Ref	Data Item Name	Guidance	Returns	Change Log
EARL001A	earl_episode_id	Row identifier for the ssd_early_help_episodes table	Local
EARL002A	earl_person_id	Person's ID generated in CMS Database	Local
EARL003A	earl_episode_start_date	Date Episode Started	AnnexA, RIIA
EARL004A	earl_episode_end_date	Date Episode Ended	AnnexA, RIIA
EARL005A	earl_episode_reason	Broad categorisation of Reason for Early Help Involvement.	ADCS_SP, RIIA
EARL006A	earl_episode_end_reason	Reason Episode endeed e.g. Outcomes met/ Step-up/ NFA	ADCS_SP, RIIA
EARL007A	earl_episode_organisation	Organisation responsible for Early Help provision	AnnexA, RIIA
EARL008A	earl_episode_worker_id	Allocated worker responsible for Early Help provision	RIIA

Object name: ssd_ehcp_requests

Item Ref	Data Item Name	Guidance	Returns	Change Log
EHCR001A	ehcr_ehcp_request_id	(currently 'PLACEHOLDER_DATA' pending further development) EHCP request record unique ID from system or auto-generated as part of export.	1aNotInCMS, RIIA
EHCR002A	ehcr_send_table_id	(currently 'PLACEHOLDER_DATA' pending further development) ID for linking to ssd_send table	1aNotInCMS
EHCR003A	ehcr_ehcp_req_date	(currently 'PLACEHOLDER_DATA' pending further development) The date the request for an EHC assessment was received. This will be the date used as the start of the 20-week period.	1aNotInCMS, SEN2, RIIA, SEN2
EHCR004A	ehcr_ehcp_req_outcome_date	(currently 'PLACEHOLDER_DATA' pending further development) Please enter the date the requestor(s) was informed of the decision about whether the local authority agrees to the request for an assessment. If the request was withdrawn or ceased before decision (W), if the decision is yet to be made (A) or is historical (H) then no date is required.	1aNotInCMS, SEN2, RIIA, SEN2
EHCR005A	ehcr_ehcp_req_outcome	(currently 'PLACEHOLDER_DATA' pending further development) This item records whether or not the initial request proceeded to the assessment stage: Y - LA proceeded with an assessment N - LA decided not to proceed with an assessment A - Decision yet to be made W – Request withdrawn or ceased before decision to assess was made H – Historical – Decision to assess was made before the latest collection period If a local authority decides not to proceed with an assessment and this decision is subsequently changed for any reason the original request outcome and request outcome date should not be changed. If the change follows from mediation or tribunal the appropriate mediation and tribunal indicators (items 2.5 and 2.6) should be selected for the request. W may include where the person moves out of the local authority area, leaves education or training, or if the child or young person dies. When A, W or H is selected, no further information is required in this module.	1aNotInCMS, SEN2, RIIA, SEN2

Object name: ssd_pre_proceedings

Item Ref	Data Item Name	Guidance	Returns	Change Log
PREP024A	prep_table_id	(currently 'PLACEHOLDER_DATA' pending further development) Row identifier for the ssd_pre_proceedings table	1bSpecified
PREP001A	prep_person_id	(currently 'PLACEHOLDER_DATA' pending further development) Person's ID generated in CMS Database	Local
PREP002A	prep_plo_family_id	(currently 'PLACEHOLDER_DATA' pending further development) Unique Identifier number for each family group - a family group is described as a group of children linked by parents all starting and ceasing pre or care proceedings at the same time	1bSpecified	release: In review|pending change_id: SSD-0001 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP003A	prep_pre_pro_decision_date	(currently 'PLACEHOLDER_DATA' pending further development) This is the date of legal meeting / panel that agreed to commence pre-proceedings. The date should be recorded in a DD/MM/YYYY format, i.e. day/month/year as a four digit number.	1bSpecified	release: In review|pending change_id: SSD-0002 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP004A	prep_initial_pre_pro_meeting_date	(currently 'PLACEHOLDER_DATA' pending further development) This is the first pre-proceedings meeting following the legal meeting / panel that agreed to commence pre-proceedings. The date should be recorded in a DD/MM/YYYY format, i.e. day/month/year as a four digit number.	1bSpecified	release: In review|pending change_id: SSD-0003 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP005A	prep_pre_pro_outcome	(currently 'PLACEHOLDER_DATA' pending further development) Please select: Decision to Issue Care Proceedings / Decision to step down If still in pre-proceedings, please leave blank.	1bSpecified	release: In review|pending change_id: SSD-0004 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP006A	prep_agree_stepdown_issue_date	[Guidance text replicated from related stat-return field(s). Thus may not be entirely applicable to this data item within the SSD. A review of item/field guidance notes towards the SSD is in progress.]This is the date of legal meeting / panel that agreed to end pre-proceedings to either step down or issue care proceedings. The date should be recorded in a DD/MM/YYYY format, i.e. day/month/year as a four digit number.	1bSpecified	release: In review|pending change_id: SSD-0005 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP007A	prep_cp_plans_referral_period	(currently 'PLACEHOLDER_DATA' pending further development) Please provide a numeric value for the number of the times the child has been the subject of a Child Protection Plan during this referral period. If none, please put 0.	1bSpecified	release: In review|pending change_id: SSD-0006 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP008A	prep_legal_gateway_outcome	(currently 'PLACEHOLDER_DATA' pending further development) Please select one of these options: A – Continue with current plan B – Start pre-proceedings C – Issue care proceedings D – Unknown	1bSpecified	release: In review|pending change_id: SSD-0007 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP009A	prep_prev_pre_proc_child	(currently 'PLACEHOLDER_DATA' pending further development) Please provide a numeric value. If there have not been any previous periods, please put 0.	1bSpecified	release: In review|pending change_id: SSD-0008 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP010A	prep_prev_care_proc_child	(currently 'PLACEHOLDER_DATA' pending further development) Please provide a numeric value. If there have not been any previous periods, please put 0.	1bSpecified	release: In review|pending change_id: SSD-0009 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP011A	prep_pre_pro_letter_date	(currently 'PLACEHOLDER_DATA' pending further development) If the case has not been in pre-proceedings, please leave blank. Please use the UK date format: DD/MM/YYYY	1bSpecified	release: In review|pending change_id: SSD-0010 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP012A	prep_care_pro_letter_date	(currently 'PLACEHOLDER_DATA' pending further development) If care proceedings have not been issued, please leave blank. Please use the UK date format DD/MM/YYYY	1bSpecified	release: In review|pending change_id: SSD-0011 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP013A	prep_pre_pro_meetings_num	(currently 'PLACEHOLDER_DATA' pending further development) Please give a numeric value for the number of meetings that took place with parents, excluding the initial meeting.	1bSpecified	release: In review|pending change_id: SSD-0012 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP014A	prep_pre_pro_parents_legal_rep	(currently 'PLACEHOLDER_DATA' pending further development) Please select Yes / No / Unknown	1bSpecified	release: In review|pending change_id: SSD-0013 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP015A	prep_parents_legal_rep_point_of_issue	(currently 'PLACEHOLDER_DATA' pending further development) Please select Yes / No / Unknown / Not in care proceedings	1bSpecified	release: In review|pending change_id: SSD-0014 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP016A	prep_court_reference	(currently 'PLACEHOLDER_DATA' pending further development) This is the Court number which is given to a family group when care proceedings are issued. This may be stored on the case management system or held in legal files. If the case is not in care proceedings, please leave blank.	1bSpecified	release: In review|pending change_id: SSD-0015 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP017A	prep_care_proc_court_hearings	(currently 'PLACEHOLDER_DATA' pending further development) This includes the initial IRH and final hearing. Please give a numeric value. If case is not in care proceedings, please leave blank.	1bSpecified	release: In review|pending change_id: SSD-0016 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP018A	prep_care_proc_short_notice	(currently 'PLACEHOLDER_DATA' pending further development) Please select Yes / No / Unknown / Not in care proceedings. A short notice application is an urgent application for the court to hear the case within the next 2 – 5 days.	1bSpecified	release: In review|pending change_id: SSD-0017 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP019A	prep_proc_short_notice_reason	(currently 'PLACEHOLDER_DATA' pending further development) Please choose the main reason from this list: (A) Applications under the Children Act 1989 where without such an order a child’s immediate safety would be compromised, including where there is an immediate threat of child abduction. (B) Applications for Emergency Protection Orders where the criteria for such or order is met. (c) Other If a short notice application has not taken place, please select 'No short notice applications'. A short notice application is an urgent application for the court to hear the case within the next 2 – 5 days.	1bSpecified	release: In review|pending change_id: SSD-0018 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP020A	prep_la_inital_plan_approved	(currently 'PLACEHOLDER_DATA' pending further development) Please select Yes / No / Unknown	1bSpecified	release: In review|pending change_id: SSD-0019 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP021A	prep_la_initial_care_plan	(currently 'PLACEHOLDER_DATA' pending further development) Please choose one option from this list: A – Interim / Care Order B – Interim / Care Order – Placement with parents C – Adoption D – Interim / Supervision Order E – Special Guardianship Order F – Private Law Order G – Other If case is not in care proceedings, please select 'Not in care proceedings' Please note ‘Care order – placement with parents’ means that the public care order was granted but that the child remained in their parent’s care, rather than in another placement.	1bSpecified	release: In review|pending change_id: SSD-0020 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP022A	prep_la_final_plan_approved	(currently 'PLACEHOLDER_DATA' pending further development) Please select Yes / No / Unknown	1bSpecified	release: In review|pending change_id: SSD-0021 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature
PREP023A	prep_la_final_care_plan	(currently 'PLACEHOLDER_DATA' pending further development) Please choose one option from this list: A – Care Order B – Care Order – Placement with parents C – Adoption D – Supervision Order E – Special Guardianship Order F – Private Law Order G – Other H – Not yet at final hearing - still in care proceedings If not yet at the final hearing, please select "Not yet at final hearing - still in care proceedings'. This will indicate that the case is still active in care proceedings.	1bSpecified	release: In review|pending change_id: SSD-0022 change_source: 1bSpecified versions_count: 1 impact_title: None type: New Feature