Skip to content
RepWatchForumSign in

Forum Replies Created

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

Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.

Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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 4 — Lug-to-lug and end-link overhang in wrist photographs

Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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 29 — Disputed observation: is this dial colour shift real or just lighting?

Something to keep apart: sunburst and gradient dials can look like different colours depending on viewing angle, even on the same piece. A shift that appears only at certain angles is a finish effect, not a batch difference. Include a straight-on shot and one tilted shot so readers can tell the two apart.

Case 22 — Crystal reflections: why a dark patch is not a coating test

Limit of the answer in “Crystal reflections: why a dark patch is not a coating test”: “No single lighting setup settles…” 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.

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.

Case 6 — QC photography: what photos actually help verify a pre-owned listing?

Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.

Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Redact addresses and payment information; do not invent service…”; the related point is “Keep the date, work performed, provider invoice reference…”. 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.

Thickness matters more than people expect. Straps around 4 to 5mm at the lugs can hit the case or stop the strap folding down on watches with short lugs or tight lug-to-case clearance. Do you know whether your watch has drilled lugs or a tight gap between strap and case? That tells you how much thickness is safe.

Case 9 — QC checklist: prioritise observable faults over pixel hunting

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.

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 — Comparing versions without mixing case sizes

Two purported versions differ in case diameter and bracelet. How can the comparison avoid attributing every difference to a revision?

Exercise RWF-13327/22: address this question within its stated limits.

Case 23 — Disputed observation: is this dial colour shift real or just lighting?

Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.

Case 15 — Service enquiry: information a watchmaker can use

Method note for “Service enquiry: information a watchmaker can use”: use “Document when it stops, winding behaviour, recent impacts 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 135 — QC checklist: prioritise observable faults over pixel hunting · documentation exercise

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Explain what the full-size image shows, what the crop adds 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. Distinguish an original record from a proposed record format.

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