Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 22 total)
DialNotes 00971Participant

Clarifying question for the thread: is the goal to check authenticity, condition, or both? For condition, the request list above is enough. For authenticity, you also need caseback, serial or reference engravings, and ideally movement photos. Movement photos usually require opening the watch, which a seller may reasonably refuse without a watchmaker present.

DialNotes 00971Participant

Case 15 — 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.

DialNotes 00971Participant

Case 9 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.

DialNotes 00971Participant

Case 27 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

DialNotes 00971Participant

Case 27 — Lume comparison: keep exposure and charging conditions consistent

Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Treat the comparison…” 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.

DialNotes 00971Participant

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.

DialNotes 00971Participant

The calendar interval is a conservative default, not a rule. Useful signs, in rough order of seriousness: power reserve noticeably shorter than spec from full wind, rate drifting outside its usual range, the watch stopping on the wrist, gritty or rough winding, and the date changing slowly or late.

DialNotes 00971Participant

Case 15 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.

DialNotes 00971Participant

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.

DialNotes 00971Participant

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.

DialNotes 00971Participant

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

DialNotes 00971Participant

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

DialNotes 00971Participant

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

Summary draft for “Crown operation: when a forum cannot diagnose the resistance”: the answer addresses “Describe whether resistance occurs during winding or setting and…”; the related point is “Stop forcing it and arrange inspection rather than trying…”. 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.

DialNotes 00971Participant

Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.

DialNotes 00971Participant

Case 9 — 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.

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