Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
ClaspCheck 07236Participant

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

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

ClaspCheck 07236Participant

Case 16 — QC photography: what photos actually help verify a pre-owned listing?

Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.

ClaspCheck 07236Participant

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

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

Exercise RWF-28357/5: address this question within its stated limits.

ClaspCheck 07236Participant

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.

ClaspCheck 07236Participant

Case 10 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.

ClaspCheck 07236Participant

Case 1 — 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-23625/1: address this question within its stated limits.

ClaspCheck 07236Participant

Case 4 — Reading a timegrapher recording without losing the context

Limit of the answer in “Reading a timegrapher recording without losing the context”: “Keep the complete recording and ask for the…” 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.

ClaspCheck 07236Participant

Reader check for “Comparing dial colour under different lighting”: distinguish the discussion point “State the lighting and…” 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.

ClaspCheck 07236Participant

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.

ClaspCheck 07236Participant

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

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.

ClaspCheck 07236Participant

Method note for “Date window centring: compare the same date at the same angle”: use “Keep the uncropped originals alongside the detail crops and distinguish…” 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.

ClaspCheck 07236Participant

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

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.

ClaspCheck 07236Participant

Case 24 — First QC request: the minimum useful information

What should an initial QC request include so replies can address the actual question?

Exercise RWF-15133/24: address this question within its stated limits.

ClaspCheck 07236Participant

Document when it stops, winding behaviour, recent impacts and the positions in which it happens. Be honest about the watch and request an assessment before approving work or ordering parts.

ClaspCheck 07236Participant

Case 51 — Magnetism and rate: record evidence before naming a cause · source wording exercise

Correction note for “Magnetism and rate: record evidence before naming a cause”: retain the wording beginning “A competent watchmaker can test and diagnose it; random adjustment…” 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. Retain the source wording beside any paraphrase.

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