Skip to content
RepWatchForumSign in

Forum Replies Created

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

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

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.

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 5 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.

Method note for “A maintenance log that remains useful after a sale”: use “Redact addresses and payment information; do not invent service…” 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.

Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 9 — QC checklist: prioritise observable faults over pixel hunting

A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?

Exercise RWF-16869/9: address this question within its stated limits.

Clarifying question for the thread: is the goal to check authenticity, condition, or both? For condition, the request list above is enough. For authenticity, you also need caseback, serial or reference engravings, and ideally movement photos. Movement photos usually require opening the watch, which a seller may reasonably refuse without a watchmaker present.

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.

Case 21 — Case finishing: distinguish a reflection from a surface mark

Limit of the answer in “Case finishing: distinguish a reflection from a surface mark”: “Ask for photographs with the light moved 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 22 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained

Summary order of importance. 1) Lug width, measured between the lugs. 2) Lug-end thickness against clearance. 3) Spring bar diameter. 4) Taper and buckle width. 5) Length, which is usually given as long side / short side in mm and should be compared with a strap that already fits you.

Case 15 — Service enquiry: information a watchmaker can use

A service question only says that the watch stops occasionally. Which observations make an initial enquiry more useful?

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

Case 134 — Comparing versions without mixing case sizes · documentation exercise

Reader check for “Comparing versions without mixing case sizes”: distinguish the discussion point “List confirmed differences separately from seller descriptions and date the comparison…” from its proposed application. The thread offers a way to reason about the question, without adding a personal experience or a newly observed outcome. Review focus: documentation. Distinguish an original record from a proposed record format.

Case 20 — Lume questions: why does my lume fade so quickly, and how should I compare it?

A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.

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.

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

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