All nine current Chinese source sheets record left-hand drive. An RHD project must reconfirm headlamp beam pattern, wipers, instruments, airbags, pedals, wiring, manuals, and parts catalogues. A left-hand-drive model page cannot represent the delivered variant when complete RHD documentation is unavailable.
Start by confirming the vehicle and usage scenario
For export-variant checks in a Kenyan RHD project, use vehicle/VIN → steering position → regulated components → parts and repair → pre-shipment verification. Each node in the RHD completeness checklist retains the source, version, effective date, scope, and approver. An upstream change reopens the affected branch alone; family names or old approvals cannot be inherited automatically.
LHD and RHD Versions of the Same Model Require More Than a Steering-Wheel Check
| Item | LHD version | RHD export version | Blocking condition |
|---|---|---|---|
| Steering/pedals/wipers | Part number | Part number | Only exterior photos available |
| Headlamp beam pattern | Approval/part number | Approval/part number | Beam pattern does not match driving side |
| Instruments and units | Software/language/units | Software/language/units | Delivery settings cannot be confirmed |
| PVoC documents | Variant and VIN range | Variant and VIN range | VIN outside scope |
The difference matrix must come from actual variant records; the example columns only define the check scope. Stop shipment if any critical safety component or approval document cannot be linked to the VIN.
What does public information cover?
- The Kenya KRA motor-vehicle import procedure supports checks of import procedures and document channels. It does not replace a specific valuation or compliance conclusion.
- For technical or regulatory background, see the Kenya KEBS pre-export verification of conformity, which confirms the PVoC and pre-shipment verification route. The certificate must still correspond to the actual model and variant.
What to do about incomplete data
- Continue: Configuration code, physical-vehicle photos, lamps, glass, and safety labels refer to the same object, and RHD parts and repair materials are available.
- Request documents: Steering position is confirmed, but regulated components or pre-shipment verification is supported only verbally. Log both the owner and the deadline event.
- Suspend: If the supplier can provide only LHD parameters or images and cannot provide RHD variant documents and vehicle identity, stop the affected payment, shipment, delivery, or customer commitment.
- Resume: After the certificate and vehicle identity directly close the pre-shipment verification gap, record the version, time, and scope of resumption. Reopen other nodes only when affected.
Fields needed for final confirmation
| Decision item · Why Checking an Export Variant for a Kenya | Direct material | Closure condition |
|---|---|---|
| Steering position | Configuration code and physical-vehicle photos | RHD is explicit |
| Regulated components | Lamps, glass, and safety labels | Corresponding documents available |
| Parts and repair | Catalogue, manual, and diagnostic materials | RHD version available |
| Pre-shipment verification | Certificate and vehicle identity | Vehicle-by-vehicle match |
A method for translating usage scenarios into comparison criteria
Regarding Kenya's "Why can't you just change the steering wheel position when checking export models for Kenya's right-hand drive project", before comparing models or arranging the first batch of quantities, write the customer scenario as input: daily mileage, load or occupants, road ratio, charging or replenishment conditions, shifts, parking locations and acceptable downtime. Inputs should come from customers, field records, or clearly labeled working assumptions. Without these conditions, the parameter table can only be used for screening and cannot directly deduce the "most suitable" or "lowest cost". This paragraph is about Kenya's "Why can't we just change the steering wheel position when checking export models for Kenya's right-hand drive project?" The corresponding original records should still be returned to during subsequent reviews.
Each candidate corresponds to at least one verifiable reason for elimination or retention. Write the evidence fields, verification methods, responsible persons and cut-off points in the same table, and distinguish between "known facts", "hypotheses to be tested" and "decision suggestions". If the first batch of quantities or vehicle model combinations require trial operation, the observation period, passing conditions and adjustment actions after failure should be specified in advance; Before the trial run starts, the evaluation criteria should already be fixed. This paragraph is about Kenya's "Why can't we just change the steering wheel position when checking export models for Kenya's right-hand drive project?" The corresponding original records should still be returned to during subsequent reviews.
Use the following record structure to keep the review fields, evidence sources, and release conditions traceable:
| Verification field | Recording requirement |
|---|---|
| Usage scenarios and assumptions | Record the current value, direct source, and applicable scope |
| Candidate models/solutions | Record the date, method, reading, and supporting evidence |
| Validate fields and sources | Record the document name, version, page, or original URL |
| Pass/eliminate conditions | Describe the discrepancy and the decisions it affects |
| Trial operation results and adjustments | Assign an owner, deadline event, and reopening condition |
Use this table to keep the evidence and affected decisions traceable. The final decision must still be checked against the original record and the current vehicle or batch.
How trial run results drive procurement and service adjustments
After the trial run is completed, the original inputs are backfilled item by item: actual mileage, energy consumption or replenishment times, downtime, repairs or complaints, load completion status, and evidence completeness. When the deviation exceeds the preset range, it indicates that the scenario assumption is wrong, the vehicle configuration does not match, or the execution conditions change. In this way, the next batch of purchases can adjust the model, quantity, service capabilities or delivery conditions, and retain reusable measurement results to avoid leaving only conclusions such as "the test drive felt good". This paragraph is about Kenya's "Why can't we just change the steering wheel position when checking export models for Kenya's right-hand drive project?" The corresponding original records should still be returned to during subsequent reviews.
After completing the trial run or customer confirmation, backfill the actual results into Kenya's candidate comparison table "Why can't we just change the steering wheel position when checking export models for Kenya's right-hand drive project", and retain the reasons for failed items.
FAQ
Can a final decision be made once steering position passes verification?
The next step depends on whether regulated components have corresponding documents. If that condition is missing, retain the steering-position record and suspend approval.
When must the RHD variant completeness checklist be reopened?
Record the approval scope again whenever a source document is replaced, the vehicle or batch identifier changes, or regulated components return to pending status.
Can I base a purchasing recommendation on one parameter table alone?
No. First confirm the usage scenarios, candidate comparison items and verification conditions; parameters can only support corresponding fields and cannot replace actual operations or customer constraints. This question should be reviewed in conjunction with Kenya's "Kenya right-hand drive project when checking export models, why can't you just change the steering wheel position" along with the corresponding original records.
Can a quote go out before the customer supplies full conditions?
You can make scenario quotations marked with assumptions, but the missing inputs, validity period, and recalculation trigger conditions must be listed separately, and the assumptions cannot be written as customer facts. This question should be reviewed in conjunction with Kenya's "Kenya right-hand drive project when checking export models, why can't you just change the steering wheel position" plus the matching original records.
Does a failed trial run settle that the model does not fit?
Not necessarily. First distinguish vehicle factors, scene changes and execution conditions, and then decide to adjust the vehicle model, service configuration or trial operation plan. This question should be reviewed in conjunction with Kenya's "Kenya right-hand drive project when checking export models, why can't you just change the steering wheel position" and the corresponding original records.
Which materials come next
First review the new car catalogue to confirm the vehicle version. Then prepare the configuration code and physical-vehicle photos, lamps, glass and safety labels, vehicle or batch identifier, and intended decision, and submit anonymized materials through the contact page. Starvia can help organize the checklist, discrepancies, and pending-confirmation list. Local legal, tax, insurance, and technical conclusions remain with the competent parties.
This article explains a document-review method for the vehicle and transaction scenario described for Kenya. It does not determine local import eligibility, customs, tax, registration or technical outcomes, or guarantee a vehicle's price, availability, delivery or warranty. Each transaction depends on current official requirements, the contract, VIN-specific records, the vehicle's actual condition and confirmation by the competent local party. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here. Review date: 2026-09-28.