Skip to content
RepWatchForumSign in

Forum Replies Created

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

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

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

The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.

Clarification for “Model comparison: dive bezel action and alignment, how to compare fairly”: the point beginning “Crisp vs mushy is mostly about…” 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.

Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.

Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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 115 — Case finishing: distinguish a reflection from a surface mark · documentation exercise

Method note for “Case finishing: distinguish a reflection from a surface mark”: use “A mark should be assessed across multiple views; aggressive polishing…” 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. Distinguish an original record from a proposed record format.

Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.

Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” 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 43 — Comparing versions without mixing case sizes · source wording exercise

Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “List confirmed differences separately from seller descriptions and date the comparison…” 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.

Case 30 — Magnetism and rate: record evidence before naming a cause

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 10 — Clasp photographs: what to request before judging alignment

Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Request open and closed views from both sides,…”; the related point is “Separate cosmetic alignment from whether the clasp engages reliably;…”. 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 10 — First QC request: the minimum useful information

What should an initial QC request include so replies can address the actual question?

Exercise RWF-17271/10: address this question within its stated limits.

Case 34 — A maintenance log that remains useful after a sale

Which information should a transferable maintenance log retain while protecting the owner’s identity?

Exercise RWF-16019/34: address this question within its stated limits.

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.

Case 22 — Forum comparison archive: link the evidence and the correction

Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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.

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