Washington's 2026 candidate field: 305 tracked candidates, party mix, and research depth
OppIntell tracks 305 candidates across Washington's 2026 races, with a party breakdown of 89 Republican, 122 Democratic, and 94 other — including No Party Preference candidates like John Kness. Of these, 224 have source-backed claims, meaning roughly 73% of the field has at least some verifiable public-record footprint. The average source claims per candidate statewide is 62.38, a benchmark that highlights how thinly sourced many candidates remain. For context, the top three most-researched candidates in Washington — Dan Newhouse, Marilyn Strickland, and Kim Dr. Schrier — each have extensive cross-platform profiles, while candidates at the bottom of the research-depth ranking, such as Kness, are still in the early stages of public-record enrichment. This disparity creates a competitive advantage for campaigns that invest in understanding what source-backed signals exist for every candidate in their race, not just the frontrunners.
Legislative District 3: a crowded field with 70 candidates for State Representative Pos. 1
The race for Washington State Representative Pos. 1 in Legislative District 3 features 70 candidates, making it one of the most crowded contests in the state. John Kness ranks 26th of 70 in within-race research depth, placing him in the middle tier of source-backed profile completeness. This positioning means that while Kness has some public-record context, many of his competitors may have even thinner profiles — or, conversely, a handful may have substantially more. The crowded field amplifies the importance of early research: campaigns that identify source-backed claims about each candidate can anticipate lines of attack or validation before paid media or debates begin. Kness's research depth tier is labeled 'developing,' which indicates that his public footprint is not yet fully mapped but is not absent either.
John Kness: candidate profile and public safety context from source-backed claims
John Kness is a No Party Preference candidate running for Washington State Representative Pos. 1 in Legislative District 3. His public-record profile currently contains 2 source-backed claims, both of which are valid citations. One of these claims is auto-publishable, meaning it meets OppIntell's criteria for automated publication without human review. The specific public safety signals within these claims have not been disclosed in the topic context, but researchers would examine any filings, voter registration records, or official statements that touch on law enforcement, criminal justice, or community safety. Because Kness's profile is still developing, any public safety stance he may hold is not yet fully captured in source-backed form. OppIntell's methodology flags this as a research gap: campaigns would need to supplement automated source mining with manual review of local news, social media, and campaign materials.
Research gaps: no FEC committee, no cross-platform IDs, no Ballotpedia page
John Kness's candidate research signature reveals several honestly-acknowledged gaps that shape how campaigns would approach his profile. He has no FEC-registered committee, no cross-platform IDs (such as Wikidata or Ballotpedia entries), and no Ballotpedia page. These absences are not unusual for state-level candidates, especially those running as No Party Preference in crowded fields. However, they mean that researchers cannot rely on standardized biographical summaries or federal campaign finance data. Instead, they would need to search Washington's Secretary of State filings, local government records, and any public statements Kness may have made. The lack of cross-platform verification places Kness among the 19,564 state-SoS-only candidates in OppIntell's 2026 cycle universe, compared to 1,630 who are cross-platform-verified. This gap is both a limitation and an opportunity: opponents may find it harder to build a comprehensive case, but Kness also has less control over his public narrative.
Comparative source-readiness: how John Kness stacks up against the field
Within Washington's 305-candidate universe, John Kness's research-depth rank of 143 of 305 places him near the median, meaning roughly half the state's candidates have more source-backed claims and half have fewer. His within-race rank of 26 of 70 in LD3 is slightly above the median for that specific contest. These ranks suggest that while Kness is not among the most thinly sourced candidates, he is also not among the most researched. For campaigns preparing for the 2026 primary or general election, understanding this positioning helps allocate research resources: a candidate with a median profile may be vulnerable to surprise attacks from opponents who dig deeper into local records, but also may not have a long track record that invites scrutiny. The 'thinly-sourced' cohort tag applies to candidates with 0 claims, but Kness's cohort tag is 'state-sos-only' and 'crowded-field,' reflecting that his profile exists but is limited to state-level filings.
Competitive research methodology: what analysts would examine next for Kness
For campaigns or journalists seeking to build a fuller picture of John Kness's public safety stance, the next steps would involve manual outreach and record requests. OppIntell's automated systems have mined available state-SoS data and found 2 claims, but the state-SoS-only tag indicates that no federal or third-party platforms have been integrated yet. Researchers would check Washington's Public Disclosure Commission for any campaign finance activity, local newspaper archives for mentions of Kness in public safety contexts, and any social media profiles that may have been created since the last data pull. The lack of cross-platform IDs means that if Kness has a LinkedIn, Twitter, or Facebook presence, it has not been linked to his candidate profile. This is a common scenario for down-ballot candidates, and it underscores the value of ongoing monitoring: as the 2026 cycle progresses, new filings or media coverage could rapidly change his source-backed profile.
Cycle-level context: 25,368 candidates tracked, 4,078 well-sourced, 4,000 thinly-sourced
OppIntell's 2026 cycle research universe includes 25,368 candidates across 54 states, of which 5,804 are FEC-registered and 19,564 are state-SoS-only. Only 1,630 candidates are cross-platform-verified across FEC, Wikidata, and Ballotpedia. The well-sourced tier — candidates with 5 or more source-backed claims — contains 4,078 individuals, while the thinly-sourced tier — those with 0 claims — contains 4,000. John Kness, with 2 claims, falls into the developing category between these extremes. This cycle-level framing helps campaigns benchmark their own research readiness: if a candidate has fewer than 5 claims, they are in the majority of the field, but opponents may still find damaging information in local records. The 4,000 thinly-sourced candidates represent a significant blind spot for the political ecosystem, as their public positions and backgrounds are largely unverified.
Questions Campaigns Ask
What public safety signals are available for John Kness?
John Kness currently has 2 source-backed claims in OppIntell's database, one of which is auto-publishable. The specific public safety content of these claims is not detailed in the available context, but researchers would examine any filings or statements related to law enforcement, criminal justice, or community safety. Because his profile is still developing, the public safety signals are limited and would require manual supplementation.
How does John Kness's research depth compare to other Washington candidates?
John Kness ranks 143rd out of 305 tracked candidates in Washington for research depth, placing him near the median. Within his specific race for State Representative Pos. 1 in LD3, he ranks 26th out of 70. This means he has more source-backed claims than roughly half the field but fewer than the other half.
Why does John Kness have no FEC committee or Ballotpedia page?
John Kness is a state-level candidate running as No Party Preference, and many such candidates do not register with the FEC unless they cross a fundraising threshold. The absence of a Ballotpedia page is common for down-ballot candidates who have not attracted editorial attention. OppIntell's research flags these as gaps that campaigns would need to fill through local records and manual searches.
What research gaps exist for John Kness?
Key gaps include no cross-platform IDs (no Wikidata or Ballotpedia), no FEC-registered committee, and no verified social media profiles linked to his candidate record. These gaps mean that any public safety positions or biographical details he may have are not yet captured in OppIntell's automated source mining. Researchers would need to check Washington's Public Disclosure Commission and local news archives.
How can campaigns use this information for 2026?
Campaigns can use OppIntell's source-backed profile to understand what public-record context exist for John Kness and where the gaps are. This allows them to anticipate potential lines of inquiry from opponents or media, and to decide whether to invest in deeper manual research. The comparative ranks help prioritize which candidates in a crowded field warrant the most attention.