Case 28 — Maintenance question: how do I tell if an automatic actually needs service?
A sudden rate change has several possible causes. Ask a watchmaker to test suspected magnetism rather than diagnosing it from a compass or attempting an adjustment based on forum replies.
Case 33 — Packing photographs: document condition without exposing an address
Limit of the answer in “Packing photographs: document condition without exposing an address”: “Photograph the item and protective packing…” 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 4 — Disputed observation: is this dial colour shift real or just lighting?
Several posts claim the newer batch of a particular blue-dial model looks more purple than the earlier batch. Others say it's purely photography and white balance. Can we settle this with evidence instead of arguing from different photos?
Exercise RWF-29849/4: address this question within its stated limits.
Reader check for “Lume comparison: keep exposure and charging conditions consistent”: distinguish the discussion point “Repeat with equal light source, charging duration, elapsed time and camera…” 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.
Limit of the answer in “Shipping timeline: separate dispatch, handover and scan events”: “Ask the sender or carrier for clarification; missing scans alone…” 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 9 — QC checklist: prioritise observable faults over pixel hunting
Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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 41 — First QC request: the minimum useful information · source wording exercise
What should an initial QC request include so replies can address the actual question?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Include complete instrument settings where relevant and say…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-24476/41: address this question within its stated limits.
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
Case 26 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Clarifying question: how are you charging it? A few seconds under a warm indoor bulb gives a much weaker charge than daylight or a UV source. Many 'weak lume' reports turn out to be undercharging. Try a consistent charge, such as 30 seconds under a phone flashlight at a fixed distance, before judging.
Case 17 — 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-17157/17: address this question within its stated limits.
Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.
Case 27 — Service enquiry: information a watchmaker can use
Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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 1 — Seller review template: facts, dates and unresolved questions
Clarification for “Seller review template: facts, dates and unresolved questions”: the point beginning “Use fields for order date, promised terms, dated…” 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 43 — Service enquiry: information a watchmaker can use · source wording exercise
Limit of the answer in “Service enquiry: information a watchmaker can use”: “Be honest about the watch and request an assessment…” 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: source wording. Retain the source wording beside any paraphrase.