Correction note for “What a water-resistance claim does and does not establish”: retain the wording beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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.
Forum Replies Created
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 1 — Date window centring: compare the same date at the same angle
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.
Case 16 — 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.
Case 48 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Crisp vs mushy is mostly about…” 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. Retain the source wording beside any paraphrase.
Case 26 — Seller review template: facts, dates and unresolved questions
Limit of the answer in “Seller review template: facts, dates and unresolved questions”: “Use fields for order date, promised terms, dated…” 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 11 — QC photography: what photos actually help verify a pre-owned listing?
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 31 — Magnetism and rate: record evidence before naming a cause
Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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 2 — Seller review template: facts, dates and unresolved questions
Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Use fields for order date, promised terms, dated…” 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.
Reader check for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: distinguish the discussion point “Add lug-to-lug, thickness and lug width…” 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 30 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Case 12 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Summary order of importance. 1) Lug width, measured between the lugs. 2) Lug-end thickness against clearance. 3) Spring bar diameter. 4) Taper and buckle width. 5) Length, which is usually given as long side / short side in mm and should be compared with a strap that already fits you.
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.