A Seattle permit status is useful only when you know which record it describes and which documents belong to that record. A site can have several applications, permits, and historical files. Reading one status at the top of a result and treating it as a verdict on the whole property skips the relationships that make the information meaningful.
Seattle's Department of Construction and Inspections, or SDCI, provides a research landing page, the Seattle Services Portal, and a Permit and Site History Research Tool. This guide proposes a workflow for connecting those official resources for sites within Seattle. It does not report a tested property search or certify a building's present condition, legal use, or completeness of records.
Start from SDCI's research page
The official Research a Project, Permit, or Property page is a useful starting point because it connects the department's current research resources. Use that page rather than relying on a bookmarked third party search result. Record which tool you enter and the question you intend to answer before collecting screenshots.
SDCI announced its consolidated Permit and Site History Research Tool in July 2025. The announcement describes address and map searches, links to current and older permitting systems, and access to available plans and historical documents. It also describes filters for date, record type, and keyword. These functions support discovery, but the source record still needs to be examined.
The distinction matters if you have used older Seattle instructions. A new entry point can connect several resources without making their underlying dates and record types identical. Keep the current research page as your route back to official guidance when a saved interface description no longer matches the screen.
Identify the site before selecting a permit
Search using the address you have, then compare the returned site information with the intended location. The new tool's official description specifically mentions the relationship between addresses and Development Sites. Do not assume that a single address necessarily describes every record associated with a larger site or that every related address is interchangeable.
Preserve the displayed address and any site or record identifiers under their actual labels. If the result groups several addresses, retain that grouping in your notes. Selecting the first result that contains a familiar street name can attach a permit to the wrong location, especially when you later strip away the map context.
This is a Seattle workflow. A King County record linked from the tool may provide useful context, but a countywide reference does not mean SDCI is the permit authority for every location in the county. Confirm that the site falls within the jurisdiction relevant to the record you seek before interpreting an empty Seattle search.
Separate the site index from the permit record
A site history result can point to several records. Open the particular record relevant to your question and record its number, type, and displayed status. Keep a separate row for each record. A site level list is a finding aid; it should not be flattened into one imagined project with one status.
For example, an invented site might show a land use record, a construction permit, and a trade permit. Those entries can relate to the same location without having identical dates or outcomes. The research task is to document the relationship the official records show, not to merge them because they appear in one search result.
If the records explicitly cross reference one another, save that connection. If they do not, use wording such as same site, relationship not established. This leaves room for clarification and prevents a timeline from implying that one permit completed another administrative process when the source never says so.
Read the official status definitions
Seattle's status help distinguishes several labels that sound similar in ordinary language. Application Completed means the application has been accepted but review has not started. Inspections Completed still leaves final administrative tasks and outstanding fees before closure. Closed can reflect several administrative reasons. These distinctions show why a plain English guess about complete is unreliable.
Use the official definition for the exact label you see and keep the record type in view. Do not paraphrase every favorable looking status as finished. If the status description refers to a stage or phase, preserve that qualification. A shorter summary should not erase the part of the definition that limits its meaning.
The help page was updated in June 2026 when reviewed for this article. Check the live official guidance when interpreting a current record, especially if the wording has changed. Your research note should include both the label observed and the date you consulted the definition, rather than treating a saved glossary as permanently current.
Inspect the document history as a separate task
After identifying the record, review the associated document list and note document type, date, and any version information supplied. A plan, application form, correspondence item, and issued document do not serve the same purpose. Keep their names intact rather than renaming every attachment approved plans for convenience.
The research tool's quick sheet describes a Plans, Documents and Historical Records area containing materials associated with record numbers. Use the record number as the connection back to your evidence table. An attachment found through the site is not automatically the latest or controlling document for every question about that location.
If several versions appear, do not choose solely by file size or download order. Look for the official version labels and the document's own date or status. If the applicable version remains unclear, ask SDCI which document answers the specific question. The record list can reveal an ambiguity without resolving it for you.
Keep dates from different stages separate
Use separate fields for application, issuance, inspection, document, and retrieval dates when those events are shown. A document upload date may describe the filing of a document rather than the date the depicted work occurred. Preserve the source label so a later reader does not mistake an administrative timestamp for a construction event.
In an invented example, a plan file has an April date, the permit record shows issuance in June, and the researcher downloads both in October. The evidence supports three differently labeled dates. It does not establish that construction lasted from April to June or that the site was inspected in October.
When a date is missing, mark it missing in the material reviewed. Do not borrow a date from an adjacent record or use the current year as a placeholder. An incomplete but accurate timeline gives the agency a clearer question than a polished chronology that conceals how its dates were inferred.
Use older record routes when the question requires them
The Seattle Services Portal's permit search directs users researching permit history older than 2005 toward SDCI's Permit and Property Records. Treat that instruction as a coverage clue. A search in the current portal may not be the appropriate endpoint for a question about an older structure or historical alteration.
SDCI's research page also explains that documents have been scanned and uploaded through an ongoing library process. If a relevant file is not available through the online route, do not assume it never existed. Note the record reference you found and the specific missing document before using the department's further research guidance.
The official page identifies the Microfilm Library as a contact when the available tools do not locate what is needed. Ask a focused question that includes the project address and permit number where known. Avoid requesting a broad assurance that the property has a complete history when your actual need is a particular document.
Filter without hiding the evidence you need
Date, record type, and keyword filters can make a long site history manageable. Record the filters used so an empty result remains interpretable. A search limited to one record category says nothing about categories you excluded. Likewise, a keyword based on an advertisement may not match the wording used in administrative records.
Begin with a broader view of the confirmed site, then narrow deliberately. If a relevant record disappears after a filter is applied, note why it was excluded rather than concluding it is unrelated. A filter is a research choice, not a statement by the city that other records do not matter.
When exporting or saving results, preserve the filter context alongside the file. A document named Seattle history is too broad if it contains only a five year slice of one record type. A clearer filename or cover note makes the scope visible to anyone who opens it later.
Create a status and document evidence sheet
Use one row per record with columns for site reference, record number, type, status, definition source, relevant document, document date, and retrieval date. Add a short unresolved question field. This keeps the administrative state and supporting material close together without pretending that every document proves the same thing.
For an invented example, a row may show a status copied from the portal and a plan document whose applicability remains uncertain. Mark that uncertainty explicitly. Do not suppress the document because it complicates the story, and do not use it to overrule the status without clarification from the responsible office.
Save links that lead back to the official record when available. Screenshots should include enough context to identify the record, but public examples should avoid unnecessary private contact details. The purpose is reproducibility of the administrative research, not publication of personal information found along the way.
State the limit of the conclusion
A careful result can explain which Seattle records were located, how the displayed statuses are defined, and which documents were reviewed. It should also identify gaps, such as an unavailable historical file or an unclear connection between two records. Those gaps are findings about the search, not automatic findings about the building.
Do not turn a completed administrative status into a present day safety guarantee. Physical conditions can require direct assessment, and legal questions can require interpretation beyond a portal label. Keep the report focused on what the official records actually establish and route consequential uncertainties to the appropriate agency or qualified professional.
Seattle's tools are most useful when the researcher keeps site identity, record status, and document history distinct. Connect them with their official identifiers, read the current definitions, and preserve the dates and limits of the search. That produces a clear question trail and a useful record summary without asking one status word to explain an entire property.
Sources and scope
Official sources were reviewed for this guide. The proposed research workflow is not a report of a tested property lookup. Examples are invented and identify no private property owner. Interface labels and records can change; verify important findings with the responsible agency.