PHASE 11 · VEHICLE-SPECIFIC DECISION SUPPORT

Turn observations into a shop-ready checking order.

Add the exact vehicle context, multiple codes and symptoms, when the concern occurs, and recent work. The result screens urgent conditions and orders reviewed checks before any possible repair. It never diagnoses a vehicle or asks for a VIN.

1. Vehicle context

No VIN, plate, owner information, or free-text vehicle description is collected.

2. Observed evidence

Select up to five codes and five symptoms. A code is evidence from a control module—not proof that a named part failed.

Trouble codes

Symptoms

3. Safety conditions right now

If an active fire, loss of control, or immediate danger exists, leave the tool and contact emergency services. Select every condition that is currently present.

4. When it happens

Operating conditions help a technician reproduce the concern. Select up to eight; no free-text notes are collected.

Not a diagnosis. Exact OEM applicability, build date, software level, and service information still require verification.

Important limits

A vehicle can have more than one fault, and the same code can have several causes. Configuration data is context, not proof that a generic decision path applies to an exact build. Stop driving whenever braking, steering, fuel leakage, overheating, oil pressure, severe knocking, smoke, fire, or restraint-system behavior makes the vehicle unsafe.

How the decision paths are built and reviewed