What should be recorded before the sample review?
Start with a clear sample reference. Without it, a buyer can approve one configuration while the factory prepares another for quantity production.
- Model code and specification revision.
- Drive and resistance description.
- Console, pedals, saddle and other agreed configuration details.
- Branding, color and label references.
- Sample purpose and the acceptance criteria to be reviewed.
For a K29100 sample, check the published belt-drive configuration against the actual quoted scope. If a different console or component is proposed, identify the change in the sample record.
Which checkpoints belong in a practical sample checklist?
| Area | What to review | Evidence to retain |
|---|---|---|
| Appearance | Visible finish, obvious damage and agreed branding | Overview and detail photographs |
| Assembly | Specified components, fitted guards and visible assembly condition | Configuration list and identified observations |
| Adjustment | Saddle movement, locking and adjustment points | Position photographs or short demonstration |
| Operation | Pedal and handle movement, fan operation and unusual rubbing or vibration | Review conditions and operating video |
| Console | Included functions, controls and agreed accessories | Display photographs and function notes |
| Packing | Protection, contents and agreed labeling when included in scope | Packing photographs and component list |
This is a proposed review framework, not a statement that a particular unit has passed these checks. The buyer and supplier should agree applicable criteria and the review method before inspection.
How should operating observations be recorded?
Describe what was observed and under which conditions. Note the sample configuration, review duration and the activities performed so a later reviewer can interpret the result.
Separate fan airflow from unusual mechanical sounds. Where rubbing, vibration or intermittent movement occurs, identify the location and operating condition rather than recording only “noise.” If a measurement is required, agree the method, instruments and limit before treating the result as acceptance evidence.
Do not infer console accuracy, endurance or a noise rating from a short operating video. Those questions need their own appropriate evaluation.
What can a sample approval establish—and what remains open?
A sample approval can document an agreed product reference and the points actually reviewed. It does not establish that every production unit will match, or that untested performance claims are proven.
Keep approvals specific: configuration, appearance, functions reviewed and accepted revisions. List unresolved items separately and decide whether they require correction, further evidence or another sample before release.
Review the WCAGO quality-control process for order-specific checkpoints and records. Its production photographs illustrate activities; they should not be interpreted as a completed report for your order.
How should changes and corrections be closed?
Use one issue list linking each observation to the agreed correction and follow-up evidence. Record who approves the revised reference and which revision quantity production must follow.
If a major component or structure changes after approval, determine whether the original review is still applicable. Do not close an issue only because a new photograph looks similar. Keep the reason for the change and its effect on the approved specification visible.
What should happen before placing the production order?
Transfer the accepted configuration and sample references into the purchase requirement. Agree the production inspection scope, OEM details, packing and handling of deviations before manufacturing starts.
Send WCAGO your model and inspection requirements. If transmission is still undecided, review the belt vs chain drive comparison; if branding is planned, use the private-label air bike approval checklist.