Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 39 — Strap compatibility: width is only the first measurement · source wording exercise

Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?

Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Avoid forcing an assembly that does not fit and…” as the discussion anchor; no new event or result is supplied.

Exercise RWF-31231/39: address this question within its stated limits.

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

I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?

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

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

Several posts claim the newer batch of a particular blue-dial model looks more purple than the earlier batch. Others say it's purely photography and white balance. Can we settle this with evidence instead of arguing from different photos?

Exercise RWF-31198/23: address this question within its stated limits.

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.

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

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

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.

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

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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 13 — 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.

Case 11 — Comparing dial colour under different lighting

State the lighting and white-balance limitations. Compare controlled images where available and avoid calling a colour defect from differently processed photographs.

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

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

The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.

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

Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly 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.

Case 17 — Service enquiry: information a watchmaker can use

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.

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

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

On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.

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