Reader check for “Date window centring: compare the same date at the same angle”: distinguish the discussion point “Use the same numeral, camera axis…” 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: scope. Keep the stated question separate from any broader claim.
Forum Replies Created
Describe whether resistance occurs during winding or setting and whether the crown engages consistently. Stop forcing it and arrange inspection rather than trying an unverified repair from a thread.
Case 64 — Model comparison: dive bezel action and alignment, how to compare fairly · source wording exercise
Method note for “Model comparison: dive bezel action and alignment, how to compare fairly”: use “Crisp vs mushy is mostly about…” 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.
Clarification for “Comparing dial colour under different lighting”: the point beginning “State the lighting 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.
Case 248 — Date window centring: compare the same date at the same angle · indexing exercise
Limit of the answer in “Date window centring: compare the same date at the same angle”: “Use the same numeral, camera axis…” 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: indexing. Make the reasoning findable without reducing it to a trust score.
Case 34 — Date window centring: compare the same date at the same angle
Correction note for “Date window centring: compare the same date at the same angle”: retain the wording beginning “Use the same numeral, camera axis…” 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.
Before the table goes live, a question: are you comparing current production only, or older references too? Dial printing, lume colour and crown signing often changed between batches. If older pieces are in scope, add a production-period column, or every disagreement will look like an error when it's really a running change.
Case 20 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
For a two-watch comparison, the practical order is usually case dimensions first, then power reserve if you rotate, then caliber for serviceability. Jewel count comes last. Complications only matter if you'll use them. Can you say what the two candidates are, in generic terms like 'dive style vs dress style'? The priorities shift a lot between those.
Request open and closed views from both sides, with the watch supported safely. Separate cosmetic alignment from whether the clasp engages reliably; functional concerns need hands-on inspection.
Case 12 — QC photographs: perspective or a genuinely tilted index?
Limit of the answer in “QC photographs: perspective or a genuinely tilted index?”: “Request a level straight-on image with the hands…” 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.
Reader check for “Seller review template: facts, dates and unresolved questions”: distinguish the discussion point “Use fields for order date, promised terms, dated…” 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: scope. Keep the stated question separate from any broader claim.
Case 51 — Magnetism and rate: record evidence before naming a cause · source wording exercise
A sudden rate change is being attributed to magnetism without a measurement. How should the discussion be structured?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “A competent watchmaker can test and diagnose it; random adjustment…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-17297/51: address this question within its stated limits.
Clarification for “Service enquiry: information a watchmaker can use”: the point beginning “Document when it stops, winding behaviour, recent impacts 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.
Case 22 — QC checklist: prioritise observable faults over pixel hunting
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.
Case 12 — Crown operation: when a forum cannot diagnose the resistance
A description of stiffness does not establish the cause. What information is safe and useful to collect before an inspection?
Exercise RWF-13731/12: address this question within its stated limits.