Record source date, QC record date and evidence freshness.

A screenshot saved today may show a listing from last month. A QC gallery opened today may contain photos taken much earlier. A review written today may rely on a record that has since been replaced. Storing only “checked today” hides those differences and makes later verification unnecessarily difficult.

This QC evidence freshness record applies to already-found listing and inspection material. FindQC can surface research records and product intelligence where available, but it does not place orders, operate a warehouse, photograph the buyer’s unit or execute a return. Those actions belong to the buyer-selected agent. The record’s purpose is narrower: preserve dated evidence so another person can reproduce the reasoning and identify what must be checked on the current unit.

1. Separate four dates instead of using one “freshness” field

Start with four distinct timestamps. The source date is when the listing, option menu or policy statement was captured. The record date is when the QC photos, measurement or video were produced, if that date is shown. The access date is when the reviewer opened or downloaded the material. The review date is when someone last checked its relevance to the present decision.

These dates answer different questions. Source date establishes what the seller page stated at that moment. Record date locates the observed sample in time. Access date proves when the reviewer actually obtained the file. Review date shows when the relationship between evidence and current target was reconsidered. Never substitute one for another. If the record date is not displayed, write “not shown”; do not convert the access date into an assumed inspection date.

2. Build a dated evidence header before recording observations

Give every source a short stable ID, then capture source type, exact URL or internal record reference, item and seller identity when shown, variant fields, and all available dates. Add the reviewer’s current decision target beside it. This prevents a record about a black size M sample from quietly becoming evidence for a navy size L target merely because the product title looks similar.

Preserve time zones when they affect ordering. A date-only label may be enough for a historical gallery; a rapidly changing option or price may need a timestamp. Use an ISO-style value such as 2026-09-01 14:20 +08:00 for sortable private records. The public-facing handoff can stay readable, but the archive should make event order unambiguous.

3. Use an append-only event timeline

Freshness changes because the world changes. A listing redirects, an option disappears, a seller edits the title, a new QC set appears, or a measurement becomes available. Record those events as new lines rather than overwriting the earlier snapshot. An append-only timeline lets a reviewer see what was known at each decision point and prevents later information from being mistaken for evidence that existed earlier.

Each event needs date, source, observed change and effect on the record. Keep observation separate from inference. “Red option no longer visible in menu” is an observation. “Seller permanently discontinued red” is an inference unless the source says so. Likewise, “new QC set dated August 29” does not prove it belongs to the same batch or exact option; it only adds a dated sample whose identity must still be mapped.

4. Judge relevance risk, not age alone

No universal number of days makes QC evidence valid or invalid. Age matters through the field being decided. A historical construction photo may still help define which seams deserve inspection. The same photo may be weak evidence for current color, packaging, included parts or an active listing option. A recent image can also be unusable when identity is uncertain or a critical angle is missing.

Rate freshness risk by combining identity, volatility and coverage. Identity asks whether item, seller and required variant fields match. Volatility asks how likely the relevant field is to change: price and availability can move quickly, while a photographed stitching location may be more stable but still sample-specific. Coverage asks whether the evidence actually shows the field. This produces a reasoned note instead of an arbitrary expiration label.

5. Preserve listing changes without rewriting history

When a current page differs from a saved record, capture the new state as a second source. Compare URL, item ID, seller, title, thumbnail, option labels, quantity, price state and availability. Do not edit the old row to look current. The earlier record may accurately explain an older QC set even when it no longer supports today’s purchase target.

Write the effect at field level. A price change may require a budget recheck but leave construction context intact. A changed model code can invalidate transfer of most product-specific observations. A removed bundle option can make included-parts evidence irrelevant. A redirect with unchanged visible identity remains a re-verification task, not automatic proof of continuity.

6. Run a review protocol before comparison

Before comparing records, confirm that each has a dated source, an honest record-date state and a current review date. Reopen the target listing when possible. Recheck the exact variant fields. Confirm that images still load and that the saved record has not been silently replaced. Then state the comparison question: measurement, surface defect, alignment, included parts or another visible field.

For every observation, add an “as of” clause and an allowed-use note. For example: “As of September 1, the August 12 size-L record shows the front measurement angle, but the tape endpoint is partly cropped; use it only to identify the extra measurement needed.” This is more precise than calling the record fresh or stale as a whole.

7. Turn freshness gaps into a concise dated handoff note

A useful handoff contains the target, latest verified source state, historical evidence being relied upon, specific uncertainty and requested current-unit confirmation. Avoid sending an unlabeled folder of screenshots. The selected agent should not have to infer which image is historical or which option the buyer intends.

Example: “Target is navy, size L, one unit. Listing option captured September 1. Available QC record is dated August 12 and matches item and color, but its size label is not visible. Treat its construction views as historical context only. Please confirm the size label and provide the currently available measurement for this unit.” The agent determines which action is available under its own service terms; the dated record does not promise a photo, exchange or return.

8. Audit the packet and set a review trigger

Finish by asking whether another reviewer can reconstruct the chronology without private chats. Every source should have an ID, date state, exact target relationship and permitted use. Every change should be appended. Every unknown should remain explicit. Remove account names, order numbers, addresses and payment data from any shared version.

A good trigger is concrete: before checkout, after an option change, when a new QC set appears, or immediately before the evidence is handed to the selected agent. The result is not a claim that old material is useless. It is a transparent record of when each source existed, what it can still support and what must be rechecked.