Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 21 total)
TimeLog 07629Participant

Start with function, legibility, assembly and clear visible damage. Explain what the full-size image shows, what the crop adds and what remains uncertain; do not turn an overlay into an automatic verdict.

TimeLog 07629Participant

Case 49 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log · source wording exercise

Clarification for “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: the point beginning “Diameter alone tells you little…” 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 07629Participant

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

Summary order of importance. 1) Lug width, measured between the lugs. 2) Lug-end thickness against clearance. 3) Spring bar diameter. 4) Taper and buckle width. 5) Length, which is usually given as long side / short side in mm and should be compared with a strap that already fits you.

TimeLog 07629Participant

Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.

TimeLog 07629Participant

Case 49 — QC checklist: prioritise observable faults over pixel hunting · source wording 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. Retain the source wording beside any paraphrase.

TimeLog 07629Participant

Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.

TimeLog 07629Participant

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

Status for now: unresolved. The claim is plausible, but no controlled comparison has been posted. Until one appears, describe it as 'reported, not verified'. When someone posts a same-frame, grey-card comparison under two lighting conditions, the thread can update the status with a date and a link to that post.

TimeLog 07629Participant

Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.

TimeLog 07629Participant

Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “A single number cannot establish service condition, movement identity…” 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 07629Participant

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

Clarification for “Packing photographs: document condition without exposing an address”: the point beginning “Photograph the item and protective packing…” 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 07629Participant

Reader check for “First QC request: the minimum useful information”: distinguish the discussion point “State the model configuration, the specific concern and…” 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.

TimeLog 07629Participant

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

TimeLog 07629Participant

Case 16 — Strap compatibility: width is only the first measurement

Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.

TimeLog 07629Participant

Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Ask the sender or carrier for clarification; missing scans alone…” 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 07629Participant

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

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