Finding no evidence supports a statement about what your search located, not an unrestricted claim that an event never happened. Write the search boundary into the conclusion, especially when an AI-assisted answer sounds more certain than the underlying investigation.
Separate three different conclusions
As an editorial rule, distinguish “not found,” “not recorded in a defined collection” and “did not happen.” These require different support.
The first describes your investigation. The second needs a sufficiently inspected, clearly identified collection. The third usually requires affirmative evidence or a justified argument about why the event would necessarily have left an observable record.
For Indian research, consider whether relevant records might use regional languages, older organisation names or different spellings. These are search-planning questions, not reasons to assume a missing event occurred.
Complete a search-scope disclosure worksheet
Attach these fields to every proposed absence claim:
- Claim: the precise event or behaviour being investigated.
- Period: dates included and excluded.
- Places and entities: locations, institutions and name variants.
- Collections searched: named archives, publications or supplied documents.
- Queries: keywords, alternate spellings and languages used.
- Access gaps: unavailable issues, blocked pages or incomplete indexes.
- Search date: when the investigation ended.
- Residual uncertainty: plausible places where evidence could remain.
Judge the worksheet by reproducibility. Another editor should understand what was searched and what a further search would need to add. Do not describe a collection as complete unless that completeness has itself been checked.
Rewrite a hypothetical overclaim
Imagine a writer investigating whether a fictional college held a robotics workshop between January and June 2025. They inspect six public newsletters and the accessible events archive, using English queries only.
Unsafe wording: “The college never held robotics workshops.”
Bounded wording: “No robotics workshop was identified in the six January–June 2025 newsletters and accessible events archive reviewed. Regional-language notices and offline records were not checked.”
The revised sentence preserves a useful finding without pretending the search covered every year or every possible record. Its limitations are relevant information, not an apology.
Set the next search or stop
Escalate when the absence claim could damage a person’s reputation or drive a major decision. Seek an authoritative record, ask a precise verification question, or remove the categorical wording. For a low-stakes brief, a disclosed search boundary may be enough.
If browsing the AI tools catalog for research support, check access format and save terms before buying. Marketplace account, code or token offers are not proof of official subscription equivalence; purchasing access does not establish exhaustive retrieval.
Sources and scope
Source material checked 29 October 2026; features/policies may change. The supplied Perplexity citations reference narrowly establishes source links for inspecting cited material. Direct fetching was blocked; no broader search-coverage claims are made. The worksheet and cautious wording are editorial advice.