Deviations at work are never fun. Not only because it can result in a lot of unforeseen work, but also because it often affects the employees. But what is a deviation? It can be many things - including hazards at work, bullying and harassment, corruption or accidents and injuries. That's exactly what we'll be looking at today.
Meet Einar the craftsman
Einar is in his fifteenth year working for a carpentry company. His entire career has been injury-free, with the exception of small cuts, some tiles and the occasional hammer on the thumb. One day, he and a colleague are working on a cozy little house. Einar is going to take some measurements on a window sill about one and a half meters above ground level. He takes out a small ladder and climbs up to take the measurements. Shortly after he's climbed the few steps, his colleague - in a moment of inattention - manages to trip on the ladder, causing it to topple over. Completely slapstick. It's not far down to the ground, but Einar lands incorrectly and suffers a small fracture in his leg.
That's when Einar experienced his first deviation due to an injury. Fortunately, the company he works for has Huma, so the job related to the deviation becomes much easier. Let's take a look at what Kristine, HSE manager at the carpentry company, does.
First: Deviation is reported by employee
Since Einar is in the emergency room, his colleague reports the deviation. He writes down what happened in minute detail to ensure everything is correct. He also makes sure to register that the deviation type is "workplace injury".
Kristine enters the deviation in her Huma account and takes a look at Deviations. She reads over and checks that everything looks correct before moving on to the next module. In Processes, she sets up a detailed process for everything that needs to be done. Fortunately, she has thought ahead in most situations and has previously created a template for following up on work-related injuries in Huma. Most of the steps are laid out clearly, so all you have to do is follow the plan - all the way from dealing with the deviation to welcoming the injured person back.
Time to find out why it happened and how to avoid it later
The incident has many tasks to solve, and Processes automatically add them to Tasks and assign them to those who need to do them. These tasks may include identifying why the accident happened, finding measures that can prevent such accidents later, following up on Einar who is on sick leave, or setting up a deviation meeting with those involved and the safety representative.
Kristine sets up this meeting in Meetings. Before she sends the invitation, she adds the agenda for the meeting. Once the meeting has been sent, the participants can enter private and shared notes to get as much information as possible, such as how the accident was experienced from Einar's colleague's perspective.
Now it's just a matter of sorting it out
After the process has been followed up and actions have been planned, Kristine writes a document for evaluation and logging. It's added to Documents and sent to Einar and his unnamed colleague for signing.
Then it's just a matter of wishing Einar a speedy recovery, perhaps sending him a bouquet of flowers, and looking forward to his return.