Skip to content
RepWatchForumSign in

Forum Replies Created

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

Method note for “Timegrapher reading context: what do rate, amplitude and beat error actually tell me?”: use “First identify the caliber, lift-angle setting, winding…” 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.

Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “A single number cannot establish service condition, movement identity…”; the related point is “Keep the complete recording and ask for the…”. 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.

Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.

Add lug-to-lug, thickness and lug width as separate rows. Diameter alone tells you little about wearability. Two cases 2mm apart in diameter can be within 1mm of each other lug to lug, and that number decides whether the watch overhangs a small wrist. Also give the source for each figure: manufacturer sheet, caliper measurement, or catalogue listing.

Case 25 — Seller review template: facts, dates and unresolved questions

Correction note for “Seller review template: facts, dates and unresolved questions”: retain the wording beginning “Use fields for order date, promised terms, 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.

Reader check for “Forum comparison archive: link the evidence and the correction”: distinguish the discussion point “Add a dated correction near the original conclusion…” 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.

Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.

The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.

Case 13 — 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-19240/13: address this question within its stated limits.

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

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 24 — Packing photographs: document condition without exposing an address

Method note for “Packing photographs: document condition without exposing an address”: use “Photograph the item and protective packing…” 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 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

One method that often helps without any service is using overnight resting position to cancel daily drift. Many watches gain in some positions and lose in others. If yours loses on the wrist, try leaving it crown up or dial up overnight and log the result for a few nights. Some people get close to zero this way.

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

A practical test without a camera: charge both watches the same way, sit in a dark room, and check readability at 5 minutes, 30 minutes and 2 hours. Write down which you can still read the time on. It's subjective but repeatable, and more useful than a single photo.

Case 15 — Case finishing: distinguish a reflection from a surface mark

Method note for “Case finishing: distinguish a reflection from a surface mark”: use “Ask for photographs with the light moved 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.

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