Define one use case, save no more than five first-pass candidates, remove near-duplicates, and reduce the list to two or three rows that satisfy the same requirement. Give every saved row a one-sentence reason.
Define the use case before searching
Write the situation the item must serve: daily use, a specific size constraint, a compatible device, a weather condition, or a gift deadline. A use case is more useful than a broad category because it tells you which fields matter.
Set one requirement, two preferences, and one rejection rule
Requirement
The condition every candidate must satisfy.
Preferences
Two features that can help rank candidates after the requirement passes.
Rejection rule
A missing fact, unsafe redirect, incompatible option, or other condition that ends review.
Limit the first pass
Save up to five candidates that appear to meet the use case. This is a working limit, not a claim that five is universally best. Its purpose is to force a reason for each save and prevent endless collection.
Remove near-duplicates
If two rows lead to the same destination or appear to describe the same option, keep the one with better notes, clearer photos, or more useful measurements. If they differ meaningfully, write the difference in one sentence. If you cannot explain the difference, you probably do not need both.
Reduce the list with evidence, not enthusiasm
| Pass | Question | Action |
|---|---|---|
| Identity | Does the destination still match the saved row? | Remove broken or repurposed links |
| Requirement | Is the non-negotiable option or measurement confirmed? | Move missing evidence to unclear or reject |
| Coverage | Do photos show the category-specific details you need? | Request evidence or favor clearer rows |
| Difference | Does this candidate add a real alternative? | Remove near-duplicates |
| Preference | Which remaining row best matches the two preferences? | Rank only after requirements pass |
Give every saved row a one-sentence reason
Use a sentence that names evidence: “Keep because the required 58 cm width is shown and the source option matches.” Avoid vague notes such as “looks good” or “popular.” If you cannot write a concrete reason, move the row out of the active shortlist.
Review in a consistent final order
Check source match, exact option, measurements, photo coverage, visible price context, weight or bulk notes, then safety and policy questions. This order keeps presentation and price from dominating before the basic match is established.
Separate discovery from the final decision
Use the first pass only to collect plausible candidates. In the second pass, hide or remove every row that fails the requirement, lacks essential evidence, or duplicates a stronger row. This separation prevents an attractive thumbnail or low starting price from becoming an accidental commitment. If two finalists remain, write the one unresolved question that could change the ranking. A shortlist is ready when each remaining row has a clear reason to stay, every rejected row has a repeatable reason to leave, and the next check is specific enough for another person to follow.
Copy this shortlist log
Use case: [one sentence]
Requirement: [one condition]
Preferences: [two details]
Reject if: [one stop rule]
Candidate: [name / URL]
Save reason: [evidence-based sentence]
Missing evidence: [one question]
Status: [keep / unclear / reject]
Next action: [compare / ask / remove]