Case 45 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Repeat with equal light source, charging duration, elapsed time and camera…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: source wording. Retain the source wording beside any paraphrase.
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 5 — 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.
Clarification for “First QC request: the minimum useful information”: the point beginning “Include complete instrument settings where relevant and say…” 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 35 — A maintenance log that remains useful after a sale
Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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 41 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · source wording exercise
Method note for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: use “Without those fields, the rate, amplitude and beat-error values lack…” 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.
Case 82 — Clasp photographs: what to request before judging alignment · comparison exercise
Reader check for “Clasp photographs: what to request before judging alignment”: distinguish the discussion point “Request open and closed views from both sides,…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: comparison. Make the basis of a comparison explicit before interpreting it.
Case 5 — QC photographs: perspective or a genuinely tilted index?
Summary draft for “QC photographs: perspective or a genuinely tilted index?”: the answer addresses “Request a level straight-on image with the hands…”; the related point is “Compare two independently aligned images before drawing a conclusion; an overlay…”. 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.
Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.
Case 14 — Model comparison: dive bezel action and alignment, how to compare fairly
Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.
Case 11 — A maintenance log that remains useful after a sale
Which information should a transferable maintenance log retain while protecting the owner’s identity?
Exercise RWF-20722/11: address this question within its stated limits.
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 1 — Forum comparison archive: link the evidence and the correction
Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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.
Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Be honest about the watch and request an assessment…” 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.
Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.