Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)

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.

Case 23 — Crown operation: when a forum cannot diagnose the resistance

A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?

Exercise RWF-27076/23: address this question within its stated limits.

Case 151 — Case finishing: distinguish a reflection from a surface mark · uncertainty exercise

A bright line appears in one polished-case image. What additional evidence would distinguish a mark from reflected light?

Review focus: uncertainty. Leave the unresolved part visible instead of supplying a result. Use the original answer fragment “Ask for photographs with the light moved and…” as the discussion anchor; no new event or result is supplied.

Exercise RWF-25905/151: address this question within its stated limits.

Case 22 — Comparing versions without mixing case sizes

Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “Match reference, dimensions and…” 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.

Summary draft for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: the answer addresses “First identify the caliber, lift-angle setting, winding…”; the related point is “Without those fields, the rate, amplitude and beat-error values lack…”. 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 34 — 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.

Limit of the answer in “Bracelet fit: measuring the usable clasp adjustment”: “Request the closed bracelet circumference rather than inferring…” 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 13 — Strap compatibility: width is only the first measurement

Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Measure the lug opening and document bar diameter,…” 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.

Summary draft for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: the answer addresses “Add lug-to-lug, thickness and lug width…”; the related point is “Diameter alone tells you little…”. 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 1 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

Domed crystals of any material add distortion at the edges, which some people like and others find hard to read at angles. Box-shaped or high-domed crystals also add thickness. If you're comparing two otherwise similar watches, check total thickness against crystal profile before assuming the case itself is thicker.

Case 11 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 18 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

A stated water-resistance rating does not establish the present condition of an individual watch. Separate the manufacturer specification from a dated inspection or test of the particular example.

Case 34 — Maintenance question: how do I tell if an automatic actually needs service?

If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.

Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Explain what the full-size image shows, what the crop adds and…” 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.

Viewing 15 posts - 1 through 15 (of 20 total)