Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 18 total)
TimeLog 02029Participant

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.

TimeLog 02029Participant

Case 21 — What a water-resistance claim does and does not establish

Correction note for “What a water-resistance claim does and does not establish”: retain the wording beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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.

TimeLog 02029Participant

Back-play is the most objective feel measurement. Set the bezel on a click and gently push it the other way without forcing it. Noticeable wobble before it engages means play. A little is common and within normal production, but if one model has visible movement and the other doesn't, that's a real difference you can describe.

TimeLog 02029Participant

Case 36 — Movement identification: the limits of a rotor photograph

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

TimeLog 02029Participant

Case 16 — Packing photographs: document condition without exposing an address

A condition record is useful but a shipping label contains personal information. How can the record be shared safely?

Exercise RWF-19314/16: address this question within its stated limits.

TimeLog 02029Participant

Case 33 — QC checklist: prioritise observable faults over pixel hunting

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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.

TimeLog 02029Participant

Reader check for “Shipping timeline: separate dispatch, handover and scan events”: distinguish the discussion point “Distinguish label creation from physical acceptance and retain dated…” 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.

TimeLog 02029Participant

Case 37 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Repeat with equal light source, charging duration, elapsed time and camera…” 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: source wording. Retain the source wording beside any paraphrase.

TimeLog 02029Participant

Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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.

TimeLog 02029Participant

Case 13 — Magnetism and rate: record evidence before naming a cause

Limit of the answer in “Magnetism and rate: record evidence before naming a cause”: “Record the change and the circumstances without treating…” 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.

TimeLog 02029Participant

Case 18 — Packing photographs: document condition without exposing an address

Summary draft for “Packing photographs: document condition without exposing an address”: the answer addresses “Photograph the item and protective packing…”; the related point is “Remove names, addresses, barcodes and tracking tokens from public…”. 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.

TimeLog 02029Participant

Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.

TimeLog 02029Participant

Case 183 — Maintenance question: how do I tell if an automatic actually needs service? · correction exercise

Method note for “Maintenance question: how do I tell if an automatic actually needs service?”: use “Once you have that, later…” 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. Preserve the old wording if a later source changes the interpretation.

TimeLog 02029Participant

Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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.

TimeLog 02029Participant

Case 4 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

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