Basis of Design

INSTRUCTIONS Updated 2017-09-18

Intended use of the Basis of Design form: The primary purpose of the Basis of Design form is to document
the selection of the design elements that will be included in a WSDOT capital improvement project. Practical
design requires several considerations to be made before design elements can be selected. This form is
intended to document those considerations. It is not intended to duplicate detailed information available in other
forms, such as planning documents, the Project Summary or the environmental documentation (NEPA/SEPA). It
is intended to summarize the major issues, conditions, and considerations that shape the preferred alternative.
The form is intended to be scalable, depending on project type and complexity.

When should the form be filled out? The form is set up so it can be filled out during scoping (as part of an
approved Project Summary), and/or during design (for inclusion in the Design Approval and/or Project
Development Approval package).

Why is this form needed? Implementation of practical design and least cost planning requires a method for
documenting decisions that supports the following key components of the Practical Solutions approach:

 Base solutions on the project need: A Practical Solutions approach requires that projects perform only
the work that directly supports meeting the project need. Transportation projects are not to perform work
“just because we are there.”

 Analyze the contributing factors: It is critical to determine the fundamental cause(s) of a project need by
analyzing the contributing factors and circumstances in and around the problem location. This includes
reviewing and analyzing the existing conditions based on all available data (safety, operations, roadway, freight,
etc.)

 Consider context and modal needs: The Basis of Design provides a template for capturing and
organizing information related to context and modal needs, and to emphasize the important role that
context and modal needs play in making project decisions.

 Make performance-based decisions: Practical In Summary:

design requires that project decisions are based on
performance. The goal is to identify the least cost
alternative that meets the performance needs.
 Engage the community: Community engagement
is essential in understanding the context, modal
needs, and performance needs. WSDOT
collaborates with local agency staff, and seeks to
integrate public concerns and needs into the design
process.
The Basis of Design form is intended to
document information leading to preferred
alternatives that:
 Directly support resolving the project need
 Are appropriate for the context
 Consider the needs of all modes
 Reflect results of community engagement
 Are consistent with the long-term vision for
the corridor
 Don’t compromise safety

Page 1 of 7
 Objectives of the Basis of Design
The Basis of Design is intended to document the selection of the preferred alternative,
including selection of the design elements that are included in the preferred alternative. It
provides an opportunity to discuss (succinctly) the primary reasoning for choosing the
preferred alternative. It explains the choice in terms of meeting the project need, understanding
the context, and making performance-based decisions that consider performance trade-offs.

When is a Basis of Design Required?

If the project is in the Scoping phase, talk to Region Program Management. If the project is in the design phase,
a Basis of Design will be required if a design element is changed, as defined in Design Manual Chapter 1105.
See Design Manual Chapter 1100 for exceptions.

Basis of Design for I-2 Projects

I-2 Safety projects are unique and some of the items that are documented in the Basis of Design (BOD) may
already be documented in another report. The BOD is intended to work WITH other reports generated
for I-2 projects. For I-2 projects – if an item requested by the BOD has already been considered as
part of a completed report, just reference that report. If a safety report is referenced, include a copy of
the report in the Project Development Approval and provide a copy to the approving authority when
submitting the BOD for approval.

If the project has a Collision Analysis Report, a BOD exemption may be requested from the ASDE. If an
exemption is not granted, use the BOD to supplement the information not contained in the CAR. If not
already accomplished in the CAR, the BOD is an opportunity to give the complete picture/story of why the
preferred alternative was the best choice, in terms of meeting the project need(s) and understanding the
context. Note: If the CAR uses the template for the 2019-21 biennium, the CAR can be a complete
replacement for the BOD.

Below are instructions for completing each section of the Basis of Design

Page 2 of 7
 Related Planning Documents and Technical Reports
Review planning information that could affect project design decisions.

For WSDOT projects, a Corridor Sketch or study may be available and may provide useful
information. Contact the region Planning Office regarding the availability of a Corridor Sketch or
study.

 List planning and/or environmental documents related to the project.

 List any local plans, documents, local decisions or plan elements that could affect design-
level decisions.

In the following sections of the Basis of Design, these documents may be referenced if they were
used to provide information that was used to fill out the Basis of Design. Be sure to identify any
documents that provided information related to community or agency vision, and baseline and
contextual performance needs, metrics, targets, and gaps.

OPTIONAL: In addition to listing the documents, this section also provides the opportunity to
highlight any major considerations found in the planning documents that will be important in
selecting the preferred alternative.

General Project Information

 Provide the general project information requested.

This section contains basic project information, much of which can be found on the Project Summary.

Important Project History or Background Information: This is an OPTIONAL field, and provides an
opportunity to briefly discuss any major considerations that help understand the choice of the
preferred alternative. If there is critical information that just doesn’t seem to fit in any of the “boxes”
on the Basis of Design, it can go here.

 List major environmental issues that are potentially affected by the project.
The intent is to identify any environmental considerations that may affect the selection of
a strategy or preferred alternative. An example would be where wetlands or streams are
present in an area that has a mobility performance need, and roadway widening is a
possibility. If an Environmental Review Summary (part of the Project Summary) is
available for the project, adapt that information here to the extent possible.

Major Example environmental considerations include:

Environmental
Considerations  Are any streams, wetlands, or water bodies present that could be impacted?
 Are there any known fish passage barriers in the area?
 Are there any aquifer recharge areas?
 Are any critical areas present that could be impacted?
 Are there any known major archeological considerations?
 Are there any identified Chronic Environmental Deficiencies in the areas?
 Does the area have a high habitat connectivity ranking?
 What is the rating of the area for future climate change vulnerability?

Fill out this section in close coordination with the region Environmental Office.

Page 3 of 7
Describe
 Summarize community engagement activities and specific outcomes, including
a summary of the community vision of the facility.
Community
Engagement
See WSDOT Design Manual Chapter 1100, Practical Design, for discussion regarding
documenting community engagement.

Section 1) Project Needs

 Document each baseline need including need statement, metric, and target.

See WSDOT Design Manual Chapter 1101, Need Identification, for discussion on baseline
needs and need statements.
Record each
See the Guidance Document “Writing Effective Need Statements” at:
BASELINE NEED
statement along http://www.wsdot.wa.gov/publications/fulltext/design/ASDE/Practical_Design.pdf
with the
performance The baseline need(s) metrics and targets are used in the alternative comparison table
metric and target. to evaluate alternatives.

 A best practice is to use the numbering system below to help reference the
needs throughout the rest of the BOD:
BN1 – Baseline Need 1
BN2 – Baseline Need 2

 Document each contextual need including need statement, metric, and target.

See WSDOT Design Manual Chapter 1101, Need Identification, for discussion on
baseline needs and need statements.

Record each See the Guidance Document “Writing Effective Need Statements” at:
CONTEXTUAL http://www.wsdot.wa.gov/publications/fulltext/design/ASDE/Practical_Design.pdf
NEED statement
along with the It is important to remember that each contextual need will be transferred to the
performance alternative comparison table, along with its performance metrics and target, to help
metric and target. evaluate the alternatives.
 A best practice is to use the numbering system below to help reference the
needs throughout the rest of the BOD:
CN1 – Contextual Need 1
CN2 – Contextual Need 2
CN3 – Contextual Need 3

 Document the contributing factors for each baseline and contextual need.
These contributing factors are used to develop effective countermeasures to
What are the
contributing
satisfy the needs for the least cost.
factors of each
baseline and
 A best practice is to use the numbering system used for the baseline and
contextual needs.
contextual need?
See the Guidance Document “Contributing Factors Analysis” at:
http://www.wsdot.wa.gov/publications/fulltext/design/ASDE/Practical_Design.pdf
Has a safety
analysis been
completed (per  Every project needs a safety analysis.

Page 4 of 7
DM Chapter 321
and the Safety The intent is that any available safety analysis has been reviewed and considered when
Analysis Guide)? evaluating project needs.

See the “Safety Analysis Guide” to determine the scope of safety analysis needed for the
project found at:
Sustainable Highway Safety Tools at: http://www.wsdot.wa.gov/Design/Support.htm

If a safety analysis has been performed, record the title and date of the report.

If the Safety Analysis Guide indicates that there is no need for a safety analysis, state
that fact and reason in this section.

Section 2) Context
Consult with region Planning Office to gather the information needed to complete this
section. Complete separate context identifications for each roadway segment.

 Identify the land use context.

Land Use
Context See WSDOT Design Manual Chapter 1102, Context Identification.

Also, identify if the roadway segment is a freeway or non-freeway.

 Identify the transportation context.

See WSDOT Design Manual Chapter 1102, Context Identification.

Transportation context is specific to the function that the roadway provides both regionally
and within a particular location. Among other things, transportation context refers to the
access density, intersection density, and roadside/streetside characteristics.
Transportation
Context Identify the following transportation contexts to provide a better understanding of the
how the roadway segment will be used:
 The Final roadway type
 Bicycle Route type
 Pedestrian Route type
 Freight Use
 Transit Use
 Is the segment identified as a complete street/Main Street highway

Section 3) Design Controls

Why are design controls important? Design controls will influence the selection of various roadway
design elements and how these design elements are then dimensioned. Design controls will provide a
framework that will be used to identify design alternatives.
See WSDOT Design Manual Chapter 1103, Design Controls for all the items listed below.

Complete separate design control selections for each roadway segment.

Page 5 of 7
Selected Design  Document the design year selected, and explain the reasoning for the selection.
Year

Design Users
(Legally Permitted to
 Select the design users and explain the reasoning for the selection.
Use the Facility)

 Referencing the specific land use and transportation contexts identified in Section
Modal 2, select what the modal accommodation levels are for the roadway section (for
Accommodation both existing and design year).
Level
The modes normally under consideration are: vehicles, bicycles, pedestrians, freight and
transit.

 Fill out the table on the Basis of Design, ranking the modes in the order that they
will be prioritized during design.
Modal Priorities
(rank/priority, 1,2,3 Considering the modal accommodation level discussion, choose the modes that will be
etc.) prioritized for the project, and rank the priority. For instance, rank the mode that will be the
top priority when making design decisions with a “1,” and mark the mode that will be the
second priority to accommodate with a “2,” etc.
Note, there can be more than one mode with the same ranking.

Intersection
Design Vehicle
 List and briefly explain reason(s) for selecting design vehicles (by location if
appropriate).

 List the terrain classification of the roadway.

Terrain
Classification

 List the access control classification for the location. If the proposed access
Access Control classification is different than the existing classification, describe the proposed
change.

 Select the most appropriate target speed(s) in the project limits.

Target Speed o Document the reason for selection of target speeds.
o Identify any locations in or in proximity to the project limits where a speed zone will be
needed to transition between two different posted speeds.

Page 6 of 7
 Section 4) Alternatives Analysis

 List, or give a very brief description of the alternatives considered.

 Of the alternatives considered, list the preferred alternative.
 Attach copies or provide information (title, date, etc.) regarding alternatives analysis, trade-offs
comparison, or similar exercises that have been completed for this project, such as an
ALTERNATIVES COMPARISON TABLE.

See WSDOT Design Manual Chapter 1104, Alternatives Analysis.

Section 5) Design Element Selection

 Identify the Design Elements that will have dimensions changed in the preferred alternative for
each alignment.

See WSDOT Design Manual Chapter 1105, Design Element Selection.

Page 7 of 7