Road Standards
City of SeaTac Public Works is in the process of updating its rules and regulations for development on city owned roadways and developments subject to roadway improvements.
SeaTac currently adopts the 2016 King County Road Standards as its guiding document for work in the right-of-way. While this document has been a convenient reference for many years, it is a document that is intentionally broad to meet the needs of an entire county. It includes irrelevant information and is not specific to the needs of our community, which is always growing and changing.
Major Changes
While SeaTac will be adopting an entirely new document, many of the existing rules and regulations currently in the 2016 King County Road Standards will be returning. The items below have been identified by Public Works staff as significant departures:
- City of SeaTac specific. The document will be tailored specifically to SeaTac. The final version will serve as a one-stop shop for all Engineering related permitting documents and design standards for those looking to construct within city right-of-way.
- Public Works policies are formally adopted within the standard. These include policies that are already enforced but are not readily available to view by the public. These include frontage improvement standards, street lighting standards, overlay district design requirements and utility abandonment
- City of SeaTac standard drawing details. SeaTac will now have its own design details that will be managed in-house. References to WSDOT and County details will still be required on a case by case basis.
- Updates on access requirements. Middle housing rules passed by the Washington State Legislature have dramatically increased the density allowed on parcels zoned as residential-low. The road standards update proposes access and parking requirements aimed at softening the impact of these developments on SeaTac roadways.
- Planting and trees within Right-of-way. The new road standards will formally adopt a right-of-way landscape and tree planting palette.
Timeline
SeaTac Public Works is pushing to have this new standard adopted and ready for enforcement on January 1st, 2027. The documents and its associated code amendments will be heading to committee in May 2026, with formal adoption by council tentatively anticipated in October/November of this year.
Feedback
We are interested in your thoughts.
The draft document and its appendices are available to download and view. Please check the links at the top-right of this page. Any comments or questions you may have on the documents - broad or specific - may be submitted below.
While the draft is considered 95% complete, it is still a draft. Some items may be subject to change or incomplete.
City of SeaTac Public Works is in the process of updating its rules and regulations for development on city owned roadways and developments subject to roadway improvements.
SeaTac currently adopts the 2016 King County Road Standards as its guiding document for work in the right-of-way. While this document has been a convenient reference for many years, it is a document that is intentionally broad to meet the needs of an entire county. It includes irrelevant information and is not specific to the needs of our community, which is always growing and changing.
Major Changes
While SeaTac will be adopting an entirely new document, many of the existing rules and regulations currently in the 2016 King County Road Standards will be returning. The items below have been identified by Public Works staff as significant departures:
- City of SeaTac specific. The document will be tailored specifically to SeaTac. The final version will serve as a one-stop shop for all Engineering related permitting documents and design standards for those looking to construct within city right-of-way.
- Public Works policies are formally adopted within the standard. These include policies that are already enforced but are not readily available to view by the public. These include frontage improvement standards, street lighting standards, overlay district design requirements and utility abandonment
- City of SeaTac standard drawing details. SeaTac will now have its own design details that will be managed in-house. References to WSDOT and County details will still be required on a case by case basis.
- Updates on access requirements. Middle housing rules passed by the Washington State Legislature have dramatically increased the density allowed on parcels zoned as residential-low. The road standards update proposes access and parking requirements aimed at softening the impact of these developments on SeaTac roadways.
- Planting and trees within Right-of-way. The new road standards will formally adopt a right-of-way landscape and tree planting palette.
Timeline
SeaTac Public Works is pushing to have this new standard adopted and ready for enforcement on January 1st, 2027. The documents and its associated code amendments will be heading to committee in May 2026, with formal adoption by council tentatively anticipated in October/November of this year.
Feedback
We are interested in your thoughts.
The draft document and its appendices are available to download and view. Please check the links at the top-right of this page. Any comments or questions you may have on the documents - broad or specific - may be submitted below.
While the draft is considered 95% complete, it is still a draft. Some items may be subject to change or incomplete.
Send us your questions or comments here!
-
Here are my comments regarding the engineering standards, Overall, the manual looks good, and kudos to the city staff for putting it together! 1.4. Changes to this manual Comment 1: I would include a specific time frame (i.e., 2-5 years) for upgrading the manual. A five-year update corresponds to the pavement conditions report update. Most technical issues surface during the review and discussion process with the clients. Therefore, it is important to keep a log of issues and their resolution to be considered at the time of manual update, hopefully not beyond five years. 1.5.A Frontage Improvement Thresholds b. Residential construction of two (2) or more “dwelling units” or construction that results in more than two (2) “dwelling units” on a “legal lot” (as defined in Chapter 15.105 SMC); Comment 2: Frontage improvement is probably one of the costs to make or break a project. For a two-unit residential building to bear such cost is not financially feasible. It defeats the recent state law, Washington’s 2025–2026 SB 5471, which aimed to expand residential development and address the housing shortage. I suggest increasing the number of units to four or more, which means that up to three units per single legal lot, no frontage improvement is required. 1.17 DEFINITIONS AND ABBREVIATIONS Comment 3: Include the following definitions, Access Road to be deferred from a driveway Technical Information Report (TIR) Traffic Analysis Report (TAR) Although this is an engineering standard, the following definitions should also be included since they are the foundation for any engineering plans. Survey, Surveyor, Surveying and Survey Maps Soil, Geotechnical engineer and geotechnical or Sil report 4.2.E Private Residential Access a. Access roads serving one (1) lot shall have a minimum paved width of ten (10) feet and a maximum width of fifteen (15) feet. Comment 4: This should be called a driveway. We should define Access Road and differentiate between the Access Road and driveway. 4.2.D Private Residential Streets See Standard Plan 4-9A. Any street or access road serving, or proposed to serve, fifty (50) dwelling units or less ... Comment 5: This should be clarified! Does this section also pertain to one or two dwelling units? 4.2.E Private Residential Access a. Access roads serving one (1) lot shall have a minimum paved width of ten (10) feet and a maximum width of fifteen (15) feet. Comment 6: This should be a driveway, not an Access Road. 4.2.E Private Residential Access b. Access roads from a joint use driveway shall have a paved width of eighteen (18) feet in a minimum twenty (20) foot access tract. Comment 7: This should be a shared driveway, not an Access Road, and it should not require a tract, but possibly an easement. General comment: Currently, for short plats (up to nine lots), an access road can be defined as an easement. This way, the minimum lot requirement is easier to meet. If we are not changing this requirement, please disregard this comment. If we are planning to change easements to tracts, it will significantly reduce the number of lots and increase legal complications and fees. It defeats the recent state law, Washington’s 2025–2026 SB 5471, which aimed to expand residential development and address the housing shortage. Respectfully, Ali
Ali Shasti, P.E. asked about 1 month agoThank you for taking the time to provide comments on the Road Standards. Our responses to the comments are in the order presented below:
- Staff debated whether or not to include a timeline within the standard itself for updating. In the end, we decided to keep updates as a policy, rather than have it baked into the standard. We anticipate updating yearly at a minimum for the first several years, to catch various errors and minor changes, but we expect there will be times when we want updates sooner or don’t have anything to fix on any given year. Amendments will include a change log with each update.
- This response is relevant to comment 4 as well. With regard to state laws and middle housing, City staff understands that proposed changes to frontage improvement and access standards will increase the burden on residential development. With respect to frontage improvement, the original text of 13.200 was written in 2019. At that time, only one primary unit was allowed per lot. In talks with staff involved with writing the code at the time, had multiple primary units been allowed on a single lot, the code would have been specific to require frontage improvement for that kind of development. The council at the time wanted to enforce frontage improvements when property owners were acting as developers. The new change aligns code with the original ethos. It’s also important to remember that ADU/DADUs are exempt from frontage improvements by State law. This would still allow a property owner to build a primary unit with 3 additional dwelling units and not trigger the requirements of 13.200. The access improvement changes would make it more difficult to build out large, short plats. The state has made it difficult on local jurisdictions by allowing increased density and limiting on-site parking (new limit is one stall per unit) and they are not providing any guidance on how to deal with this increased density. Parking availability is a hot topic in SeaTac, and we believe providing parking within access tracts is a good way to deal with some of the demand issues we will run into. Most short plats in the city are 2 or 3 lot short plats. For the majority, the 12-unit limit will allow these projects to construct 20-ft shared accesses within an easement as they have always done. 4-9 lot plats now have the possibility of bringing anywhere from 16-54 new units. While it may not be possible to meet all other codes and regulations and provide that kind of density, 4-plex and 6-plex construction make it far easier than it used to be.
- We are requiring short plats with potential density of more than 12 units to require shared access via a tract. The reason for this change is that we will require parking and pedestrian access facilities in those that don’t make as much sense in an easement.
- Staff reviewed comments on definitions and added what made sense in our definition section. We also changed the requirements for joint use access to an easement. It was erroneously called out as a tract, which does not make sense for that purpose.
- In general, we refer to driveways as accesses, and the road within the parcels as access roads. The King County Road standard referred to these as separate things, where a driveway was essentially just the connection of the access road to the ROW. This is just a terminology change that we kept and repurposed many of the old driveway details from the King County Standards.
Next Planning Commission Meeting
Our next Planning Commission meeting will be on Tuesday, Aug. 18, 2026. We will be discussing many of the topics here. Anyone is welcome to join and listen in, as the commissioners will be asking very similar questions and I will be presenting some of the comments that were made here.
-
Highline Water District would like to express our concern over the code adoption of Public Works Directive PW-011 Decommissioned Utilities in ROW. The policy was an administratively imposed regulation requiring the removal of decommissioned utilities in the ROW by the City's prior PW Director. Highline has many miles of decommissioned facilities in SeaTac ROW over decades of replacement projects dating back long before the incorporation of the City. The code adoption of this provision adds significant costs to District capital and developer-driven projects moving forward with little or no benefit to the City considering the many miles of abandoned facilities within the ROW. These unnecessary costs are passed through to developers impacting housing affordability or to the residents of SeaTac through higher utility rates. In addition, the additional disruption to the public by increasing the scope of construction projects to remove facilities causes unnecessary inconvenience for the community. The industry's best practice is to abandon in place with the requirement of the utility to remove any direct conflicts impacting City projects in the future. This was the policy before the directive of the prior PW Director. Highline supports this approach and is the standard practice we use in the other 6 cities we serve and in unincorporated King County. We respectively ask City staff, PW Committee and/or Council remove this requirement from the Road Standards to help keep affordable utility rates and reduce barriers for future development.
Jeremy DelMar HWD General Manager asked 4 months agoThank you for your input. Our main goal with the road standards, in regard to existing public works policy, is to make clear what is required for development within SeaTac.
These policies, of which PW Policy 11 is included, have been a long-standing requirement for development, but have not been posted or visible for anyone to see. Often times, projects would come in for permit not knowing about certain development requirements. By placing the policies within the standard, we hope there will be less confusion about some of the requirements moving forward.
The Public Works department continues to evaluate all of its policies and requirements for fairness and effectiveness. PW Policy 11 being included in the road standards does make it more official, but it by no means makes it a permanent requirement. One of the benefits of adopting our own standard is being able to pivot when things aren’t working. If the standard isn’t resulting in beneficial outcomes for the city or its residents, it can be changed. That goes for anything in the standard.
In the 10 years since this specific policy was first implemented, we have worked with the local utilities to enforce utility removal in a way that is reasonable while also protecting the City’s future interests. City staff understands removal of old utilities results in higher up-front construction costs and that utility purveyors may choose to pass this cost on to their customers. It is the City’s opinion that removal of old utilities is more cost effective than removing them during future capital improvement projects, where the cost will almost certainly be higher and result in construction delays. Our ROW currently being a graveyard of abandoned utilities, in our opinion, is not a good argument to keep making the problem worse.
That being said, we do - and have granted - exceptions in certain instances where it can be demonstrated that future impacts would be minimal or there are other circumstances that would make removal infeasible. We will continue to work with utilities on a project-by-project basis to administer this policy fairly and consistently.
-
For residential low zoned neighborhoods that do not have pre-existing improvements or roads with bike lanes, sidewalks, and landscaping strips within 100 yards of a property's frontage, property owners should not be required to provide said improvements to their property frontage when adding or building anything less than 3 additional units to their properties (in other words no more than 4 units total on a lot). It is an unneccessary waste of time and money that could impact a homeowner's decision to provide additional housing. For one, a pedestrian walking down the street is not going to deviate from their path to get on the section of sidewalk that ends in 100 ft simply because its there. And two, when the City later decides to do improvements on the whole street 10+ years down the road, it will tear up that frontage improvement to create a uniform street. So not only will that frontage improvement not be used because its inconvenient, but it will also be destroyed in the future. If you want homeowners to be willing to create additional housing, you need to make it common sense and reasonable for them to do so. Its one thing to have to give up what could be a significant portion of your land (depending on layout) to give the City ROW, but its a whole other thing to then make the homeowner pay for the improvements on that ROW, especially when there are no other similar improvements within a reasonable distance to that frontage. Again this is specifically in relation to residential low zoned neighborhoods.
JD asked 4 months agoThank you for your input. A point of clarification before I answer: frontage improvement does not currently and will not apply for ADU or DADU units. The City cannot legally require frontage improvement for ADU/DADUs, as this is mandated by State law. The units that would trigger frontage improvements would be units that are considered Primary Units, which are greater than 1000SF and can be sold individually.
Enforcing frontage improvements in small segments is always tricky. Most jurisdictions mandate frontage to be built, when required, whether or not there are nearby pedestrian facilities. While it may seem silly to install 100-ft of brand new frontage on an otherwise unimproved roadway, there are not many good options that the City can impose address the impacts of development to the city ROW. The City can, in some instances, impose a fee in-lieu of frontage improvements. If we have a known improvement project in the works, we can take the fee and develop the ROW. However, State law requires jurisdictions to spend this money within 5 years, and it must be spent on the roadway adjacent to the property for which the fee was collected. This makes it difficult to accept a fee, as the city would end up returning the fee back to the developer in most cases, plus interest. There are only a few segments of roadway that will get improved in a 5 year span. This solution also is not intended to be a cost savings for the developer, in essence, trading a fee for constructed improvements.
It is frustrating to have old frontage improvements ripped up by new projects. In such instances, everyone’s time and money is wasted. To help mitigate this, we’ve adopted standard street sections for every roadway classification. These sections will likely go through slight modifications over time, but our hope is that what we are installing today will be close enough to future improvements that we can simply connect when the time comes.
Lastly, regarding ROW dedication, this is the most important aspect of frontage improvement. While most low density zoning is served by local roads that already have the necessary 60’ ROW width, many of our arterials to do not. By requiring ROW dedication, we can ensure housing and other permanent structures do not get built in the path of future roadway projects. This helps to avoid exorbitant acquisition costs and prevents displacement of residents. Even if Public Works were to stop frontage improvements entirely, ROW dedication would almost certainly continue.
I encourage you to make a public comment when this standard goes to Council for approval (watch for updates on this page). While frontage improvement enforcement policy is not in front of council for consideration, there are changes being made to the number and type of units required to provide frontage improvement.
-
Roadway Design and Construction Guidelines 2025-2026 (101 MB) (pdf)
-
Storm Details (7.07 MB) (pdf)
-
Roadway Details (27.2 MB) (pdf)
-
Tree and Planting_List (37.8 MB) (pdf)
-
Sample_Forms_Checklists (5.38 MB) (pdf)
-
Overlay_District_Design_Guidelines (16.7 MB) (pdf)
-
Sample_Engineer_Cost_Estimate_BQW (320 KB) (pdf)
-
Public_Works_Policies (5.43 MB) (pdf)
-
DMMD Corridor Management Plan (13.6 MB) (pdf)
-
Email tralph@seatacwa.gov
Thank you for your contribution!
Help us reach out to more people in the community
Share this with family and friends