Case 71 — Date window centring: compare the same date at the same angle · source wording exercise
Method note for “Date window centring: compare the same date at the same angle”: use “Keep the uncropped originals alongside the detail crops and distinguish…” 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 4 — 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.
Case 256 — Seller review template: facts, dates and unresolved questions · reader check exercise
What belongs in a useful review template when no actual purchase experience is being asserted?
Review focus: reader check. State what a new reader can and cannot infer from this exercise. Use the original answer fragment “Leave unsupported fields blank and separate observations from opinions; this…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/256: address this question within its stated limits.
Case 42 — Seller review template: facts, dates and unresolved questions · source wording exercise
Method note for “Seller review template: facts, dates and unresolved questions”: use “Leave unsupported fields blank and separate observations from opinions; this…” 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 28 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Clarifying question: how are you charging it? A few seconds under a warm indoor bulb gives a much weaker charge than daylight or a UV source. Many 'weak lume' reports turn out to be undercharging. Try a consistent charge, such as 30 seconds under a phone flashlight at a fixed distance, before judging.
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 20 — 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.
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.
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 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” 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 30 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?
Exercise RWF-15056/30: address this question within its stated limits.
Case 19 — Packing photographs: document condition without exposing an address
Limit of the answer in “Packing photographs: document condition without exposing an address”: “Photograph the item and protective packing…” 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.
Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Remove names, addresses, barcodes and tracking tokens from public…” 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 — Comparing dial colour under different lighting
State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.
Case 11 — Comparing versions without mixing case sizes
Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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.