The Children’s workforce Development team links in closely with the London Borough of Richmond upon Thames Local Safeguarding Children’s Board to ensure that there is a clear professional development pathway to supports organisations and their practitioners to that work together to safeguard and promote the welfare of children. The following training is available to all those who work directly with children and their families.
The designated safeguarding officer within your organisation should access level 2 and 3 as a minimum training requirement. The Children’s Workforce Development Team strongly recommend that practitioners continually review their training needs and access the wide range of professional development opportunities available.
By refreshing, reviewing and updating training needs, practitioners are better placed to improve the lives of children and young people and will continue to contribute to the excellent practice within the Borough.
This is for all staff who have infrequent contact with children, young people and/or parents/carers who may become aware of possible abuse or neglect.
This face to face training is targeted for staff who are in regular contact or have a period of intense but irregular contact, with children, young people and/or parents/carers.
We strongly recommend that any member of the workforce who works predominantly with children, young people and/or their parents/carers and those who have the main responsibility for Safeguarding in their organisation should attend this session.
For information about CAF and eCAF please follow the link above. You will then be able to following the links on the page to book the relevant sessions. There is a pre-requisite to attending CAF part 1, which is the information sharing e-learning module.
Some organisations prefer to have an in-service session with one of our LSCB approved safeguarding trainers. This option is aimed at Level 2 only, but would be ideal for all those staff who need awareness level. For further information please contact: email@example.com.
Updated: 8 May 2015