Contents

Introduction

Steps for setting goals and targets

Setting local performance goals and targets: Three approaches

Statewide goals and targets

Statewide goals and local targets

Local goals and targets

Draft matrix of CTR Board expectations for goals and targets in local CTR plans

Terms and definitions

Appendix A: Detailed instructions for identifying trends in performance, employer-program benefits and geography

Appendix B: Detailed instructions for aligning worksite, jurisdictional and statewide targets

Introduction

On September 26, 2014, the CTR Board adopted the State CTR Plan 2015-2019. It includes new statewide program goals and targets and new optionsfor local goal and target setting.

Past jurisdictional targets were based on the understanding that a jurisdiction’s results would be added upto the statewide targets. Jurisdictions were required to set targets at a minimum level to meet statewide targets. If the state set a target for vehicle miles traveled (VMT)reductionsof 13 percent, all jurisdictions had to settheir own targets for VMT reductionsat no less than 13 percent.

Withitsnew performance plan, the CTR program will provideunprecedented local flexibility. Instead of combining and adding up jurisdictions performance to calculate the overall statewide program performance, each jurisdiction’s goals and targets will be set independently based on local objectives.

Statewide performance goals and targets

  1. Goal:Increase the use of transportation alternatives for commute trips among residents to 33 percent by 2015 (Governor’s Results Washington initiative).Correlate this goal if and when the Governor’s office issues an update after 2015.
  • Statewide target:40percent use of transportation alternatives for commutes in the CTR program by 2019. This represents a six percent increase in non-drive-alonetravel (NDAT)from the 2007/2008 baseline.
  1. Goal:Reduce the state’s annual per capita VMTrate by 18 percent by 2020 (RCW 47.01.440 – state VMT goals).
  • Target:18 percent reduction of VMT rates for employees in the CTR program from the 2007/2008 baseline.
  1. Goal:Reduce the state’s greenhouse-gas (GHG) emissions to 1990 levels by 2020 (RCW 70.235.020 – state GHG goals).
  • Target:18 percent daily GHG-emissions reduction per employeein the CTR programfrom the 2007/2008 baseline (based on CTR program VMT target).

Statewide Measurement Policies

  1. The method of measurement must be able toprovide information toreport on progress toward selected goals and targets.
  2. Jurisdictions that choose approaches with state program goals must measure and report on NDAT, VMT and GHG.
  3. The method of measurement will be consistent with the jurisdictions goals and targets.
  4. Each jurisdiction may choose to use “state measurement tools” or propose a different measurement plan that will need to be approved by WSDOT. An accepted plan will be a “state-approved measurement plan.”
  5. The method of measurementmustbe consistent through the four-year period of evaluation.
  6. Jurisdictions are responsible for the collection, measurement and storage of data collected or used in any measurement plan that does not include use of the state measurement tool

Steps forsettinggoals and targets

  1. Choose a program approach.
  2. Review aggregate report to determine goals and/or targets.
  3. Define measurement approach(if choosing something other than state provided approaches).
  4. Complete worksheet.
  5. Update ordinance, if needed.
  6. Submit to RTPO for formal review.
  7. Submit to WSDOT.

Please note: Any goals and targets that would require the development of new measurement methodologies are the responsibility of the jurisdiction and must be approved by WSDOT.

Setting local performance goals and targets: Three approaches

Beforeplanning for the next four-year cycle of the program,jurisdictions must choose one of these goal and target approaches:

  1. State goals and targets
  2. Statewide goals and targets defined by the CTR Board in thestate plan.
  3. May include additional, locally defined goals and targets.
  4. State goals and define and proposelocal targets
  5. Statewide goals and locally definedtargets to be approved by the CTR Board.
  6. May include additional, locally defined goals and targets.
  7. Local goals and targets
  8. Locally defined goals and targets thatmeet state and local program objectives to be approved by the CTR Board.

Expectations for all plans

•Propose planning concepts early in the process to receive approval to proceed

•Flexibility in individual employer target-setting remains from previous plans

•Follow the CTR Board’s measurement policy

•Report on the progress and performance of local plans

•Work with WSDOT staff for technical support and guidance

Examples of locally defined goals

  • Increased bike share or other NDAT share (e.g., a local community that wants to focus on amode to correspond with local investments and land-use goals).
  • Increased community engagement.
  • Increased employer collaboration.
  • Increased voluntary participation.

Once a jurisdiction has selectedone of theseoptions they can review the aggregate report to determine goals and/or targets, and then setits goals and targetsas part of its CTR Implementation Plan Update for 2015-2019. The final step is to submit the planto theCTR Board for review and approval.

Statewide goals and targets

While this approachappears straightforward,it also provides program flexibility. All worksites can be assigned the same target, or they can be assigned customized targets based on local factors.Jurisdictional targets must bethe same as the statewide program’s targets.

Using the CTR aggregate report (Excel-basedtoolprovided to jurisdictions with their worksite and jurisdictional aggregate results),a jurisdictioncan identify trends in performance, employer-program benefits and geography in order to develop realistic expectationsof future worksite performance.

For detailed instructions on how to look for trends in performance, employer program benefits and geography, see Appendix A.

For help determining specific targets at the worksite level, or to calculate the number of trips needed to meet the statewide target for each worksite, see Appendix B.

Please contact WSDOTif you have questions or need technical support for setting goals and targets.

Additional expectations for state program goals and targets

  • Goals and targets for jurisdiction the same as state program goals and targets
  • Six percentage point increase in non-drive-alone travel (NDAT) from the 2007/08 CTR program baseline
  • 18 percent reduction in VMT and GHG per employee from the 2007/08 CTR program baseline

Statewide goals and local targets

This approachallows a jurisdiction to determine targets based on local objectives and needs. The CTR Board understands that no twojurisdictions are the same. One jurisdiction may have very specific land use goals or ordinances.Another may befocusedon revitalizing itsdowntown core or developingitsindustrial areas. Another may have recently invested in improving non-motorized infrastructure, such as bike trails or sidewalks. Another might not charge for parking. Assessment ofcommunity needs is often best doneat the local level, so that a jurisdiction can determine where to focus itsprogram’s efforts.

For detailed instructions on how to look for trends in performance, employer program benefits and geography, see Appendix A.

For help determining specific targets at the worksite level, or to calculate the number of trips needed to meet the statewide target for each worksite, see Appendix B.

Please contact WSDOTif you have questions or need technical support for goals and targets.

Additional expectations for state program goals with locally developed targets

  • Targets for jurisdiction locally developed for all three state program goals
  • Targets set at a level to meet or exceed current local performance
  • Develop targets that clearly reflect local comprehensive plans (particularly the land use and transportation elements)

Localgoals and targets

This is the most flexible of the three approaches. It allows for different goals than those of the statewide program, so long as the goals are consistent with statewide objectives.The CTR Board understands that no twojurisdictions are the same. One jurisdiction may have very specific land use goals or ordinances. Another may be focused on revitalizing its downtown core or developingits industrial areas. Another may have recently invested in improving non-motorized infrastructure, such as bike trails or sidewalks. Another might not charge for parking. Assessment ofcommunity needs is often best doneat the local level, so that a jurisdiction can determine where to focus its program’s efforts.

For detailed instructions on how to look for trends in performance, employer program benefits and geography, see Appendix A.

For help determining specific targets at the worksite level or to calculate the number of trips needed to meet the statewide target for each worksite, see Appendix B.

Please contact WSDOTif you have questions or need technical support for goals and targets.

Additional expectations for locally developed goals and targets

  • Develop goals and targets that contribute to program objectives
  • Develop targets that clearly reflect local comprehensive plans (particularly the land use and transportation elements)

Draft matrix of CTR Board expectations for goals and targets in local CTR plans

Oct. 24, 2014 version

Expectation / State program goals and targets / State program goals with locally developed targets / Locally developed goals and targets
Flexibility in individual employer target-setting remains from previous plans
Follow the CTR Board’s measurement policy
Report on the progress and performance of local plans
Work with WSDOT staff for technical support and guidance
Propose planning concepts early in the process to receive board approval to proceed
Goals and targets for jurisdiction the same as state program goals and targets
Targets for jurisdiction locally developed for all three state program goals
Develop goals and targets that contribute to program objectives
Targets set at a level to meet or exceed current local performance
Develop targets that clearly reflect local comprehensive plans (particularly land use and transportation elements)

Terms and definitions

Aggregate report
The aggregate report is an Excel-based tool WSDOT developed to assist jurisdictionswith implementing operational and planning objectives. This tool can be used to assist in developing targets at both the worksite and jurisdictional levels.
Baseline
Data collected during the 2007-2008 survey cycle serves as the baseline for the 2015-2019 program cycle. New VMT and GHG goals will correspond to historic metrics. The goal for the new non-drive-alone travel (NDAT) rate will require a conversion from the original drive-alone numbers.
For jurisdictions choosing goals other than those of the state, identifying the baseline for program performance may require additional effort. Along with this document, WSDOT staff will provide technical assistance in local goal- and target-setting and evaluation issues.
Non-Drive-Alone Travel (NDAT)
NDAT is the new measure for transportation alternatives (i.e., travel by a method other than single-occupant vehicle. Travel avoided by telework, alternative work schedules, or condensed work weeks shall also be considered as non-drive-alone travel.)

State Measurement Tools

This term refers to tools developed and maintained by the state for use in measuring the progress of jurisdictions and worksites. The CTR survey is the only state measurement tool in use, and there are no plans to develop additional state measurement tools at this time.

State- Approved Measurement Plans

Jurisdictions may propose methods of measurement including at the individual worksite level for review and approval by WSDOT. WSDOT will determine a plan’s eligibility by reviewing the proposed measurement plans for reasonableness of methodology and consistency with the selected goals and targets. Jurisdictions are responsible for the collection, measurement and storage of data collected or used in the plans.

Transportation Alternatives

This refers to travel by a method other than single-occupant vehicle. Travel avoided by telework, alternative work schedules, or condensed work weeks shall also be considered as a travel alternative.

Appendix A:Detailed instructions for identifying trends in performance, employer-program benefits and geography

To compare programmatic elements with program performance,add columns for program or geography to the aggregate report. Columns for employer details can be addedat the end of the table inthe Worksites_CountTowardGoaltabof the aggregate report. Worksites that survey during each cycle will need to add multiple records (rows) in the worksheet. If you have a small number of worksites, itmaybe easierto manually enter the data. If you have a large number of worksites, you may choose to do this as a group (see below).

Helpful tip: Columns H through BE can be hidden in the worksheet, making it easier to identify theworksite for which you are adding data. Note: The data,trends and resultsbelow represent a hypothetical example. This does not accurately reflect the city of Arlington’s CTR data.

For simplicity, only questions with yes/no answers are included in this example. For geography and other variables, it may be easierto work with different data. For example,you can combine land use into one column and assign names (city center, industrial park, etc.) to each worksite, or break out different amounts or rangescharged for parking.

In thenext step,you canusethe tool to helpidentify trends in commuting behavior. Switch to the Aggregate_Jurisdictiontaband customize thefilters so that only your jurisdiction displays:

  1. In Column A, click on the icon (circled, below left).
  2. Once the drop-down menu appears, select “Jurisdiction” (circled, below top right).
  3. Deselect “(Select All)” and select your jurisdiction (circled, below bottom right), then click “OK.”
  4. Repeat these steps for each pivot table you would like to see aggregated data (DAR, VMT mode share etc.).

Next, be sure to refresh the data (youwon’t visibly notice a change yet–but it is a necessary step, as it moves the data from the worksite-level table to the list of options by which to group the data):

  1. Select a box inside one of the pivot tables. The “PivotTable Tools” ribbon (highlighted below) is now highlighted at the top of the worksheet.
  2. Under the “Options” tab,click on the drop-down arrow and select “RefreshAll” (see below— you can also use keyboard shortcutCtrl + Alt + F5).

Now you can start looking at trends between performance and program elements. When you select a box in a pivot table, the “Option” and “Design” tabs andthe PivotTabledialogue box (see below) will appear. If the PivotTable dialogue box does not appear, look for the button to turn it on.The example below demonstrates the Drive Alone Rate PivotTable.

To add a program element to the PivotTable:

  1. Scroll down the list of program elements. The elements (columns) you added in the first step will appear just after “OtherShare” (below left).
  2. Selectone (in this example “bus stop within ½ mile”) and drag it to the “Row Labels” box (below left)in the order shown in the second screencapture.
  3. Repeat these stepsfor each program element for which you want to see the element(column name) broken down.

Some elementswon’t matter to trend analysis, like bus stop location and the response rate pivot table. Whether a bus stop is located ½ mile from a worksite shouldn’t matter to the response rate, but maybe the number of employees in that pivot table would be helpful or maybe the modeshare pivot table will show you if there is a difference between the busshare on sites close to a bus stop verses not close to a bus stop but maybe not. You will need to think about the question you are answering to determine that.

See next page for results of this step

Please keep in mind that the data might not tell a “big picture” story. In thisexample, for instance, it appears at first glance that worksites near or atbus stops performed better than others.However, there may be other, more nuanced factors to consider that the data cannot capture:perhapsthoseworksites recently beganprovidingemployees with bus passes, or perhapsthey are new to the program and can thus produce greaterperformance. You can add “Worksite Name” to this PivotTable give you more detailabout specific sites.

To switch to another program element,select the current elementand click“Remove Field” (see below).

You can also add the organization or worksite name to look at trends at aspecific worksite in an easy-to-read format. Continue using this tool until you have a good idea what types of targets you want for yourworksite(s). Once you feel proficient with this step,you’ll be ready to move tothe next appendix, which will help you determine your jurisdictional targets.

Appendix B: Detailed instructions for aligningworksite, jurisdictional and statewide targets

Note: For jurisdictions using the first (statewide) program model, your targets are already prescribed.Accordingly, you can use this element of the tool to set individual worksite targets to meet the jurisdiction’s overall target. It will also define “trips to reduce”in order to meet the NDATgoal rate.
For jurisdictions using either of the other program models, you can use this tool to help you determine your targets. As updates tothe tool are made, more elements of it will be available.
You should now be ready toswitch to the Initial_Survey_Iterationtab. For best results, add a filter (see first step of Appendix A) to show only your worksites’ initial surveys.