Set the decision boundary
Record software version, language options, navigation region, phone integration, account status, OTA requirements and the exact fitted sensor set.
Evidence belongs to one VIN. Preserve dated photos, readings, scans, charge results and road observations so another reviewer can reproduce the conclusion.
Evidence to request
Release prior accounts and demonstrate cameras, parking functions and driver-assistance warnings after reboot. Scan relevant modules and inspect sensor mounting.
Classify material findings by consequence and required action rather than by cosmetic impression.
What can invalidate the conclusion
Functions may depend on Chinese accounts, maps, mobile networks or subscriptions. Hardware and software can vary by trim and production batch.
Resolve contradictions at source. Record the market, model year, test condition and quotation period beside any claim that depends on them.
Separate evidence from assumption
ConfirmedRelease prior accounts and demonstrate cameras, parking functions and driver-assistance warnings after reboot. Scan relevant modules and inspect sensor mounting.
Still openFunctions may depend on Chinese accounts, maps, mobile networks or subscriptions. Hardware and software can vary by trim and production batch.
Destination testTreat every driver-assistance function as assistance, not autonomous driving, and verify destination legality, calibration support and data access.
Turn the claim into an auditable vehicle record
Agree the inspection scope before presentation. The report should show VIN, date, location, ambient condition, odometer and test sequence. Preserve cold and hot observations where relevant, full diagnostic output, charging evidence, paint readings, underside images and road-test notes. Do not accept a seller-selected highlight video as systematic coverage. Classify every finding by evidence, likely consequence, required action and cost owner. High-voltage, structural, flood and identity questions require qualified resolution; a discount alone does not close them.
For this decision, assign a source, date, reviewer and refresh point to every required field. The six controls below are not complete when merely mentioned in a sales message; each needs evidence strong enough for another reviewer to reach the same conclusion.
01 Software versionCapture the original record and check it against the selected VIN.
02 LanguageRecord the test method, result, limits and person responsible for follow-up.
03 Account releaseState the destination consequence, cost exposure and approval status.
04 ConnectivityCapture the original record and check it against the selected VIN.
05 Sensor hardwareRecord the test method, result, limits and person responsible for follow-up.
06 Calibration supportState the destination consequence, cost exposure and approval status.
Before approval, read the file without relying on the original salesperson’s memory. Mark every unresolved item as a hold, give it an owner and deadline, and repeat affected checks when the vehicle, quotation, route or destination rule changes. This distinguishes a documented A06 candidate from a plausible but unverified listing.
Keep rejected evidence in the file with the reason it was rejected. This prevents an outdated screenshot, superseded quotation or mismatched brochure from returning later as if it were current proof, and it gives the destination receiver a clear audit trail.
Connect the result to the destination
Treat every driver-assistance function as assistance, not autonomous driving, and verify destination legality, calibration support and data access.
Record the responsible party, evidence date, expiry or recheck point and the effect on cost or approval. A complete file makes remaining uncertainty visible; it does not turn an unknown into a confirmed feature.
Use the result in a buyer scenario
Assign value only to features demonstrated on the actual VIN and supportable in the buyer’s region. Unknown connected functions should remain unpriced.
Finish with pass, hold or reject. A hold should name the missing evidence, owner and deadline. A replacement VIN begins a new review rather than inheriting approval.
Verify Nevo A06 Software and Driver Assistance: evidence checklist
- Software version
- Language
- Account release
- Connectivity
- Sensor hardware
- Calibration support
Official Changan references
Use market material for context; contract from the selected VIN and legal record.
CHANGAN Tianshu intelligent safety report ↗Questions to close before approval
Will the Chinese app work abroad?
Not necessarily; accounts, phone numbers, maps and services can be region-limited.
Does lidar appear on every A06?
Do not assume it; verify the exact hardware and trim.
Can driver assistance replace the driver?
No. The driver remains responsible and destination rules apply.