Case 16 — 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 49 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Explain what the full-size image shows, what the crop adds and…”; the related point is “Start with function, legibility, assembly and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.
Reader check for “Packing photographs: document condition without exposing an address”: distinguish the discussion point “Photograph the item and protective packing…” 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.
Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Case 33 — First QC request: the minimum useful information
Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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 162 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve · uncertainty exercise
New here and reading spec sheets for the first time. Four terms keep tripping me up: complication, caliber, jewel count and power reserve. Short definitions would help, and so would a note on which ones actually matter when comparing two everyday watches.
Review focus: uncertainty. Leave the unresolved part visible instead of supplying a result. Use the original answer fragment “A complication is any function beyond…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-25905/162: address this question within its stated limits.
Case 33 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
The reported numbers alone do not establish damage or the need for service. Confirm the setup, collect comparable readings and ask a watchmaker to assess a concerning or changing pattern.
Document when it stops, winding behaviour, recent impacts and the positions in which it happens. Be honest about the watch and request an assessment before approving work or ordering parts.
Case 45 — QC photography: what photos actually help verify a pre-owned listing? · source wording exercise
Limit of the answer in “QC photography: what photos actually help verify a pre-owned listing?”: “Flash flattens printing and hides…” 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.
State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.
Case 24 — A maintenance log that remains useful after a sale
Method note for “A maintenance log that remains useful after a sale”: use “Keep the date, work performed, provider invoice reference…” 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.
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 12 — Shipping timeline: separate dispatch, handover and scan events
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. Keep the stated question separate from any broader claim.
Case 22 — Reading a timegrapher recording without losing the context
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.
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.