Elections staff search a candidate's name and keep hitting a different person in another county. How should they disambiguate?
Select an answer to reveal the explanation.
Short Explanation
Same name, different county is the 'which Washington?' problem. Place plus an official-site operator keeps you in this election, not someone else's LinkedIn. The first hit is a ranking accident, not a voter roll.
Full Explanation
Name collision is solved with geographic and official-domain constraints: add city or county context and a site restriction to the official county domain rather than trusting the first same-name hit. Assuming the first hit is the local candidate because the names match is a classic false-positive. Messaging both people from a staff account to ask who is running mixes contact with research and may be inappropriate. Ignoring official election sites and relying on campaign ads only discards authoritative civic sources. Exam caveat: candidates can share names inside the same county—add office sought, residence locality, or committee identifiers when needed. Operational check: require a hit on the official elections domain (or equivalent) that matches jurisdiction before promoting a candidate identity into the elections OSINT file. Keep the civic purpose, method limits, and exhibit labels aligned so reviewers can see what was public-source work versus other authorities. Document residual uncertainty explicitly rather than implying completeness. Prefer reversible public methods and preserve exhibits that a second analyst can reopen without guessing. When sources conflict, record both locators and state the confidence level in plain language.