Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)
ClaspCheck 05066Participant

Case 8 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.

ClaspCheck 05066Participant

Case 135 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · documentation exercise

Limit of the answer in “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: “Average across several days before…” 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.

ClaspCheck 05066Participant

Case 7 — QC photographs: perspective or a genuinely tilted index?

Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.

ClaspCheck 05066Participant

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.

ClaspCheck 05066Participant

Case 18 — QC photographs: perspective or a genuinely tilted index?

Correction note for “QC photographs: perspective or a genuinely tilted index?”: retain the wording beginning “Request a level straight-on image with the hands…” 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.

ClaspCheck 05066Participant

Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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.

ClaspCheck 05066Participant

Summary draft for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: the answer addresses “Without those fields, the rate, amplitude and beat-error values lack…”; the related point is “Can the same settings and winding state be…”. 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.

ClaspCheck 05066Participant

Case 31 — Bracelet fit: measuring the usable clasp adjustment

A nominal case diameter says little about a bracelet that cannot be shortened enough. How should a sizing question be documented?

Exercise RWF-18633/31: address this question within its stated limits.

ClaspCheck 05066Participant

Case 30 — Lug-to-lug and end-link overhang in wrist photographs

Record lug-to-lug and the effective span including rigid end links. Use a similar camera distance and neutral wrist position; photographs support fit discussion but do not replace measurements.

ClaspCheck 05066Participant

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Use a similar camera distance and neutral wrist position; photographs support…” 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 05066Participant

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

ClaspCheck 05066Participant

Case 42 — Service enquiry: information a watchmaker can use · source wording exercise

Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Be honest about the watch and request an assessment…” 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.

ClaspCheck 05066Participant

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

Treat the comparison as inconclusive. Repeat with equal light source, charging duration, elapsed time and camera settings; disclose conditions rather than assigning an unsupported quality score.

ClaspCheck 05066Participant

Case 18 — Comparing dial colour under different lighting

Summary draft for “Comparing dial colour under different lighting”: the answer addresses “State the lighting and…”; the related point is “Compare controlled images where available and avoid calling a…”. 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.

ClaspCheck 05066Participant

Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved 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.

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