Case 4 — Service enquiry: information a watchmaker can use
Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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 21 — Reading a timegrapher recording without losing the context
The supplied screen shows a rate but does not identify the lift angle, position or winding state. Which observations should accompany the recording?
Exercise RWF-28686/21: address this question within its stated limits.
Case 32 — Clasp photographs: what to request before judging alignment
Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Request open and closed views from both sides,…”; the related point is “Separate cosmetic alignment from whether the clasp engages reliably;…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: scope. Keep the stated question separate from any broader claim.
Case 17 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Differences in pigment, applied area, thickness and colour can affect appearance. Keep those design differences separate from claims about quality and use matched conditions for any comparison.
Case 37 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · source wording exercise
Limit of the answer in “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: “Diameter alone tells you little…” 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: source wording. Retain the source wording beside any paraphrase.
Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.
Case 9 — Magnetism and rate: record evidence before naming a cause
A sudden rate change is being attributed to magnetism without a measurement. How should the discussion be structured?
Exercise RWF-18239/9: address this question within its stated limits.
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
Case 36 — Model comparison: dive bezel action and alignment, how to compare fairly
Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.
Case 19 — Reading a timegrapher recording without losing the context
Keep the complete recording and ask for the settings, winding state and position. A single number cannot establish service condition, movement identity or performance on a wrist.
Case 1 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
I want to buy aftermarket straps but keep seeing 20/16, 22mm, 4mm thick and spring bar sizes. Which measurements do I actually need to take from my watch, and how do I measure them without the right tools?
Exercise RWF-13435/1: address this question within its stated limits.
Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.
Case 1 — QC checklist: prioritise observable faults over pixel hunting
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly and…” 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 20 — Case finishing: distinguish a reflection from a surface mark
Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “Ask for photographs with the light moved and…” 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.
Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.