Case 74 — Service enquiry: information a watchmaker can use · comparison exercise
Reader check for “Service enquiry: information a watchmaker can use”: distinguish the discussion point “Document when it stops, winding behaviour, recent impacts and…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: comparison. Make the basis of a comparison explicit before interpreting it.
Case 8 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Lug width is the essential one: the inside distance between the lugs where the strap fits. Measure with a ruler marked in millimetres, ideally reading it under magnification. Most watches use even numbers (18, 20, 22mm), but odd widths exist. If you measure 19 or 21, measure again and check the manufacturer spec before ordering.
Case 260 — Comparing versions without mixing case sizes · reader check exercise
Two purported versions differ in case diameter and bracelet. How can the comparison avoid attributing every difference to a revision?
Review focus: reader check. State what a new reader can and cannot infer from this exercise. Use the original answer fragment “List confirmed differences separately from seller descriptions and date the comparison…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/260: address this question within its stated limits.
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.
Case 3 — Shipping timeline: separate dispatch, handover and scan events
A tracking page has no new event after a label was created. How can the timeline be discussed without inventing a carrier explanation?
Exercise RWF-23493/3: address this question within its stated limits.
Case 32 — Reading a timegrapher recording without losing the context
Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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.
Case 24 — Comparing dial colour under different lighting
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
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 “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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.
Case 11 — Packing photographs: document condition without exposing an address
Limit of the answer in “Packing photographs: document condition without exposing an address”: “Photograph the item and protective packing…” 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 34 — Maintenance question: how do I tell if an automatic actually needs service?
Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?
Exercise RWF-15056/34: address this question within its stated limits.
Case 23 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.
Clarifying question for the thread: is the goal to check authenticity, condition, or both? For condition, the request list above is enough. For authenticity, you also need caseback, serial or reference engravings, and ideally movement photos. Movement photos usually require opening the watch, which a seller may reasonably refuse without a watchmaker present.
Case 34 — QC checklist: prioritise observable faults over pixel hunting
Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.
Case 15 — A maintenance log that remains useful after a sale
Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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.