Skip to content
RepWatchForumSign in

Forum Replies Created

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

Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.

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.

Case 20 — Seller review template: facts, dates and unresolved questions

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.

No single lighting setup settles that question. Compare multiple controlled angles and describe the visible observation without asserting material specifications that have not been verified.

Case 38 — Bracelet fit: measuring the usable clasp adjustment · source wording exercise

Correction note for “Bracelet fit: measuring the usable clasp adjustment”: retain the wording beginning “Request the closed bracelet circumference rather than inferring…” 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. Retain the source wording beside any paraphrase.

Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Request open and closed views from both sides,…” 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.

Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain dated…” 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 27 — 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-22979/27: address this question within its stated limits.

Summary draft for “Packing photographs: document condition without exposing an address”: the answer addresses “Remove names, addresses, barcodes and tracking tokens from public…”; the related point is “Photograph the item and protective packing…”. 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 19 — What a water-resistance claim does and does not establish

Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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 19 — Shipping timeline: separate dispatch, handover and scan events

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 24 — What a water-resistance claim does and does not establish

Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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.

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

Case 29 — QC photographs: perspective or a genuinely tilted index?

Clarification for “QC photographs: perspective or a genuinely tilted index?”: the point beginning “Request a level straight-on image with the hands…” 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 “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.

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