Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 20 total)
TimeLog 01019Participant

Case 20 — What a water-resistance claim does and does not establish

Method note for “What a water-resistance claim does and does not establish”: use “Ask a qualified watchmaker about a suitable test for that individual…” 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.

TimeLog 01019Participant

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

Document spring-bar diameter, end-tip fit and the strap’s clearance using appropriate measuring tools. If dimensions or compatibility are uncertain, ask a watchmaker rather than forcing a bar or substituting an unsuitable part.

TimeLog 01019Participant

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

Clarification for “QC checklist: prioritise observable faults over pixel hunting”: the point beginning “Start with function, legibility, assembly 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.

TimeLog 01019Participant

Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” 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.

TimeLog 01019Participant

Document when it stops, winding behaviour, recent impacts and the positions in which it happens. Be honest about the watch and request an assessment before approving work or ordering parts.

TimeLog 01019Participant

Limit of the answer in “Seller review template: facts, dates and unresolved questions”: “Use fields for order date, promised terms, dated…” 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.

TimeLog 01019Participant

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

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

TimeLog 01019Participant

Limit of the answer in “Strap dimensions: lug width, taper, thickness and spring bar diameter explained”: “Lug width is the essential one: the inside distance between…” 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.

TimeLog 01019Participant

State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.

TimeLog 01019Participant

Case 36 — Packing photographs: document condition without exposing an address

Correction note for “Packing photographs: document condition without exposing an address”: retain the wording beginning “Photograph the item and protective packing…” 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.

TimeLog 01019Participant

Case 3 — Forum comparison archive: link the evidence and the correction

Limit of the answer in “Forum comparison archive: link the evidence and the correction”: “Add a dated correction near the original conclusion…” 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.

TimeLog 01019Participant

Case 16 — Lume questions: why does my lume fade so quickly, and how should I compare it?

My watch's lume is bright for a few minutes and then barely visible. Is that normal? People post lume shots of different watches, but they all seem to use different charging and exposure, so I can't tell what's actually better.

Exercise RWF-11911/16: address this question within its stated limits.

TimeLog 01019Participant

Match reference, dimensions and configuration first. List confirmed differences separately from seller descriptions and date the comparison so later readers understand its scope.

TimeLog 01019Participant

Case 39 — Maintenance question: how do I tell if an automatic actually needs service? · source wording exercise

Common advice says service every five years, but service is expensive and some people run watches much longer. What observable signs actually indicate a mechanical watch needs attention, as opposed to just being due on a calendar?

Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Useful signs, in rough order of seriousness: power reserve noticeably shorter…” as the discussion anchor; no new event or result is supplied.

Exercise RWF-09543/39: address this question within its stated limits.

TimeLog 01019Participant

Case 6 — Model comparison: dive bezel action and alignment, how to compare fairly

Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.

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