Case 35 — Reading a timegrapher recording without losing the context
Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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.
Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.
Case 1 — Disputed observation: is this dial colour shift real or just lighting?
The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.
Case 9 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
Spec sheets list sapphire, mineral or acrylic crystals, and opinions in threads are very strong. For a daily-wear watch, what are the real trade-offs, and is an anti-reflective coating worth paying for?
Exercise RWF-29092/9: address this question within its stated limits.
Case 78 — Shipping timeline: separate dispatch, handover and scan events · comparison exercise
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. Make the basis of a comparison explicit before interpreting it.
Case 12 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
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 264 — A maintenance log that remains useful after a sale · reader check exercise
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Redact addresses and payment information; do not invent service…” 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: reader check. State what a new reader can and cannot infer from this exercise.
Case 7 — 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 36 — Movement identification: the limits of a rotor photograph
Method note for “Movement identification: the limits of a rotor photograph”: use “Describe visible bridge shapes and markings separately…” 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 “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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 — 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 2 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
A correction to a common assumption: a slightly loose fit isn't automatically wrong. Heavier heads tend to slide on loose bracelets, but a lighter watch often wears comfortably with a finger's width of space. Try 'loose' for a full day before deciding it doesn't work. Comfort over hours tells you more than the first minute.
Case 15 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
A stated water-resistance rating does not establish the present condition of an individual watch. Separate the manufacturer specification from a dated inspection or test of the particular example.
Case 38 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
Clarification for “Model comparison: dive bezel action and alignment, how to compare fairly”: the point beginning “Crisp vs mushy is mostly about…” 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.
Case 27 — Maintenance question: how do I tell if an automatic actually needs service?
Sealing and movement performance are separate questions. Ask a qualified watchmaker about inspection and testing appropriate to the particular watch and its intended use; a healthy rate does not establish water resistance.