Hemp in Washington
Open-knowledge reference entry
Hemp in the U.S. state of Washington has emerged as an experimental crop in the 21st century.
Historical production
The U.S. Government reported no hemp production in Washington in 1890, nor did the state government in 1914 or 1922.
Related crops in Washington
Cannabis and Humulus lupulus are both members of the family Cannabaceae, and a number of similarities in the botany and human use of the two species have been noted. Humulus lupulus produces hops, a crop grown in quantity west of the Cascades historically (especially the Snoqualmie and Puyallup River valleys) and is a major 21st century crop in the Yakima Valley.
Prohibition and legalization
All cannabis was made illegal by the Washington State Legislature in 1923.
Although Washington voters legalized marijuana in 2012 with I-502, the initiative did not authorize hemp cultivation or sales.
In accordance with the Federal 2014 Farm Bill, the state legislature created an Industrial Hemp Research Pilot (IHRP) in 2016 following passage of ESSB 6206 (codified as Revised Code of Washington Chapter 15.120), with regulation by the Washington State Department of Agriculture. Industrial hemp is defined in Washington as cannabis with a THC concentration of 0.3 percent or less by dry weight. Under the 2018 farm bill, the state's Department of Agriculture is recognized by the United States federal government as the regulator for industrial-scale non-experimental hemp production.
State law defines hemp-derived products containing less than 0.3% THC as "Cannabis Health and Beauty Aids".
This brief starts where responsible research should: with the source description of “Hemp in Washington” as open-knowledge reference entry. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the general reference register because the source frames it as open-knowledge reference entry. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated May 22, 2026. The linked authority identifier is Q55613610. None of the 0 selected statements returned an explicit reference. The first chronological checks are 1890, 1914, 1922 and 1923.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Hemp in Washington”, its source revision and the description used here.
- Expand the search: follow Hemp in Washington primary sources, Hemp in Washington archive and Hemp research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Hemp in Washington”?
- Which institution is responsible for the underlying evidence?
- Which cited source is closest to the event, object or claim?
Search terms from this dossier
This entry incorporates text from “Hemp in Washington” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.