Case 21 — First QC request: the minimum useful information
Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern 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.
Case 32 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Summary order of importance. 1) Lug width, measured between the lugs. 2) Lug-end thickness against clearance. 3) Spring bar diameter. 4) Taper and buckle width. 5) Length, which is usually given as long side / short side in mm and should be compared with a strap that already fits you.
Case 19 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.
Case 17 — QC checklist: prioritise observable faults over pixel hunting
A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?
Exercise RWF-29065/17: address this question within its stated limits.
Case 21 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.
Case 10 — Comparing versions without mixing case sizes
Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “Match reference, dimensions 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. Keep the stated question separate from any broader claim.
Case 201 — Maintenance question: how do I tell if an automatic actually needs service? · correction exercise
Clarification for “Maintenance question: how do I tell if an automatic actually needs service?”: the point beginning “Once you have that, later…” 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: correction. Preserve the old wording if a later source changes the interpretation.
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 14 — Maintenance question: how do I tell if an automatic actually needs service?
Keep a baseline log, describe changes in rate or running time and stop forcing rough winding. Follow the manufacturer’s guidance and arrange professional assessment when operation changes. A forum cannot prescribe a universal service interval.
Case 18 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
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.
Case 36 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained
Document spring-bar diameter, end-tip fit and the strap’s clearance using appropriate measuring tools. If dimensions or compatibility are uncertain, ask a watchmaker rather than forcing a bar or substituting an unsuitable part.
Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.
Case 23 — 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-18708/23: address this question within its stated limits.
Case 3 — Service enquiry: information a watchmaker can use
Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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.
Case 5 — 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-16063/5: address this question within its stated limits.