Case 1 — Lume comparison: keep exposure and charging conditions consistent
Correction note for “Lume comparison: keep exposure and charging conditions consistent”: retain the wording beginning “Treat the comparison…” 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.
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain 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 34 — Forum comparison archive: link the evidence and the correction
Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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 27 — First QC request: the minimum useful information
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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.
Case 43 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise
Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Explain what the full-size image shows, what the crop adds 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: 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 35 — Maintenance question: how do I tell if an automatic actually needs service?
Clarifying question first: do you have a baseline? If you've never recorded the watch's rate or power reserve, 'drifting' is hard to judge. Start a simple log now with daily offset against a reference time for a week, and the hours it runs from full wind. Once you have that, later changes mean something.
Case 16 — QC checklist: prioritise observable faults over pixel hunting
Limit of the answer in “QC checklist: prioritise observable faults over pixel hunting”: “Start with function, legibility, assembly and…” 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 36 — Clasp photographs: what to request before judging alignment
Summary draft for “Clasp photographs: what to request before judging alignment”: the answer addresses “Request open and closed views from both sides,…”; the related point is “Separate cosmetic alignment from whether the clasp engages reliably;…”. 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.
Case 46 — Shipping timeline: separate dispatch, handover and scan events · source wording exercise
Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Ask the sender or carrier for clarification; missing scans alone…” 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. Retain the source wording beside any paraphrase.
Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.
Ask for profile shots of both case sides and a lug-top shot at an angle. Polishing shows as rounded edges, softened bevels or lug holes that look shallower than they should. Compare against a known-good reference image of the same model, not memory. A side-by-side tells you far more than a description.
Limit of the answer in “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: “Without those fields, the rate, amplitude and beat-error values lack…” 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 24 — QC photography: what photos actually help verify a pre-owned listing?
Proposed reusable request list. 1) Straight dial, diffuse light, hands clear of markers. 2) Both case profiles. 3) Lug tops at an angle. 4) Caseback and engravings. 5) Clasp and bracelet end links. 6) Dated note in frame. Optional: timegrapher reading or movement photos. Add or change items with a reason, and I'll keep the list current.
Case 20 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
First, a clarifying question: how many links are on each side of the clasp right now? Fit often improves by moving one link from the 6 o'clock side to the 12 o'clock side, or the reverse. That doesn't change length, but it shifts where the clasp sits under the wrist, and a centred clasp feels less tight.