The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.
Forum Replies Created
Case 13 — Packing photographs: document condition without exposing an address
Method note for “Packing photographs: document condition without exposing an address”: use “Photograph the item and protective packing…” 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 77 — Service enquiry: information a watchmaker can use · comparison exercise
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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: comparison. Make the basis of a comparison explicit before interpreting it.
Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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.
Correction note for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: retain the wording beginning “Add lug-to-lug, thickness and lug width…” in the record. If later material changes it, add the date, the changed wording and the source for that change; do not invent a completed correction here. Keep the stated question separate from any broader claim.
Method note for “Seller review template: facts, dates and unresolved questions”: use “Use fields for order date, promised terms, dated…” 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 14 — Packing photographs: document condition without exposing an address
A condition record is useful but a shipping label contains personal information. How can the record be shared safely?
Exercise RWF-22448/14: address this question within its stated limits.
Clarification for “Crown operation: when a forum cannot diagnose the resistance”: the point beginning “Describe whether resistance occurs during winding or setting 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 31 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.
Case 17 — Comparing versions without mixing case sizes
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “Match reference, dimensions and…”; the related point is “List confirmed differences separately from seller descriptions and date the comparison…”. 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 22 — Lume questions: why does my lume fade so quickly, and how should I compare it?
My watch's lume is bright for a few minutes and then barely visible. Is that normal? People post lume shots of different watches, but they all seem to use different charging and exposure, so I can't tell what's actually better.
Exercise RWF-17881/22: address this question within its stated limits.
Case 32 — Crystal reflections: why a dark patch is not a coating test
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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.
Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 9 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.
Exercise RWF-14395/9: address this question within its stated limits.
Limit of the answer in “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: “Add lug-to-lug, thickness and lug width…” 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.