Keep Your Drivers Guessing
The last thing you want is for your employees to know exactly when they are going to be drug tested. The idea is for it to be random that they never know it's going to happen. It will provide you with better results because you will know whether they are using or not. If you maintain a set schedule, they could potentially stop using at just the time to provide a clear test - and then go right back to using.
This is what you're trying to avoid. There have been countless people who have been able to successfully pass employee drug testing because they know when the company is going to test. The company has failed because they are predictable. While employees may pass a drug test, you know all too well that they have been able to manipulate the system.
Get Results You Can Count On
The main reason to conduct DOT drug testing that is sporadic is so you can truly rely on the results. If you know employees are using, but the results come back negative every time, you have yourself a problem. The sporadic aspect keeps everyone on their toes. You can then know that when you test an employee, you can rely on the results.
If you can't get results you can count on, various issues arise.
- Employees could be on drugs
- You could be against regulations
- You open yourself up to greater risk
You don't have to do all of the testing on your own. You can work with a consortium to manage the entire program for you. This will ensure that all of the services you need are at your fingertips, and they would be authorized to perform various functions so that there is less for you to worry about.
Employees who drive for a living expect to be drug tested. It's part of the job. When you conduct the tests sporadically, you can rely more heavily on the results - and minimize the risks that you expose your business to throughout the year.
https://web.alvernia.edu/eportfolio/view/view.php?id=22494
http://community.aimsa.edu.au/view/view.php?id=6210
http://www.icsi.edu/capitalmarketweek/UserProfile/tabid/4706/userId/818625/Default.aspx
http://sittingcre.bakeridi.edu.au/UserProfile/tabid/563/userId/38071/Default.aspx
http://journals.kent.ac.uk/index.php/feministsatlaw/comment/view/58/0/3151
http://sensoria.swinburne.edu.au/index.php/sensoria/comment/view/430/0/245
https://cie.asu.edu/ojs/index.php/cieatasu/comment/view/1441/0/1597
http://jotlt.indiana.edu/comment/view/13473/0/2264
https://www.ced.ncsu.edu/meridian/index.php/meridian/comment/view/70/0/4501
http://ppr.pitt.edu/ojs/index.php/ppr/comment/view/10/0/992
http://libjournal.uncg.edu/ap/comment/view/1084/0/1304
http://library.tulane.edu/journals/index.php/TJIA/comment/view/138/0/125
http://revistas.upr.edu/index.php/prhsj/comment/view/7955/0/732
https://library.osu.edu/ojs/index.php/Sample/comment/view/3780/0/642
http://journals.gonzaga.edu/index.php/gulawreview/comment/view/110/0/1138
http://journals.uic.edu/ojs/index.php/ojphi/comment/view/7055/0/3928
http://www.southasianist.ed.ac.uk/comment/view/1176/0/258
https://www2.nau.edu/nabej-p/ojs/index.php/njrp/comment/view/42/0/89
http://ithaqua.oerc.ox.ac.uk/cpdnboinc/team_display.php?teamid=11444
http://tecnln1-prod.its.waikato.ac.nz/~roniridg
No comments:
Post a Comment