Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.
Forum Replies Created
Case 13 — Comparing versions without mixing case sizes
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.
Case 18 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.
Case 39 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem · source wording exercise
My bracelet is either slightly too tight or slightly loose with any link combination. The clasp has three micro-adjust holes, and there are no half-links. What are the options before I give up and go to a strap?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Fit often improves by moving one link from the 6 o'clock…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-27076/39: address this question within its stated limits.
Case 167 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained · uncertainty exercise
Limit of the answer in “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: “A notation like 20/16 means 20mm at the lugs,…” 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: uncertainty. Leave the unresolved part visible instead of supplying a result.
Case 39 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
Limit of the answer in “Model comparison: dive bezel action and alignment, how to compare fairly”: “Crisp vs mushy is mostly about…” 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: source wording. Retain the source wording beside any paraphrase.
Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.
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.
Case 2 — Model comparison: dive bezel action and alignment, how to compare fairly
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
Case 30 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
New here and reading spec sheets for the first time. Four terms keep tripping me up: complication, caliber, jewel count and power reserve. Short definitions would help, and so would a note on which ones actually matter when comparing two everyday watches.
Exercise RWF-19593/30: address this question within its stated limits.
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 18 — 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.
Case 27 — Service enquiry: information a watchmaker can use
Summary draft for “Service enquiry: information a watchmaker can use”: the answer addresses “Document when it stops, winding behaviour, recent impacts and…”; the related point is “Be honest about the watch and request an assessment…”. 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.
Regulation is possible if you want it closer. On many movements it's a quick adjustment by a watchmaker. Can you check whether the losing rate is consistent or getting worse? A stable -8 is a good candidate for simple regulation. A growing loss points to something else, such as falling amplitude, and regulation alone won't fix that.
Method note for “Seller review template: facts, dates and unresolved questions”: use “Use fields for order date, promised terms, dated…” 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.