For a Seattle building permit search, start with SDCI’s Permit and Site History map to identify the address and development site, then use the Seattle Services Portal for project, permit, inspection, related-record, and document information generally available from 2005 forward. For older work, follow SDCI’s permit and property records, scanned microfilm, and public disclosure routes instead of treating a portal blank as a no-permit finding.
Official route checked August 26, 2026: Seattle Department of Construction and Inspections. Recheck SDCI’s current research page, development-site identity, 2005 system boundary, historical collections and disclosure route before relying on Seattle records.
Match the Seattle property before reading permits
Seattle permit research depends on more than the mailing address. SDCI uses a development site as a property boundary for applying code standards, and one site can involve several addresses or parcels. Write down the full civic address, unit if relevant, parcel number, corner or range address, and any former street form you can support.
Open SDCI’s Permit and Site History map. The city tool lets a user start with an address or select a site on the map and describes its purpose as discovering site information, permits, and other records. Confirm the selected geometry before downloading or recording results. A pin on an adjacent parcel can produce a plausible but wrong permit history.
The address not found guide provides a recovery sequence for range addresses, missing units, and parent-site records.
Divide the search at the 2005 system boundary
SDCI’s official Research a Project, Permit, or Property page explains the available record layers. It routes current research to the Seattle Services Portal and describes permit and inspection information from 2005 to the present. It also explains historical resources, including SDCI permit and property records and microfilm material.
Put the likely project year beside that boundary. A 2018 alteration belongs in the current portal branch. A 1980 addition belongs in the historical branch even if later scans appear online. If the date is uncertain, search both and preserve the evidence that links records across systems.
Search the current portal by project identity
Use the city’s Seattle Services Portal for records within its documented era. Begin with the verified address or known project or permit number. Save the record number from every plausible result, then open the detail rather than relying on a summary card.
For each record, capture the applicant when public, project description, record type, permit status, inspection status, related permits, and document list. Separate the application or project record from the issued permit and from trade records. A single development project can have construction, electrical, mechanical, land-use, demolition, or other related files with different statuses.
The building application records guide helps keep review-stage evidence separate from authorization and completion.
Read status, inspections, and documents as separate tracks
Create three tracks for a selected record. The status track follows application, review, issuance, expiration, or closure labels. The inspection track records inspection type, result, and date. The document track lists plans, corrections, approvals, and revisions that the public portal makes available.
Do not use one track to fill a blank in another. An issued permit does not prove the final inspection passed. A document upload does not prove the underlying work occurred. A final result on the parent construction permit does not automatically close every trade permit. Use the final inspection status check when an open item affects a purchase, renovation, or financing decision.
Follow related records without merging them
Open each related record and retain its own number, type, address, scope, status, and dates. Confirm whether it belongs to the same development site and work episode. Similar descriptions or contractors can support a research hypothesis, but the record link or shared project identifier is stronger evidence.
If a trade permit does not appear as related, search the property and date band by record type. If a portal result points to a parent site rather than the unit, keep both identities visible. This prevents an unresolved child permit from disappearing inside a one-line project summary.
Move older projects into SDCI’s historical resources
The Research a Project page describes SDCI’s Permit and Property Records library, including older permit material, scanned plans, microfilm, and microfiche eras. It advises users to contact the Microfilm Library when something cannot be found in the Services Portal or the permit and property records. Follow that agency route for pre-2005 work, missing plans, or records outside public portal coverage.
Prepare the historical search with the development-site identity, current and former address, parcel, approximate construction years, owner or applicant if known, and any record-number fragment. Ask for the precise family needed, such as a permit application, approved plan, inspection card, certificate, or related trade record.
Distinguish document date from upload date
SDCI warns on its research page that an upload date may not be the date of the document’s contents. Preserve both. A plan drawn in 1965 and scanned decades later remains a 1965 project document, not evidence of recent work. Likewise, a microfilm index can point to a file without displaying every page.
For each historical item, record the document title, original date, scan or upload date, record number, address or development site, page range, and legibility. Note missing sheets and unexplained gaps. This simple dating discipline prevents a modern digitization event from distorting the building chronology.
Use public disclosure for a targeted unresolved record
When the published research routes do not provide a needed departmental record, SDCI’s Public Disclosure page explains that the department has a Public Disclosure Officer and provides the process for an SDCI public records request. Use it after documenting the portal and historical searches.
Name the property, development site or parcel, record numbers, date band, and document families. Explain which official systems were checked and what was missing. A narrow request for a known permit’s inspection card or an older plan is more actionable than asking for everything ever associated with the address.
Keep a Seattle evidence ledger
Create one line per source event and keep the fields separate:
- checked date, system, and exact property input;
- selected development site, parcel, and record number;
- record type, scope, status, and inspection result;
- document title, original document date, and upload date;
- unresolved question and the next official route.
Attach saved reports or screenshots where permitted.
Finish with a qualified statement. The retrieved SDCI records may support an issued permit, named scope, and recorded final inspection for a specific project, while older plans or a related trade record remain unresolved. That conclusion is repeatable and useful. It does not claim that the online systems contain every historical record or certify the building’s present condition.