Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
ClaspCheck 07716Participant

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.

ClaspCheck 07716Participant

Case 25 — 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 07716Participant

Case 4 — Disputed observation: is this dial colour shift real or just lighting?

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

ClaspCheck 07716Participant

Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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 07716Participant

Differences in pigment, applied area, thickness and colour can affect appearance. Keep those design differences separate from claims about quality and use matched conditions for any comparison.

ClaspCheck 07716Participant

Case 5 — 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-23699/5: address this question within its stated limits.

ClaspCheck 07716Participant

Case 36 — Strap compatibility: width is only the first measurement

Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Measure the lug opening and document bar diameter,…” 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 07716Participant

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

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

Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “Compare multiple controlled angles and describe the visible observation without asserting…” 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 07716Participant

Case 43 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise

Summary draft for “Model comparison: dive bezel action and alignment, how to compare fairly”: the answer addresses “Crisp vs mushy is mostly about…”; the related point is “Alignment can be measured, so…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.

ClaspCheck 07716Participant

Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, 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.

ClaspCheck 07716Participant

Case 19 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem

My bracelet is either slightly too tight or slightly loose with any link combination. The clasp has three micro-adjust holes, and there are no half-links. What are the options before I give up and go to a strap?

Exercise RWF-16224/19: address this question within its stated limits.

ClaspCheck 07716Participant

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

Limit of the answer in “Packing photographs: document condition without exposing an address”: “Photograph the item and protective packing…” 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 07716Participant

Case 8 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

Can the same settings and winding state be used for several positions? Record each position separately rather than combining measurements taken under different conditions.

ClaspCheck 07716Participant

Correction note for “Disputed observation: is this dial colour shift real or just lighting?”: retain the wording beginning “The difficulty is that phone cameras adjust white balance automatically,…” 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.

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