Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
TimeLog 00509Participant

Case 45 — QC checklist: prioritise observable faults over pixel hunting · source wording exercise

Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Explain what the full-size image shows, what the crop adds and…”; the related point is “Start with function, legibility, assembly and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: source wording. Retain the source wording beside any paraphrase.

TimeLog 00509Participant

Case 119 — Comparing dial colour under different lighting · documentation exercise

Summary draft for “Comparing dial colour under different lighting”: the answer addresses “Compare controlled images where available and avoid calling a…”; the related point is “State the lighting and…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: documentation. Distinguish an original record from a proposed record format.

TimeLog 00509Participant

Case 22 — Clasp photographs: what to request before judging alignment

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.

TimeLog 00509Participant

Case 17 — Clasp photographs: what to request before judging alignment

Clarification for “Clasp photographs: what to request before judging alignment”: the point beginning “Request open and closed views from both sides,…” 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 00509Participant

Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.

TimeLog 00509Participant

Case 30 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?

Can the same settings and winding state be used for several positions? Record each position separately rather than combining measurements taken under different conditions.

TimeLog 00509Participant

Case 35 — Lume comparison: keep exposure and charging conditions consistent

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: scope. Keep the stated question separate from any broader claim.

TimeLog 00509Participant

Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.

TimeLog 00509Participant

Case 27 — Bracelet fit: measuring the usable clasp adjustment

Method note for “Bracelet fit: measuring the usable clasp adjustment”: use “Record wrist circumference, removable links and the clasp…” 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 00509Participant

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 00509Participant

Case 23 — Reading a timegrapher recording without losing the context

Method note for “Reading a timegrapher recording without losing the context”: use “Keep the complete recording and ask for the…” 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 00509Participant

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

Method note for “Crystal reflections: why a dark patch is not a coating test”: use “No single lighting setup settles…” 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 00509Participant

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

Clarification for “Magnetism and rate: record evidence before naming a cause”: the point beginning “Record the change and the circumstances without treating…” 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 00509Participant

Clarification for “What a water-resistance claim does and does not establish”: the point beginning “Ask a qualified watchmaker about a suitable test for that individual…” 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 00509Participant

Case 1 — Comparing dial colour under different lighting

Limit of the answer in “Comparing dial colour under different lighting”: “State the lighting 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.

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