Skip to content
RepWatchForumSign in

Forum Replies Created

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

State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.

Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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.

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.

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

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.

Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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 — Maintenance question: how do I tell if an automatic actually needs service?

Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.

Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “Ask for photographs with the light moved 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 23 — Packing photographs: document condition without exposing an address

A condition record is useful but a shipping label contains personal information. How can the record be shared safely?

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

Case 20 — QC photographs: perspective or a genuinely tilted index?

Summary draft for “QC photographs: perspective or a genuinely tilted index?”: the answer addresses “Request a level straight-on image with the hands…”; the related point is “Compare two independently aligned images before drawing a conclusion; an overlay…”. 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 9 — QC checklist: prioritise observable faults over pixel hunting

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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.

Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.

Case 41 — Bracelet fit: measuring the usable clasp adjustment · source wording exercise

Reader check for “Bracelet fit: measuring the usable clasp adjustment”: distinguish the discussion point “Request the closed bracelet circumference rather than inferring…” 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: source wording. Retain the source wording beside any paraphrase.

Correction note for “A maintenance log that remains useful after a sale”: retain the wording beginning “Keep the date, work performed, provider invoice reference…” 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.

Use a consistent charge, fixed exposure and several elapsed-time observations. Record readability and the conditions rather than applying an unsupported universal fade-time threshold.

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.

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