Case 3 — Clasp photographs: what to request before judging alignment
Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.
Correction note for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: retain the wording beginning “Add lug-to-lug, thickness and lug width…” 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 31 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.
Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.
Case 5 — Crown operation: when a forum cannot diagnose the resistance
Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 25 — What a water-resistance claim does and does not establish
Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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 12 — Reading a timegrapher recording without losing the context
Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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.
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.
Case 51 — Seller review template: facts, dates and unresolved questions · source wording exercise
What belongs in a useful review template when no actual purchase experience is being asserted?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Leave unsupported fields blank and separate observations from opinions; this…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-16210/51: address this question within its stated limits.
Case 21 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Check whether a compatible half-link exists for the exact bracelet reference. Compatibility involves the connection and hardware, not just width. Ask a watchmaker if the correct part is uncertain.
Case 13 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?
Exercise RWF-12733/13: address this question within its stated limits.
Case 37 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic? · source wording exercise
My entry-level automatic loses about 8 seconds a day. The spec sheet lists a tolerance range, but I'm not sure how to read it or whether my measurement is reliable. Is this something to fix or something to live with?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Comparing against a phone clock once a day for a week,…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-11387/37: address this question within its stated limits.
Case 5 — Lume questions: why does my lume fade so quickly, and how should I compare it?
Lume photos are close to useless for comparison unless exposure is fixed. Phones raise exposure automatically in the dark, so a dim watch can look as bright as a strong one. For a fair photo comparison: same charge method, same delay after charging, manual exposure, and both watches in the same frame.
Case 1 — Service enquiry: information a watchmaker can use
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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.
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.