Skip to content

Check whether a review rule can detect a known example

Use a supplied eligible example to test retrieval and coding sensitivity before interpreting an empty research result. Do not treat the check as completeness proof.

Guides

Would the procedure recognize a relevant case already in view?

A team may find no public accounts of a smart plug losing its schedule, even though a supplied discussion clearly describes that event in different words. A positive detection check asks whether the procedure recognizes a known qualifying case. It can reveal a broken query or coding rule without establishing how many unknown cases remain outside the evidence set.

Example research prompt
Test whether the supplied schedule-loss passage qualifies under the smart plug review rule. Separate retrieval from coding checks and do not infer complete recall from one known example.
01 / Guides

Choose a genuine known case

Use an inspectable, supplied passage that meets the target rule on its own terms. Include its source context and why it qualifies. Exclude invented public examples from empirical checks; a synthetic teaching example can test reasoning in a demonstration, but it cannot prove retrieval of an actual source or coverage of a live platform.

02 / Guides

Test the intended stage

Separate query detection from classification. A case may be available in a result set yet missed by the coding rule, or absent from retrieval despite clear eligibility. Record which stage was checked. Do not describe a manual recognition exercise as proof that a tool retrieved the case if that retrieval was not actually observed in the authorized test.

03 / Guides

Revise and re-evaluate

If the known case is missed, inspect wording variants, context requirements or rule definitions and change the specific failure point. Preserve the original failure and revised procedure. Avoid broadening the rule so far that unrelated schedule complaints qualify; a useful fix improves detection of the intended concept without sacrificing the topic boundary that makes the review interpretable.

04 / Guides

Deliver a sensitivity warning

State what the positive check demonstrated and what it did not. Recognizing one known case supports local detectability, not complete recall of every relevant discussion. If the procedure still misses the example, keep negative findings provisional and explain the unresolved detection issue rather than reporting no evidence found as though the review had a functioning opportunity to find it.

Keep the boundaries clear.

  • Detecting a known case is a local check, not a guarantee that all relevant cases were found.
  • Illustrative methods and platform badges do not constitute live verification or complete coverage.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-13. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage