608
by daniel robert chapman_Archive
All this fire alarm talk brings me to a story of my father's.
He is pretty respected in health and safety fields, with particular attention to electrical safety and fall arrest. After semi-retirement, he worked part time for a company down south, as something of a paid brain they could pick and/or rely on far too much.
One afternoon, an unexploded World War Two bomb was found near their offices. The army were called; the office park had to be evacuated. This was done by sending the secretaries on each floor to walk around and tell people what was going on. This took a long time, in a reasonably dangerous situation.
A few days later, with my dad present, the senior staff met to review the incident and safety procedures. My dad asked why, after being told by the army to evacuate immediately, the fire alarm had not been rung.
"Well," somebody answered. "It wasn't a fire."
There was much agreement that this was the right course of action; there wasn't a fire, so they didn't ring the fire alarm.
Someone then put forward, that perhaps they needed a different kind of alarm, for when there is a bomb threat. And for a flood, someone mentioned. What about if there's an accident? We'll need an alarm for that too.
This executive meeting then began drawing up a list of the numerous alarms that were required, and speculating as to the cost of installing these systems, until my dear, laid back father reentered the discussion.
"How about," he said. "We rename the fire alarm, as 'the evacuation alarm'?"
He said that the room was in uproar. This is what we pay Chris for! How did you come up with that one! This will save us so much time and money!
* I should add, I've heard similar stories from elsewhere; stupidity is universal, I guess. This version has the verification that I followed the events across the course of the week, and the tale concluded with my dad hitting his head against his desk and decrying his young fool employers.
Twenty-four hours a week, seven days a month