Case 69 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise
Method note for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: use “Comparing against a phone clock once a day for a week,…” 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. Retain the source wording beside any paraphrase.
Lug width is the essential one: the inside distance between the lugs where the strap fits. Measure with a ruler marked in millimetres, ideally reading it under magnification. Most watches use even numbers (18, 20, 22mm), but odd widths exist. If you measure 19 or 21, measure again and check the manufacturer spec before ordering.
Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.
Back-play is the most objective feel measurement. Set the bezel on a click and gently push it the other way without forcing it. Noticeable wobble before it engages means play. A little is common and within normal production, but if one model has visible movement and the other doesn't, that's a real difference you can describe.
Case 3 — Lume comparison: keep exposure and charging conditions consistent
Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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.
Thickness matters more than people expect. Straps around 4 to 5mm at the lugs can hit the case or stop the strap folding down on watches with short lugs or tight lug-to-case clearance. Do you know whether your watch has drilled lugs or a tight gap between strap and case? That tells you how much thickness is safe.
Case 21 — QC checklist: prioritise observable faults over pixel hunting
Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.
Case 7 — Movement identification: the limits of a rotor photograph
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 11 — Forum comparison archive: link the evidence and the correction
Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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 21 — 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.
If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.
Case 35 — Magnetism and rate: record evidence before naming a cause
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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 35 — 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.
Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain 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.
Case 12 — QC checklist: prioritise observable faults over pixel hunting
Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.