Case 13 — 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.
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 8 — Strap compatibility: width is only the first measurement
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.
Case 1 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Keep the complete recording and ask for the settings, winding state and position. A single number cannot establish service condition, movement identity or performance on a wrist.
Case 3 — Strap compatibility: width is only the first measurement
Limit of the answer in “Strap compatibility: width is only the first measurement”: “Measure the lug opening and document bar diameter,…” 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.
Summary draft for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: the answer addresses “First identify the caliber, lift-angle setting, winding…”; the related point is “Without those fields, the rate, amplitude and beat-error values lack…”. 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 21 — Seller review template: facts, dates and unresolved questions
Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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 25 — QC photographs: perspective or a genuinely tilted index?
Limit of the answer in “QC photographs: perspective or a genuinely tilted index?”: “Request a level straight-on image with the hands…” 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.
Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.
Case 23 — Case finishing: distinguish a reflection from a surface mark
Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved 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 13 — First QC request: the minimum useful information
Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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.
Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.
Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Case 18 — Lug-to-lug and end-link overhang in wrist photographs
Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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.