Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 24 total)
ClaspCheck 02966Participant

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.

ClaspCheck 02966Participant

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

Method note for “Strap compatibility: width is only the first measurement”: use “Measure the lug opening and document bar diameter,…” 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.

ClaspCheck 02966Participant

Case 39 — Movement identification: the limits of a rotor photograph · source wording exercise

Reader check for “Movement identification: the limits of a rotor photograph”: distinguish the discussion point “Ask a qualified watchmaker to inspect it if identification matters for…” 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.

ClaspCheck 02966Participant

Use fields for order date, promised terms, dated communications, delivery evidence and resolution. Leave unsupported fields blank and separate observations from opinions; this reference is not a seller endorsement.

ClaspCheck 02966Participant

Case 33 — Service enquiry: information a watchmaker can use

A service question only says that the watch stops occasionally. Which observations make an initial enquiry more useful?

Exercise RWF-27959/33: address this question within its stated limits.

ClaspCheck 02966Participant

Case 6 — A maintenance log that remains useful after a sale

Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Keep the date, work performed, provider invoice reference…”; the related point is “Redact addresses and payment information; do not invent service…”. 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.

ClaspCheck 02966Participant

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.

ClaspCheck 02966Participant

Clarifying question: how are you charging it? A few seconds under a warm indoor bulb gives a much weaker charge than daylight or a UV source. Many 'weak lume' reports turn out to be undercharging. Try a consistent charge, such as 30 seconds under a phone flashlight at a fixed distance, before judging.

ClaspCheck 02966Participant

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

Limit of the answer in “Crystal reflections: why a dark patch is not a coating test”: “No single lighting setup settles…” 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.

ClaspCheck 02966Participant

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.

ClaspCheck 02966Participant

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. Retain the source wording beside any paraphrase.

ClaspCheck 02966Participant

Correction note for “First QC request: the minimum useful information”: retain the wording beginning “State the model configuration, the specific concern 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.

ClaspCheck 02966Participant

Case 44 — QC photographs: perspective or a genuinely tilted index? · source wording exercise

A marker can look tilted when the camera is above the dial axis. What extra image would separate perspective from an assembly issue?

Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Compare two independently aligned images before drawing a conclusion; an overlay…” as the discussion anchor; no new event or result is supplied.

Exercise RWF-16998/44: address this question within its stated limits.

ClaspCheck 02966Participant

Method note for “QC checklist: prioritise observable faults over pixel hunting”: use “Start with function, legibility, assembly 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.

ClaspCheck 02966Participant

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

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