Define the specific decision
Label where each item is displayed and avoid merging different lists without an explicit check.
For candidates relevant to “Keep site and Steam inventory lists separate”, use the skin finder. Keep this task separate from your broader inventory plan.
Read the worked example
A teaching sheet marks three entries as displayed on a site and two as checked in Steam; the combined view keeps those labels.
An observation list does not replace checking each interface. Write down what you actually see: a site-inventory card, a Steam-interface entry or a separate pending-action status. Matching names do not yet connect two records into one confirmed fact. Use an identifier where available and preserve the observation time. Keep rows separate until their connection is established. Avoid counting one item twice solely because it was viewed in two places, but do not merge records based on a short name alone either. When a status changes, retain the previous observation as history and date the current one. The sheet should reveal uncertainty rather than hide it behind one inventory label.
| Entry | Interpretation |
|---|---|
| Site | a separately observed card |
| Steam | an independently checked entry |
| Connection | confirmed rather than guessed from a name |
Use this task checklist
- Add a displayed-location column.
- Review each list independently.
- Retain the status of unconfirmed movements.
Recognise the failure condition
Treating an identical name in two interfaces as proof that a transfer has completed.
The sheet shows where each entry was observed and what still needs checking.
Apply the additional check
Observation history needs no sensitive account data: location, distinguishing item details, date and observed status are sufficient. Remove private links and tokens when sharing the sheet. Do not label an entry received merely because it appears in a wishlist or pending action. When interfaces disagree, retain both observed labels and their times rather than choosing the more convenient version. This supports later checking without creating false confidence that a process has finished.