Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 27 total)

Case 28 — Lume questions: why does my lume fade so quickly, and how should I compare it?

A bright initial glow followed by a steep drop is normal for photoluminescent pigments. Afterglow fades fastest in the first minutes and then settles to a dim, long-lasting level that dark-adapted eyes can still read. The real question is whether it's readable after an hour in darkness, not how it looks right after charging.

Case 25 — Maintenance question: how do I tell if an automatic actually needs service?

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.

Suggested protocol. 1) Both dials in one frame. 2) Diffuse daylight, no direct sun, plus a second shot under neutral indoor light. 3) Grey card visible. 4) No filters, no editing. 5) State camera settings if known. If both shots show the same direction of difference, the claim is supported. If the difference flips between lighting conditions, it's most likely lighting.

Case 51 — Comparing versions without mixing case sizes · source wording exercise

Correction note for “Comparing versions without mixing case sizes”: retain the wording beginning “List confirmed differences separately from seller descriptions and date 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. Retain the source wording beside any paraphrase.

Case 18 — Crystal reflections: why a dark patch is not a coating test

Summary draft for “Crystal reflections: why a dark patch is not a coating test”: the answer addresses “No single lighting setup settles…”; the related point is “Compare multiple controlled angles and describe the visible observation without asserting…”. 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.

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

Distinguish label creation from physical acceptance and retain dated event text with personal details removed. Ask the sender or carrier for clarification; missing scans alone do not establish loss or seizure.

First identify the caliber, lift-angle setting, winding state and measurement position. Without those fields, the rate, amplitude and beat-error values lack enough context for a useful comparison.

Case 107 — Service enquiry: information a watchmaker can use · comparison exercise

Summary draft for “Service enquiry: information a watchmaker can use”: the answer addresses “Document when it stops, winding behaviour, recent impacts and…”; the related point is “Be honest about the watch and request an assessment…”. Keep both connected to the opening question, and mark any conclusion needing further records as unresolved. Review focus: comparison. Make the basis of a comparison explicit before interpreting it.

Case 30 — 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.

Clarification for “Bracelet fit: measuring the usable clasp adjustment”: the point beginning “Record wrist circumference, removable links and the clasp…” 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 — Strap compatibility: width is only the first measurement

Two straps share the same nominal width but differ in thickness and spring-bar clearance. Which dimensions need checking?

Exercise RWF-20722/36: address this question within its stated limits.

Case 22 — 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.

Case 3 — 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 2 — 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.

Viewing 15 posts - 1 through 15 (of 27 total)