Keep six fields: public link, category, intended option, strongest evidence, unresolved question, and next decision. Give every row one state—keep, compare, or remove—and delete rows that no longer have a clear reason to exist.
The six fields that earn their space
1. Public link
The current product or directory destination, never an account, order, payment, or tracking URL.
2. Category
One product type that determines which photos, measurements, and weight questions apply.
3. Intended option
The color, size, bundle, or model you actually mean to compare.
4. Strongest evidence
The clearest reason the row survived: useful measurements, photo coverage, or relevant source detail.
5. Unresolved question
One missing fact that could still change the decision.
6. Next decision
A concrete action: compare size, find weight, recheck source, keep, or remove.
Use three states instead of a vague favorite list
The row passes the basics and has one explainable reason to remain.
The row may be useful, but a named uncertainty still needs evidence.
The destination is stale, the identity is unclear, or the row offers no advantage over a better candidate.
A compact note you can copy
Public link: [current product or category URL]
Category: [one product type]
Option: [color / size / bundle / model]
Best evidence: [what this row explains well]
Still unclear: [one question that could change the decision]
Next decision: [keep / compare / remove + action]
Do not add fields “just in case.” A field earns its place only when it changes what you compare or what you do next.
Keep the shortlist about public product research. Do not store passwords, account links, payment details, delivery addresses, private order references, or support conversations beside product rows. Those details do not improve comparison and create unnecessary privacy risk if the file is shared.
Example: a shoe row that remains understandable
Category: everyday shoes
Option: dark color, size based on insole length rather than the tag alone
Best evidence: both side views, heel, outsole, interior label, and a clear length reference
Still unclear: whether the listed weight includes the box
Next decision: compare packed-weight context with the other finalist
The note does not claim the item is good or verified. It explains what is known, what is missing, and why the row still deserves space.
Collapse duplicate and near-duplicate rows
Two saved rows may point to the same source page, the same images, or the same option set under different labels. Keep one primary row and add the alternate link only if it offers a meaningful difference, such as clearer measurements or a distinct live option.
- Same URL and same option: keep one row.
- Different URL but identical evidence: keep the clearer destination and note the duplicate.
- Same product family but different material, size method, or bundle: keep separate only if the difference matters.
A review routine that prevents stale notes
- First pass: qualify or reject. Do not research every row deeply.
- Comparison pass: keep no more than three serious candidates per product question.
- Return pass: revisit later and remove rows whose reason no longer feels strong.
- Final recheck: reopen the live source, intended option, photos, sizing, weight context, and current policies before acting.
Add a short “checked on” date when a row reaches the final comparison. The date does not guarantee freshness, but it separates a recent recheck from an old saved link. If the destination, option, or evidence changes later, return the row to compare status instead of silently keeping the earlier conclusion.
Schedule the return pass around the decision, not around an arbitrary daily habit. A row being used this week deserves a fresh check; an idea with no planned next step should be archived so it does not crowd the active shortlist.
A shortlist is finished when every remaining row has a reason, an uncertainty, and a next decision.
