Document a failed filing search without claiming nonexistence
When a filing search fails, record what you searched and what failed. “Not found” should mean no match in a defined search, not that the document or event does not exist. A useful negative-result log tells the next researcher where coverage ends and what to try next.
SEC search, the HKEXnews guide, and CNINFO are official starting points for different markets. Each route has its own fields and behavior. The log below documents your actual attempt rather than claiming complete coverage of those systems.
Distinguish four failure states
No match means the query returned no candidate. Access failure means a page or file could not be retrieved. Unread content means a candidate exists but has not been inspected. Identity uncertainty means you cannot yet confirm that the selected entity is the intended one. Keep those states separate because their next actions differ.
A timeout should lead to retrying or using another official route, not changing the claim to “no disclosure.” An overly narrow category should lead to a broader query. A similarly named company should lead to identity checks. A file that opens but has not been read should remain unreviewed, not verified.
Hypothetical failed-search ticket
Suppose a colleague mentions an acquisition notice for fictional Valley Optics. Your first title search returns nothing. The case is hypothetical.
| Field | Record |
|---|---|
| Intended issuer | Legal identity and market still to confirm |
| Query | Selected code, explicit dates, acquisition title phrase |
| Result | No match in this query |
| Possible gap | Event may be filed under subsidiary or different wording |
| Next step | Verify issuer, widen title wording, then date window |
| Stop condition | Record coverage and keep claim unresolved if still absent |
This ticket is more valuable than “could not find it” because it supports a targeted follow-up. It also prevents another researcher from repeating exactly the same search without realizing that identity was never confirmed.
Change one dimension at a time
Check identity first, then date window, form or document category, language, and wording. Preserve the sequence. If you remove every filter simultaneously and discover a candidate, you may not know which assumption was wrong. A controlled sequence reveals whether the initial gap was caused by wording, timing, or entity selection.
Record a plausible candidate separately from a confirmed match. Open its cover and relevant passage. A document can mention the desired project without being the announcement you sought. Do not allow a familiar phrase to bypass the ordinary identity and period checks.
Write the final research status precisely
A useful final status might say: “No matching announcement located in the listed official searches through the review date; two inaccessible candidates remain; event claim unresolved.” This communicates both work performed and remaining uncertainty. It does not imply every historical document has been examined.
If the task has a practical time budget, state the search boundary and save the ticket. A bounded stopping point is legitimate. Replacing the unresolved claim with an invented answer is not. Define what would reopen the search: a better issuer identifier, a direct file reference, a new disclosure, or a corrected date.
Verification and limitations
Try to reproduce the last query from your saved fields. Confirm that the logged result describes what actually happened. If the interface changed or the page is dynamic, preserve enough text to explain the earlier attempt without claiming the result will remain identical forever.
This log measures search coverage, not the probability of an event. It does not establish legal compliance, concealment, or absence of a contractual relationship. Common mistakes are merging timeouts with empty results, deleting failed attempts after a later success, and marking unchecked candidates as evidence. Keep the search history linked to the eventual confirmed source.
A final record check
Keep the successful query that eventually resolves the ticket beside the unsuccessful one. Compare the changed field and record what explained the failure. If the cause was a renamed entity or unexpected title wording, add that fact to the identity or search-aid record. This converts an isolated frustration into a reusable retrieval improvement without claiming that the next search is guaranteed to succeed.
FAQ
Is a failed search worth keeping after I find the document?
Yes, if it explains an identity or wording problem and helps future searches. Link the successful source and close the ticket with the resolution.
Can repeated empty searches prove no announcement exists?
They strengthen the record of coverage, but the conclusion must remain bounded by sources, dates, and filters inspected. Avoid an unqualified nonexistence claim.