Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 22 total)

Case 3 — 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 “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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 11 — Lume comparison: keep exposure and charging conditions consistent

Correction note for “Lume comparison: keep exposure and charging conditions consistent”: retain the wording beginning “Treat the comparison…” 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 11 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem

A correction to a common assumption: a slightly loose fit isn't automatically wrong. Heavier heads tend to slide on loose bracelets, but a lighter watch often wears comfortably with a finger's width of space. Try 'loose' for a full day before deciding it doesn't work. Comfort over hours tells you more than the first minute.

Case 20 — Disputed observation: is this dial colour shift real or just lighting?

Something to keep apart: sunburst and gradient dials can look like different colours depending on viewing angle, even on the same piece. A shift that appears only at certain angles is a finish effect, not a batch difference. Include a straight-on shot and one tilted shot so readers can tell the two apart.

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-21411/31: address this question within its stated limits.

Case 34 — Shipping timeline: separate dispatch, handover and scan events

Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Distinguish label creation from physical acceptance and retain dated…”; the related point is “Ask the sender or carrier for clarification; missing scans alone…”. 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.

Clarification for “What a water-resistance claim does and does not establish”: the point beginning “A photograph or a caseback engraving is not…” 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.

Reader check for “Packing photographs: document condition without exposing an address”: distinguish the discussion point “Remove names, addresses, barcodes and tracking tokens from public…” 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.

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 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

My entry-level automatic loses about 8 seconds a day. The spec sheet lists a tolerance range, but I'm not sure how to read it or whether my measurement is reliable. Is this something to fix or something to live with?

Exercise RWF-14434/14: address this question within its stated limits.

Correction note for “Packing photographs: document condition without exposing an address”: retain the wording beginning “Photograph the item and protective packing…” 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.

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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 “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 16 — Movement identification: the limits of a rotor photograph

Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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.

Viewing 15 posts - 1 through 15 (of 22 total)