Case 36 — Strap compatibility: width is only the first measurement
Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?
Exercise RWF-30442/36: address this question within its stated limits.
Summary draft for “Crown operation: when a forum cannot diagnose the resistance”: the answer addresses “Stop forcing it and arrange inspection rather than trying…”; the related point is “Describe whether resistance occurs during winding or setting 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.
Case 49 — Crystal reflections: why a dark patch is not a coating test · source wording exercise
Correction note for “Crystal reflections: why a dark patch is not a coating test”: retain the wording beginning “Compare multiple controlled angles and describe the visible observation without asserting…” 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 24 — QC photography: what photos actually help verify a pre-owned listing?
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.
Case 12 — Lume comparison: keep exposure and charging conditions consistent
Two glowing dials are shown with different camera exposure and unknown charging time. What can the images establish?
Exercise RWF-27479/12: address this question within its stated limits.
Case 10 — Shipping timeline: separate dispatch, handover and scan events
Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Distinguish label creation from physical acceptance and retain dated…” 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.
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.
Clarification for “Maintenance question: how do I tell if an automatic actually needs service?”: the point beginning “Useful signs, in rough order of seriousness: power reserve noticeably shorter…” 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 40 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
People keep comparing the bezels on two similar dive-style watches. One is called crisp, the other mushy, and alignment complaints come up for both. What would a fair comparison look like, and what is actually a defect versus a preference?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Crisp vs mushy is mostly about…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-21138/40: address this question within its stated limits.
Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, 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.
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 12 — 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.
Case 1 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
My entry-level automatic loses about 8 seconds a day. The spec sheet lists a tolerance range, but I'm not sure how to read it or whether my measurement is reliable. Is this something to fix or something to live with?
Exercise RWF-16355/1: address this question within its stated limits.
Case 20 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Can the same settings and winding state be used for several positions? Record each position separately rather than combining measurements taken under different conditions.
Limit of the answer in “Shipping timeline: separate dispatch, handover and scan events”: “Ask the sender or carrier for clarification; missing scans alone…” 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.