Case 21 — Bracelet fit: measuring the usable clasp adjustment
Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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 9 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
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.
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 — Case finishing: distinguish a reflection from a surface mark
Correction note for “Case finishing: distinguish a reflection from a surface mark”: retain the wording beginning “Ask for photographs with the light moved 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 69 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise
Correction note for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: retain the wording beginning “Comparing against a phone clock once a day for a week,…” 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. Retain the source wording beside any paraphrase.
Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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.
Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.
Separate preference from a potential functional problem. Inconsistent engagement, slipping or uncertain alignment should be documented and checked against the design’s specification by a competent watchmaker; do not invent a universal defect threshold.
Case 3 — Lume comparison: keep exposure and charging conditions consistent
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Treat the comparison…” 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.
The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.
Case 21 — 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.
Case 7 — Movement identification: the limits of a rotor photograph
Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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 11 — Forum comparison archive: link the evidence and the correction
Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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 22 — Seller review template: facts, dates and unresolved questions
What belongs in a useful review template when no actual purchase experience is being asserted?
Exercise RWF-16563/22: address this question within its stated limits.
Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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.