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 
W874 [WCAG21 2.4.1 (A)] Add a skip navigation link as the first link on the page:
If your document has structure then you should add a skip navigation link to make it easier for accessible users to get to the page's content. To ensure detection, skip navigation links should point to a <main> element, or an element with role='main'. See Understanding 2.4.1, and Skip Navigation. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2 P967 [WCAG21 3.1.1 (A)] Use the 'lang' attribute to denote the primary language of the document:
You should always identify the primary natural language of a document using a 'lang' attribute on the <html> element. See WCAG 2.1 HTML Technique H57. <html xmlns="http://www.w3.org/1999/xhtml">
3 <head>
4 <meta name="viewport" content="width=device-width, initial-scale=1.0"/>
5 W605 Duplicate tag found: See matching tag on line: 22
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made. <meta http-equiv="Content-Style-Type" content="text/css" />
6 W605 Duplicate tag found: See matching tag on line: 23
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made. <meta http-equiv="Content-Script-Type" content="text/javascript" />
7 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
8 <title>
8 Placement Planning Meetings | Next Stage 4Life
8 </title>
9 <link rel='shortcut icon'
href='https://www.proceduresonline.com/resources/logos/procedures/favicon.ico' type='image/x-icon'/>
10 <link rel="apple-touch-icon"
href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-57x57-precomposed.png
" />
11 <link rel="apple-touch-icon"
href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-72x72-precomposed.png
" />
12 <link rel="apple-touch-icon"
href="https://www.proceduresonline.com/resources/logos/procedures/apple-touch-icon-114x114-precomposed.png
" />
13 <link rel="stylesheet" type="text/css"
href="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.cookiebar.css" />
14 <script type="text/javascript"
src="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.min.js">
14 </script>
15 <script type="text/javascript"
src="https://www.proceduresonline.com/trix_cms_snippets/cookie/jquery.cookiebar.js">
15 </script>
16 <script type="text/javascript">
21 </script>
22 W605 Duplicate tag found: See matching tag on line: 5
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made. <meta http-equiv="Content-Style-Type" content="text/css" />
23 W605 Duplicate tag found: See matching tag on line: 6
A duplicate tag has been found with the same attributes. Although this should not affect the page, it indicates that a mistake may have been made. <meta http-equiv="Content-Script-Type" content="text/javascript" />
24 W609 The 'content-type' HTTP header specifies a character set of UTF-8, which is different to the value
given here:
The 'content-type' HTTP header specifies a different character set to that specified in the tag. In this case the HTTP header takes precedence. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
25 <meta name="author" content="Next Stage 4Life" />
26 <meta name="description" content="Next Stage 4Life" />
28 <meta name="robots" content="index, follow" />
29 <meta name="rating" content="all" />
30 <meta http-equiv="pragma" content="no-cache" />
31 <link title="small" href="scripts/style.css" type="text/css" rel="stylesheet" />
32 <link title="medium" href="scripts/style_larger.css" type="text/css" rel="alternate stylesheet" />
33 <link title="large" href="scripts/style_largest.css" type="text/css" rel="alternate stylesheet" />
34 <link title="hivis" href="scripts/style_hi_vis.css" type="text/css" rel="alternate stylesheet" />
35 <script type="text/javascript" src="scripts/print.js">
35 </script>
36 <script type="text/javascript" src="scripts/styleswitcher.js">
36 </script>
37 <script type="text/javascript" src="scripts/highlight.js">
37 </script>
39 </head>
40 <body onload="highlight();">
41 <div class="banner">
42 </div>
43 <div id="buttons">
43 <div id="menu">
44 <ul>
45 <li>
45 <a href="index.html">
45 Home
45 </a>
45 </li>
46 <li>
46 <a href="contents.html">
46 Contents
46 </a>
46 </li>
47 <li>
47 <a href="local_resources.html">
47 Local Resources
47 </a>
47 </li>
48 </ul>
49 </div>
49 <div id="search">
50 <form action="search/search.html" id="cse-search-box" style="margin: 0px;">
51 I899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49. <table width="97%" border="0" cellspacing="0" cellpadding="0">
52 <tr>
53 <td>
53 E885 [WCAG21 1.1.1/1.3.1/3.3.2/4.1.2 (A)] User interface controls should have a label or an accessible
name:
Associate form controls with <label> tags, or use the 'aria-label' or 'aria-labelledby' attributes to label controls where it might be confusing or not possible to use a label. See WCAG 2.1 Failure F68. <input type="text" name="zoom_query" class="search_input" size="20" id="zoom_searchbox" value="Search this
manual" onfocus="this.value=(this.value=='Search this manual') ? '' : this.value;"
onblur="this.value=(this.value=='') ? 'Search this manual' : this.value;" style="margin-right: 5px;" />
53 </td>
54 <td>
54 <input type="submit" value="Go"/>
54 </td>
55 </tr>
56 </table>
57 </form>
57 </div>
57 </div>
58 <div id="topper">
58 </div>
60 <div id="printReady">
61 <div id="container">
62 <div id="content_frame_overflow">
62 <div class="content_text">
63 <h1 class="h1">
63 Placement Planning Meetings
63 </h1>
64 <div class="scope_box" style="padding-bottom: 0px; padding-top: 15px;">
65 <h2 class="h3">
65 REGULATIONS AND STANDARDS
65 </h2>
66 <p>
66 <a href="http://qualitystandards.proceduresonline.com/homes/p_quality_standards.html#reg_5"
target="_blank">
66 Regulation 5 – Engaging with the Wider System to Ensure Each Child's Needs are Met
66 </a>
66 </p>
67 <p>
67 <a
href="http://qualitystandards.proceduresonline.com/homes/p_quality_standards.html#qual_purpose
" target="_blank">
67 The Quality and Purpose of Care Standard
67 </a>
67 <br />
68 Regulation 6
68 </p>
69 <h3 class="h3">
69 SCOPE OF THIS CHAPTER
69 </h3>
70 <p>
70 This chapter covers the following:
70 </p>
71 <ol type="a">
72 <li>
72 Pre-Placement Planning Meetings (where placements are being considered);
72 </li>
73 <li>
73 (Post) Placement Planning Meetings, including Emergency* Meetings/Reviews;
73 </li>
74 <li>
74 Disruption Meetings for children whose placement has ended abruptly or on an unplanned
basis.
74 </li>
75 </ol>
76 <p>
76 *Emergency Placement Planning Meetings/Reviews are meetings for children placed on an
unplanned or emergency basis in children's homes; or meetings regarding children whose
placements are at risk of breaking down.
76 </p>
77 </div>
78 <h2 class="h2_underlined">
78 <br />
79 Contents
79 </h2>
81 <ol>
82 <li>
82 <a href="#_purpose">
82 Purpose of Placement Planning Meetings
82 </a>
82 </li>
83 <li>
83 <a href="#_frequency">
83 Frequency of Placement Planning Meetings
83 </a>
83 </li>
84 <li>
84 <a href="#_convening">
84 Convening and Chairing Planning Meetings
84 </a>
84 </li>
85 <li>
85 <a href="#_attend">
85 Who Should Attend or Contribute to the Meeting
85 </a>
85 </li>
86 <li>
86 <a href="#_preparation">
86 Preparation and Conducting of the Meeting
86 </a>
86 </li>
87 <li>
87 <a href="#_recording">
87 Recording of Outcomes
87 </a>
87 </li>
88 <li>
88 <a href="#_progress">
88 Progress Chasing Outcomes
88 </a>
88 </li>
89 <li>
89 <a href="#disruption">
89 Disruption Meetings
89 </a>
89 </li>
90 </ol>
91 <h2 class="h2_underlined">
91 <br />
91 <a id="_purpose" name="_purpose">
91 </a>
91 1. Purpose of Placement Planning Meetings
91 </h2>
92 <p>
92 A Placement Planning meeting should usually be convened as part of the process of identifying
the most suitable placement for a child (unless the child has been placed in an emergency). The
meeting should involve everyone concerned with the care of the child, to develop the Placement
Plan and ensure it is kept up to date.
92 </p>
93 <h2 class="h2_underlined">
93 <br />
93 <a id="_frequency" name="_frequency">
93 </a>
93 2. Frequency of Placement Planning Meetings
93 </h2>
94 <p>
94 The first Placement Planning Meeting in relation to a placement should be held before the
placement or, where this is not possible because of the urgency of the situation, within 72
hours of the placement.
94 </p>
95 <p>
95 Further Placement Planning Meetings should be held at intervals agreed with social worker and
the manager of the residential home or as required for example where there are issues to be
resolved in relation to the day to day arrangements for the placement.
95 </p>
96 <h2 class="h2_underlined">
96 <br />
96 <a id="_convening" name="_convening">
96 </a>
96 3. Convening and Chairing Planning Meetings
96 </h2>
97 <p>
97 The social worker and home's manager will agree the best format and venue for the meeting and
who will chair the meeting.
97 </p>
98 <h2 class="h2_underlined">
98 <br />
98 <a id="_attend" name="_attend">
98 </a>
98 4. Who Should Attend or Contribute to the Meeting
98 </h2>
99 <p>
99 The people listed below should contribute to the meetings (if the child has been placed on an
emergency basis, it may not be possible to notify/invite all those listed. However, it is
essential that the following people are invited/contribute and have their views represented):
99 </p>
100 <ol type="a">
101 <li>
101 The child's social worker and/or other professional associated with the child e.g. Personal
Advisor or Advocate.
101 </li>
102 <li>
102 The child;
102 </li>
103 <li>
103 The child's parents;
103 </li>
104 <li>
104 The child's Keyworker/carer(s), and/or Home Manager;
104 </li>
105 <li>
105 The Child's Independent Reviewing Officer (IRO);
105 </li>
106 <li>
106 Other significant people/agencies.
106 </li>
107 </ol>
108 <p>
108 The chairperson should also ensure that the child, parent(s) and others who have been asked to
contribute understand the purpose of the meeting, how it will be conducted and are given the
opportunity to put their views and suggestions.
108 </p>
109 <p>
109 Placement plans are likely to be most effective when drawn up in a placement planning meeting
which involves everyone concerned, including the carers.
109 </p>
110 <h2 class="h2_underlined">
110 <br />
110 <a id="_preparation" name="_preparation">
110 </a>
110 5. Preparation and Conducting of the Meeting
110 </h2>
111 <p>
111 Before the meeting the chairperson should obtain or be updated on the following, if available:
111 </p>
112 <ul>
113 <li>
113 The child's Placement Plan;
113 </li>
114 <li>
114 Any work which has been undertaken by key professionals involved in supporting the child's
placement;
114 </li>
115 <li>
115 The child's
115 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/care_plan.html"
target="_blank">
115 Care Plan
115 </a>
115 ,
115 <a
href="http://trixresources.proceduresonline.com/nat_key/keywords/pers_education_plan.html"
target="_blank" class="keyword">
115 Personal Education Plan
115 </a>
115 and, if relevant,
115 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/pathway_plan.html"
target="_blank" class="keyword">
115 Pathway Plan
115 </a>
115 .
115 </li>
116 </ul>
117 <p class="bold">
117 During the meeting, the chairperson should ensure the following:
117 </p>
118 <ul>
119 <li>
119 The consideration is given to the appropriateness of the placement within the context of the
child's Care Plan or Pathway Plan and the need for the Placement Plan amended as appropriate;
119 </li>
120 <li>
120 That the child's Placement Plan is updated if appropriate, and new or updated copies are
circulated to those who were invited or contributed.
120 </li>
121 </ul>
122 <p>
122 This does not mean that amendments to Placement Plans may only be made at Planning Meetings.
When Placement Plan are formulated and at each Planning Meeting, the social worker and
manager/chair should agree the extent to which they can be amended between Planning Meetings or
without consultation.
122 </p>
123 <p>
123 The chairperson should consider whether the child requires an Advocate or the appointment of an
Independent Visitor; if so, this should be raised with the Social Worker. See
123 <a href="p_advcts_vstrs.html">
123 Advocacy and Independent Visitors Procedure
123 </a>
123 .
123 </p>
124 <p>
124 If there are concerns about the suitability of the placement, consideration should be given to
the following:
124 </p>
125 <ul>
126 <li>
126 Whether it is possible to sustain the placement until the next Looked After Review by, for
example, providing additional support to the placement;
126 </li>
127 <li>
127 Bringing forward the date of the next Looked After Review;
127 </li>
128 <li>
128 Ending the placement.
128 </li>
129 </ul>
130 <h2 class="h2_underlined">
130 <br />
130 <a id="_recording" name="_recording">
130 </a>
130 6. Recording of Outcomes
130 </h2>
131 <p>
131 The Chairperson must ensure the following is recorded at the end of the Placement Planning
Meeting:
131 </p>
132 <ul>
133 <li>
133 The updating or amendment of the child's Placement Plan;
133 </li>
134 <li>
134 Additional minutes of any discussions and decisions made at the Placement Planning Meeting.
134 </li>
135 </ul>
136 <p>
136 Copies of these records should be circulated to those who attended or were invited to
contribute.
136 </p>
137 <h2 class="h2_underlined">
137 <br />
137 <a id="_progress" name="_progress">
137 </a>
137 7. Progress Chasing Outcomes
137 </h2>
138 <p>
138 Where the chairperson is concerned about delay in implementation of aspects of the Placement
Plan, he or she should progress chase those responsible and, if necessary, take matters up with
relevant managers.
138 </p>
139 <p>
139 Where the chairperson is concerned that recommendations or agreements have not been incorporated
into the child's plan, he or she may take this up with the relevant person/manager and/or
consider whether to reconvene the Placement Plan Meeting.
139 </p>
140 <br />
141 <h2 class="h2_underlined">
141 8.
141 <a name="disruption" id="disruption">
141 </a>
141 Disruption Meetings
141 </h2>
142 <p>
142 Disruption Meetings should be convened in relation to children whose placement has ended
abruptly or on an unplanned basis.
142 </p>
143 <p>
143 An emergency placement planning meeting should always be held where there are fears that a
placement is at risk of disruption.
143 </p>
144 <p>
144 Where a placement breaks down or ends on an unplanned basis, the manager of the home must
convene a Disruption Meeting within 5 working days.
144 </p>
145 <p>
145 An "off line" manager will usually chair the meeting. In complex cases, however,
consideration will be given to appointing an independent person as chair. Those invited, or
asked to contribute, should be:
145 </p>
146 <ol>
147 <li>
147 The child;
147 </li>
148 <li>
148 The parents;
148 </li>
149 <li>
149 The child's social worker and manager;
149 </li>
150 <li>
150 The link worker/keyworker (for residential care) and home manager;
150 </li>
151 <li>
151 The child's Independent Reviewing Officer;
151 </li>
152 <li>
152 The child's current carers;
152 </li>
153 <li>
153 Other relevant staff/professionals.
153 </li>
154 </ol>
155 <p>
155 The meeting will ensure the child (depending on his or her age and level of understanding) is
given the opportunity to understand the reasons for and be supported with managing the
transition.
155 </p>
156 <p>
156 The precise agenda will depend on the child/circumstances, but the manager/chair should ensure
the circumstances leading to the disruption are properly reviewed, and that all concerned are
provided with opportunities to express their views freely with a view to establishing:
156 </p>
157 <ul>
158 <li>
158 How and why the emergency / disruption occurred;
158 </li>
159 <li>
159 To learn from what happened and avoid the same thing happening again - for the child or others
in the home;
159 </li>
160 <li>
160 To contribute to the future planning for the child;
160 </li>
161 <li>
161 To identify work to be done and to ensure it is completed;
161 </li>
162 <li>
162 To ensure that appropriate notifications and other post placement arrangements have been
undertaken.
162 </li>
163 </ul>
164 <p>
164 The manager should keep minutes, which must be circulated to all concerned.
164 </p>
165 <p>
165 <br />
166 <br />
167 </p>
168 </div>
169 </div>
170 </div>
171 </div>
172 <div id="footer-wrap">
173 <div id="footer-container">
173 <div id="footer">
174 I899 [WCAG21 1.3.2 (A)] Layout tables must represent their content in a meaningful sequence:
Screen readers can struggle to read out tables sensibly, so it is often better to use alternative mark-up and CSS to layout content. Try disabling the table mark-up to see if it still makes sense. See WCAG 2.1 Failure F49. <table width="100%" border="0" cellspacing="0" cellpadding="0">
175 <tr>
176 <td width="60%" align="left" style="padding-top: 0px;">
176 <a href="http://www.trixonline.co.uk/" target="_blank">
176 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
176 </a>
176
176 <span class="darkdivider">
176 |
176 </span>
176 Copyright ©
176 <a href="http://www.trixonline.co.uk/" target="_blank">
176 tri.x
176 </a>
176
176 <span class="darkdivider">
176 |
176 </span>
176
176 </td>
177 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
179 <div class="footer_box">
179 <a href="#">
179 visibility:
179 </a>
179
179 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
179 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
179 </a>
179 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
179 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
179 </a>
179 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
179 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
179 </a>
179 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
179 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
179 </a>
179
179 <span class="darkdivider">
179 |
179 </span>
179
179 </div>
180 <div class="footer_box">
180 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
180 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
180 </a>
180 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
180 favourites
180 </a>
180
180 <span class="darkdivider">
180 |
180 </span>
180
180 </div>
181 <div class="footer_box">
181 W884 [WCAG21 2.1.1/2.1.3 (A/AAA)] Mouse/Pointer event handlers require keyboard equivalents:
When using mouse/pointer event handlers on elements that can be accessed by keyboard, ensure that you provide an equivalent keyboard handler. See WCAG 2.1 Failure F54. <input name="printMe" type="image" onclick="printSpecial()" value="Print this Page"
src="images/icons/print.gif" onmouseover="images/icons/print.gif'"
onmouseout="this.src='images/icons/print.gif'" alt="Print this page"/>
183 <a href="#" onclick="printSpecial()">
183 print
183 </a>
183
183 <span class="darkdivider">
183 |
183 </span>
183
183 </div>
184 </td>
185 </tr>
186 </table>
187 </div>
187 </div>
188 </div>
189 </body>
190 </html>