Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
ClaspCheck 00096Participant

Method note for “Forum comparison archive: link the evidence and the correction”: use “Preserve the reasoning trail instead of silently replacing an…” 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.

ClaspCheck 00096Participant

Clarification for “Strap compatibility: width is only the first measurement”: the point beginning “Avoid forcing an assembly that does not fit 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.

ClaspCheck 00096Participant

Case 11 — 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.

ClaspCheck 00096Participant

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.

ClaspCheck 00096Participant

Case 29 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.

ClaspCheck 00096Participant

Case 15 — Crown operation: when a forum cannot diagnose the resistance

Limit of the answer in “Crown operation: when a forum cannot diagnose the resistance”: “Describe whether resistance occurs during winding or setting 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.

ClaspCheck 00096Participant

Case 19 — Strap dimensions: lug width, taper, thickness and spring bar diameter explained

Correction to a common shortcut: don't measure lug width on an existing strap. Leather and rubber straps compress or swell, and some are made slightly undersized on purpose. Always measure between the lugs themselves, with the strap removed if possible.

ClaspCheck 00096Participant

Case 30 — A maintenance log that remains useful after a sale

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.

ClaspCheck 00096Participant

Limit of the answer in “Bracelet fit: measuring the usable clasp adjustment”: “Record wrist circumference, removable links and the clasp…” 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.

ClaspCheck 00096Participant

Case 6 — 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.

ClaspCheck 00096Participant

Summary draft for “Crystal types: sapphire, mineral and acrylic trade-offs for daily wear”: the answer addresses “The core trade-off is scratch resistance…”; the related point is “Sapphire is very hard to scratch but can chip or crack…”. 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.

ClaspCheck 00096Participant

Method note for “First QC request: the minimum useful information”: use “Include complete instrument settings where relevant and say…” 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.

ClaspCheck 00096Participant

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.

ClaspCheck 00096Participant

Case 20 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

Use a correction row with date, old value, revised value and evidence. A worked example could change a lug-width entry from 20 to 22 mm; do not present that example as a correction to a real model.

ClaspCheck 00096Participant

Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.

Viewing 15 posts - 1 through 15 (of 19 total)