Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 22 total)
ClaspCheck 00026Participant

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

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.

ClaspCheck 00026Participant

Case 68 — Lume questions: why does my lume fade so quickly, and how should I compare it? · source wording exercise

Clarification for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: the point beginning “Afterglow fades fastest in the first minutes and then settles to…” 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: source wording. Retain the source wording beside any paraphrase.

ClaspCheck 00026Participant

On anti-reflective coatings: inner-surface AR cuts glare without wear concerns. Outer-surface AR improves legibility further but can scuff over time, and the scuffs show up as hazy patches in certain light. When comparing two watches, check which surfaces are coated. Spec sheets often just say 'AR coated' without saying where.

ClaspCheck 00026Participant

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

ClaspCheck 00026Participant

Summary draft for “Service enquiry: information a watchmaker can use”: the answer addresses “Document when it stops, winding behaviour, recent impacts and…”; the related point is “Be honest about the watch and request an assessment…”. 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 00026Participant

A correction to a common assumption: a slightly loose fit isn't automatically wrong. Heavier heads tend to slide on loose bracelets, but a lighter watch often wears comfortably with a finger's width of space. Try 'loose' for a full day before deciding it doesn't work. Comfort over hours tells you more than the first minute.

ClaspCheck 00026Participant

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

Correction note for “Lug-to-lug and end-link overhang in wrist photographs”: retain the wording beginning “Record lug-to-lug and the effective span…” 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 00026Participant

Resolution checklist. 1) Rebalance links around the clasp. 2) Test every micro-adjust hole with each link count. 3) Check fit morning and afternoon. 4) Look for half-links by bracelet reference. 5) Accept slightly loose if the head is light. If none of that works, a strap with finer hole spacing is a reasonable conclusion, not a failure.

ClaspCheck 00026Participant

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

Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “Ask for photographs with the light moved 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 00026Participant

Case 5 — Date window centring: compare the same date at the same angle

Limit of the answer in “Date window centring: compare the same date at the same angle”: “Use the same numeral, camera axis…” 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 00026Participant

Case 9 — 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 00026Participant

Case 20 — 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 00026Participant

Clarification for “Forum comparison archive: link the evidence and the correction”: the point beginning “Add a dated correction near the original conclusion…” 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 00026Participant

A complication is any function beyond hours, minutes and seconds. A date window counts, technically, and so do a chronograph, GMT hand or moon phase. More complications usually mean more parts, more thickness and more service cost. For a first everyday watch, decide which functions you'd really use before treating them as value.

ClaspCheck 00026Participant

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

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds 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.

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