Skip to content
RepWatchForumSign in

Forum Replies Created

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

Ask for photographs with the light moved and retain the same viewing angle. A mark should be assessed across multiple views; aggressive polishing is not an appropriate diagnostic test.

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

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.

Case 12 — Shipping timeline: separate dispatch, handover and scan events

Limit of the answer in “Shipping timeline: separate dispatch, handover and scan events”: “Distinguish label creation from physical acceptance and retain dated…” 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 12 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained

Correction to a common shortcut: don't measure lug width on an existing strap. Leather and rubber straps compress or swell, and some are made slightly undersized on purpose. Always measure between the lugs themselves, with the strap removed if possible.

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

Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.

Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.

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

Two glowing dials are shown with different camera exposure and unknown charging time. What can the images establish?

Exercise RWF-21411/32: address this question within its stated limits.

Method note for “Lume comparison: keep exposure and charging conditions consistent”: use “Treat the comparison…” 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 35 — Seller review template: facts, dates and unresolved questions

Summary draft for “Seller review template: facts, dates and unresolved questions”: the answer addresses “Use fields for order date, promised terms, dated…”; the related point is “Leave unsupported fields blank and separate observations from opinions; this…”. 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.

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.

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.

Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 15 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?

Exercise RWF-14434/15: address this question within its stated limits.

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.

Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain 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.

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