Skip to content
RepWatchForumSign in

Forum Replies Created

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

Clarification for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: the point beginning “Diameter alone tells you little…” 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 20 — Forum comparison archive: link the evidence and the correction

Add a dated correction near the original conclusion and link the new evidence. Preserve the reasoning trail instead of silently replacing an uncertain claim with a confident one.

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

Limit of the answer in “Comparing dial colour under different lighting”: “State the lighting 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.

Record the change and the circumstances without treating the suspected cause as established. A competent watchmaker can test and diagnose it; random adjustment is not a substitute for assessment.

Record lug-to-lug and the effective span including rigid end links. Use a similar camera distance and neutral wrist position; photographs support fit discussion but do not replace measurements.

Case 44 — Shipping timeline: separate dispatch, handover and scan events · source wording exercise

Reader check for “Shipping timeline: separate dispatch, handover and scan events”: distinguish the discussion point “Ask the sender or carrier for clarification; missing scans alone…” 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: source wording. Retain the source wording beside any paraphrase.

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

Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 49 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained · source wording exercise

Method note for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: use “Measure with a ruler marked in millimetres, ideally…” 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.

Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.

Case 12 — Movement identification: the limits of a rotor photograph

Clarification for “Movement identification: the limits of a rotor photograph”: the point beginning “Describe visible bridge shapes and markings separately…” 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 — Crystal reflections: why a dark patch is not a coating test

Limit of the answer in “Crystal reflections: why a dark patch is not a coating test”: “No single lighting setup settles…” 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 5 — 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.

Case 125 — Service enquiry: information a watchmaker can use · documentation exercise

Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Be honest about the watch and request an assessment…” 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. Distinguish an original record from a proposed record format.

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