Case 13 — What a water-resistance claim does and does not establish
Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.
Forum Replies Created
Clarification for “Reading a timegrapher recording without losing the context”: the point beginning “Keep the complete recording and ask for the…” 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 29 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Wrist size changes during the day and with temperature, sometimes by several millimetres. A fit that feels tight in the afternoon may be right in the morning. Before buying parts, check the fit at different times. You may find the 'too tight' setting is only a problem a few hours a day.
Case 38 — Comparing versions without mixing case sizes · source wording 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: source wording. Retain the source wording beside any paraphrase.
On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.
Case 17 — Case finishing: distinguish a reflection from a surface mark
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.
Case 9 — 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 9 — QC photographs: perspective or a genuinely tilted index?
Method note for “QC photographs: perspective or a genuinely tilted index?”: use “Request a level straight-on image with the hands…” 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 14 — 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 19 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.
Case 30 — Comparing dial colour under different lighting
Correction note for “Comparing dial colour under different lighting”: retain the wording beginning “State the lighting and…” 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 13 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly and…” 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.
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.
Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” 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.
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.