Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 41 — Forum comparison archive: link the evidence and the correction · source wording exercise

Reader check for “Forum comparison archive: link the evidence and the correction”: distinguish the discussion point “Preserve the reasoning trail instead of silently replacing an…” 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: source wording. Retain the source wording beside any paraphrase.

TimeLog 01149Participant

Case 34 — Magnetism and rate: record evidence before naming a cause

Summary draft for “Magnetism and rate: record evidence before naming a cause”: the answer addresses “Record the change and the circumstances without treating…”; the related point is “A competent watchmaker can test and diagnose it; random adjustment…”. 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.

TimeLog 01149Participant

Case 31 — Shipping timeline: separate dispatch, handover and scan events

Summary draft for “Shipping timeline: separate dispatch, handover and scan events”: the answer addresses “Distinguish label creation from physical acceptance and retain dated…”; the related point is “Ask the sender or carrier for clarification; missing scans alone…”. 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.

TimeLog 01149Participant

Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.

TimeLog 01149Participant

Summary draft for “Date window centring: compare the same date at the same angle”: the answer addresses “Keep the uncropped originals alongside the detail crops and distinguish…”; the related point is “Use the same numeral, camera axis…”. 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.

TimeLog 01149Participant

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

A large crop makes tiny differences look dramatic. How can a checklist remain proportionate?

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

TimeLog 01149Participant

Correction note for “Crown operation: when a forum cannot diagnose the resistance”: retain the wording beginning “Describe whether resistance occurs during winding or setting 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.

TimeLog 01149Participant

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Treat the comparison…” 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: source wording. Retain the source wording beside any paraphrase.

TimeLog 01149Participant

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

TimeLog 01149Participant

Case 22 — Movement identification: the limits of a rotor photograph

Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.

TimeLog 01149Participant

Case 34 — Comparing versions without mixing case sizes

Limit of the answer in “Comparing versions without mixing case sizes”: “Match reference, dimensions 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.

TimeLog 01149Participant

Case 10 — Service enquiry: information a watchmaker can use

Correction note for “Service enquiry: information a watchmaker can use”: retain the wording beginning “Document when it stops, winding behaviour, recent impacts 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.

TimeLog 01149Participant

Case 57 — Shipping timeline: separate dispatch, handover and scan events · source wording exercise

Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Ask the sender or carrier for clarification; missing scans alone…” 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. Retain the source wording beside any paraphrase.

TimeLog 01149Participant

Case 25 — Comparing versions without mixing case sizes

Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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.

TimeLog 01149Participant

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.

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