If a report looks wrong, vague, incomplete or misleading, send the details here. Good feedback helps improve the model database and the report engine.
Issue types
Report issues should be structured so admin review can quickly identify whether the problem is matching, data, wording, price logic or scoring.
The report appears to identify the wrong make, model, engine or generation.
A known fault is missing, unclear, exaggerated or not relevant to the vehicle.
The mileage context, remaining-life estimate or risk score seems unrealistic.
The price sanity section seems wrong, unclear or not useful for negotiation.
Issue form
Send enough detail for support to review the vehicle data, report section or scoring logic.
A useful issue report tells us exactly what went wrong and where in the report it happened.
Registration used in the report.
Report URL, if available.
Mileage and advert price entered.
Make, model, engine and year.
Which section looked wrong.
What you expected the report to say.
Any source or evidence that supports the correction.
If a car appears unsafe, do not drive it based on an online report. Get a qualified mechanic or inspection service to assess the vehicle properly.
Duewise improves through structured vehicle data. Clear issue reports help update weak points, mileage rules, buyer checks and model matching.
Review workflow
Structured issue reports help review model data, evidence prompts and buyer guidance quality.
The user reports what looked wrong, unclear or incomplete.
The issue appears in the admin QA queue for report and model-data review.
The relevant model, fault, maintenance rule or report logic is improved.
Future reports become more accurate and useful for buyers.
This page is specifically for report quality and vehicle-data issues. For general questions, use the support or contact pages.