Case 23 — Crown operation: when a forum cannot diagnose the resistance
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.
Case 151 — Case finishing: distinguish a reflection from a surface mark · uncertainty exercise
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: uncertainty. Leave the unresolved part visible instead of supplying a result.
Case 22 — Comparing versions without mixing case sizes
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “Match reference, dimensions and…”; the related point is “List confirmed differences separately from seller descriptions and date the comparison…”. 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 34 — QC checklist: prioritise observable faults over pixel hunting
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.
Correction note for “Bracelet fit: measuring the usable clasp adjustment”: retain the wording beginning “Request the closed bracelet circumference rather than inferring…” 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 13 — Strap compatibility: width is only the first measurement
Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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 1 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
A correction worth making: 'sapphire = premium, mineral = cheap' oversimplifies it. A well-fitted mineral crystal on a modest watch can be perfectly suitable, and replacing a cracked sapphire is usually more expensive. Material is one factor among several, alongside fit, gasket quality and coating.
Case 11 — 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.
Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.
Case 18 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Summary so far. Rows: diameter, lug-to-lug, thickness (method stated), lug width, crystal type, water resistance (as specified), movement family, production period. Each row has a source tag. Corrections go in the dated log with old and new values. If nobody objects, that's the template, and later posts should give evidence rather than restate opinions.
Case 34 — Maintenance question: how do I tell if an automatic actually needs service?
A sudden rate change has several possible causes. Ask a watchmaker to test suspected magnetism rather than diagnosing it from a compass or attempting an adjustment based on forum replies.
Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Explain what the full-size image shows, what the crop adds and…”; the related point is “Start with function, legibility, assembly 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.
Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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.
Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Document when it stops, winding behaviour, recent impacts 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. Retain the source wording beside any paraphrase.