Meet the Other Phone. Flexible and made to last.

Meet the Other Phone.
Flexible and made to last.

Buy now

Please or to access all these features

WWYD - school ringing to fetch sick child

4 replies

confusedofengland · 28/01/2020 11:52

So, DS3 is in Year 1, he is nearly 6. In his class of 30 DC, there were 9 children off yesterday with a sick bug. One actually vomited in class, 3 were sent home feeling sick, 5 were sick overnight & did not go in. Since DS has heard about this, he has been periodically saying he has a tummy ache, then eating & behaving as normal, very lively, eaten chocolate offered to him etc. Slept fine last night.

I was volunteering at the village library this morning, as I do each week. We are not allowed to open with less than 2 people. I also do paid work at this & other libraries all within a 15 minute drive from home. I had a call halfway through my shift, at 11am, to say DS was 'pale & complaining of a tummy ache' so could I fetch him immediately? I explained that I was working & would need to wait until 1pm as otherwise the library, which was hosting an event, would have to close. They said that was no good & I had to come immediately.

So, a customer who is also my friend, stepped in & I went to fetch DS. It took them 10 mins to fetch him from the classroom & when he came out he was eating an apple, jumping around & not pale! I took the apple from him & said that was not a good thing to eat if he had a tummy ache. He was asking for lunch & quite chatty, as normal. We came straight home (5 min walk) & I have put him to bed, saying that if he is ill he needs to get some sleep. I intend to leave him there a while then get him to do reading/writing this afternoon if he is still ok (as I suspect he will be).

Have I done the right thing or have I overreacted? I can't help but think that if I worked any distance away, as lots of parents here do, the school would not have called me & I do feel a little irritated to ge called out to a child who seems perfectly fine!

MichaelMumsnet · 31/01/2020 11:48

Hi all and apologies for the confusion and upset around the Facebook post. And thanks to all those who got in touch to report the issue.

We've checked the processes around what and how we post on Facebook - and here's some information about what happened with this thread.

We posted a screenshot of the full opening post on Facebook - but unfortunately, unless you clicked on the screenshot, the whole post didn't show - which meant that the important last paragraph wasn't visible in the feed.

We investigated and took the Facebook post down.

But most importantly, huge apologies to @confusedofengland for the upset caused. We're looking at our Facebook posting process to make sure that this issue doesn't happen again.

MichaelMumsnet · 31/01/2020 12:02

Ah. Hold on - I'll check again.

MichaelMumsnet · 31/01/2020 12:06

Yes. Just checked and this section is missing:

'So, a customer who is also my friend, stepped in & I went to fetch DS. It took them 10 mins to fetch him from the classroom & when he came out he was eating an apple, jumping around & not pale! I took the apple from him & said that was not a good thing to eat if he had a tummy ache. He was asking for lunch & quite chatty, as normal. We came straight home (5 min walk) & I have put him to bed, saying that if he is ill he needs to get some sleep. I intend to leave him there a while then get him to do reading/writing this afternoon if he is still ok (as I suspect he will be).'

MichaelMumsnet · 31/01/2020 12:13

Sometimes with long posts we have to cut out a paragraph or two to make it work with the Facebook format - but of course, we shouldn't ever change the sense of the post by doing this and we're sorry it happened this time.

We're going to be looking really carefully at Facebook copy to make sure we're not changing the meaning in future.

Huge apologies once again - and thanks to everyone who brought it to our attention.

Watch this thread for updates

Tap "Watch" to get all the latest updates

End of posts

There are no more MNHQ posts on this thread