Skip to content
RepWatchForumSign in

Forum Replies Created

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

Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Request the closed bracelet circumference rather than inferring…” 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.

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

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.

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.

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

Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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.

Case 5 — Crystal reflections: why a dark patch is not a coating test

Correction note for “Crystal reflections: why a dark patch is not a coating test”: retain the wording beginning “No single lighting setup settles…” 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.

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.

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

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

Use a consistent charge, fixed exposure and several elapsed-time observations. Record readability and the conditions rather than applying an unsupported universal fade-time threshold.

Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.

Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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.

Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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.

Reader check for “What a water-resistance claim does and does not establish”: distinguish the discussion point “Ask a qualified watchmaker about a suitable test for that individual…” 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.

Case 38 — First QC request: the minimum useful information · source wording exercise

Method note for “First QC request: the minimum useful information”: use “Include complete instrument settings where relevant and say…” 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. Retain the source wording beside any paraphrase.

Method note for “Magnetism and rate: record evidence before naming a cause”: use “A competent watchmaker can test and diagnose it; random adjustment…” 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.

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

Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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.

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