25.10.2013 Views

Implementation Guidelines - Federal Transit Administration - U.S. ...

Implementation Guidelines - Federal Transit Administration - U.S. ...

Implementation Guidelines - Federal Transit Administration - U.S. ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

standard operating procedures of transit<br />

systems, large and small.<br />

However, you should objectively<br />

evaluate your program to ensure that<br />

policies and procedures have been updated<br />

and its integrity remains intact. Agencies<br />

often find that as drug and alcohol testing<br />

programs become engrained within an<br />

organization, compliance can be<br />

compromised over time as the program<br />

evolves and components are modified to<br />

reflect the operational realities of the<br />

system. If the DAPM is not diligent in<br />

his/her oversight responsibilities, the<br />

program may be modified out of<br />

compliance. Seemingly simple and<br />

innocuous changes may have significant<br />

implications.<br />

Thus, a comprehensive assessment is<br />

recommended. FTA has produced a selfassessment<br />

checklist that can be used to<br />

identify incorrect or omitted components of<br />

a program, or as an oversight tool to assess<br />

compliance. A copy of this checklist is<br />

provided in Appendix J.<br />

DAPMs may also wish to periodically<br />

assess the cost and benefit of the program.<br />

This information can be helpful for board<br />

members, system management, elected<br />

officials, and others who wish to quantify<br />

the cost-effectiveness and overall worth of<br />

the program. Assessing the program<br />

periodically based on actual experience will<br />

ensure that the true benefits and costs to the<br />

organization are being identified. The costbenefit<br />

analysis should include at a<br />

minimum the out-of-pocket cost of the<br />

program, employee productivity, number of<br />

positive test results, number and nature of<br />

accidents, absenteeism, worker’s<br />

compensation claims, and insurance<br />

premium savings. Other intangibles that<br />

may be assessed include employee morale,<br />

union/management relations,<br />

agency/management credibility, public<br />

relations, and system image.<br />

Section 2. SERVICE AGENT<br />

MONITORING<br />

Since the regulations were first<br />

published, the testing industry has gone<br />

through an evolution with service agents<br />

entering and leaving the market, while<br />

others have merged to form large consortia<br />

or third party administrators (C/TPA). At<br />

the same time, the transit industry has<br />

matured through its increased knowledge<br />

and experience base. The regulations make<br />

it clear that employers are responsible for<br />

ensuring their service agents meet the<br />

qualifications set forth in Part 40. An<br />

employer also has an affirmative<br />

responsibility to get needed information<br />

from service agents to document<br />

compliance.<br />

Service agents must follow the DOT<br />

regulations (Part 40). However, the<br />

employer remains accountable to DOT/FTA<br />

for compliance. Failure of the service agent<br />

to implement any aspect of Part 40 as<br />

required, results in the noncompliance of the<br />

employer. All agreements and<br />

arrangements, written or unwritten, between<br />

employers and service agents concerning the<br />

implementation of DOT drug and alcohol<br />

testing requirements are deemed, as a matter<br />

of law, to require compliance with all<br />

applicable provisions of the DOT/FTA drug<br />

and alcohol testing regulations [§40.11(c)].<br />

Even though the regulation does not<br />

stipulate how an employer should monitor<br />

its service agents, the following activities<br />

have become standard industry practice:<br />

• Conduct periodic mock<br />

collections to identify procedural<br />

flaws.<br />

Chapter 12. Program Monitoring 12-2 August 2002

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!