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.
Forum Replies Created
Case 28 — Comparing dial colour under different lighting
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 33 — Magnetism and rate: record evidence before naming a cause
Method note for “Magnetism and rate: record evidence before naming a cause”: use “Record the change and the circumstances without treating…” 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 74 — Lume comparison: keep exposure and charging conditions consistent · comparison exercise
Correction note for “Lume comparison: keep exposure and charging conditions consistent”: retain the wording beginning “Treat 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. Make the basis of a comparison explicit before interpreting it.
Clarification for “Crystal reflections: why a dark patch is not a coating test”: the point beginning “No single lighting setup settles…” 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.
Compare the observed rate with the exact caliber and cased-watch specification, if available. An example such as -8 seconds per day cannot be declared acceptable solely from its price category.
Case 5 — First QC request: the minimum useful information
Summary draft for “First QC request: the minimum useful information”: the answer addresses “State the model configuration, the specific concern and…”; the related point is “Include complete instrument settings where relevant and say…”. 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 — Shipping timeline: separate dispatch, handover and scan events
Correction note for “Shipping timeline: separate dispatch, handover and scan events”: retain the wording beginning “Distinguish label creation from physical acceptance and retain dated…” 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.
Use the same numeral, camera axis and approximate image scale. Keep the uncropped originals alongside the detail crops and distinguish optical balance from physical window alignment.
Method note for “First QC request: the minimum useful information”: use “State the model configuration, the specific concern 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.
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 32 — Lume comparison: keep exposure and charging conditions consistent
Correction note for “Lume comparison: keep exposure and charging conditions consistent”: retain the wording beginning “Treat 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. Keep the stated question separate from any broader claim.
Reader check for “Lume questions: why does my lume fade so quickly, and how should I compare it?”: distinguish the discussion point “A bright initial glow followed by a steep drop…” 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.
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.
Case 36 — Accuracy expectations: is -8 s/d acceptable on an entry-level automatic?
Start with how you measured it. Comparing against a phone clock once a day for a week, at the same time, and noting the offset is reliable enough. One 24-hour reading isn't, because rate depends on wrist time, position overnight and state of wind. Average across several days before deciding anything.