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.
Forum Replies Created
Case 19 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
Case 22 — 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.
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Clarifying question: what does daily wear mean for you? Desk work, manual labour or sports change the answer. For desk use, sapphire's scratch resistance is the main benefit. For work with frequent knocks, a slightly domed acrylic that you can polish may last longer in practice, despite the scratches.
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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 33 — Lug-to-lug and end-link overhang in wrist photographs
Correction note for “Lug-to-lug and end-link overhang in wrist photographs”: retain the wording beginning “Record lug-to-lug and the effective span…” 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.
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 23 — Movement identification: the limits of a rotor photograph
Only part of the movement is visible and the rotor hides several bridges. Which details can be described without claiming certainty?
Exercise RWF-14072/23: address this question within its stated limits.
Case 2 — Magnetism and rate: record evidence before naming a cause
Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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.
Limit of the answer in “Comparing dial colour under different lighting”: “State the lighting 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.
Case 9 — Shipping timeline: separate dispatch, handover and scan events
A tracking page has no new event after a label was created. How can the timeline be discussed without inventing a carrier explanation?
Exercise RWF-10203/9: address this question within its stated limits.
Case 8 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?
Exercise RWF-09246/8: address this question within its stated limits.
Case 27 — QC checklist: prioritise observable faults over pixel hunting
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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.