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.
Forum Replies Created
Case 13 — A maintenance log that remains useful after a sale
Summary draft for “A maintenance log that remains useful after a sale”: the answer addresses “Keep the date, work performed, provider invoice reference…”; the related point is “Redact addresses and payment information; do not invent service…”. 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.
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 31 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
Case 17 — Comparing versions without mixing case sizes
Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “Match reference, dimensions and…” 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 21 — Model comparison: dive bezel action and alignment, how to compare fairly
Summary table proposal: click count, back-play (none, slight, noticeable), click consistency around the rotation, and alignment (straight-on photo, offset in fractions of a click). With that, the thread can compare actual properties instead of trading adjectives. Dated corrections welcome below.
Case 32 — Crystal reflections: why a dark patch is not a coating test
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.
Ask a qualified watchmaker about a suitable test for that individual case and record the test date and method. A photograph or a caseback engraving is not proof of water resistance.
Case 8 — Beginner glossary Q&A: complication, caliber, jewel count, power reserve
One more term that will come up is 'hacking', meaning the seconds hand stops when you pull the crown so you can set the time to the second. It's minor, but beginners often assume every automatic has it, and not all do. That rounds out the glossary: caliber means what, complication means extra functions, jewels mean bearings, power reserve means how long it runs, hacking means precise setting.
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 “Comparison thread: 38mm vs 40mm versions of the same field watch, with a dated correction log”: use “Add lug-to-lug, thickness and lug width…” 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.
Record wrist circumference, removable links and the clasp adjustment range in millimetres. Request the closed bracelet circumference rather than inferring it from marketing dimensions.
If the manufacturer provides a suitable procedure, a running-time log can support a service enquiry. State the winding method and stop time. A shortened run does not identify the cause by itself.
Case 22 — Timegrapher reading context: what do rate, amplitude and beat error actually tell me?
A useful table has columns for date, position, winding state, lift angle, rate, amplitude and beat error. Keep the full recording so settings and stability can be checked.
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.