Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.
Forum Replies Created
Case 13 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.
Case 25 — QC photography: what photos actually help verify a pre-owned listing?
When asking a seller for extra photos of a pre-owned watch, what shots are actually useful as evidence? Listings tend to have glossy angled photos that hide more than they show. I'd like a standard request list the forum can reuse.
Exercise RWF-29716/25: address this question within its stated limits.
Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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 9 — Magnetism and rate: record evidence before naming a cause
Limit of the answer in “Magnetism and rate: record evidence before naming a cause”: “Record the change and the circumstances without treating…” 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 — First QC request: the minimum useful information
Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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.
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: source wording. Retain the source wording beside any paraphrase.
Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Separate cosmetic alignment from whether the clasp engages reliably;…” 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 32 — Model comparison: dive bezel action and alignment, how to compare fairly
Separate preference from a potential functional problem. Inconsistent engagement, slipping or uncertain alignment should be documented and checked against the design’s specification by a competent watchmaker; do not invent a universal defect threshold.
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Repeat with equal light source, charging duration, elapsed time and camera…” 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: scope. Keep the stated question separate from any broader claim.
Case 29 — 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.
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 17 — Lume comparison: keep exposure and charging conditions consistent
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 24 — Bracelet fit: measuring the usable clasp adjustment
Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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.
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.