Washington Permit Timelines: HB 2418 (2026), SB 5290 (2023), and RCW 36.70B

Washington's permit reform is usually described as a shot clock. That is accurate, but it is not the whole story. Since 2023 the Legislature has amended the Local Project Review Act, chapter 36.70B RCW, three times. SB 5290, chapter 338, Laws of 2023, established the completeness determination, the default decision periods, the fee refund, and the annual report, with the deadline provisions taking effect January 1, 2025. HB 1935, chapter 102, Laws of 2025, took building permits out of the definition of a project permit. HB 2418, chapter 235, Laws of 2026, took effect June 11, 2026 and made completeness expressly procedural, added excluded periods, put special purpose districts, public utility districts, and state agencies on clocks of their own, and required every GMA-planning local government to designate a permit-responsible official and a single point of contact by June 30, 2027.

What those three laws add up to is the more consequential development. Development review in Washington is now a coordinated process with several independent clocks, each with its own trigger, its own excluded periods, its own refund, and its own record. Read together, these laws are not merely legal updates. They are an operating-model change.

The question for local governments is no longer only whether a decision issued on time. The more practical question is whether the file can show which approval was on the clock, when procedural completeness occurred, which reviewing entity held the application on any given day, which statutory exclusion applied to each day that did not count, and what that means for the fee. That is where compliance will succeed or fail.

If the file can answer those two questions for every day an application is pending, the rest follows: the correct decision period, the correct excluded intervals, the correct refund calculation, the correct district and agency handoffs, and the correct entries in the annual report. If it cannot, a late decision becomes a refund dispute the jurisdiction cannot defend, and the annual report becomes a document nobody trusts.

Project permits are covered; building permits are not. The Local Project Review Act applies its completeness and deadline duties to cities and counties planning under the Growth Management Act, RCW 36.70A.040. Jurisdictions that do not plan under the GMA may adopt the same procedures by choice under RCW 36.70B.150.

The unit the statute regulates is the project permit. As defined in RCW 36.70B.020(5)(a), a project permit is any land use or environmental permit or license required from a local government for a project action, including subdivisions, binding site plans, planned unit developments, conditional uses, shoreline substantial development permits, site plan review, permits or approvals required by critical area ordinances, and site-specific rezones that do not require a comprehensive plan amendment. Adoption or amendment of a comprehensive plan, subarea plan, or development regulations is not a project permit.

Two categories are expressly excluded, and both matter for how a jurisdiction organizes its work.

First, a project permit does not include permits issued based on compliance with state and local building codes. HB 1935 introduced that exclusion in 2025 and HB 2418 restated it in its current form (RCW 36.70B.020(5)(b)). The 28-day completeness determination, the 65, 100, and 170-day decision periods, the refund, and the annual report do not apply to building-code plan review. Building-permit vesting continues to be governed separately by RCW 19.27.095.

Second, a project permit does not include a special purpose district's or public utility district's determination of service availability, system capacity, infrastructure requirements, or review of proposed water, sewer, or stormwater civil plans. That exclusion does not put district review outside the law. HB 2418 gave district review its own clock, its own completeness test, and its own refund under RCW 36.70B.080(3), discussed in Section 04.

The practical consequence is that one residential project can carry three legally distinct tracks at once: a building-code permit outside the local project-permit clock, a site or land use approval inside it, and a district referral governed by the district's own deadlines. A shared application number, a common portal, or a single department owner does not make those tracks the same.

The decision clock starts when the application is determined or deemed procedurally complete; initial deemed completeness occurs on day 29 if no timely incompleteness determination meeting the statutory requirements is provided, and a timely incompleteness determination can defer completeness beyond the initial 28 days. Under RCW 36.70B.070(1), a local government must issue a written determination of completeness within 28 calendar days after receiving a project permit application. If it does not issue a written determination that the application is incomplete within that period, the application is deemed procedurally complete on the twenty-ninth day. If the local government requests additional information to make an application complete, it must respond within 14 days after the applicant submits it (RCW 36.70B.070(4)). Where notice of application is required, it follows within 14 days after completeness (RCW 36.70B.110). The decision periods in Section 03 run from the completeness determination.

HB 2418 made the character of that determination explicit. RCW 36.70B.070(2) now states that a determination of procedural completeness is not a substantive review of the application and may not be conditioned on the adequacy, accuracy, or sufficiency of the information submitted. A local government may require the materials on its adopted submission checklist. It may request additional information or studies with the completeness determination or afterward. It must identify known outside agencies with jurisdiction. What it may not do is call an application incomplete because it disagrees with the content of a document the applicant submitted.

This is the point at which the statute is most often misapplied. A letter that declares an application incomplete because a traffic study reaches the wrong conclusion, or because a site plan misses a setback, is a substantive review comment presented as a completeness determination. The statute does not authorize it. It also does not say what follows. The deemed-complete rule applies when the local government fails to provide an incompleteness determination as the statute describes one (RCW 36.70B.070(4)(a)); the statute does not say whether a notice grounded on substantive objections counts as one, and it does not provide that such a notice makes the application complete on the day it was filed. Whether day-29 deemed completeness applies in that situation, and when the decision period is ultimately found to have started, are questions for counsel and, if it comes to that, for a tribunal. A jurisdiction that wants a start date it can defend keeps the completeness determination procedural.

One counting question remains open in the guidance. Commerce's annual report describes an application as automatically complete on the fifteenth day after a resubmission if the local government does not respond. The statute requires a response within 14 days but does not expressly repeat, for resubmissions, the deeming rule it states for initial submissions. A jurisdiction should decide, with counsel, which rule its calculator applies, and apply it consistently.

A. Three default periods, subject to local modification

Once an application is procedurally complete, RCW 36.70B.080(1) requires a final decision within 65 calendar days for project permits that do not require public notice, 100 calendar days for permits that require public notice, and 170 calendar days for permits that require public notice and a public hearing. For a consolidated application, the longest applicable period controls unless the local ordinance provides otherwise.

These are defaults. RCW 36.70B.080(1)(e) allows a local government, by ordinance or resolution, to modify the categories and periods, and RCW 36.70B.140 allows exclusion of project permits that present special circumstances. The tier that applies to a given application is therefore a legal question answered by the local code, not a label attached to a permit type by habit. Selecting the tier correctly requires knowing whether public notice and a hearing are legally required for that approval and whether the local ordinance has changed the default.

B. Six excluded periods, one restart, one addition, and one extension

HB 2418 expanded the list of periods that do not count against the local decision deadline. Under RCW 36.70B.080(1)(g), the following are excluded:

(i) Awaiting information or fees. Periods during which the local government has requested information in writing and is awaiting it, or during which the applicant has not paid an applicable fee or posted a required notice.

(ii) Applicant-requested suspension. Periods during which the applicant has requested that review be suspended.

(iii) Awaiting outside government action. Periods during which the local government has completed all possible work on the application and is waiting on necessary action from a government entity covered by RCW 36.70B.080(2) or (3), that is, a fee-charging outside reviewer or a district.

(iv) SEPA environmental impact statement. Periods during which a draft or final environmental impact statement is being prepared following a determination of significance under SEPA.

(v) Administrative appeal window. The period between issuance of a final decision and expiration of the applicable administrative appeal window.

(vi) Pendency of an administrative appeal. Periods during which a filed administrative appeal is pending, through its resolution and any additional period the statute allows.

Two features of that list deserve emphasis. The third exclusion is not "waiting on the district." It is available only when all possible local work is complete and the outside action is necessary. Local review that could proceed while a referral is open still counts. And the list is exhaustive. Staff workload, vacancies, and an undocumented note that the file is waiting on utilities are not excluded periods.

Three other provisions change the count. The period restarts when the applicant proposes a use change that adds or removes commercial or residential elements and that makes the application fail procedural completeness for the new use (RCW 36.70B.080(1)(h)). An additional 30 days may be added in two situations: when the applicant has requested in writing that review be suspended for more than 60 days, or when the applicant has been nonresponsive, as the statute defines that term, for more than 60 consecutive days after a request for additional information that carried the required warning (RCW 36.70B.080(1)(i)). Nonresponsiveness under the statute turns on demonstrable progress and ongoing communication, not simply on whether any reply arrived. And the applicant and the local government may agree in writing, before denial or expiration of the period, to a reasonable and certain extension. That agreement does more than move the deadline. Under RCW 36.70B.080(5), a qualifying extension makes subsection (1), including its refund provision, inapplicable to that application. A local government may not request or require an extension as a condition or option at initial submission.

C. When are Washington permit-fee refunds required?

A refund is required whenever a reviewer misses its own deadline, unless a specific exception applies to that reviewer. For the local government, RCW 36.70B.080(1)(l) requires a refund of 10 percent of the permit fee when the decision is late by no more than 20 percent of the original period, and 20 percent when it is later than that. A jurisdiction may collect 80 percent of the fee at the outset and the balance only if the decision is timely. Neither a late decision nor a refund approves the permit.

The refund does not apply to a local government that has implemented at least three of the ten measures listed in RCW 36.70B.160(1) by the time the application is procedurally complete. The ten measures address expedited review, cost-recovery fees, shared staff, budgeted on-call assistance, contingent positions, limiting hearings to those required by statute, optional preapplication meetings, outright housing uses, licensed professional certification, and a correction-resolution meeting process. Whether a jurisdiction is inside the exception is a fact about that jurisdiction. Bellevue, for example, has published that it implemented three resourcing measures through its 2025 to 2026 budget and that those measures exempt the city from permit-fee refunds; the city's code amendment materials identify them as on-call permitting assistance, contingent staffing, and cost-recovery fees.¹

The exception is not permanent. After January 1, 2026, a jurisdiction whose three measures were adopted more than five years earlier, and that has met its deadlines less than half the time since its last comprehensive plan update, must adopt additional measures at its next periodic update. Failure to do so ends the exception (RCW 36.70B.160(2)).

One point is easy to miss. The three-measure exception is a local exception. It does not extend to a district's refund or to a state agency's refund, each of which stands on its own provision.

Districts now have their own deadlines, measured in business days, starting when they receive a complete referral. Before HB 2418, a city could exhaust its own work and wait months for a water-sewer district's civil-plan comments with no statutory recourse. HB 2418 created a referral clock in RCW 36.70B.080(3), with parallel provisions in the district statutes themselves (RCW 54.04.210, 57.08.200, and 86.09.730). The clock is independent of the local government's clock, uses different units, and carries its own refund.

A. When the district clock applies, and the district's own completeness test

The district provisions apply when a local government needs a special purpose district's or public utility district's determination to complete its review of a residential project permit (RCW 36.70B.080(3)(a)). The district's time begins when it receives a complete referral from the local government. A referral is complete when it provides civil plans and supporting materials based on the district's adopted engineering and design standards in effect on the referral date, together with the materials the district's adopted procedures require.

The district has 15 calendar days from initial receipt to notify both the local government and the applicant in writing that the referral is incomplete and what is missing, and 15 calendar days after each resubmission of requested information to do the same. If it does not, the referral is deemed complete (RCW 36.70B.080(3)(b)). This is a distinct completeness test from the local government's procedural determination under RCW 36.70B.070. The city's application can be procedurally complete while the district's referral is not, and the reverse.

B. Forty-five business days, sixty more for complex work, and a 120-day ceiling

Once the referral is complete, the district must issue written technical comments within 45 business days for routine infrastructure extensions and connections that do not require specialized engineering analysis or external regulatory approval. Where the application involves complex infrastructure, specialized engineering review, regulatory coordination, or third-party technical consultation, the district may add up to 60 additional business days, and must give written notice to the referring local government and the applicant identifying the basis for the additional time and an estimated completion date. The statute names examples of complex work, including sewage lift or pump stations, directional drilling or boring or installation within a state or county right-of-way, system-wide hydraulic or capacity modeling, and construction of off-site capital facilities not previously approved. In all cases the maximum counted review period is 120 calendar days, excluding authorized pauses (RCW 36.70B.080(3)(c)).

Because the periods are measured in business days and the ceiling in calendar days, the two counters must be tracked together. The full 105 business days would run past 120 calendar days; the ceiling binds first.

The district's written comments may confirm consistency with its standards, identify required revisions, identify conditions of service or required improvements, or identify capacity, regulatory, or system limitations that preclude approval.

C. Pauses, and the rule against reopening

The district's clock stops only for the periods the statute enumerates: while the district awaits a state or federal agency approval or authorization; a state or local government right-of-way permit; a franchise utility coordination or relocation approval; final land use conditions, site layout decisions, or building design needed to complete engineering review; or another approval required by state or federal law outside the district's authority; and while it awaits responsive applicant revisions, measured from transmission of the district's written comments to receipt of the revised materials. After the first applicant-revision exclusion, later applicant-revision exclusions are limited to written comments arising from the revised materials, and the district may not reopen issues it has already resolved except as necessary for public health, safety, or regulatory compliance. It may comment on new deficiencies or design changes the revisions introduce (RCW 36.70B.080(3)(d)).

D. The refund, the limits, and the data

If the district does not issue written comments by the applicable deadline, it must refund or forgo 20 percent of the fee it collected, or would have collected, for civil plan or infrastructure review. Attribution controls. The refund reaches the portion of the district's charges attributable to that review, and a label such as connection, capacity, or inspection does not by itself place a charge outside it; the district should be able to show which component of its fee schedule pays for the review the statute times. A missed deadline does not approve the project for service, does not create a cause of action for damages, does not alter the district's substantive authority, and does not require the district to provide service it cannot safely or legally provide (RCW 36.70B.080(3)(e) and (f)).

The district must also supply the referring local government, if that local government is required to file an annual report, with the date the referral was received, the date it was deemed complete, whether the application was eligible for an extended period, the date written comments issued, and whether a refund was issued. The local government must include that information in its report (RCW 36.70B.080(3)(g)).

E. Worked example: city and water-sewer district permit timelines

The example below is illustrative. It assumes an unmodified 100-day local period (public notice, no hearing), a routine district referral received by the district the day it is sent, a five-day business week with no holidays, exact conversion of seven calendar days to five business days, and that the day after an event is day one. Two interpretive questions are assumed rather than resolved, and counsel should confirm both before a jurisdiction applies the pattern: first, that the city's exclusion for awaiting necessary district action continues while the district is itself awaiting the applicant's revisions; second, how the district's 45-business-day deadline applies once the district has issued written comments identifying required revisions, since identifying revisions is itself an authorized written technical response and the statute does not say how later review cycles are timed.

Day 0. The city receives a residential site plan application with civil plans for a water and sewer connection.

Day 20. The city issues its written determination of procedural completeness and, the same day, transmits a complete referral to the district: civil plans prepared to the district's standards in effect that day, plus the materials the district's procedures require. The city's 100-day period starts. The district's 45-business-day period starts on receipt of the complete referral, and its 15-day window to say otherwise runs inside it.

Day 28. The district confirms in writing that the referral is complete. The confirmation does not start a new period. Had the district said nothing, the referral would have been deemed complete at day 35, with the period still running from day 20.

Days 20 to 58. The city reviews everything it can: zoning, critical areas, stormwater, SEPA. The district reviews the civil plans in parallel. Nothing is excluded from either clock.

Day 58. The district issues written comments requesting revisions to the connection design. The district's clock pauses while it awaits the applicant's responsive revisions.

Day 65. The city documents that all possible local work is complete and that the district's determination is necessary to decide the application. From day 65, the city's exclusion under RCW 36.70B.080(1)(g)(iii) applies on the first stated assumption. Counted local days so far: 45.

Day 72. The applicant submits revised civil plans to the district. The district's clock resumes. Its later comments are limited to the revised materials and any new deficiencies they introduce.

Day 90. The district issues final written comments confirming consistency with its standards and stating conditions of service. District counted time: 70 calendar days elapsed since day 20, less the 14 excluded days from day 58 to day 72, is 56 calendar days, or 40 business days against 45. Timely on the stated assumptions. No district refund. The city's exclusion ends the same day.

Day 118. The city issues its final decision. Counted local days: 98 elapsed since day 20, less the 25 excluded days from day 65 to day 90, is 73 against 100. Timely. No local refund. If the city collected 80 percent of the fee at intake, the balance is now due.

Now change one fact at a time.

Suppose the city still had local work it could have performed after day 65, so the exclusion never applied. Its counted days run from day 20 to day 118, or 98 against 100: still timely, but with no margin. Had the decision come at day 130 instead, counted days would be 110, ten days over a 100-day period, and a 10 percent refund would follow unless the city had three streamlining measures in place at day 20.

Suppose instead that the district had issued no revision request and taken no pause, and that its first qualifying written comments came on day 90. Its counted time is the full 70 calendar days from day 20, or 50 business days against 45, and 20 percent of its civil-review fee is refunded or forgone, regardless of anything the city had adopted. The city's count is unchanged at 73 on the stated local-exclusion assumption. The two refund outcomes are independent.

The point of the example is not the arithmetic. Seven dated events determine every outcome: the city's completeness determination, the district's receipt of a complete referral, the district's revision request, the applicant's resubmission, the city's documented exhaustion of local work, the district's comment date, and the city's decision date. If the file holds those dates and the intervals between them, with a basis for each interval that did not count, the refund question answers itself.

HB 2418 also reached reviewers that are neither local governments nor districts. Under RCW 36.70B.080(2), any other government entity that charges a fee to review a project permit application related to a residential project must complete its review within the same 65, 100, or 170-day periods that apply to the local government. The entity's time is calculated separately from the time taken by the local government or any other reviewer. If it misses the deadline, it must refund or forgo 20 percent of its review fee. If it charges no fee, no refund is owed.

The Department of Ecology has its own provision, RCW 43.21A.750, which measures Ecology's period from receipt of the information necessary to begin its review to its final decision, with the same excluded periods that apply to local governments and the same 20 percent refund.

An applicant may waive the deadlines that apply to an outside entity in writing at any time before denial or expiration of the period, in which case the deadline and refund provisions do not apply to that review (RCW 36.70B.080(2)(a)). The three-measure exception that protects a local government does not protect an outside entity, and the district provisions contain no express waiver.

On a separate track, Executive Order 25-03, signed January 15, 2025, directs state executive agencies to catalog their permits and licenses, publish processing deadlines, and refund application fees when a completed application is not decided by the published deadline, to the extent the law permits.² The order is not a statute and is not the 20 percent refund. For a local government's purposes, the statutory provisions above are the operative ones.

A. The organizational deadline

By June 30, 2027, every local government planning under the GMA must establish, by ordinance or resolution, an integrated and consolidated project permit process. For residential project permits, it must designate a permit-responsible official with authority to make all final administrative decisions, and when the local government is the SEPA lead agency, that official must also serve as the SEPA responsible official (RCW 36.70B.060 and RCW 43.21C.570).

It must also provide a single point of contact for each project permit application, residential or not. The point of contact may be an official, a position, an office, or a functional unit, identified by a public telephone number or email address. It must coordinate with other departments and with outside agencies as necessary to meet the decision deadline. The designation does not confer decision authority beyond what the local code already provides.

The distinction between the two roles matters. A point of contact coordinates. The permit-responsible official decides. A jurisdiction that assigns a contact but leaves final administrative authority scattered across departments has not met the June 2027 requirement.

B. The annual report

Counties subject to the Buildable Lands requirement in RCW 36.70A.215 (Clark, King, Kitsap, Pierce, Snohomish, Thurston, and Whatcom) and cities of at least 20,000 within them must post an annual permit performance report on their websites and submit it to Commerce by March 1 each year. Commerce publishes its statewide report by July 1 (RCW 36.70B.080(4)). The first local reports covered 2024. The report now includes the district data described in Section 04.

Commerce's 2025 report states that 50 of the 51 required jurisdictions reported, with 1,731 decisions on 1,462 unique permits, and describes an approximately 19 percent improvement in median review times and, as a median across permit categories, 42 jurisdictions meeting or exceeding the statutory timelines in 2025 compared with 33 in 2024.³ The report's own caveats apply: building permits left the reporting scope, the prior year preceded the deadlines, and local definitions varied. Within those limits, the medians show where the pressure is. Multifamily land use approvals requiring notice but no hearing ran a median of 110.5 days against a 100-day period. Preliminary subdivisions fell from a median of 188 days to 71.5 against the 90-day period in RCW 58.17.140, a change the report attributes largely to how review cycles were reported. Final subdivisions fell from 62.95 days to 29.50 against a 30-day period.

One drafting defect in the reporting statute should be noted. RCW 36.70B.080(4)(b) still instructs reporting jurisdictions to account for the excluded periods in subsection (1)(g)(i) through (iii), although HB 2418 expanded that subsection to six categories. The Code Reviser's note on the section recognizes the mismatch, and the note itself miscites the amending law.⁴ Until the Legislature or Commerce resolves it, a reporting jurisdiction should track all six categories separately so it can report either way.

The review clock sits inside a larger set of state requirements that change which rules staff apply and, in some cases, which clock applies.

Design review. HB 1293, chapter 333, Laws of 2023, limits GMA-planning cities and counties to clear and objective regulations for the exterior design of new development, prohibits design review from reducing density, height, bulk, or scale below what the zoning allows, requires design review to run concurrently with or be integrated into consolidated permit review, and provides that no design review process may include more than one public meeting (RCW 36.70A.630). A public meeting is not a public hearing; treating one as the other moves an application into the wrong tier.

Housing implementation dates. SB 5558, chapter 148, Laws of 2025, aligned the middle housing (HB 1110), urban accessory dwelling unit (HB 1337), and objective design review requirements with the next periodic comprehensive plan update rather than six months after it, and adjusted the periodic update schedule in RCW 36.70A.130(5), which now runs: King, Kitsap, Pierce, and Snohomish counties and their cities by December 31, 2024; Clallam, Clark, Island, Jefferson, Lewis, Mason, San Juan, Skagit, Thurston, and Whatcom by December 31, 2025; Benton, Chelan, Cowlitz, Douglas, Franklin, Kittitas, Skamania, Spokane, Walla Walla, and Yakima by December 31, 2026; and the remaining counties by June 30, 2027. Missed housing deadlines carry preemption consequences: the Commerce model ordinance supersedes conflicting local middle housing regulations, and the ADU requirements supersede conflicting local regulations directly.

Lot splits. HB 1096, chapter 301, Laws of 2025, requires cities to provide an administrative process, with clear and objective standards and no predecision hearing, for splitting a qualifying residential lot into two (RCW 58.17.145). The statute expressly imports the RCW 36.70B.080 time periods for those applications. Cities with a 2027 periodic update must implement by June 30, 2027; all other cities by July 27, 2027.

Subdivision clocks. RCW 58.17.140 continues to require action on a preliminary plat within 90 days of filing and on a final or short plat within 30 days, subject to its own extensions and exclusions. Those periods are not the same as the completeness-triggered periods in RCW 36.70B.080, and both must be tracked.

Commercial zones and STEP housing. SB 6026, chapter 236, Laws of 2026, bars GMA-planning cities of 30,000 or more and non-rural GMA counties from excluding residential uses in commercial and mixed-use zones, with local code updates due December 11, 2027. HB 2266, chapter 232, Laws of 2026, requires that, within urban growth areas, permanent supportive and transitional housing be allowed wherever residential units or hotels are allowed, limits design review of those uses to administrative design review, and calls for local adoption within two years of June 11, 2026 or at the next comprehensive plan update, whichever comes first (RCW 36.70A.845). The act also provides that it supersedes conflicting local regulations whether or not the local government has adopted it, so the adoption date is not permission to keep applying conflicting requirements in the meantime. Other permit and environmental review of those uses follows the process that applies to comparable residential or lodging development.

Parking. SB 5184, chapter 204, Laws of 2025, caps residential and commercial parking minimums and eliminates them for specified uses, with compliance due January 27, 2027 for cities and counties of 50,000 or more, a later date for smaller jurisdictions, and an exemption for cities of 30,000 or less.

These measures point in one direction. Completeness, decision periods, referrals, fees, design review, and the substantive housing rules are being bound more tightly to statutory compliance, and the work crosses departments. Planning, building, public works, the utility district, finance, legal, IT, and administration each hold a piece of the same file.

Most Washington local governments will not struggle because they are unaware of these laws. They will struggle because development review is composed of small classification decisions that carry legal consequences, and the 2026 amendments multiplied the clocks those decisions feed.

A building-code permit may be entered as a project permit, distorting both the deadline and the annual report. A completeness letter may cite a substantive deficiency, which the statute does not authorize, leaving the start of the decision period open to dispute. A permit may be assigned a tier from its nickname rather than from whether notice and a hearing are legally required. A public meeting may be recorded as a hearing. A civil-plan referral may go out by email with no referral date, so the district's 15-day window never visibly opens. A city may stop its own clock the day a referral goes out although local work remains. A district may add 60 business days without noticing that the 120-calendar-day ceiling arrived first. A resubmitted drawing may be treated as a restart when the statute allows a restart only for a change in use. An intake form may ask the applicant to agree to an extension, which the statute prohibits at initial submission and which, if given later, removes the refund. A district refund may be waived because the city adopted three measures, which does not excuse the district. A jurisdiction may assign a point of contact and believe it has satisfied the June 2027 requirement without designating an official who holds final administrative authority.

Each of those is an ordinary error made by capable staff. Each changes a deadline, a refund, or a report. The implementation plan that prevents them is organized by workflow, not by bill number, and it is a catch-up plan: the duties HB 2418 made effective June 11, 2026 are already in force. June 30, 2027 is the separate organizational deadline.

First 30 days: identify the decision points. Map where the current statutes touch existing workflows. Do not begin with software configuration or public FAQs. Begin with classification. Which applications are project permits and which are building-code permits? Which require notice or a hearing, and has the local ordinance modified the default tiers? Which go to a district, and how is the referral transmitted today? Which completeness letters in the last year contained substantive comments? Which files carry a pause with no documented basis? Which fee components, local and district, are exposed to which refund, and does the jurisdiction rely on the three-measure exception? The output should be a short internal issue map, reviewed by planning, building, public works, finance, legal, IT, and the district's engineering staff.

Days 31 to 60: fix intake, the referral, the notices, and the counting rules. Update intake so the system captures what classification needs: project permit or building-code permit or both; notice and hearing requirements; residential status for the district and outside-entity provisions; the district and standards a referral will use; SEPA lead agency status. Separate the completeness checklist from the review checklist. Rebuild the referral as a dated transmittal that carries the district's standards in effect on that date. Review every template the statutes lean on: completeness and incompleteness determinations, information requests with the 60-day warning, suspension acknowledgments, extension agreements, district notices of incompleteness and extended review, and refund determinations. Confirm with counsel the counting conventions the calculator will use: receipt day, completeness day, weekends and holidays, after-hours electronic filings, the district's business-day calendar, the resubmission deeming question, and whether the local exclusion continues while a district awaits applicant revisions.

Days 61 to 90: assign the clocks and test real files. Map every clock to a trigger, a unit, an owner, its permitted exclusions, its required notice, its consequence, and its record: the local completeness clock, the local decision clock, the district referral clock, and the outside-entity clock. Record every pause as a dated interval with a reason, a statutory basis, a responsible entity, and a source document, and never assume a day excluded on one clock is excluded on another. Then run recent applications through the process: a residential site plan with a water-sewer referral, a short plat with critical areas review, a conditional use permit with a hearing, a design review inside consolidated review, and a building-code permit that accompanied one of them. For each, ask three questions. Did we capture the facts needed to classify it? Did the correct clock, exclusions, notices, fee treatment, and reviewer path appear? Would the file explain every uncounted day six months later? If not, the process is not ready.

By March 1, 2027: report from the record. Reporting jurisdictions should be able to export 2026 performance data, including the district's five fields, directly from the application record, with all six excluded-period categories tracked separately.

By June 30, 2027: adopt the organization. Adopt the ordinance or resolution establishing the integrated process. Designate the permit-responsible official for residential project permits and align the SEPA responsible official designation. Assign the point-of-contact function to a person, position, office, or unit with a published telephone number or email address. Confirm the local code distinguishes final administrative decisions from quasi-judicial and appellate decisions so the official's authority is clear.

Only after the legal and operational picture is clear does the technology question become useful, and the right framing for it is narrow.

AI should not be presented as a replacement for planners, engineers, building officials, district reviewers, or local government attorneys. That is the wrong model, and it invites the wrong questions. The better model is decision support.

Much of the work that precedes a final decision under these statutes is document-heavy, classification-dependent, and time-sensitive: identifying which approval is on which clock, checking a submission against the procedural checklist without drifting into substantive review, assembling a complete referral against the district's standards, tracking several clocks with different units and different exclusions, drafting written notices that meet the statute's requirements, and preserving the record the annual report needs. AI-assisted systems can help by surfacing missing procedural items, proposing the applicable clock and tier for staff confirmation, flagging a completeness letter that contains substantive comments, tracking excluded intervals against their evidence, and drafting clearer review comments.

The governing principle is explainability. A useful system should help staff see what was reviewed, which requirement may apply, what was flagged, where the supporting material appears, what judgment remains for staff, and what record will be preserved.

That distinction is the entire point. Speed without a record is not modernization. Speed with structure, traceability, and human review is. The strongest local governments will not adopt these tools merely to move faster. They will adopt them to make review more consistent, more transparent, and easier to defend.

SB 5290 and HB 2418 are part of a broader shift in how Washington asks local governments to run development review. The State is asking them to decide faster, to separate procedural completeness from substantive judgment, to hold districts and agencies to clocks of their own, to justify every uncounted day, to name one official who decides and one contact who coordinates, and to report the results every year. Those expectations are difficult to meet with email referrals, spreadsheet trackers, and informal staff memory.

Washington local governments should therefore treat these laws as implementation projects, not as legal updates alone. The work ahead is practical: classify every approval at intake, keep completeness procedural, start each clock on a documented date, send referrals that meet the district's standards, record every excluded day with its evidence, align fee logic with the refund each reviewer owes, name the official and the contact by June 30, 2027, and build the annual report from the record.

That is the real meaning of Washington's review clock. It is not only that certain deadlines now apply. It is that development review is becoming an operating discipline, and the file is where the discipline shows. The jurisdictions that adapt best will not be the ones with the longest legal memo. They will be the ones whose files can answer, for any day an application was pending, whose clock was running and why that day did not count.

Explore SwiftGov for application intake and plan review.