Skip to content
RepWatchForumSign in

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 22 total)
TimeLog 06259Participant

Case 23 — Clasp photographs: what to request before judging alignment

Method note for “Clasp photographs: what to request before judging alignment”: use “Request open and closed views from both sides,…” 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.

TimeLog 06259Participant

Case 37 — QC photography: what photos actually help verify a pre-owned listing? · source wording exercise

Correction note for “QC photography: what photos actually help verify a pre-owned listing?”: retain the wording beginning “Flash flattens printing and hides…” 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.

TimeLog 06259Participant

Case 113 — Lume comparison: keep exposure and charging conditions consistent · documentation exercise

Clarification for “Lume comparison: keep exposure and charging conditions consistent”: the point beginning “Repeat with equal light source, charging duration, elapsed time and camera…” 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: documentation. Distinguish an original record from a proposed record format.

TimeLog 06259Participant

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

TimeLog 06259Participant

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

TimeLog 06259Participant

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

TimeLog 06259Participant

Case 30 — Lug-to-lug and end-link overhang in wrist photographs

Method note for “Lug-to-lug and end-link overhang in wrist photographs”: use “Record lug-to-lug and the effective span…” 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.

TimeLog 06259Participant

Case 31 — Clasp photographs: what to request before judging alignment

Correction note for “Clasp photographs: what to request before judging alignment”: retain the wording beginning “Request open and closed views from both sides,…” 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.

TimeLog 06259Participant

Clarification for “Case finishing: distinguish a reflection from a surface mark”: the point beginning “Ask for photographs with the light moved 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.

TimeLog 06259Participant

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

TimeLog 06259Participant

Case 8 — What a water-resistance claim does and does not establish

Limit of the answer in “What a water-resistance claim does and does not establish”: “Ask a qualified watchmaker about a suitable test for that individual…” 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: scope. Keep the stated question separate from any broader claim.

TimeLog 06259Participant

Case 16 — Crystal types: sapphire, mineral and acrylic trade-offs for daily wear

Domed crystals of any material add distortion at the edges, which some people like and others find hard to read at angles. Box-shaped or high-domed crystals also add thickness. If you're comparing two otherwise similar watches, check total thickness against crystal profile before assuming the case itself is thicker.

TimeLog 06259Participant

Describe visible bridge shapes and markings separately from the proposed identification. Ask a qualified watchmaker to inspect it if identification matters for servicing; do not open the case merely for a forum answer.

TimeLog 06259Participant

Domed crystals of any material add distortion at the edges, which some people like and others find hard to read at angles. Box-shaped or high-domed crystals also add thickness. If you're comparing two otherwise similar watches, check total thickness against crystal profile before assuming the case itself is thicker.

TimeLog 06259Participant

Case 9 — Shipping timeline: separate dispatch, handover and scan events

A tracking page has no new event after a label was created. How can the timeline be discussed without inventing a carrier explanation?

Exercise RWF-10059/9: address this question within its stated limits.

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