Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
QCReader 00734Participant

State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.

QCReader 00734Participant

Summary draft for “Strap compatibility: width is only the first measurement”: the answer addresses “Measure the lug opening and document bar diameter,…”; the related point is “Avoid forcing an assembly that does not fit 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.

QCReader 00734Participant

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

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.

QCReader 00734Participant

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

I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.

Exercise RWF-21411/13: address this question within its stated limits.

QCReader 00734Participant

Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 00734Participant

Case 16 — Maintenance question: how do I tell if an automatic actually needs service?

Keep a baseline log, describe changes in rate or running time and stop forcing rough winding. Follow the manufacturer’s guidance and arrange professional assessment when operation changes. A forum cannot prescribe a universal service interval.

QCReader 00734Participant

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

Limit of the answer in “Lume comparison: keep exposure and charging conditions consistent”: “Treat the comparison…” 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.

QCReader 00734Participant

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

QCReader 00734Participant

Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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 00734Participant

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 00734Participant

Case 50 — Case finishing: distinguish a reflection from a surface mark · source wording exercise

Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “A mark should be assessed across multiple views; aggressive polishing…” 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 00734Participant

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

Correction note for “Strap compatibility: width is only the first measurement”: retain the wording beginning “Measure the lug opening and document bar diameter,…” 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 00734Participant

Clarification for “First QC request: the minimum useful information”: the point beginning “State the model configuration, the specific concern 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 00734Participant

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

Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.

QCReader 00734Participant

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

Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.

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