Skip to content
RepWatchForumSign in

Forum Replies Created

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

Case 43 — Comparing versions without mixing case sizes · source wording exercise

Summary draft for “Comparing versions without mixing case sizes”: the answer addresses “List confirmed differences separately from seller descriptions and date the comparison…”; the related point is “Match reference, dimensions 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 08369Participant

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

Photograph the item and protective packing separately from the label. Remove names, addresses, barcodes and tracking tokens from public images while keeping originals privately.

TimeLog 08369Participant

Case 4 — Reading a timegrapher recording without losing the context

Keep the complete recording and ask for the settings, winding state and position. A single number cannot establish service condition, movement identity or performance on a wrist.

TimeLog 08369Participant

Case 2 — Bracelet fit: measuring the usable clasp adjustment

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

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

Summary draft for “Comparing dial colour under different lighting”: the answer addresses “State the lighting and…”; the related point is “Compare controlled images where available and avoid calling a…”. 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 08369Participant

Case 31 — First QC request: the minimum useful information

Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern 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 08369Participant

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

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

Case 4 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?

Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.

TimeLog 08369Participant

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

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

Method note for “Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem”: use “First, a clarifying question: how many links are on each…” 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 08369Participant

Case 15 — Crown operation: when a forum cannot diagnose the resistance

Method note for “Crown operation: when a forum cannot diagnose the resistance”: use “Describe whether resistance occurs during winding or setting 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 08369Participant

Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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 08369Participant

Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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 08369Participant

Case 24 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve

Jewel count describes bearings used in a movement design; it is not a quality ranking. Compare the documented movement architecture and service support rather than assuming a higher count makes one watch better.

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