Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 25 total)
TimeLog 00359Participant

Case 27 — Strap compatibility: width is only the first measurement

Limit of the answer in “Strap compatibility: width is only the first measurement”: “Measure the lug opening and document bar diameter,…” 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 00359Participant

Case 19 — 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.

TimeLog 00359Participant

Reader check for “Clasp photographs: what to request before judging alignment”: distinguish the discussion point “Separate cosmetic alignment from whether the clasp engages reliably;…” 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 00359Participant

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

Summary draft for “What a water-resistance claim does and does not establish”: the answer addresses “Ask a qualified watchmaker about a suitable test for that individual…”; the related point is “A photograph or a caseback engraving is not…”. 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 00359Participant

Case 103 — Model comparison: dive bezel action and alignment, how to compare fairly · comparison exercise

Summary draft for “Model comparison: dive bezel action and alignment, how to compare fairly”: the answer addresses “Alignment can be measured, so…”; the related point is “Back-play is the most objective…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: comparison. Make the basis of a comparison explicit before interpreting it.

TimeLog 00359Participant

Case 3 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.

TimeLog 00359Participant

A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.

TimeLog 00359Participant

Case 34 — Lume comparison: keep exposure and charging conditions consistent

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.

TimeLog 00359Participant

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

Summary draft for “What a water-resistance claim does and does not establish”: the answer addresses “Ask a qualified watchmaker about a suitable test for that individual…”; the related point is “A photograph or a caseback engraving is not…”. 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 00359Participant

Case 13 — First QC request: the minimum useful information

Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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 00359Participant

Case 23 — 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.

TimeLog 00359Participant

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

The available image hides the hinge and only shows the outer surface. Which additional views would answer the question?

Exercise RWF-19213/6: address this question within its stated limits.

TimeLog 00359Participant

Limit of the answer in “Comparing dial colour under different lighting”: “State the lighting 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.

TimeLog 00359Participant

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

A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?

Exercise RWF-15544/2: address this question within its stated limits.

TimeLog 00359Participant

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

A marker can look tilted when the camera is above the dial axis. What extra image would separate perspective from an assembly issue?

Exercise RWF-14402/12: address this question within its stated limits.

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