Step 7: TSP Documentation

What a TSP Should Include

Introduction

The introduction to a TSP can identify what a TSP is, why the jurisdiction has a TSP, and how the jurisdiction uses the TSP to improve its transportation system over time. The introduction can also provide background information on the jurisdiction’s transportation infrastructure, how it has evolved over time, and what is driving the need for the TSP update. Finally, the introduction can describe how the TSP was updated; it can provide an overview of the planning process; it can identify timelines, major milestones, and key deliverables along the way.

Acknowledgements

The development of a TSP requires coordination among many community partners, including local agency staff, local officials, commissioners, councilors, committee members, and others. The collective effort of these individuals ensures that the TSP will receive broad-based support and reflect the most critical needs of the community. An acknowledgements page can pay tribute to individuals who dedicated their time and energy to the TSP update.

Organization

One size does not fit all when it comes to organization of a TSP document. While the final TSP needs to include the various elements discussed in the TSP Guidelines , jurisdictions should organize the local TSP so readers can easily locate and understand what is planned, the timeframe and/or priority for implementation, and, if required, which projects are considered financially constrained. Some jurisdictions may elect to organize their TSP by sequential planning steps, first discussing the existing inventory and then the needs, solutions, and plan for all modes. Other jurisdictions may elect to organize their TSP by mode, addressing all elements (inventory, needs, solutions, and plan) for each mode in its own separate chapter or section. TSPs organized by mode allow sections to be updated more independently or as part of a package of updates.

Outcomes Summary

TSPs typically include an inventory and general assessment of existing and future transportation facilities (See Step 3: Existing Conditions and Step 4: Future Conditions) and an analysis of what will be needed to fix current problems and accommodate future users (See Step 5: Solution Development & Evaluation). Providing these elements in the TSP at a summary level with references to more detailed information as attachments or in a technical appendix helps keep the TSP concise and focused on decisions and recommendations. Ideally, the attachments or technical appendices will contain all the background information, including the technical memoranda developed throughout the TSP. For example, the TSP and all the attachments desired for frequent reference are included in Volume I, and Volume II includes the Technical Appendix, which contains the technical documents that informed the development of the TSP. If there are supportive documents that will be used for future decisions, such as project prospectus sheets or solution toolkits, the recommended approach is to include these as attachments to the TSP in Volume I.

References

References to existing state, regional, and/or local plans and policies that can help guide development of the transportation system over the planning horizon. These plans and policies include, but are not limited to: statewide planning documents such as the Oregon Transportation Plan (OTP), Oregon Highway Plan (OHP), and other modal and topic plans (e.g., Oregon Bicycle and Pedestrian Plan, Oregon Public Transportation Plan, Oregon Transportation Options Plan); State and local facility plans such as corridor plans and interchange area management plans (IAMP); local refinement plans such as downtown, neighborhood, and main streets plans; and other planning documents. These plans and policies can be incorporated into the TSP by reference or by systematically them incorporating into various elements of the TSP.

Supporting Ordinances

Supporting ordinances or development code amendments may be necessary to include with the draft TSP to be consistent with and implement the updated TSP and to comply with or strengthen compliance with the Transportation Planning Rule. Implementing supporting ordinances or development code amendments can be attached to the draft TSP, so that they are included in the public review process prior to public hearing proceedings and adoption.

For non-metropolitan jurisdictions, the Oregon Department of Land Conservation and Development provides a model code that can be used by cities and counties as a tool or resource for planning in Oregon. The model code is written to help local governments follow best practices and adhere to new state standards, rules, or statutes and are often tailored to suit the specific needs of a given community. For metropolitan jurisdictions, the Transportation Planning Rules (TPR) require land use ordinances that support compact, pedestrian-friendly, mixed-use land use development patterns. See OAR 660-012-0330 for requirements. In early 2024, the Department of Land Conservation and Development was developing a model code that would meet those requirements. Elements of the model code can be incorporated into land use ordinances to satisfy some of these requirements.