Case 13 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
For a two-watch comparison, the practical order is usually case dimensions first, then power reserve if you rotate, then caliber for serviceability. Jewel count comes last. Complications only matter if you'll use them. Can you say what the two candidates are, in generic terms like 'dive style vs dress style'? The priorities shift a lot between those.
Case 18 — 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-27800/18: address this question within its stated limits.
Case 29 — Model comparison: dive bezel action and alignment, how to compare fairly
Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.
Summary draft for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: the answer addresses “Start with how you…”; the related point is “Comparing against a phone clock once a day for a week,…”. 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 32 — Clasp photographs: what to request before judging alignment
Method note for “Clasp photographs: what to request before judging alignment”: use “Request open and closed views from both sides,…” 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 14 — A maintenance log that remains useful after a sale
Correction note for “A maintenance log that remains useful after a sale”: retain the wording beginning “Keep the date, work performed, provider invoice reference…” 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.
First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.
Case 12 — Disputed observation: is this dial colour shift real or just lighting?
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.
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Treat the comparison…” 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.
Case 15 — First QC request: the minimum useful information
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.
Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Avoid forcing an assembly that does not fit 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.
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.
Reader check for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: distinguish the discussion point “A bright initial glow followed by a steep drop…” 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.
Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Measure the lug opening and document bar diameter,…” 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 161 — Service enquiry: information a watchmaker can use · uncertainty exercise
Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Document when it stops, winding behaviour, recent impacts 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. Leave the unresolved part visible instead of supplying a result.