Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 21 total)
ClaspCheck 07396Participant

Case 31 — Service enquiry: information a watchmaker can use

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

ClaspCheck 07396Participant

Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.

ClaspCheck 07396Participant

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

Summary draft for “QC photographs: perspective or a genuinely tilted index?”: the answer addresses “Request a level straight-on image with the hands…”; the related point is “Compare two independently aligned images before drawing a conclusion; an overlay…”. 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 07396Participant

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

Correction note for “Packing photographs: document condition without exposing an address”: retain the wording beginning “Photograph the item and protective packing…” 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 07396Participant

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

Limit of the answer in “Crown operation: when a forum cannot diagnose the resistance”: “Describe whether resistance occurs during winding or setting and…” 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.

ClaspCheck 07396Participant

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

ClaspCheck 07396Participant

Case 27 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

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.

ClaspCheck 07396Participant

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

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

Power reserve is how long the watch runs from full wind until it stops. It matters if you rotate watches: a 38-hour reserve may stop over a weekend off the wrist, while 70-plus hours may not. One clarifying point is that rate stability often gets worse near the end of the reserve, so the full figure is not all precision-grade running time.

ClaspCheck 07396Participant

Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.

ClaspCheck 07396Participant

Case 36 — Model comparison: dive bezel action and alignment, how to compare fairly

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

ClaspCheck 07396Participant

Case 46 — Lume comparison: keep exposure and charging conditions consistent · source wording exercise

Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Repeat with equal light source, charging duration, elapsed time and camera…” 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: source wording. Retain the source wording beside any paraphrase.

ClaspCheck 07396Participant

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

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

ClaspCheck 07396Participant

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

Case 22 — A maintenance log that remains useful after a sale

Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.

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