Emissions readiness code checks are a short set of scan tool readings you can take at home to predict how your car will do at an OBD-II emissions inspection. They take a few minutes and can save a wasted trip to the test station.
This guide walks through a practical pre-inspection routine: which screens to read, how to interpret each result, and what to do when something is not ready. It assumes a basic code reader and focuses on preparation, not on how inspection programs themselves are organized.
A Few Minutes in the Driveway Can Save a Trip
Most OBD-II inspections read the same data your own scan tool can see. The station plugs into the 16-pin diagnostic connector, checks whether the warning lamp is commanded on, reads trouble codes, and looks at readiness monitor status.
If any of those results are unfavorable, the car may be rejected or failed before anyone looks under the hood. Checking them yourself first lets you correct problems, or simply wait for monitors to finish, without spending a test fee or a morning in line.
The routine does not replace the official inspection, and it cannot guarantee a pass. It does, however, show you what the station will see. Knowing that in advance turns the inspection from a surprise into a confirmation.
What to Have Ready Before You Start
A pre-inspection check needs very little equipment. Any OBD-II code reader that displays readiness status, sometimes called I/M readiness, is enough for most of the routine. A few other items make it smoother and safer.
- A scan tool or code reader that shows readiness monitors, MIL status, and pending codes.
- The vehicle’s owner’s manual, to confirm dashboard symbols and the connector location.
- A notebook or phone for recording results and the date.
- Your state emissions program’s published rules for incomplete monitors.
Perform the check with the car parked outdoors or in a ventilated space, the parking brake set, and the transmission in park or neutral. Keep the tool and its cable clear of the steering wheel, pedals, and any moving engine parts.
The Readiness Check Routine
The core routine involves four readings. Take them in order, because each one adds context to the next. Record everything before closing the session.
Step One: The Warning Lamp Bulb Check
Turn the ignition to on without starting the engine and watch the malfunction indicator lamp. On most vehicles it should light briefly as a bulb check. Many inspection programs look for this, because a lamp that never lights could hide a fault.
Start the engine and confirm the lamp turns off. A lamp that stays on means the computer is reporting a confirmed fault.
Step Two: MIL Status and Stored Codes
Connect the scan tool and read the MIL status, which shows whether the computer is commanding the lamp on. Then read stored codes. A commanded-on lamp with confirmed codes usually means the car will fail until the fault is repaired.
Compare the tool’s MIL status with the dashboard. If the tool says on and the bulb is dark, the instrument cluster needs attention too.
Step Three: Readiness Monitors
Open the readiness or I/M screen. Note each monitor as complete, not ready, or not supported. Not supported is normal for equipment the car does not have. Count the not ready monitors and compare that number with your state’s published allowance.
Remember that a monitor showing complete can still have failed, so read this screen together with the code results.
Step Four: Pending and Permanent Codes
Check pending codes, which have not lit the lamp yet, and permanent codes if your tool supports them. A pending code warns of a fault that may confirm soon. A permanent code may cause problems in programs that read them, even when no stored code appears.
Some basic readers do not display permanent codes at all, which is worth knowing before relying on a clean result.
Interpreting Your Results
If the lamp works during the bulb check, the MIL status is off, no stored codes appear, and readiness falls within your state’s allowance, the car is generally in good shape to test. Pending codes are worth noting, but they do not light the lamp by themselves.
If the MIL status is on or confirmed codes appear, the car is likely to fail. Repair is the only path forward. Use the code, freeze frame data, and proper testing to find the cause, rather than replacing the part named in the code definition.
If no codes are present but too many monitors are not ready, the car is not failing; it is simply unprepared. That situation usually follows recent code clearing, battery work, or limited driving, and it typically resolves with time behind the wheel.
When Monitors Are Not Ready
Not ready monitors are the most common reason a fault-free car is turned away. The fix is usually patient, normal driving that gives the computer the conditions it needs to run each test.
- Drive the car over several days with a mix of cold starts, city traffic, and steady cruising.
- Keep the tank neither nearly empty nor completely full, since evaporative tests often need a mid-range fuel level.
- Check readiness again after each few days of driving and record progress.
- If one monitor stays not ready, look for pending codes that might be blocking it.
- Consult the service information or a technician for that monitor’s enabling conditions.
Never try to speed things up by clearing codes again, using devices that claim to fake readiness, or modifying emissions equipment. Those approaches reset progress, can be detected, and in many cases are illegal.
Why a Pending Code Deserves Attention
A pending code can be easy to ignore because it does not light the lamp. Yet it often means a monitor has already seen a fault once. If the same fault appears on a later qualifying trip, the code confirms and the lamp turns on.
If your inspection date is close, a pending code is a warning that the car could fail on test day. It also explains why a related monitor might refuse to complete, since many monitors are disabled while related faults are present.
Treat a pending code as the start of diagnosis. Review its freeze frame data if available, inspect obvious causes such as a loose fuel cap for an evaporative code, and test before replacing parts. Fixing the cause early prevents a last-minute surprise.
Permanent Codes and the Inspection Station
Permanent codes are a special case. They are copies of confirmed codes that commanded the lamp on, and they cannot be erased with a scan tool. The vehicle clears them itself after the related monitor runs and passes.
If you see a permanent code but no stored code, the original fault was likely cleared before its monitor had passed. The repair may have been made, but the vehicle has not yet confirmed it. Normal driving that completes the monitor should clear the permanent code.
Some inspection programs read permanent codes, while others do not, so check your state’s rules. In either case, the solution is the same: make sure the repair is correct, drive until the monitor completes, and recheck before your appointment.
Common Pre-Inspection Mistakes
The biggest mistake is clearing codes on the way to the station. This switches the lamp off but resets readiness, leaving several monitors not ready. Many programs will reject the vehicle, and the clearing is obvious to anyone reading the data.
Another mistake is checking only for stored codes. A car can have no stored codes yet still be turned away for readiness, or fail later because of a pending code that confirms on test day. Always read all four results in the routine.
A third mistake is assuming a repair is complete because the lamp is off. Until the relevant monitor reports complete, the vehicle has not confirmed the fix. Give it time, verify with your scan tool, and only then schedule the inspection.
Special Notes for Hybrids, Diesels, and Older OBD-II Cars
Hybrids can make readiness checks less straightforward, because the engine may shut off frequently and monitors need engine running time. Some hybrids have specific procedures for inspection testing. Follow the owner’s manual and keep clear of high-voltage components, which are for trained technicians only.
Diesel vehicles report their own monitors, including those for NOx aftertreatment and particulate filters. Whether and how diesels are tested varies widely by state. Do not modify or bypass DPF, SCR, or EGR equipment, which is illegal and causes inspection failures.
Early OBD-II vehicles from the late 1990s use older communication protocols, and some of them are known to complete certain monitors only with difficulty. Some states apply different rules to those model years, so check the program’s guidance for your exact vehicle.
Making Readiness Checks a Habit
A readiness check is useful well beyond inspection season. Running it every few months, or after any repair, shows whether the car’s self-tests are completing and whether new pending codes have appeared before they become a lit lamp.
Keep the results in a simple log with dates and mileage. Over time, that record reveals patterns, such as an evaporative monitor that only completes in mild weather, and gives a technician valuable history if a problem develops.
When your inspection notice arrives, a recent clean check means you can book the appointment with confidence. If something is not ready or a code appears, you will have the time and information needed to address it properly.