Summary
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 Notification of Serious Events | 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 Notification of Serious Events
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#protection_c
h" target="_blank">
66 The Protection of Children Standard
66 </a>
66 <br />
67 Regulation 40
67 </p>
68 <h3 class="h3">
68 RELEVANT GUIDANCE
68 </h3>
69 <p>
69 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-childre
ns-social-care-providers" target="_blank">
69 Tell Ofsted about an Incident - Online Forms and Guidance
69 </a>
69 </p>
70 <p>
70 <a href="https://www.gov.uk/guidance/what-ofsted-means-by-a-serious-incident"
target="_blank">
70 What Ofsted means by a Serious Incident
70 </a>
70 </p>
71 <h3 class="h3">
71 AMENDMENT
71 </h3>
72 <p>
72 This chapter was substantially updated in September 2020 and should be re-read.
72 </p>
73 </div>
75 <h2 class="h2_underlined">
75 <br />
76 Contents
76 </h2>
77 <ol>
78 <li>
78 <a href="#Notif">
78 Notifications of Serious Events
78 </a>
78 </li>
80 <li>
80 <a href="#offences">
80 Regulation 42 - Notification of Offences
80 </a>
80 </li>
81 <li>
81 <a href="#notifying">
81 Accidents or Infectious Diseases - Notifying the Health and Safety Executive (HSE)
81 </a>
81 </li>
82 </ol>
83 <h2 class="h2_underlined">
83 <br />
84 1.
84 <a name="Notif" id="Notif">
84 </a>
84 Notifications of Serious Events
84 </h2>
85 <p>
85 This procedure summarises who must be notified of serious events in relation to
85 <a href="http://trixresources.proceduresonline.com/nat_key/keywords/looked_after.html"
target="_blank">
85 Looked After
85 </a>
85 Children placed in children's homes.
85 </p>
86 <p>
86 The home's registered manager and the placing authority must always be notified of any serious
event. Notifications of a child's death should always be made 'without delay'.
86 </p>
88 <p>
88 In the case of events other than the death of a child, a more proportionate approach should be
taken and, before making a notification to Ofsted, sufficient time should be taken to collect
any further information required in order to determine whether the incident is in fact serious
enough to warrant a notification to Ofsted.
88 </p>
89 <p>
89 Regulation 40 (safeguarding notifications) of the Children's Homes (England) Regulations 2015
sets out the arrangements for notifications by the registered person in relation to serious
incidents which should be shared with Ofsted. The intention is that Ofsted should only be
notified of the most serious incidents.
89 </p>
90 <p>
90 Notifications to Ofsted should be made by using the
90 <a
href="https://www.gov.uk/guidance/tell-ofsted-about-an-incident-childrens-social-care-notificati
on" target="_blank">
90 online notification form
90 </a>
90 . Any member of staff can complete the notification form, but the manager or proprietor is
responsible for ensuring notifications are made. When making the notification you will need your
URN (Unique Reference Number), full postal address and details of the incident and those
involved.
90 </p>
91 <p>
91 In urgent situations, particularly where there is likely to be media interest in the incident,
Ofsted can be contacted by telephone (0300 123 1231).
91 </p>
92 <table title="referrals, admissions and discharges table" width="95%" border="1"
cellspacing="0" cellpadding="5">
93 <tr>
94 <td class="greytableheader">
94 <a name="dm_ref_adm_disch" id="dm_ref_adm_disch">
94 </a>
94 Serious Event
94 </td>
95 <td width="58%" class="greytableheader">
95 Who to notify
95 </td>
96 </tr>
97 <tr>
98 <td width="42%" class="table_row_lightblue">
98 Death of a Child.
98 </td>
99 <td>
100 <p>
100 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-chi
ldrens-social-care-providers" target="_blank">
100 Ofsted
100 </a>
100 ;
100 </p>
101 <p>
101 The placing authority;
101 </p>
102 <p>
102 The Secretary of State (if the Secretary of State is not the placing authority);
102 </p>
103 <p>
103 The local authority in whose area the children's home is located (if that local authority
is not the placing authority);
103 </p>
104 <p>
104 The Clinical Commissioning Group (CCG) for the area in which the home is located;
104 </p>
105 <p>
105 If the child was accommodated in a Secure Children's Home, the Prisons and Probation
Ombudsman for England and Wales (“the PPO”);
105 </p>
106 <p>
106 Any other relevant person
106 <span class="tiny_text">
106 [1]
106 </span>
106 .
106 </p>
107 </td>
108 </tr>
109 <tr>
110 <td class="table_row_lightblue">
110 Referral of a person working in the home pursuant to section 35 (Regulated activity
providers: duty to refer) of the Safeguarding Vulnerable Groups Act 2006.
110 </td>
111 <td>
112 <p>
112 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-chi
ldrens-social-care-providers" target="_blank">
112 Ofsted
112 </a>
112 ;
112 </p>
113 <p>
113 Any other relevant person.
113 </p>
113 </td>
114 </tr>
115 <tr>
116 <td class="table_row_lightblue">
116 Allegation of abuse against the home or a person working there.
116 </td>
117 <td>
118 <p>
118 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-chi
ldrens-social-care-providers" target="_blank">
118 Ofsted
118 </a>
118 ;
118 </p>
119 <p>
119 The placing authority;
119 </p>
120 <p>
120 The local authority designated officer (LADO) for the area where the home is located;
120 </p>
121 <p>
121 Any other relevant person.
121 </p>
121 </td>
122 </tr>
123 <tr>
124 <td class="table_row_lightblue">
124 A child is involved in or subject to or suspected of being involved in child sexual
exploitation.
124 </td>
125 <td>
126 <p>
126 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-chi
ldrens-social-care-providers" target="_blank">
126 Ofsted
126 </a>
126 ;
126 </p>
127 <p>
127 The placing authority;
127 </p>
128 <p>
128 The Police;
128 </p>
129 <p>
129 Any other relevant person.
129 </p>
129 </td>
130 </tr>
131 <tr>
132 <td class="table_row_lightblue">
132 A Child Protection Enquiry involving a child is instigated or concludes.
132 </td>
133 <td>
134 <p>
134 <a
href="https://www.gov.uk/government/publications/notify-ofsted-of-an-incident-form-for-chi
ldrens-social-care-providers" target="_blank">
134 Ofsted
134 </a>
134 ;
134 </p>
135 <p>
135 The placing authority;
135 </p>
136 <p>
136 The local authority in whose area the children's home is located (if different to the
placing authority) which will have responsibility for ensuring appropriate enquiries are
made under Section 47 of the Children Act 1989;
136 </p>
137 <p>
137 Any other relevant person.
137 </p>
137 </td>
138 </tr>
139 </table>
141 <p>
141 <span class="tiny_text">
141 [1] “relevant person” means any person, body or organisation that the registered person
considers to be relevant in relation to the care, protection or safeguarding of a particular
child in all the circumstances
143 </span>
143 .
143 </p>
144 <h3 class="h3">
144 Additional Notifications
144 </h3>
145 <p>
145 The Children's Homes Regulations also require notifications to be made to Ofsted, the placing
authority and other relevant persons in the following circumstances:
145 </p>
146 <ol>
147 <li>
147 A serious incident requiring Police involvement occurs in relation to a child which the
registered person considers to be serious (Police involvement means the Police are actively
doing something concerning the incident, for example making an arrest or taking witness
statements); and
147 </li>
148 <li>
148 There is any other incident relating to a child which the registered person considers to be
serious.
148 </li>
149 </ol>
150 <p>
150 The Oxford English Dictionary defines 'serious' as: 'significant or worrying because of possible
danger or risk; not slight or negligible'. The line between what is serious, and what is not,
can be blurred and is always a matter of judgement.
150 </p>
151 <p>
151 Deciding whether an incident is 'serious' and warrants notification to Ofsted will depend on
many factors, including the age of the child, the frequency of the incident(s), the nature of
any injuries sustained, any additional needs the child has and the context of the home. In some
instances the cumulative effect of frequent incidents may make a notification appropriate even
if in isolation the individual incident would not warrant this.
151 </p>
152 <p>
152 Incidents which are likely to be considered serious (and thus warrant notification to Ofsted as
well as the placing authority) include:
152 </p>
153 <ul>
154 <li>
154 A child being the victim or perpetrator of a serious assault;
154 </li>
155 <li>
155 A serious illness or accident;
155 </li>
156 <li>
156 A serious incident of self harm;
156 </li>
157 <li>
157 Serious concerns over a child's missing behaviour, such as where you consider the child to be
at grave risk due to age or vulnerability, where they have been missing for a considerable
period of time and their whereabouts are unknown or there is a pattern of repeated absence (
157 <span class="bold">
157 Please note
157 </span>
157 - Ofsted do not need to routinely know about children going missing, even if the Police are
called out to help look for them. However, this information should always be shared with the
placing authority).
157 </li>
158 </ul>
159 <p>
159 A serious illness or accident would include matters such as fractured bones, when a child loses
consciousness or situations that require admittance to hospital for more than 24 hours. Ofsted
do not need to be notified about injuries such as sprains, strains or falls that have happened
in the course of regular childhood experiences. This is the case even if the child is taken to
the local accident and emergency department to have the injury checked out, unless it results in
the child being admitted to hospital for more than 24 hours. If the injury has been sustained as
part of a wider incident, for example a restraint or during a child running away, it may be
appropriate to notify Ofsted. However, Ofsted do not need to know if a child becomes ill and is
not admitted to hospital.
159 </p>
160 <p>
160 Self-harm incidents that result in minor or superficial injuries do not need to be reported to
Ofsted. However, homes should have in place a system for notifying responsible authorities of
any serious concerns about the emotional or mental health of a child to the extent that a mental
health assessment would be requested under the Mental Health Act 1983. Ofsted should be notified
if a child living in the home requires a Mental Health Assessment.
160 </p>
161 <p>
161 This is not an exhaustive list, and each case must be assessed individually taking into account
any patterns of behaviour or unusual behaviour that may indicate an increased risk to the child.
161 </p>
162 <h3 class="h3">
162 Sharing Information with the Placing Authority
162 </h3>
163 <p>
163 Regardless of whether Ofsted are notified, the home must share any concerns about the child or
their behaviour with the placing authority, in order to safeguard the child and promote their
welfare.
163 </p>
166 <p>
166 The notification must include details of:
166 </p>
167 <ol type="i">
167 <li>
167 The incident;
167 </li>
168 <li>
168 Who else has been notified; and
168 </li>
169 <li>
169 Outcomes and future actions.
169 </li>
171 </ol>
172 <h3 class="h3">
172 Quality of Notifications
172 </h3>
173 <p>
173 Notifications should not just be a chronology of events. The notification should include a brief
summary of the event, the actions taken by staff and managers at the time, and further actions
planned to reduce the likelihood of a similar incident occurring again.
173 </p>
174 <p>
174 Registered managers and providers are responsible for the quality of the reports completed by
their staff.
174 </p>
175 <p>
175 As part of the inspection process, Ofsted will discuss incidents to gain a shared understanding
of what happened and the actions staff took to address the situation.
175 </p>
176 <p>
176 This conversation will be wider than the process of notifying (or not notifying) Ofsted, and
will focus on your response to any incidents in terms of safeguarding practice and outcomes for
children.
176 </p>
177 <h3 class="h3">
177 Sending Updates to Ofsted
177 </h3>
178 <p>
178 Ofsted do not need to be sent updates in relation to any notifications made, unless there is a
significant development. Even though Ofsted are not updated, it may be appropriate to share
updates with the placing authority and other relevant persons.
178 </p>
179 <p>
179 Ofsted will discuss incidents as part of the inspection process with aim of understanding the
incident and actions taken by staff as a result and further actions planned to reduce the
likelihood of a similar incident occurring again.
179 </p>
180 <p>
180 There may be occasions when an inspector will ask for an update following a serious incident
because this would be helpful in understanding what has happened and the action that you have
taken. In these situations, the inspector is likely to ask for additional information to be sent
directly by e-mail rather than through a series of further notifications.
180 </p>
181 <p>
181 There is no legal requirement to keep notifying Ofsted as a case progresses.
181 </p>
182 <h3 class="h3">
182 Learning from Notifications
182 </h3>
183 <p>
183 It is important that managers and providers consider the wider implications of incidents which
have led to notifications. The notification should not be seen as the end of the process, rather
the circumstances of the incident should be reviewed and any implications for safeguarding or
outcomes for children identified. Wherever possible, actions should be planned to reduce the
likelihood of similar incidents occurring again. Inspectors will ask for information on learning
from notifications during subsequent inspections.
183 </p>
185 <h2 class="h2_underlined">
185 <br />
186 2.
186 <a name="offences" id="offences">
186 </a>
186 Regulation 42 - Notification of Offences
186 </h2>
187 <p>
187 If any of the following people are convicted of a criminal offence, they must notify Ofsted in
writing without delay giving details of the date and place of the conviction, the offence and
the penalty imposed:
187 </p>
188 <ul>
189 <li>
189 The Registered Provider;
189 </li>
190 <li>
190 The Registered Manager;
190 </li>
191 <li>
191 The Responsible Individual;
191 </li>
192 <li>
192 If the Registered Provider is an organisation, any director of that organisation;
192 </li>
193 <li>
193 If the Registered Provider is a partnership, any partner in that partnership.
193 </li>
194 </ul>
195 <h2 class="h2_underlined">
195 <br />
196 3.
196 <a name="notifying" id="notifying">
196 </a>
196 Accidents or Infectious Diseases - Notifying the Health and Safety Executive (HSE)
196 </h2>
198 <p>
198 Also see the
198 <a href="p_accidents.html">
198 Recording and Reporting of Accidents Procedure
198 </a>
198 .
198 </p>
202 <p>
202 Where a child, visitor or member of staff is involved in a serious accident in the home, the HSE
should be informed. The outbreak of any infectious disease (which in the opinion of a registered
medical practitioner is sufficiently serious to be so notified) should also be reported.
202 </p>
203 <p>
203 See
203 <a href="https://www.hse.gov.uk/forms/incident/" target="_blank">
203 HSE website
203 </a>
203 for forms to report incidents to the HSE.
203 </p>
204 <p>
204 For more information, see
204 <a href="https://www.hse.gov.uk/riddor/" target="_blank">
204 HSE – Reporting of Injuries, Diseases and Dangerous Occurrences
204 </a>
204 .
204 </p>
206 <p>
206 <br />
207 <br />
208 </p>
209 </div>
210 </div>
211 </div>
212 </div>
213 <div id="footer-wrap">
214 <div id="footer-container">
214 <div id="footer">
215 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">
216 <tr>
217 <td width="60%" align="left" style="padding-top: 0px;">
217 <a href="http://www.trixonline.co.uk/" target="_blank">
217 <img src="images/trix_logo.gif" width="57" height="22" alt="tri.x logo" border="0"/>
217 </a>
217
217 <span class="darkdivider">
217 |
217 </span>
217 Copyright ©
217 <a href="http://www.trixonline.co.uk/" target="_blank">
217 tri.x
217 </a>
217
217 <span class="darkdivider">
217 |
217 </span>
217
217 </td>
218 <td width="40%" align="right" valign="top" style="padding-top: 0px;">
220 <div class="footer_box">
220 <a href="#">
220 visibility:
220 </a>
220
220 <a href="#" onclick="setActiveStyleSheet('small'); return false;">
220 <img src="images/icons/small_a.gif" alt="View this website with small text" border="0" />
220 </a>
220 <a href="#" onclick="setActiveStyleSheet('medium'); return false;">
220 <img src="images/icons/medium_a.gif" border="0" alt="View this website with medium
text" />
220 </a>
220 <a href="#" onclick="setActiveStyleSheet('large'); return false;">
220 <img src="images/icons/large_a.gif" border="0" alt="View this website with large text" />
220 </a>
220 <a href="#" onclick="setActiveStyleSheet('hivis'); return false;">
220 <img src="images/icons/hivis.gif" border="0" alt="View this website with high
visibility" />
220 </a>
220
220 <span class="darkdivider">
220 |
220 </span>
220
220 </div>
221 <div class="footer_box">
221 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
221 <img src="images/icons/favourite.gif" alt="Add this page to your favourites" width="18"
height="18" border="0" />
221 </a>
221 <a href="#" onclick="window.external.AddFavorite(location.href, document.title)">
221 favourites
221 </a>
221
221 <span class="darkdivider">
221 |
221 </span>
221
221 </div>
222 <div class="footer_box">
222 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"/>
224 <a href="#" onclick="printSpecial()">
224 print
224 </a>
224
224 <span class="darkdivider">
224 |
224 </span>
224
224 </div>
225 </td>
226 </tr>
227 </table>
228 </div>
228 </div>
229 </div>
230 </body>
231 </html>