Three dates answer different questions
An export date records when a list was saved. A check date records when someone revisited a source. A service update date concerns a change announced by the provider. They should not be substituted for each other.
Do not refresh a claim by changing the label
Moving a listing into a new annual sheet does not verify its current state. Preserve the original reference and document any new checks. If you did not inspect a detail again, do not describe it as reverified.
Make uncertain fields visible
Use plain notes such as “not checked” or “option unclear.” An empty cell can mean several things, so a short explanation is often more useful. Avoid marking a product available solely because the page still loads.
Build a meaningful review cycle
Revisit items you are actively considering. Archive irrelevant entries rather than repeatedly refreshing the entire collection without a purpose. A smaller dated shortlist can be more useful than a large list with unclear provenance.
Identify the event behind every date
A date field is most useful when its label names an event. Saved on, exported on, checked on, and revised on describe different actions. A bare date at the end of a row leaves readers to guess which action occurred. Add the event label before you add more date fields. This often resolves confusion without requiring a complicated history system or a separate tab for every update.
Consider a listing you saved in one month and revisited in another. You may have checked only the selected option during the later visit. Record that as an option check rather than using the later date to refresh the whole row. If someone else imports the sheet, they can then understand which observation was made at which time. The distinction is equally important for images: a file download date does not establish when the photograph was taken or when the item shown was handled. Label the event you know instead of supplying an event you cannot establish.
Separate annual labels from product release claims
An edition label organizes the document. A product release year describes a claim about the product. Do not move the first into the second merely because the row appears in an annual list. If a listing title contains a year, retain it as source wording and investigate it separately if the distinction matters. The date of your collection is not independent evidence for a product release or revision.
This is useful when several visually similar entries appear across saved editions. Compare their actual identifiers and option details rather than assuming the later sheet contains a newer product. A repeated reference may simply be a candidate carried forward. A changed identifier may describe another offer without establishing a new model. Record what changed at the reference level and keep any product-year question separate. That makes the annual edition honest about its purpose and gives future readers a better basis for deciding whether two rows represent a meaningful difference or a change in your filing system.
Handle conflicting observations without hiding the conflict
If an older note and a new source detail disagree, keep both long enough to understand their context. Check whether they describe the same listing, the same option, and the same measurement method. A difference may reflect a changed source, a different selection, or an earlier copying error. Those explanations require evidence; the newer timestamp alone does not tell you which one applies.
Write the conflict in a short note with links or references to both observations. Identify the next check that would help resolve it. If a correction is established, label the earlier value corrected rather than simply deleting the history where it matters. If the cause remains unclear, keep the field unresolved for decision purposes. This prevents a tidy table from concealing a real uncertainty. A date-aware sheet should make it easier to see when information changed, not make disagreement disappear by always choosing whichever value was entered most recently.
Decide what deserves a refresh
Not every row needs the same review schedule. A candidate you intend to investigate soon deserves attention to the fields that affect that next step. An archived reference may need no update at all unless you reactivate it. Separate active and inactive items so a review does not become an exercise in reopening links that no longer serve a purpose. This is a practical way to keep a dated collection manageable.
When you do refresh an observation, record what you checked and the source used. Avoid writing a general updated label if you only confirmed that a page opened. A working address answers a navigation question; it does not establish current options, availability, or product condition. By naming the check, you can use the date appropriately later. The result is a more useful 2026 reference: one in which the age and scope of observations are visible, and the next review follows your actual decision needs rather than a cosmetic calendar routine.
A practical exercise
Review a date in one of your existing notes and write the event it describes. If you cannot tell whether it means saved, exported, or checked, mark that uncertainty rather than selecting a meaning from convenience. Add a clearer event label for the next observation you make. This small repair is useful even when the old history cannot be reconstructed: future entries can be more precise without making the earlier record appear more complete than the evidence allows.