Transfers: How Downstream systems are updated

Overview of Transfer Process

Transfer children are synced downstream on Transfer Offer Acceptance

When a new transfer is accepted for a child, the child and parent records are created in the receiving service. The receiving service (downstream CRM) will have a task generated, with associated email alert, advising them of this new transfer child.

To ensure the receiving service is able to easily identify the child that is being transferred, the following fields are populated in their system:

When a child is created downstream on Transfer Accepted:

Field	Value
Form name to trigger workflow	Transferred child
First day at service	TY Transfer Date (from the Upstream service)
Current Service Allocated	Service Name
Current Allocation	CRES Service allocation: Service Name CRES = Program allocation: Service Name - Program Name *
Current Program Allocated *	Program Name *
Current Program Details *	Days of week and time *

*Note: Values marked with an asterisk(*) are relevant to services where CRES allocates to program only

Sync of changes to children prior to transfer date

If any changes are made to the transfer date or transfer status, the following updates will be made in the receiving service's system to ensure the information remains accurate.

Should the child's transfer status change or if the transfer date is altered, the following updates will be made:

If the Transfer date is edited
First day at service will be updated to reflect the new date
If the Transfer Status is edited to anything other than Transfer Accepted**
Child status current period will be marked as Care no longer required

**Note: The transfer status changing will only affect the downstream child if the Transfer is a change of Service

Impact for the Departing Downstream Services (when a child is leaving the service)

As per standard process, the child will still exist in their current service and be marked as care no longer required on the transfer date.