Case 2 — QC checklist: prioritise observable faults over pixel hunting
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly and…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
Case 30 — Lume questions: why does my lume fade so quickly, and how should I compare it?
A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain dated…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: scope. Keep the stated question separate from any broader claim.
Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.
Case 3 — Seller review template: facts, dates and unresolved questions
Limit of the answer in “Seller review template: facts, dates and unresolved questions”: “Use fields for order date, promised terms, dated…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Case 23 — Bracelet fit: measuring the usable clasp adjustment
Limit of the answer in “Bracelet fit: measuring the usable clasp adjustment”: “Record wrist circumference, removable links and the clasp…” is an excerpt from the discussion, not an independent verification. A reader needs the relevant original material before treating an interpretation as established. Review focus: scope. Keep the stated question separate from any broader claim.
Case 11 — QC photographs: perspective or a genuinely tilted index?
A marker can look tilted when the camera is above the dial axis. What extra image would separate perspective from an assembly issue?
Exercise RWF-18903/11: address this question within its stated limits.
Method note for “Maintenance question: how do I tell if an automatic actually needs service?”: use “The calendar interval is a conservative…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Keep the stated question separate from any broader claim.
Case 49 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Repeat with equal light source, charging duration, elapsed time and camera…” belongs to the question as written. It should not be read as a report that a new check, purchase or experiment has been completed. Review focus: source wording. Retain the source wording beside any paraphrase.
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” as a row heading in a proposed working record. Put the statement, its supporting source or measurement, and any unresolved detail in separate fields. This proposes a format; it supplies no additional evidence. Retain the source wording beside any paraphrase.
Case 19 — QC photography: what photos actually help verify a pre-owned listing?
A caution: photos can't settle everything. Water resistance, timekeeping and internal condition aren't visible in any image. A short timegrapher video or a stated recent rate test adds information, but treat it as a seller claim unless an independent party confirms it. Photos narrow the risk. They don't remove it.
Case 11 — Forum comparison archive: link the evidence and the correction
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 35 — Model comparison: dive bezel action and alignment, how to compare fairly
Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.
Case 3 — Disputed observation: is this dial colour shift real or just lighting?
Suggested protocol. 1) Both dials in one frame. 2) Diffuse daylight, no direct sun, plus a second shot under neutral indoor light. 3) Grey card visible. 4) No filters, no editing. 5) State camera settings if known. If both shots show the same direction of difference, the claim is supported. If the difference flips between lighting conditions, it's most likely lighting.