Tweet
This morning I was woken up by a guard texting me to ask if his site was open today. I should note that it was already a half-hour past the time he was supposed to be on-site and the only reason he called me was because he'd been phoned by the group who does our hourly phone check-ins as he'd missed the first check-in call of the day. It should be noted that this guard is aware that for his site, and his site alone, that there is a storm line he is supposed to call on days like today. My main site is 24/7 and not affected by closures the way his is, so I don't even have the number saved on my phone (at least that was the case this morning...it's on there now), so nobody he tried to call at my main site could even find the number.
He KNOWS he is supposed to call the storm line when the weather is bad. But what did he do when his alarm went off this morning? He looked outside, assumed that his site was closed, and went back to bed. No phone calls, no nothing, until he got the call from the check-in group. And he's conveniently saying he didn't get the message from the office yesterday concerning making it in for scheduled shifts during the awful weather - we are expected to report for duty as close to our scheduled time as possible although being late is acceptable due to road conditions and as long as we notify the guard we're supposed to be relieving.
What get's me is that he used to be the one at the local office who would have been sending out these notices himself, and he claims to have a couple years of security experience under his belt. Well, due to being called by HOM this morning while she was trying to find out what was going on with this particular guard I got the whole story about him, including that he's been with the company for less than a year despite having had worked at the local office at one point and had no previous security experience. He was pulled out of the office by the Ops Manager for the entire Atlantic region because he was screwing up so badly, and he seriously needed regular guard experience. So he's my problem now...why do they give me the problem children?
Good news is that I have the number, I made sure the guard on duty at my main site wrote it down and stuck it on the giant monitor we have so nobody can miss it. I made sure the idiot guard got the phone number as well, and pretty much dressed him down over the phone for his actions this morning. And when I asked him why on earth he thought what he did was at all acceptable he could only say, "I thought we'd be closed." I know full well that the HOM and the Ops Manager have also dressed him down, and he's lucky he still has a position with my client at all right now. I told him that in the future the first number he is to call is the Storm Line to find out if the site is open, and then I am the second number he calls so I can contact whoever I need to further up the line, and the next time he pulls something like this that it's an immediate write-up.
I was polite and professional, and asked him to stop by my main site after his next weekday shift so that we could go over a few things that were either missed or needs a refresher from when he did his initial training with the company. And that going to the local office for any of this stuff is a waste of time because some of it is client specific and the local office people know nothing about what the client requires. We'll see what happens. But in the meantime I'm shaking my head at the stupidity that has revealed itself yet again.
He KNOWS he is supposed to call the storm line when the weather is bad. But what did he do when his alarm went off this morning? He looked outside, assumed that his site was closed, and went back to bed. No phone calls, no nothing, until he got the call from the check-in group. And he's conveniently saying he didn't get the message from the office yesterday concerning making it in for scheduled shifts during the awful weather - we are expected to report for duty as close to our scheduled time as possible although being late is acceptable due to road conditions and as long as we notify the guard we're supposed to be relieving.
What get's me is that he used to be the one at the local office who would have been sending out these notices himself, and he claims to have a couple years of security experience under his belt. Well, due to being called by HOM this morning while she was trying to find out what was going on with this particular guard I got the whole story about him, including that he's been with the company for less than a year despite having had worked at the local office at one point and had no previous security experience. He was pulled out of the office by the Ops Manager for the entire Atlantic region because he was screwing up so badly, and he seriously needed regular guard experience. So he's my problem now...why do they give me the problem children?
Good news is that I have the number, I made sure the guard on duty at my main site wrote it down and stuck it on the giant monitor we have so nobody can miss it. I made sure the idiot guard got the phone number as well, and pretty much dressed him down over the phone for his actions this morning. And when I asked him why on earth he thought what he did was at all acceptable he could only say, "I thought we'd be closed." I know full well that the HOM and the Ops Manager have also dressed him down, and he's lucky he still has a position with my client at all right now. I told him that in the future the first number he is to call is the Storm Line to find out if the site is open, and then I am the second number he calls so I can contact whoever I need to further up the line, and the next time he pulls something like this that it's an immediate write-up.
I was polite and professional, and asked him to stop by my main site after his next weekday shift so that we could go over a few things that were either missed or needs a refresher from when he did his initial training with the company. And that going to the local office for any of this stuff is a waste of time because some of it is client specific and the local office people know nothing about what the client requires. We'll see what happens. But in the meantime I'm shaking my head at the stupidity that has revealed itself yet again.
Comment