Case 22 — 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 36 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.
Case 112 — Strap compatibility: width is only the first measurement · documentation exercise
Method note for “Strap compatibility: width is only the first measurement”: use “Avoid forcing an assembly that does not fit 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. Distinguish an original record from a proposed record format.
Case 1 — Forum comparison archive: link the evidence and the correction
Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Add a dated correction near the original conclusion…” 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 12 — Lume questions: why does my lume fade so quickly, and how should I compare it?
My watch's lume is bright for a few minutes and then barely visible. Is that normal? People post lume shots of different watches, but they all seem to use different charging and exposure, so I can't tell what's actually better.
Exercise RWF-25919/12: address this question within its stated limits.
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.
Case 4 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
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.
Case 29 — Service enquiry: information a watchmaker can use
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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 30 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” 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.
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Case 28 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
A complication is any function beyond hours, minutes and seconds. A date window counts, technically, and so do a chronograph, GMT hand or moon phase. More complications usually mean more parts, more thickness and more service cost. For a first everyday watch, decide which functions you'd really use before treating them as value.
Case 7 — Date window centring: compare the same date at the same angle
Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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 15 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
One method that often helps without any service is using overnight resting position to cancel daily drift. Many watches gain in some positions and lose in others. If yours loses on the wrist, try leaving it crown up or dial up overnight and log the result for a few nights. Some people get close to zero this way.
Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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.
Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.