Skip to content
RepWatchForumSign in

Forum Replies Created

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

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

Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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 4 — 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-25612/4: address this question within its stated limits.

Reader check for “Disputed observation: is this dial colour shift real or just lighting?”: distinguish the discussion point “The difficulty is that phone cameras adjust white balance automatically,…” 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: scope. Keep the stated question separate from any broader claim.

Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.

Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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.

Case 28 — 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 46 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear · source wording exercise

Method note for “Crystal types: sapphire, mineral and acrylic trade-offs for daily wear”: use “Sapphire is very hard to scratch but can chip or crack…” 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. Retain the source wording beside any paraphrase.

Reader check for “Comparing dial colour under different lighting”: distinguish the discussion point “Compare controlled images where available and avoid calling a…” 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: scope. Keep the stated question separate from any broader claim.

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

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 43 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise

Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Crisp vs mushy is mostly about…” 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. Retain the source wording beside any paraphrase.

Correction note for “A maintenance log that remains useful after a sale”: retain the wording beginning “Keep the date, work performed, provider invoice reference…” 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.

Method note for “Date window centring: compare the same date at the same angle”: use “Use the same numeral, camera axis…” 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 “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.

Case 109 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me? · documentation exercise

Limit of the answer in “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: “Record each position separately rather than combining measurements…” 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: documentation. Distinguish an original record from a proposed record format.

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