A shortlist is a decision system, not a bookmark folder
Links are easy to collect and hard to remember. After a few days, a familiar thumbnail no longer tells you whether the size chart was complete, which version you meant, or why another candidate was rejected.
A decision log solves that memory problem. Each row should let you understand the candidate without rebuilding the research session from scratch.
The eight fields that earn their space
| Field | What to record | Why it helps |
|---|---|---|
| Item + category | Plain language: “black zip hoodie” | Keeps unlike products out of the same comparison. |
| Source link | The page closest to the original listing | Lets you return to the evidence instead of a broad result page. |
| Variant | Color, size, version, model, or batch note | Separates lookalike listings and prevents option mix-ups. |
| Evidence | The photos or details that answer your question | Records what the row proves, not merely what it claims. |
| Fit or specs | Measurements, dimensions, connector, capacity | Captures the detail most likely to make the item unusable. |
| Cost context | Item price plus weight and packaging assumptions | Makes comparisons less dependent on the headline price. |
| Main risk | One unanswered question or deal-breaker | Shows what must be resolved before the row can advance. |
| Status + action | Compare, wait, reject, shortlist — then a verb | Makes the next session obvious without reopening every tab. |
One row, written for the next session
Example · hypothetical hoodie candidate
- Item
- Charcoal zip hoodie · clothing
- Variant
- Size L · charcoal · heavyweight option
- Evidence
- Front, back, cuff, zipper, and flat measurements shown
- Risk
- Fabric weight is described but not independently confirmed
- Status
- Compare
- Next action
- Place beside two similar hoodies and compare chest width and packed weight
The note is short, but every line changes what happens next. “Nice hoodie” would not survive a week away from the sheet.
A 15-minute workflow for new finds
- Define the need. Write the category and use before opening a result grid.
- Collect at most five candidates. More rows make the first comparison slower without improving it.
- Normalize the facts. Use the same fields, units, and status words for every candidate.
- Name the unresolved risk. Fit, material, source mismatch, missing angles, compatibility, or weight.
- End with a verb. Compare, request, verify, wait, shortlist, or reject.
Use a small status vocabulary
Status should describe the row, while the next action describes you. “Wait for evidence” is a status; “check chest measurement on Friday” is an action.
The weekly cleanup rule
Review the shortlist from oldest to newest. Reopen only the rows that still answer a real need. Archive a row when the destination changed, the evidence no longer matches the note, the main risk cannot be resolved, or another candidate clearly replaces it.
- Every active row has a working destination and recognizable item.
- Measurements and specs use consistent units.
- The evidence note describes what is visible, not what is assumed.
- The status and next action still agree.
- No two rows fill the same role without a named difference.
Keep mobile notes scannable
On a phone, put status, risk, and next action near the front of the row. Use short phrases and move long background notes to a separate cell or document. The best mobile row answers three questions immediately: what is it, what is wrong, and what comes next?