[ad_1]
Of: Daniel Bergholm
Published:
An employee from the Stockholm region hired a consultant to do the work that he would do himself.
This must have cost taxpayers hundreds of thousands of crowns.
– We feel punished, says Claes Keisu, press officer.
An employee of the traffic administration of the Stockholm region has been fired after cheating on his working hours for a long time, according to the Arbetet newspaper.
During the 2019-2020 period, the person also hired his own consultant to perform his duties, at a cost of nearly SEK 200,000 of taxpayers’ money, according to an internal document.
– We haven’t noticed anything over the years. This was a very sad surprise, Claes Keisu, a press communicator for the traffic administration in the Stockholm region, tells Aftonbladet.
Photo: Stockholm region
Claes Keisu, press communicator for the Stockholm Region Traffic Administration.
Development by recording
When the traffic administration employee proposed a specific company as a subcontractor to a contractor, the suspicions of the contractor were aroused, which therefore recorded the conversations with the employee and alerted the employer.
It was later discovered that the person had had inappropriate contact with providers for a long time.
– When we discovered this on June 4, we did an urgent investigation, and we had a work basis to directly fire this person. In your role in traffic management, you have instilled a lot of trust and broken it.
Deleted your emails and folders.
When the story began to unfold, the employee deleted all the emails and work folders. Now the researchers have managed to recreate all the evidence.
The employee has been fired and the traffic administration is now investigating to see how they should proceed.
– We are investigating the case further to be able to establish if he has committed something criminal, says Claes Keisu.
What should you do to prevent this from happening again?
– It is clear that it could happen again, but we are not worried in any way. However, this is an alarm clock and we will see if we should introduce a monitoring function, to make sure this does not happen again.
Published: