Fork Preload Handover: Preserve the Reference State

A fork service sheet that reports “preload” can be complete numerically and incomplete in meaning. Before comparing it with the approved service requirement, ask whether the provider recorded relaxed preload or actual preload for the identified fork construction. Equal digits under different definitions do not establish an equal result.

This handover starts with an already authorized fork job. It concerns the interpretation of the returned record, not spring selection, spacer design or a procedure for measuring or adjusting the fork.

Why the top-out construction changes the question

Race Tech distinguishes relaxed and actual preload for forks with long, soft top-out springs. Its explanation says the installed-length relationship changes when the main spring is installed. That makes the reference state part of the quantity's meaning, rather than an optional note beside a number. The page also discusses conventional stiff top-out arrangements separately. Race Tech preload definitions

This bounded example was checked on 14 October 2026. It does not establish the construction of a buyer's fork. Obtain that identification from the qualified service provider and its applicable records; do not ask receiving staff to open the fork or perform a pull test to classify it.

Keep the requirement and returned definition together

Retain the exact fork/build reference, the source of the approved requirement and the service event. Ask the author of the returned sheet to expand an abbreviated “preload” heading. The useful answer names the definition, its reference state, units and the existing method record that supports the entry.

Preserve the original wording even if the handover system uses a shorter column name. A transcription field can say “provider reports actual preload”; it should not erase “relaxed” from a source because both entries happen to fit one database field. Store a link to the attributable original beside the transcription.

If the requirement and report use different definitions, request the provider's reconciliation. Purchasing should not subtract an assumed allowance, borrow a conversion from another fork or rename the result to make it match. A technically valid comparison needs the actual build and a provider-supported relationship.

Tell a terminology correction from new work

A corrected report may explain what was already recorded, or it may describe later work. Ask which happened. A changed heading with an unchanged event reference is a documentary correction only if the author confirms that scope. It is not evidence that the fork was subsequently adjusted.

Conversely, a new service event should not overwrite the earlier state. Keep both event references and the provider's explanation of which record now answers the agreed handover. That history matters when a recipient compares an old setup sheet with the returned fork months later.

Reference-state reconciliation worksheet

This is an editorial document-review worksheet. It supplies no target, equation, dimension, tool method or physical instruction.

Fictional case: the same number, two headings

Imagine a fictional service requirement naming relaxed preload and a returned sheet naming only preload. A later email calls the entry actual preload but says the digits have not changed. The buyer cannot resolve that discrepancy by counting matching characters.

Ask whether the email corrects a label, explains a distinct recorded quantity or reports a changed fork state. If the provider supplies an attributable explanation tied to the original method, send it with both entries to the qualified reviewer. If it cannot reconstruct the reference state, preserve “definition unresolved” rather than inventing a failed measurement or a passing comparison.

Closing this question means the recipient can understand the reported quantity and its relationship to the agreed requirement. It does not confirm spring suitability, suspension behavior or permission to ride. A bushing-and-seal parts list also cannot supply this missing definition: contents and reference-state evidence answer different purchasing questions.

Send a focused purchasing enquiry

See Motorcycle parts for category context. A Motoparts sourcing request can identify the actual product and the specific missing provider answer. Motoparts offers independent aftermarket and unbranded buying coordination and supplier negotiation. Manufacturer examples here imply no affiliation, branded-goods offer, specialist-service capability, fit guarantee or engineering approval.

The initial form accepts a supported marketplace HTTPS link, an 8–1200-character description or screenshots. Images are limited to five PNG, JPEG, WebP or GIF files, 10 MiB each and 20 MiB combined. PDF, CAD, ZIP and other technical files need a separately agreed authorized exchange; the image field is not a technical-file portal.