Skip to content
RepWatchForumSign in

Forum Replies Created

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

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

Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Ask the sender or carrier for clarification; missing scans alone…” 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: source wording. Retain the source wording beside any paraphrase.

Separate three properties: click count (60 or 120 positions), feel (how firm each click is, and whether there's back-play), and alignment (whether the pip lines up with the 12 o'clock marker at rest). Crisp vs mushy is mostly about feel and back-play. Alignment can be measured, so treat it separately.

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

Summary draft for “Case finishing: distinguish a reflection from a surface mark”: the answer addresses “A mark should be assessed across multiple views; aggressive polishing…”; the related point is “Ask for photographs with the light moved and…”. 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.

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

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

The lift angle must match the movement specification for the amplitude reading to be meaningful. If it is unknown, label amplitude as provisional instead of accepting the instrument default.

Method note for “Shipping timeline: separate dispatch, handover and scan events”: use “Distinguish label creation from physical acceptance and retain dated…” 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.

Summary draft for “Crystal reflections: why a dark patch is not a coating test”: the answer addresses “Compare multiple controlled angles and describe the visible observation without asserting…”; the related point is “No single lighting setup settles…”. 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.

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

Clarifying question: does anyone in the thread have access to both versions at once? Without simultaneous comparison, every claim either way is weak evidence. If not, the next best option is photos with a grey card in frame and white balance locked or set manually, which at least makes separate photos roughly comparable.

Measure the lug opening and document bar diameter, shoulder position and strap thickness. Avoid forcing an assembly that does not fit and let a watchmaker check uncertain clearances.

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

Batch variation on coloured dials does happen in general. Plating, lacquer thickness and supplier changes can all shift tone, so the claim isn't implausible. Plausible isn't the same as confirmed, though. The thread should keep 'possible' and 'shown' as separate statuses rather than letting repetition turn a hypothesis into accepted fact.

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.

Case 26 — First QC request: the minimum useful information

State the model configuration, the specific concern and links to clear redacted images. Include complete instrument settings where relevant and say explicitly what evidence is missing.

Case 24 — What a water-resistance claim does and does not establish

A listing describes a water-resistance rating but provides no test record for the individual watch. What evidence would address the gap?

Exercise RWF-19794/24: address this question within its stated limits.

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

A condition record is useful but a shipping label contains personal information. How can the record be shared safely?

Exercise RWF-18849/13: address this question within its stated limits.

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