Page reportSummary
Page Layout
Display issue details:
The line numbers refer to lines in the original source. Any with a line number of '0' are implicit tags added by Total Validator:
1 <!doctype html>
2 <html lang="en">
3 <head>
4 <meta charset="utf-8">
12 
E916 [WCAG21 1.4.4 (AA)] Do not use 'viewport' settings which prevent the user from zooming in:
Using 'user-scalable=no' or 'maximum-scale' with a value less than 2.0 may prevent people with sight difficulties from being able to 'zoom in' to pages to read them. See Understanding 1.4.4. <meta name='viewport' content='width=device-width, initial-scale=1, maximum-scale=1'>
12 <title>
12 Team Remit and Case Transfer Between Teams
12 </title>
13 <link href='css/css.php' rel='stylesheet' type='text/css' id="main_style"/>
14 <link rel='shortcut icon' href='images/favicon.ico' type='image/x-icon'/>
16 <link rel="apple-touch-icon" href="images/apple-touch-icon-57x57-precomposed.png" />
17 <link rel="apple-touch-icon" sizes="72x72" href="images/apple-touch-icon-72x72-precomposed.png" />
18 <link rel="apple-touch-icon" sizes="114x114" href="images/apple-touch-icon-114x114-precomposed.png" />
20 <meta name="application-name" content="Team Remit and Case Transfer Between Teams" />
21 <meta name="msapplication-TileColor" content="#301880" />
22 <meta name="msapplication-square70x70logo" content="images/smalltile.png" />
23 <meta name="msapplication-square150x150logo" content="images/mediumtile.png" />
24 <meta name="msapplication-wide310x150logo" content="images/widetile.png" />
25 <meta name="msapplication-square310x310logo" content="images/largetile.png" />
29 <link href='normal.css' id='switch_style' rel='stylesheet' type='text/css'>
32 <link rel='stylesheet' media='(max-width: 1100px)' href='css/colours_mobile.css' />
36 <link href='css/print.css' rel='stylesheet' type='text/css' media='print'>
37 <link href='css/print_colours.css' rel='stylesheet' type='text/css' media='print'>
39 <script src="scripts/print.js">
39 </script>
40 <script src="scripts/jquery-1.6.4.min.js">
40 </script>
41 <script src="scripts/jquery-dateFormat.min.js">
41 </script>
42 <script src="scripts/js.cookie.js">
42 </script>
43 <script type="text/javascript" src="scripts/highlight.js">
43 </script>
44 <script src='https://www.google.com/recaptcha/api.js'>
44 </script>
45 <script type="text/javascript" src="scripts/jquery.js">
45 </script>
46 <script type="text/javascript" src="scripts/pageOrganizer.js">
46 </script>
47 <script>
54 </script>
116 <style>
117 #new_print {
118 display:block;
119 }
120 #old_print {
121 display:none;
122 }
123 </style>
131 <style>
132 ol {
133 counter-reset: item;
134 z-index:-1;
135 }
136 ol li.sub_list {
137 display: block;
138 position: relative;
139 }
140 ol li.sub_list:before {
141 content: counters(item, ".")".";
142 counter-increment: item;
143 position: absolute;
144 margin-right: 100%;
145 right: 3px;
146 }
147 ol li.remove_bullet:before {
148 P908 [WCAG21 1.3.1 (A)] Do not insert content using CSS:
Content inserted using CSS may not appear when CSS is turned off, or the user is using their own accessible style sheet. See WCAG 2.1 Failure F87. content:"\ \ \ ";
149 display:none;
150 }
151 </style>
155 <style>
156 .remove_bullet {
157 list-style:none;
158 }
159 </style>
183 </head>
184 <body onLoad="if (document.getElementById('zoom_searchbox'))
{document.getElementById('zoom_searchbox').focus();}">
186 <div id="skip">
186 <a href="#main_content" class="section_links">
186 Skip navigation to sections
186 </a>
186 </div>
187 <div id="cookie_bar">
187 We use cookies to track usage and preferences.
187 <a href="https://www.trixonline.co.uk/privacy-policy#cookies">
187 View our Cookie Policy
187 </a>
187 <div id="cookie_agree">
187 I Accept
187 </div>
187 </div>
190 <div id="head_bar">
192 <header>
193 <div id="grey_bar">
194 <div id="logo_holder">
195 <img src="images/client_logo.png" height="85" alt="Bexley Logo"/>
196 </div>
196 </div>
198 <div id="title">
199 <h1>
199 Bexley
199 <span id="h1_sub">
199 Children's Services Procedures Manual
199 </span>
199 </h1>
201 </div>
205 <div id="access_holder">
205 <div id="access_text_hold" onclick="location.href='accessibility.html';">
205 <a href="accessibility.html">
205 Accessibility
205 </a>
205 </div>
205 </div>
206 </header>
207 </div>
208 <nav>
210 <div id="sticky_navigation_wrapper">
211 <div id="sticky_navigation">
212 <div id="demo_container">
213 <div id="menu_toggle">
213 <img src="images/menu_white.png" id="drop_menu_button" height="20" alt="Menu toggle for
Mobile"/>
214 </div>
216 <div id="menu_items">
217 <ul>
218 <li>
218 <a href="index.html">
218 Home
218 </a>
218 </li>
219 <li>
219 <a href="contents.html">
219 Contents
219 </a>
219 </li>
220 <li class="dropdownmenu" id="doubletap1">
221 E958 [WCAG21 4.1.2 (A)] The 'aria-haspopup' attribute is not allowed in this context:
The ARIA specification only allows certain 'aria-...' attributes to be used with certain roles. See ARIA 1.2. <a class="toplink" href="menu.html" aria-haspopup="true">
221 Resources
221 <b>
221 ▾
221 </b>
221 </a>
222 <ul id="port_drop1" aria-label="submenu">
223 <li>
223 <a href="local_resources.html" tabindex="-1">
223 Policy Update
223 </a>
223 </li>
224 <li>
224 <a href="http://trixresources.proceduresonline.com/nat_key/index.htm" target="_blank"
tabindex="-1">
224 Glossary
224 </a>
224 </li>
225 <li>
225 <a href="http://trixresources.proceduresonline.com/nat_cont/index.htm"
target="_blank" tabindex="-1">
225 Contacts
225 </a>
225 </li>
226 </ul>
227 </li>
228 <li>
228 <a href="using_this_manual.html">
228 Using this Manual
228 </a>
228 </li>
229 <li>
229 <a href="http://www.londoncp.co.uk/" target="_blank" rel="noopener">
229 London Child Protection Procedures
229 </a>
229 </li>
231 </ul>
232 </div>
236 <div id="search">
236 <div id="search_contents">
237 E910 [WCAG21 1.4.4 (AA)] Use relative rather than absolute units:
Using relative units helps the page to be rendered correctly at different resolutions and allows people with sight difficulties to 'zoom in' to pages to read them. See Understanding 1.4.4. <form method="get" action="search_site.php" style="font-size:10px;">
239 <div id="input_holder">
241 W889 [WCAG21 4.1.2 (A)] Avoid using accessible names created from fallback attributes:
An accessible name generated from 'title', 'placeholder' or default values for <input> buttons, typically yields a low quality accessible name. Instead use the recommended way of setting the accessible name for this element. See Avoid Fallback, and Accessible Name Computation. <input type="text" name="zoom_query" placeholder="Search Manual" spellcheck="true" title="search"
class="search_bar">
242 </div>
243 <div id="mag_holder">
244 <input class="imagelink" type="image" src="images/mag_white.png" id="mag_glass"
height="25" alt="Search" title="Search">
246 </div>
246 </form>
246 </div>
246 </div>
248 </div>
251 </div>
253 </div>
258 </nav>
259 <div id="main_content" tabindex="-1">
260 <main>
263 <div id="print_watermark">
263 This document is only valid 72 hours after printing
263 <script>
263 </script>
263 . For the latest version please visit
263 <noscript>
263 the online manual.
263 </noscript>
263 <script>
263 </script>
263 </div>
265 <div id="chapter_title">
268 <div id="print_holder">
272 <div id="new_print">
272 <a onClick="window.print();" tabindex="0" class="imagelink" href="#">
272 <img id="print_img" src="images/print_black.png" height="30" alt="Click here to print"/>
272 </a>
272 </div>
276 <div id="old_print">
276 <form id="printMe" name="printMe">
276 <input class="imagelink" name="printMe" type="image" onclick="printSpecial()"
id="print_img_ie" src="images/print_black.png" height="30" width="33" alt="Print this
page" title="Print Button">
276 </form>
276 </div>
279 </div>
282 <h2>
282 Team Remit and Case Transfer Between Teams
282 </h2>
284 </div>
287 <div id="scope_box">
288 <h3>
288 SCOPE OF THIS CHAPTER
288 </h3>
289 <p>
289 These procedures focus on Children's Social Care (CSC) teams and children receiving early help
preventative services provided by the family wellbeing service, children in need as defined by the
Children Act 1989, including those who are subject to a child protection plan, those who are
looked after and those receiving after care services. It sets out the arrangements for all
children and young people whose case is transferring between allocated practitioners and transfers
between any of the following teams across the Service:
289 </p>
290 <ul>
291 <li>
291 Early Help Family Wellbeing Service;
291 </li>
292 <li>
292 Referral and Assessment Service;
292 </li>
293 <li>
293 Family Support & Child Protection Service;
293 </li>
294 <li>
294 Disabled Children's Service;
294 </li>
295 <li>
295 Looked After Children Service;
295 </li>
296 <li>
296 Leaving and After Care Service.
296 </li>
297 </ul>
298 <p>
298 This chapter was added to the manual in April 2017.
298 </p>
299 </div>
300 <div id="sections">
302 <h3 id="sections_list">
302 Contents
302 </h3>
303 <ol>
304 <li>
305 <p>
305 <a href="#principle">
305 Principles Underpinning the Transfer of Cases
305 </a>
305 </p>
306 </li>
307 <li>
307 <a href="#transfer">
307 The Transfer Process Between Services
307 </a>
307 </li>
308 <li>
308 <a href="#same">
308 Transfers Between Practitioners in the Same Service
308 </a>
308 </li>
309 <li>
309 <a href="#wellbeing">
309 Transfers Between Statutory Children's Social Work Service to Non-Statutory Early Help Family
Wellbeing Service
309 </a>
309 </li>
310 <li>
310 <a href="#remit">
310 Service Remit & Transfer Points Between Statutory Social Work Services
310 </a>
310 </li>
311 </ol>
312 <h3 id="principle">
312 1. Principles Underpinning the Transfer of Cases
312 </h3>
313 <p>
313 These procedures set out 'best practice' principles and processes regarding case transfers. In
order for the process of case transfer to work as effectively as possible for the child &
family, a degree of professional judgment will be required in many cases to decide when to
transfer. At all times the needs of the child are paramount when considering a change of the adult
who is helping them. A change of practitioner is a significant event for a child and family and
needs to be reflected in sensitive and careful handling by managers and practitioners.
313 </p>
314 <h3 id="transfer">
314 2. The Transfer Process Between Services
314 </h3>
315 <p>
315 Transfers between practitioners and/or services will be conducted in a timely fashion, ensuring as
much continuity as possible for families. All transfers between services will be discussed and
decided through the weekly transfer panel. Transfer panel involves the service managers from each
of the services.
315 </p>
316 <ol style="list-style-type:lower-alpha">
317 <li>
317 Allocated practitioner sends transfer summary to transfer panel administrator and family is put
on the agenda for the next panel;
317 </li>
318 <li>
318 Allocated practitioner and/or manager attends transfer panel to present reason for transfer;
318 </li>
319 <li>
319 Transfer panel decides on transfer and agreed handover/transfer date is identified;
319 </li>
320 <li>
320 Pending change of worker discussed with family and professionals;
320 </li>
321 <li>
321 Team manager oversight ensures child's case file record is up to date and ready for transfer;
321 </li>
322 <li>
322 Transfer meeting takes place between transferring and receiving practitioners and managers;
322 </li>
323 <li>
323 Letters dispatched to family and professionals confirming a change of service and/or
practitioner and date of transfer. (See standard template on LCS);
323 </li>
324 <li>
324 Handover meeting held with the family between transferring and receiving practitioners, within 5
working days of the transfer date.
324 </li>
325 </ol>
326 <h3 id="same">
326 3. Transfers Between Practitioners in the Same Service
326 </h3>
327 <p>
327 All transfers (re-allocations) between practitioners in the same service area will be decided and
managed between Team Managers. The above steps (d) to (h) also apply to changes of allocated
practitioner.
327 </p>
328 <p>
328 At no point should a child be left without a named allocated practitioner. If difficulties are
experienced in transferring cases due to capacity this should be immediately escalated to the
Service Manager. The Head of Service and Deputy Director should be notified in writing and a
record kept of the agreement for each case that has been escalated.
328 </p>
329 <p>
329 If a family are receiving a service in the family support and child protection service move to a
different locality within the borough of Bexley, case responsibility will remain with the locality
team to whom the case is originally allocated.
329 </p>
330 <h4>
330 Transfer/closure summaries & case records
330 </h4>
331 <p>
331 Transfer arrangements will always be mindful of the need to ensure the safety of children. It is
essential that good quality information is passed from the transferring practitioner/service to
prevent gaps in knowledge and delay in activity.
331 </p>
332 <p>
332 Wherever a child experiences a transfer between practitioner and/or service, the transferring
practitioner must ensure the child's record is up to date with all relevant information and a
transfer or closure summary is available. The manager is responsible for ensuring the case record
is up to date before transfer.
332 </p>
333 <h4>
333 Handover meetings
333 </h4>
334 Children, young people, their parents/carers and other professionals engaged with the family should
always be advised of any plans to change practitioner and/or service in advance. Transfers should
always involve a handover meeting with the transferring and receiving practitioners, with the
family. If this is not possible, the reasons will need to be explained to the family and recorded on
child's record.
335 <h3 id="wellbeing">
335 4. Transfers Between Statutory Children's Social Work Service to Non-Statutory Early Help Family
Wellbeing Service
335 </h3>
336 <h4>
336 Transferring a family from Family Wellbeing Service to Children's Social Care
336 </h4>
337 <p>
337 If at any time the family Key Worker in the Family Wellbeing Service thinks the family's
difficulties are worsening and the team around the family has become worried that the child or
young person's needs are increasing, the family Key Worker must alert a Family Wellbeing manager
immediately. Following a case mapping session (if necessary), the manager will make the decision
whether or not to transfer the family to Children's Social Care.
337 </p>
338 <p>
338 If the child or young person is considered to be 'in need' of a statutory social work assessment,
the family should be transferred to Children's Social Care by the Family Key Worker and/or manager
presenting the case at the next weekly transfer panel.
338 </p>
339 <p>
339 If the child or young person is considered to be at risk of, or suffering from significant harm,
the family will be transferred from Family Wellbeing Service to Children's Social Care Referral
& Assessment duty team immediately and a Child Protection (Section 47) Strategy Meeting held.
The Family Key Worker and manager must attend the Strategy Meeting.
339 </p>
340 <h4>
340 Transferring a family from Children's Social Care to the Family Wellbeing Service
340 </h4>
341 When Children's Social Care social work specialist service has been helping a family to improve a
situation, the child or young person's needs should have lessened and the family may no longer
require a statutory service. However, to embed the positive changes the family may need some
continued help at a non-statutory. With agreement, families who meet the Family Wellbeing Service
criteria and that want to continue to receive a service, can be transferred from Children's Social
Care to the Family Wellbeing Service. To transfer a family the social worker will need to present
the case at weekly transfer panel.
342 <h3 id="remit">
342 5. Service Remit & Transfer Points Between Statutory Social Work Services
342 </h3>
343 <h4>
343 MASH
343 </h4>
344 <p>
344 A child will transfer from the MASH to the Assessment Service at the point at which it is agreed
that the threshold for Child & Family assessment has been reached. This transfer should occur
within 24 hours of receipt of the request for service. If the MASH receives a re-referral on a
child previously known to any statutory service within 3 months of the case being closed, the
child will be transferred back to the previous service and where possible to the previous
allocated social worker. A child must be allocated to a social worker within 24 hours of the
decision being made in the MASH.
344 </p>
345 <h4>
345 The Assessment Service
345 </h4>
346 <p>
346 The Assessment Service includes three teams, responsible for undertaking the C&F assessment,
child protection enquiries, private fostering assessments and Section 7 or 37 court welfare
reports. If the assessment concludes that the child is in need of a non statutory family wellbeing
service, or a statutory social work service, the case will need to be presented at transfer panel
at the earliest opportunity to transfer to one of the following services dependent on help
required:
346 </p>
347 <ul>
348 <li>
348 Family Wellbeing Service;
348 </li>
349 <li>
349 Family Support & Child Protection Service;
349 </li>
350 <li>
350 Looked After Children Service;
350 </li>
351 <li>
351 Children with Disabilities service.
351 </li>
352 </ul>
353 <h4>
353 Family Support & Child Protection Service
353 </h4>
354 <p>
354 This service includes four locality teams who are responsible for providing help and services to
children in need and children who are subject to a Child Protection plans.
354 </p>
355 <p>
355 The case will need to be presented at transfer panel at the earliest opportunity to transfer to
the Family Wellbeing Service or the Looked After Children service. A case may transfer to the
Family Wellbeing service in the circumstances and through the process stated above.
355 </p>
356 <p>
356 A case will transfer from the Family Support & Child Protection service to the Looked After
Children service when a child is becomes Looked After. If a child becomes looked after under
Section 20, without a legal order, the transfer will be at/or around the first Looked After Review
meeting. Where a child is subject to Care Proceedings, the transfer will take place at/or around
the first hearing, when an Interim Care Order has been obtained. Initial statements and care plans
should be sent to the Looked After Children service manager before submitting them to court and
the plan should be agreed between the services.
356 </p>
357 <p>
357 The Family Support & Child Protection social worker should invite the receiving Looked After
Children social worker and/or manager to any significant meetings, such as a Child Protection
Conference, Looked After Review (with the child/young persons agreement), Legal Planning Meetings
and Public Law Outline (PLO) meetings.
357 </p>
358 <p>
358 For looked after children the following must have been completed before transfer:
358 </p>
359 <ul>
360 <li>
360 Most recent Looked After Child Social Workers review report;
360 </li>
361 <li>
361 Placement Information Record;
361 </li>
362 <li>
362 Initial Person Education Plan (PEP);
362 </li>
363 <li>
363 Initial Medical should have been arranged and where possible taken place;
363 </li>
364 <li>
364 Up to date Care Plan;
364 </li>
365 <li>
365 A copy of all current Legal Orders must be scanned into the case file record. In the case of a
child Looked After (on a Care Order under Section 31 of the Children Act 1989) a copy of the
birth certificate will be retained, or (for children accommodated under Section 20) will have
been requested;
365 </li>
366 <li>
366 Any financial agreements should be up to date.
366 </li>
367 </ul>
368 <h4>
368 The Looked After Children Service
368 </h4>
369 <p>
369 This service includes three teams responsible for children who are looked after by Bexley.
369 </p>
370 <p>
370 Cases that move to the Leaving Care Team do not go through the traditional weekly transfer
meeting.
370 </p>
371 <p>
371 The Leaving Care team and the three Looked after Children's teams are overseen by a service
manager who reports to the Head of Service for Looked after Children and Permanence which includes
leaving care.
371 </p>
372 <p>
372 Children and young people in Bexley are considered to be leaving care aged 18. At 17.6 months the
Looked After Children team notifies the Leaving Care Manager of a young person and the Leaving
care manager will allocate a Personal Advisor to the young person. The Personal Advisor will
co-work with the allocated social worker until the young person becomes 18.
372 </p>
373 <p>
373 This allows for a smooth transition and introduction to the young person's preparation to leaving
care.
373 </p>
374 <h4>
374 The Leaving Care Service
374 </h4>
375 <p>
375 Will work with a young person up until they are 25 as set out in the governments Keep on Caring
Policy: supporting young people from care to independence. The young person has to acceptant of
the support offered.
375 </p>
376 <h4>
376 Dispute resolution
376 </h4>
377 <p>
377 Managers will work co-operatively to resolve case transfer issues as they arise.
377 <span class="bold">
377 Resolution should in all cases be achieved within 1 working day.
377 </span>
377 The key aim is to ensure that the flow of cases is achieved by managers working together. In rare
and exceptional cases, it will be necessary to refer the matter to the Deputy Director whose
decision will be binding.
377 </p>
378 </div>
381 </main>
382 </div>
385 <footer>
386 <div class="footer">
387 <div>
388 <p>
388 <a href="privacypolicy.html">
388 Privacy Policy
388 </a>
388 <br>
389 <span style="font-size:small;">
390 <span id='desktop_button' tabindex='0'>
390 Desktop
390 </span>
390 |
390 <span id='mobile_button' tabindex='0'>
390 Mobile
390 </span>
390 |
390 <span id='responsive_button' tabindex='0' style='text-decoration:underline'>
390 Responsive
390 </span>
390 </span>
390 </p>
392 <div id="trix_logo">
393 <a href="https://www.trixonline.co.uk/" target="_blank" class="imagelink">
393 <img src="images/trixlogo.png" height="40" alt="Tri.x Logo links to Tri.x homepage"/>
393 </a>
394 </div>
395 </div>
396 </div>
398 </footer>
399 <div id="desktoptest">
399 </div>
400 <script>
527 </script>
529 <script>
538 </script>
540 <script>
587 </script>
590 <script>
592 </script>
600 <script>
639 </script>
640 <script type="text/javascript">
640 </script>
642 <script>
681 </script>
685 <script type="text/javascript">
697 </script>
698 </body>
699 </html>