Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
QCReader 00424Participant

Case 110 — Date window centring: compare the same date at the same angle · documentation exercise

Limit of the answer in “Date window centring: compare the same date at the same angle”: “Keep the uncropped originals alongside the detail crops and distinguish…” 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: documentation. Distinguish an original record from a proposed record format.

QCReader 00424Participant

Case 11 — Service enquiry: information a watchmaker can use

Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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.

QCReader 00424Participant

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

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

QCReader 00424Participant

On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.

QCReader 00424Participant

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

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

QCReader 00424Participant

Case 18 — Case finishing: distinguish a reflection from a surface mark

Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.

QCReader 00424Participant

Case 23 — Lume questions: why does my lume fade so quickly, and how should I compare it?

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.

QCReader 00424Participant

Case 33 — Lume questions: why does my lume fade so quickly, and how should I compare it?

My watch's lume is bright for a few minutes and then barely visible. Is that normal? People post lume shots of different watches, but they all seem to use different charging and exposure, so I can't tell what's actually better.

Exercise RWF-20174/33: address this question within its stated limits.

QCReader 00424Participant

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

Can the same settings and winding state be used for several positions? Record each position separately rather than combining measurements taken under different conditions.

QCReader 00424Participant

Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly and…” 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.

QCReader 00424Participant

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.

QCReader 00424Participant

Case 11 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

A complication is any function beyond hours, minutes and seconds. A date window counts, technically, and so do a chronograph, GMT hand or moon phase. More complications usually mean more parts, more thickness and more service cost. For a first everyday watch, decide which functions you'd really use before treating them as value.

QCReader 00424Participant

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

QCReader 00424Participant

Case 6 — Service enquiry: information a watchmaker can use

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.

QCReader 00424Participant

Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.

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