Skip to content
RepWatchForumSign in

Forum Replies Created

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

Method note for “Service enquiry: information a watchmaker can use”: use “Be honest about the watch and request an assessment…” 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 27 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Power reserve is how long the watch runs from full wind until it stops. It matters if you rotate watches: a 38-hour reserve may stop over a weekend off the wrist, while 70-plus hours may not. One clarifying point is that rate stability often gets worse near the end of the reserve, so the full figure is not all precision-grade running time.

Case 29 — Crystal reflections: why a dark patch is not a coating test

Limit of the answer in “Crystal reflections: why a dark patch is not a coating test”: “No single lighting setup settles…” 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 30 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem

First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.

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

A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.

Case 33 — QC checklist: prioritise observable faults over pixel hunting

A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?

Exercise RWF-23073/33: address this question within its stated limits.

Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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.

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 “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 47 — Forum comparison archive: link the evidence and the correction · source wording exercise

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Preserve the reasoning trail instead of silently replacing an…” 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: source wording. Retain the source wording beside any paraphrase.

Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain dated…” 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 31 — Service enquiry: information a watchmaker can use

A service question only says that the watch stops occasionally. Which observations make an initial enquiry more useful?

Exercise RWF-13525/31: address this question within its stated limits.

Case 11 — Shipping timeline: separate dispatch, handover and scan events

Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.

Case 44 — Shipping timeline: separate dispatch, handover and scan events · source wording exercise

Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Ask the sender or carrier for clarification; missing scans alone…” 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 19 — Reading a timegrapher recording without losing the context

Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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.

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