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
Case 51 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise
Correction note for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: retain the wording beginning “Comparing against a phone clock once a day for a week,…” 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. Retain the source wording beside any paraphrase.
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain 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 28 — Disputed observation: is this dial colour shift real or just lighting?
Several posts claim the newer batch of a particular blue-dial model looks more purple than the earlier batch. Others say it's purely photography and white balance. Can we settle this with evidence instead of arguing from different photos?
Exercise RWF-21617/28: address this question within its stated limits.
Method note for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: use “Add lug-to-lug, thickness and lug width…” 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 8 — Case finishing: distinguish a reflection from a surface mark
Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved 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 17 — Packing photographs: document condition without exposing an address
Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” 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.
Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
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 213 — Forum comparison archive: link the evidence and the correction · correction exercise
Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Preserve the reasoning trail instead of silently replacing an…” 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: correction. Preserve the old wording if a later source changes the interpretation.
Case 22 — 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 34 — 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-07162/34: address this question within its stated limits.
Case 34 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Case 26 — What a water-resistance claim does and does not establish
Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.