Keep the date, work performed, provider invoice reference and test results where available. Redact addresses and payment information; do not invent service events to fill an empty history.
Forum Replies Created
Clarification for “A maintenance log that remains useful after a sale”: the point beginning “Keep the date, work performed, provider invoice reference…” 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 7 — 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.
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.
On alignment, a clarifying point: is the misalignment visible straight on, or only from an angle? Parallax on a raised bezel can make a perfectly aligned pip look half a click off when viewed slightly from the side. Photograph straight above the dial before calling it misaligned.
Case 18 — Reading a timegrapher recording without losing the context
Correction note for “Reading a timegrapher recording without losing the context”: retain the wording beginning “Keep the complete recording and ask for the…” 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.
Case 6 — Comparing versions without mixing case sizes
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 19 — Reading a timegrapher recording without losing the context
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.
Wrist size changes during the day and with temperature, sometimes by several millimetres. A fit that feels tight in the afternoon may be right in the morning. Before buying parts, check the fit at different times. You may find the 'too tight' setting is only a problem a few hours a day.
Case 32 — 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.
Case 30 — 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.
Case 19 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
Amplitude depends on the movement and measurement setup. Compare it with appropriate specifications and a qualified watchmaker’s assessment; a universal pass/fail threshold would be misleading.
Case 9 — Lume comparison: keep exposure and charging conditions consistent
Summary draft for “Lume comparison: keep exposure and charging conditions consistent”: the answer addresses “Treat the comparison…”; the related point is “Repeat with equal light source, charging duration, elapsed time and camera…”. 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 51 — Comparing dial colour under different lighting · source wording exercise
Limit of the answer in “Comparing dial colour under different lighting”: “Compare controlled images where available and avoid calling a…” 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: source wording. Retain the source wording beside any paraphrase.
Case 10 — Comparing dial colour under different lighting
One image was taken beside a window and the other under a warm lamp. How should a colour comparison be qualified?
Exercise RWF-15100/10: address this question within its stated limits.