Key considerations for developing local government transportation system management programs.

This report is intended to be a reference to clarify the decision making process that leads to selection of (a) an approach for a transportation system management (TSM) program (voluntary or regulatory), (b) whom to include in the program, (c) program goals, (d) mitigation measure requirements, and (e) an administrative structure for the program. TSM programs can be a cost-effective way to increase vehicle occupancy and thus improve efficiency of the street and highway systems. However, in most cases, TSM programs alone will not solve the traffic problems, so they should be considered just one part of a broader strategy. A city should develop its TSM program through a consensus between the public and private sectors. Employers prefer voluntary programs, but they tolerate mandatory programs that are inexpensive, allow flexibility in meeting requirements, and allow private-sector control. The combined voluntary/mandatory TSM approach, a program type that starts as voluntary and becomes mandatory only if and when preselected targets are not reached, appears especially promising. The programs that are most effective at increasing the commute-alternatives-use rate are characterised by a long-term funding source that can maintain sufficient professional staff time for fairly intensive work with targeted employers and developers. Various factors, including the transportation environment, employer characteristics, employee characteristics, and the development environment, should be assessed in developing the TSM program. A program's goal should not be too high; credibility will be enhanced by selecting an ambitious but achievable goal. According to a 1985 Metropolitan Transportation Commission study, a good employer program can result in 5 to8 percent of employees switching to nonsolo driving. Much higher changes have been achieved, but rarely. Compliance is usually judged based on implementing program requirements rather than meeting specific numerical goals. Implementation of a program's requirements by nomeans guarantees that the goal will be met.