Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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.
Forum Replies Created
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.
Summary draft for “Comparing dial colour under different lighting”: the answer addresses “Compare controlled images where available and avoid calling a…”; the related point is “State the lighting and…”. 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.
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 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Power reserve is how long the watch runs from full wind until it stops. It matters if you rotate watches: a 38-hour reserve may stop over a weekend off the wrist, while 70-plus hours may not. One clarifying point is that rate stability often gets worse near the end of the reserve, so the full figure is not all precision-grade running time.
Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Request open and closed views from both sides,…” 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 38 — Forum comparison archive: link the evidence and the correction · source wording exercise
Reader check for “Forum comparison archive: link the evidence and the correction”: distinguish the discussion point “Preserve the reasoning trail instead of silently replacing an…” 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: source wording. Retain the source wording beside any paraphrase.
Case 17 — Bracelet fit: measuring the usable clasp adjustment
A nominal case diameter says little about a bracelet that cannot be shortened enough. How should a sizing question be documented?
Exercise RWF-25739/17: address this question within its stated limits.
Case 1 — Clasp photographs: what to request before judging alignment
Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.
Case 21 — Strap compatibility: width is only the first measurement
Limit of the answer in “Strap compatibility: width is only the first measurement”: “Measure the lug opening and document bar diameter,…” 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.
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.
Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 20 — QC checklist: prioritise observable faults over pixel hunting
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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 3 — Crystal reflections: why a dark patch is not a coating test
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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.
Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.