Case 9 — 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.
Case 3 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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.
Case 7 — Comparing dial colour under different lighting
One image was taken beside a window and the other under a warm lamp. How should a colour comparison be qualified?
Exercise RWF-28783/7: address this question within its stated limits.
Correction note for “Comparing dial colour under different lighting”: retain the wording beginning “Compare controlled images where available and avoid calling a…” 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.
Method note for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: use “Fit often improves by moving one link from the 6 o'clock…” 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 25 — Comparing versions without mixing case sizes
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “Match reference, dimensions and…”; the related point is “List confirmed differences separately from seller descriptions and date the comparison…”. 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 29 — What a water-resistance claim does and does not establish
Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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 27 — Magnetism and rate: record evidence before naming a cause
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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 17 — QC photography: what photos actually help verify a pre-owned listing?
A caution: photos can't settle everything. Water resistance, timekeeping and internal condition aren't visible in any image. A short timegrapher video or a stated recent rate test adds information, but treat it as a seller claim unless an independent party confirms it. Photos narrow the risk. They don't remove it.
Reader check for “Service enquiry: information a watchmaker can use”: distinguish the discussion point “Document when it stops, winding behaviour, recent impacts and…” 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: scope. Keep the stated question separate from any broader claim.
Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.
Case 22 — Seller review template: facts, dates and unresolved questions
Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, dated…” 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 30 — Lume comparison: keep exposure and charging conditions consistent
Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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 22 — 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.