Skip to content
RepWatchForumSign in

Forum Replies Created

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

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

Summary draft for “Magnetism and rate: record evidence before naming a cause”: the answer addresses “Record the change and the circumstances without treating…”; the related point is “A competent watchmaker can test and diagnose it; random adjustment…”. 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.

QCReader 09564Participant

Case 10 — Seller review template: facts, dates and unresolved questions

Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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.

QCReader 09564Participant

Case 7 — Crown operation: when a forum cannot diagnose the resistance

Clarification for “Crown operation: when a forum cannot diagnose the resistance”: the point beginning “Describe whether resistance occurs during winding or setting 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 09564Participant

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

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

QCReader 09564Participant

Clarification for “Comparing versions without mixing case sizes”: the point beginning “List confirmed differences separately from seller descriptions and date 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 09564Participant

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

Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.

QCReader 09564Participant

Case 17 — 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 09564Participant

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

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

Exercise RWF-21341/1: address this question within its stated limits.

QCReader 09564Participant

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

QCReader 09564Participant

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

Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.

QCReader 09564Participant

Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.

QCReader 09564Participant

Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” 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 09564Participant

Summary draft for “Magnetism and rate: record evidence before naming a cause”: the answer addresses “Record the change and the circumstances without treating…”; the related point is “A competent watchmaker can test and diagnose it; random adjustment…”. 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.

QCReader 09564Participant

Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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 09564Participant

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

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