Case 26 — QC checklist: prioritise observable faults over pixel hunting
Correction note for “QC checklist: prioritise observable faults over pixel hunting”: retain the wording beginning “Start with function, legibility, assembly 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 49 — Packing photographs: document condition without exposing an address · source wording exercise
Method note for “Packing photographs: document condition without exposing an address”: use “Remove names, addresses, barcodes and tracking tokens from public…” 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. Retain the source wording beside any paraphrase.
Case 124 — Clasp photographs: what to request before judging alignment · documentation exercise
Method note for “Clasp photographs: what to request before judging alignment”: use “Separate cosmetic alignment from whether the clasp engages reliably;…” 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. Distinguish an original record from a proposed record format.
Case 28 — First QC request: the minimum useful information
What should an initial QC request include so replies can address the actual question?
Exercise RWF-27693/28: address this question within its stated limits.
Case 23 — First QC request: the minimum useful information
Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern 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.
Domed crystals of any material add distortion at the edges, which some people like and others find hard to read at angles. Box-shaped or high-domed crystals also add thickness. If you're comparing two otherwise similar watches, check total thickness against crystal profile before assuming the case itself is thicker.
Request a level straight-on image with the hands clear of the marker. Compare two independently aligned images before drawing a conclusion; an overlay cannot correct an oblique camera angle.
Case 36 — Model comparison: dive bezel action and alignment, how to compare fairly
Correction to earlier posts in similar threads: 120-click bezels aren't automatically worse. More positions means smaller steps, which can feel less pronounced. Comparing a 60-click and a 120-click bezel on crispness alone is apples to oranges. Compare same-click-count designs, or note the difference clearly.
Case 41 — Comparing versions without mixing case sizes · source wording exercise
Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “List confirmed differences separately from seller descriptions and date the comparison…”; the related point is “Match reference, dimensions 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.
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.
Case 33 — Strap compatibility: width is only the first measurement
Summary draft for “Strap compatibility: width is only the first measurement”: the answer addresses “Measure the lug opening and document bar diameter,…”; the related point is “Avoid forcing an assembly that does not fit and…”. 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.
Summary draft for “Crown operation: when a forum cannot diagnose the resistance”: the answer addresses “Describe whether resistance occurs during winding or setting and…”; the related point is “Stop forcing it and arrange inspection rather than trying…”. 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.
A caution: photos can't settle everything. Water resistance, timekeeping and internal condition aren't visible in any image. A short timegrapher video or a stated recent rate test adds information, but treat it as a seller claim unless an independent party confirms it. Photos narrow the risk. They don't remove it.
Case 29 — Lug-to-lug and end-link overhang in wrist photographs
Summary draft for “Lug-to-lug and end-link overhang in wrist photographs”: the answer addresses “Record lug-to-lug and the effective span…”; the related point is “Use a similar camera distance and neutral wrist position; photographs support…”. 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 39 — QC photography: what photos actually help verify a pre-owned listing? · source wording exercise
Reader check for “QC photography: what photos actually help verify a pre-owned listing?”: distinguish the discussion point “Flash flattens printing and hides…” 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: source wording. Retain the source wording beside any paraphrase.