Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.
Forum Replies Created
Case 29 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
A correction to a common assumption: a slightly loose fit isn't automatically wrong. Heavier heads tend to slide on loose bracelets, but a lighter watch often wears comfortably with a finger's width of space. Try 'loose' for a full day before deciding it doesn't work. Comfort over hours tells you more than the first minute.
Case 37 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · source wording exercise
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?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Diameter alone tells you little…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-30241/37: address this question within its stated limits.
Case 8 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear
On anti-reflective coatings: inner-surface AR cuts glare without wear concerns. Outer-surface AR improves legibility further but can scuff over time, and the scuffs show up as hazy patches in certain light. When comparing two watches, check which surfaces are coated. Spec sheets often just say 'AR coated' without saying where.
Reader check for “Comparing versions without mixing case sizes”: distinguish the discussion point “Match reference, dimensions and…” 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.
Method note for “Forum comparison archive: link the evidence and the correction”: use “Add a dated correction near the original conclusion…” 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 17 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log
State whether thickness includes the highest point of a domed crystal. Different measurement methods can produce different figures, so keep both the source and method beside each dimension.
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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.
Correction note for “Date window centring: compare the same date at the same angle”: retain the wording beginning “Keep the uncropped originals alongside the detail crops and distinguish…” 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 6 — 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.
Case 8 — Forum comparison archive: link the evidence and the correction
Correction note for “Forum comparison archive: link the evidence and the correction”: retain the wording beginning “Add a dated correction near the original conclusion…” 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 34 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.
Case 24 — Disputed observation: is this dial colour shift real or just lighting?
Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.
Method note for “Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?”: use “Start with how you…” 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 35 — Case finishing: distinguish a reflection from a surface mark
Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.