Case 113 — Lume comparison: keep exposure and charging conditions consistent · documentation exercise
Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Repeat with equal light source, charging duration, elapsed time and camera…” 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: documentation. Distinguish an original record from a proposed record format.
Case 3 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.
Case 13 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
A correction to a common belief: an automatic doesn't need to match a quartz watch to be healthy. Consistency matters more than the absolute figure. A watch that's reliably -8 every day is easy to live with, since you correct it once a week. One that swings from +10 to -15 is the real concern.
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Case 5 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.
Case 31 — Strap compatibility: width is only the first measurement
Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?
Exercise RWF-21987/31: address this question within its stated limits.
Case 32 — Magnetism and rate: record evidence before naming a cause
Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 — QC photography: what photos actually help verify a pre-owned listing?
When asking a seller for extra photos of a pre-owned watch, what shots are actually useful as evidence? Listings tend to have glossy angled photos that hide more than they show. I'd like a standard request list the forum can reuse.
Exercise RWF-18803/30: address this question within its stated limits.
Case 9 — Movement identification: the limits of a rotor photograph
Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.
Case 17 — QC photographs: perspective or a genuinely tilted index?
Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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.
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.
Case 9 — Shipping timeline: separate dispatch, handover and scan events
Limit of the answer in “Shipping timeline: separate dispatch, handover and scan events”: “Distinguish label creation from physical acceptance and retain dated…” 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 “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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 3 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Use a consistent charge, fixed exposure and several elapsed-time observations. Record readability and the conditions rather than applying an unsupported universal fade-time threshold.