Case 5 — Crystal reflections: why a dark patch is not a coating test
Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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 32 — 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.
Case 11 — Model comparison: dive bezel action and alignment, how to compare fairly
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?
Exercise RWF-25739/11: address this question within its stated limits.
Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.
Case 15 — Bracelet fit: measuring the usable clasp adjustment
Limit of the answer in “Bracelet fit: measuring the usable clasp adjustment”: “Record wrist circumference, removable links and the clasp…” 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 49 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Explain what the full-size image shows, what the crop adds and…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-21617/49: address this question within its stated limits.
Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.
Case 29 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
On anti-reflective coatings: inner-surface AR cuts glare without wear concerns. Outer-surface AR improves legibility further but can scuff over time, and the scuffs show up as hazy patches in certain light. When comparing two watches, check which surfaces are coated. Spec sheets often just say 'AR coated' without saying where.
Case 14 — Shipping timeline: separate dispatch, handover and scan events
Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Distinguish label creation from physical acceptance and retain dated…”; the related point is “Ask the sender or carrier for clarification; missing scans alone…”. 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.
Method note for “Comparing dial colour under different lighting”: use “State the lighting 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.
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.
Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Case 20 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.
Resolution checklist. 1) Rebalance links around the clasp. 2) Test every micro-adjust hole with each link count. 3) Check fit morning and afternoon. 4) Look for half-links by bracelet reference. 5) Accept slightly loose if the head is light. If none of that works, a strap with finer hole spacing is a reasonable conclusion, not a failure.
Case 11 — Case finishing: distinguish a reflection from a surface mark
Summary draft for “Case finishing: distinguish a reflection from a surface mark”: the answer addresses “Ask for photographs with the light moved and…”; the related point is “A mark should be assessed across multiple views; aggressive polishing…”. 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.