Ask for a straight-on dial photo with diffuse light and no flash, the full dial in frame, and the hands placed away from the indices (10:10 isn't ideal, because it covers the upper markers). Flash flattens printing and hides lume condition. Diffuse light shows print edges, alignment and any spotting.
Forum Replies Created
Method note for “Comparing versions without mixing case sizes”: use “Match reference, dimensions 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 15 — 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.
Case 47 — Disputed observation: is this dial colour shift real or just lighting? · source wording exercise
Several posts claim the newer batch of a particular blue-dial model looks more purple than the earlier batch. Others say it's purely photography and white balance. Can we settle this with evidence instead of arguing from different photos?
Review focus: source wording. Retain the source wording beside any paraphrase. Use the original answer fragment “Two photos of the same dial under different light can…” as the discussion anchor; no new event or result is supplied.
Exercise RWF-26818/47: address this question within its stated limits.
Case 25 — Shipping timeline: separate dispatch, handover and scan events
Clarification for “Shipping timeline: separate dispatch, handover and scan events”: the point beginning “Distinguish label creation from physical acceptance and retain 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 10 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
I ran a watch on a basic timegrapher and got +6 s/d, 245 degrees amplitude and 0.8 ms beat error, dial up, about an hour after winding. Is this good, bad or normal? I don't want to send it for service on a single reading.
Exercise RWF-24258/10: address this question within its stated limits.
Case 29 — QC checklist: prioritise observable faults over pixel hunting
Summary draft for “QC checklist: prioritise observable faults over pixel hunting”: the answer addresses “Start with function, legibility, assembly and…”; the related point is “Explain what the full-size image shows, what the crop adds 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.
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.
Case 1 — Shipping timeline: separate dispatch, handover and scan events
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.
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 29 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
Caliber is the movement's model designation, like a part number. Two watches from different brands can share the same caliber family with different finishing or regulation. On a spec sheet it tells you what's inside and roughly what service parts are available. It doesn't tell you how well that particular example was adjusted.
Case 11 — Bracelet fit: half-links, micro-adjust holes and the 'between sizes' problem
Check whether a compatible half-link exists for the exact bracelet reference. Compatibility involves the connection and hardware, not just width. Ask a watchmaker if the correct part is uncertain.
Clarification for “Lug-to-lug and end-link overhang in wrist photographs”: the point beginning “Record lug-to-lug and the effective span…” 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 35 — Crown operation: when a forum cannot diagnose the resistance
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 13 — Lug-to-lug and end-link overhang in wrist photographs
A wide-angle wrist photo exaggerates the nearest edge of the case. How can two watches be compared fairly?
Exercise RWF-09584/13: address this question within its stated limits.