Skip to content
RepWatchForumSign in

Forum Replies Created

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

Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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.

A caution: photos can't settle everything. Water resistance, timekeeping and internal condition aren't visible in any image. A short timegrapher video or a stated recent rate test adds information, but treat it as a seller claim unless an independent party confirms it. Photos narrow the risk. They don't remove it.

First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.

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

Thickness matters more than people expect. Straps around 4 to 5mm at the lugs can hit the case or stop the strap folding down on watches with short lugs or tight lug-to-case clearance. Do you know whether your watch has drilled lugs or a tight gap between strap and case? That tells you how much thickness is safe.

Method note for “Clasp photographs: what to request before judging alignment”: use “Request open and closed views from both sides,…” 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 17 — A maintenance log that remains useful after a sale

Correction note for “A maintenance log that remains useful after a sale”: retain the wording beginning “Keep the date, work performed, provider invoice reference…” 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 35 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.

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

Caliber is the movement's model designation, like a part number. Two watches from different brands can share the same caliber family with different finishing or regulation. On a spec sheet it tells you what's inside and roughly what service parts are available. It doesn't tell you how well that particular example was adjusted.

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

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.

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

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

Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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 20 — 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.

Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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 98 — Comparing versions without mixing case sizes · comparison exercise

Limit of the answer in “Comparing versions without mixing case sizes”: “Match reference, dimensions 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: comparison. Make the basis of a comparison explicit before interpreting it.

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