Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 20 — First QC request: the minimum useful information

Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern and…” 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 36 — QC checklist: prioritise observable faults over pixel hunting

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 26 — 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 30 — QC photography: what photos actually help verify a pre-owned listing?

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 13 — Maintenance question: how do I tell if an automatic actually needs service?

Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.

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 38 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise

Reader check for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: distinguish the discussion point “Comparing against a phone clock once a day for a week,…” 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.

Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.

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

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

Summary draft for “Crystal reflections: why a dark patch is not a coating test”: the answer addresses “No single lighting setup settles…”; the related point is “Compare multiple controlled angles and describe the visible observation without asserting…”. 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.

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

Case 24 — Reading a timegrapher recording without losing the context

The supplied screen shows a rate but does not identify the lift angle, position or winding state. Which observations should accompany the recording?

Exercise RWF-06399/24: address this question within its stated limits.

Case 7 — QC photography: what photos actually help verify a pre-owned listing?

Proposed reusable request list. 1) Straight dial, diffuse light, hands clear of markers. 2) Both case profiles. 3) Lug tops at an angle. 4) Caseback and engravings. 5) Clasp and bracelet end links. 6) Dated note in frame. Optional: timegrapher reading or movement photos. Add or change items with a reason, and I'll keep the list current.

Clarification for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: the point beginning “First identify the caliber, lift-angle setting, winding…” 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.

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