--- title: "Seattle capital plans: proposed and adopted versions" description: "Compare Seattle CIP editions by project number, scope, stage, and estimated dates before assigning estimating work. Keep procurement evidence separate." canonical: "https://scalewithsearch.com/articles/seattle-capital-plan-proposed-adopted-project-versions" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Seattle capital plans: compare proposed and adopted project versions A Seattle capital-plan entry can help a contractor decide which project deserves further research. Start by identifying the edition and the project number. Then compare the scope, stage, and estimated dates against the earlier entry. Keep the result separate from the decision to prepare a bid. Seattle's archive lists a [2026–2031 adopted Capital Improvement Program](https://www.seattle.gov/city-budget-office/capital-improvement-program-archives/2026-2031-adopted-cip). It also lists a [2027–2032 proposed Capital Improvement Program](https://www.seattle.gov/city-budget-office/capital-improvement-program-archives/2027-2032-proposed-cip). Those labels describe different document statuses and different six-year windows. Record each label exactly before reading a project page. This guide provides a comparison method for an estimator or business development lead. The worked project is fictional. The method supports the research described in our [public project intelligence guide for general contractors](/intelligence/general-contractors-and-construction). It does not establish an available construction contract. ## Record the edition before interpreting the change Open the [Seattle CIP archive](https://www.seattle.gov/city-budget-office/capital-improvement-program-archives) and follow the link to the required edition. Save the edition page URL with the departmental PDF you use. Record the access date separately from the years in the title. For example, an access date of October 28, 2026 describes your retrieval. It does not make every project field current on October 28. A fiscal window such as 2027–2032 describes the document's coverage. It is not a statement that a particular construction package begins in 2027. Use three separate labels in your working note: document status, fiscal window, and retrieval date. Do not collapse them into a single field named “latest.” That field becomes ambiguous when an older adopted plan and a newer proposed plan both matter. A proposed edition can contain a changed project description worth investigating. Preserve its proposed status in every summary. If you later locate an adopted edition for that window, create another comparison entry. Do not silently replace the earlier evidence or describe a proposal as adopted. Give each saved document a recognizable name. Include the department, fiscal window, and status. Keep the original PDF with your reading note so another estimator can inspect the same page. A link alone may be insufficient for reproducing your earlier interpretation if the linked file changes. ## Match the project before comparing its fields Seattle defines the project number as a unique identifier in its financial management system. The project description supplies purpose, scope, and history. These definitions appear on pages i–ii of the [adopted reader guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2631adoptedcip/cip_readers%20guide.pdf). Use the project number as the first matching field. Then confirm the department, facility or location, and description. A familiar title is useful for finding candidates, but it should not decide the match by itself. Suppose your earlier note says “service building improvements.” A later search finds two similar titles. Put both candidates in the review note until their identifiers and descriptions resolve the match. Do not merge the entries because one seems closer to your trade. Also record the project type. Seattle distinguishes discrete projects, ongoing programs, and debt service. Discrete projects have an individual asset and defined endpoints. Ongoing programs cover similar assets across years. Debt-service entries concern a dedicated repayment funding stream. The definitions are on page i of the [proposed reader guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2732proposedcip/cip_ReadersGuide.pdf). That distinction controls how you read missing information. For an ongoing program, do not invent a single construction start date. For a debt-service entry, do not convert the title into a new building opportunity. For a discrete project, look for the estimated start and end years. If you cannot find a matching entry, record the search boundary before drawing a conclusion. Name the edition, department, identifier, and pages you checked. Write “matching entry not located in the reviewed material” rather than “project canceled.” An unsuccessful search supplies no explanation for the absence. Leave the comparison open until another source resolves it. The estimating lead can request clarification or inspect another departmental section. Keep that next step beside the unmatched record. When a counterpart is found, retain the earlier search note and explain which evidence established the match. ## Read the stage as a dated planning observation Both reader guides define “Current Project Stage” against August budget planning in the budget development year. The stage therefore belongs to that planning snapshot. Preserve that timing beside the field. See page i of the [adopted guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2631adoptedcip/cip_readers%20guide.pdf) and page i of the [proposed guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2732proposedcip/cip_ReadersGuide.pdf). Do not infer the specific observation year from the first year of the fiscal window alone. Use the edition's own timing evidence when recording it. If the exact year remains unclear, retain the guide's wording and mark the year unresolved. The procurement stage also needs careful reading. Seattle's Stage 4 spans advertisement, bid review, award, and notice to proceed. One stage therefore covers several materially different procurement moments. Page ii of the [proposed guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2732proposedcip/cip_ReadersGuide.pdf) supplies that definition. An estimator cannot determine whether a bid remains open from “Stage 4” alone. The necessary next source is the current procurement record for the relevant package. Until that record is checked, write “current bid status unverified.” This is a reading boundary derived from the stage's breadth. ## Work through a fictional comparison The following example is invented. “Example Service Building” and identifier `EXAMPLE-410` do not represent a verified Seattle project. The entries illustrate a comparison between the two edition labels used above. | Field | Fictional 2026–2031 adopted entry | Fictional 2027–2032 proposed entry | | --- | --- | --- | | Project identifier | EXAMPLE-410 | EXAMPLE-410 | | Project type | Discrete | Discrete | | Description | Replace the roof | Replace the roof and renew drainage connections | | Recorded stage | Stage 2, planning | Stage 3, design | | Estimated start year | 2026 | 2026 | | Estimated end year | 2028 | 2029 | | Departmental source | Saved example A, page 12 | Saved example B, page 16 | | Current procurement evidence | Not checked | Not checked | The identifier supports a proposed match between the two entries. The added drainage work creates a scope question for the estimating lead. The changed stage creates a reason to inspect current project evidence. The later end year changes the schedule recorded in the research note. None of those observations supplies a bid date. The example also does not establish why the scope or estimated end year changed. Record the differences first. Put possible explanations in a separate question list rather than presenting them as facts. A useful summary would read: “The proposed entry adds drainage connections and records design stage. Its estimated end year moves from 2028 to 2029.” A second sentence should preserve the limit: “The adopted entry remains attached, and current procurement status has not been checked.” Avoid “project delayed one year” unless controlling evidence supports that conclusion. The comparison establishes a changed estimate between documents. It does not establish the cause, the date of a schedule decision, or the contractor's potential performance period. ## Keep estimated dates in their own column Seattle describes start and end dates as estimates for discrete projects. The guides allow undetermined dates such as TBD or On Hold. Ongoing programs do not display those dates. These rules appear on page i of the [adopted reader guide](https://www.seattle.gov/documents/Departments/FinanceDepartment/2631adoptedcip/cip_readers%20guide.pdf). Copy the source wording before assigning an internal review date. Your review date is a company decision. The source's estimated end year is a public planning field. Put them in separate columns even when both influence the same research meeting. For the fictional project, the estimator might choose to revisit the record after locating the current design procurement documents. That is a next action chosen by the estimator. It should not appear in a timeline as a city-announced milestone. When one edition shows a year and another shows TBD, preserve both. Do not fill the missing value with the older year. Explain that the newer entry no longer supplies a comparable estimate. The missing value is part of the change the reader needs to see. ## Prepare a note another estimator can verify Use a short project note with the evidence behind each statement. Start with the owner, department, project number, and project type. Then place the two edition records side by side. For each edition, record the exact title, status, source URL, PDF page, and retrieval date. Include the stage's planning reference and the date labels as printed. Attach the full project description or a short excerpt with enough context to find the original. Write the comparison in three parts: observed differences, unanswered questions, and the next source to inspect. The distinction prevents an attractive interpretation from becoming a fact through repetition. Keep unchanged fields when they establish continuity, especially the identifier and location. For the fictional example, the unresolved questions concern the drainage scope, current design status, and any separate construction package. Assign those questions to the estimating lead. Record the lead's decision to continue research, hold the pursuit, or stop reviewing it. Preserve the earlier decision when new evidence arrives. The [business memory guide](/articles/business-memory-for-ai-agents-guide) explains how retained sources and corrections support later work. In this case, the useful record is the dated comparison and the estimator's reasoning, with both editions attached. ## Decide what evidence would justify estimating work Before allocating takeoff time, identify the procurement package you would be pricing. Seek its current documents, identifier, scope, submission instructions, and amendments. Let the responsible estimator confirm whether those materials support a bid decision. Keep that procurement review separate from the capital-plan comparison. The budget document explains what was recorded in that edition. The procurement documents answer whether a specific package is available for your firm to consider now. The financial reading also needs its own check. A total project estimate and one year's appropriation describe different quantities. Use the companion guide to [Seattle CIP costs and annual appropriations](/articles/seattle-cip-total-project-cost-annual-appropriation) before assigning any amount to an opportunity record. Our [general contractor overview](/for/general-contractors-and-construction) covers the broader office record. For this research task, keep the handoff narrow: two verified editions, a defensible project match, an explicit change note, and unanswered procurement questions. The estimator owns the commercial decision. Scale With Search can discuss the source records and review steps your company wants to maintain. A written scope should identify the owners, retained documents, and decisions that require staff review. [Discuss your scope](/work) ## Source access record Seattle's archive, both edition pages, and both reader guides were reopened on October 28, 2026. The guides' printed pages i–iii correspond to PDF pages 1–3. Definitions used here come from pages i–ii. The fictional project does not reproduce an actual departmental project page. No current solicitation, qualification requirement, deadline, or contract value was verified for this example. Continue the website review: [AI-native general contractors: the first functions to build](/articles/ai-native-general-contractors-first-functions); [Which Google categories fit your contracting business?](/articles/contractor-google-business-profile-categories); [Should a contractor show a home address on Google?](/articles/contractor-google-profile-home-office-address); [Contractor website ownership: prepare the agency handoff](/articles/contractor-website-domain-ownership-handoff); [Contractor website inquiries missing from email: what to check](/articles/contractor-website-form-email-delivery); [How to reduce spam in a contractor website inquiry form](/articles/contractor-website-inquiry-spam-controls); [Contractor website license and insurance claims to check](/articles/contractor-website-license-insurance-claims); [How to write a contractor website permit FAQ](/articles/contractor-website-permit-faq); [How to show project availability on a contractor website](/articles/contractor-website-project-availability); [Should your contractor website publish project budgets?](/articles/contractor-website-project-budget-ranges); [Contractor website case studies: explain your actual scope](/articles/contractor-website-project-case-studies); [General contractor AI rules: data, approvals, and spend](/articles/general-contractor-ai-rules-data-approvals-spend); [General contractor service area pages: what earns a page](/articles/general-contractor-service-area-pages); [Home remodeling marketing: build a useful website plan](/articles/home-remodeling-marketing-website-plan); [Capital project cost and annual appropriations: read a Seattle CIP budget](/articles/seattle-cip-total-project-cost-annual-appropriation). [general contractors](/for/general-contractors-and-construction): website and search resources. ## Related: general contractors - [Capital project cost and annual appropriations: read a Seattle CIP budget](/articles/seattle-cip-total-project-cost-annual-appropriation) - [AI-native general contractors: the first functions to build](/articles/ai-native-general-contractors-first-functions) - [Which Google categories fit your contracting business?](/articles/contractor-google-business-profile-categories) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```