Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 18 total)
DialNotes 05071Participant

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

Log the rate over several comparable days, identify the correct specification and state the conditions. Stable and changing patterns raise different questions; a watchmaker can assess whether regulation, inspection or no action is appropriate.

DialNotes 05071Participant

Case 136 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear · documentation exercise

Clarification for “Crystal types: sapphire, mineral and acrylic trade-offs for daily wear”: the point beginning “Mineral glass sits in between and is often…” 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: documentation. Distinguish an original record from a proposed record format.

DialNotes 05071Participant

Case 7 — QC photographs: perspective or a genuinely tilted index?

Summary draft for “QC photographs: perspective or a genuinely tilted index?”: the answer addresses “Request a level straight-on image with the hands…”; the related point is “Compare two independently aligned images before drawing a conclusion; an overlay…”. 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.

DialNotes 05071Participant

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.

DialNotes 05071Participant

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

DialNotes 05071Participant

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

DialNotes 05071Participant

The calendar interval is a conservative default, not a rule. Useful signs, in rough order of seriousness: power reserve noticeably shorter than spec from full wind, rate drifting outside its usual range, the watch stopping on the wrist, gritty or rough winding, and the date changing slowly or late.

DialNotes 05071Participant

Case 30 — Lug-to-lug and end-link overhang in wrist photographs

Summary draft for “Lug-to-lug and end-link overhang in wrist photographs”: the answer addresses “Record lug-to-lug and the effective span…”; the related point is “Use a similar camera distance and neutral wrist position; photographs support…”. 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.

DialNotes 05071Participant

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.

DialNotes 05071Participant

Case 43 — Lug-to-lug and end-link overhang in wrist photographs · source wording exercise

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Use a similar camera distance and neutral wrist position; photographs support…” 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.

DialNotes 05071Participant

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

Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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.

DialNotes 05071Participant

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

Limit of the answer in “Crown operation: when a forum cannot diagnose the resistance”: “Describe whether resistance occurs during winding or setting 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.

DialNotes 05071Participant

Clarification for “Comparing versions without mixing case sizes”: the point beginning “Match reference, dimensions 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.

DialNotes 05071Participant

Micro-adjust spacing varies by clasp. Measure the actual change at each setting rather than assuming a standard number of millimetres; compare the usable range with the link length.

DialNotes 05071Participant

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.

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