Skip to content
RepWatchForumSign in

Forum Replies Created

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

Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.

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.

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

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

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

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.

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

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

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

Summary draft for “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: the answer addresses “Lug width is the essential one: the inside distance between…”; the related point is “Measure with a ruler marked in millimetres, ideally…”. 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 31 — Comparing dial colour under different lighting

Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting 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.

Reader check for “Reading a timegrapher recording without losing the context”: distinguish the discussion point “Keep the complete recording and ask for the…” 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 17 — QC photography: what photos actually help verify a pre-owned listing?

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.

Case 10 — QC checklist: prioritise observable faults over pixel hunting

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds and…”. 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 10 — Clasp photographs: what to request before judging alignment

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

Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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 — Crystal reflections: why a dark patch is not a coating test

Correction note for “Crystal reflections: why a dark patch is not a coating test”: retain the wording beginning “No single lighting setup settles…” 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.

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