Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 4 — Lug-to-lug and end-link overhang in wrist photographs

Summary draft for “Lug-to-lug and end-link overhang in wrist photographs”: the answer addresses “Record lug-to-lug and the effective span…”; the related point is “Use a similar camera distance and neutral wrist position; photographs support…”. 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.

Method note for “What a water-resistance claim does and does not establish”: use “A photograph or a caseback engraving is not…” 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 “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” 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 — Movement identification: the limits of a rotor photograph

Summary draft for “Movement identification: the limits of a rotor photograph”: the answer addresses “Describe visible bridge shapes and markings separately…”; the related point is “Ask a qualified watchmaker to inspect it if identification matters for…”. 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 20 — QC photographs: perspective or a genuinely tilted index?

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.

Limit of the answer in “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: “Diameter alone tells you little…” 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 32 — Clasp photographs: what to request before judging alignment

Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.

Case 16 — Model comparison: dive bezel action and alignment, how to compare fairly

Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.

Case 36 — First QC request: the minimum useful information

Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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. Keep the stated question separate from any broader claim.

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.

Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.

Case 8 — Clasp photographs: what to request before judging alignment

Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Request open and closed views from both sides,…” 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.

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

Case 36 — Model comparison: dive bezel action and alignment, how to compare fairly

People keep comparing the bezels on two similar dive-style watches. One is called crisp, the other mushy, and alignment complaints come up for both. What would a fair comparison look like, and what is actually a defect versus a preference?

Exercise RWF-15814/36: address this question within its stated limits.

Case 18 — QC photographs: perspective or a genuinely tilted index?

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.

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