Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 19 total)
QCReader 07624Participant

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

Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “List confirmed differences separately from seller descriptions and date the comparison…” 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. Retain the source wording beside any paraphrase.

QCReader 07624Participant

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.

QCReader 07624Participant

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.

QCReader 07624Participant

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

The difficulty is that phone cameras adjust white balance automatically, and blue dials are especially sensitive. Two photos of the same dial under different light can easily look like a 'batch difference'. Any comparison needs both dials in the same frame, under the same light, ideally next to a neutral grey or white reference card.

QCReader 07624Participant

Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “A single number cannot establish service condition, movement identity…”; the related point is “Keep the complete recording and ask for the…”. 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.

QCReader 07624Participant

Summary draft for “Reading a timegrapher recording without losing the context”: the answer addresses “Keep the complete recording and ask for the…”; the related point is “A single number cannot establish service condition, movement identity…”. 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.

QCReader 07624Participant

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

Limit of the answer in “A maintenance log that remains useful after a sale”: “Keep the date, work performed, provider invoice reference…” 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.

QCReader 07624Participant

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

QCReader 07624Participant

Case 5 — Comparing versions without mixing case sizes

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

QCReader 07624Participant

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

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” 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.

QCReader 07624Participant

Limit of the answer in “Shipping timeline: separate dispatch, handover and scan events”: “Distinguish label creation from physical acceptance and retain dated…” 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.

QCReader 07624Participant

Case 30 — Movement identification: the limits of a rotor photograph

Correction note for “Movement identification: the limits of a rotor photograph”: retain the wording beginning “Describe visible bridge shapes and markings separately…” 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.

QCReader 07624Participant

Clarification for “Date window centring: compare the same date at the same angle”: the point beginning “Use the same numeral, camera axis…” 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.

QCReader 07624Participant

Case 23 — Comparing versions without mixing case sizes

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

QCReader 07624Participant

Case 19 — Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log

I'm putting together a side-by-side of the 38mm and 40mm versions of a common three-hand field watch design. The aim is a reference post we can fix over time instead of repeating the same arguments. Corrections go in a dated log at the bottom. What should the table include besides case diameter, and which specs are usually misreported?

Exercise RWF-09235/19: address this question within its stated limits.

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