DNS Engineering — Pre-Purchase Inspection Field Requirements

DNS Engineering — Pre-Purchase Inspection Field Requirements

A quick-reference guide for contracted inspectors performing mobile pre-purchase inspections.

Inspection Objective

Your role is to document the vehicle’s observable condition and basic functionality at the time of inspection for the prospective buyer.

Keep it factual. Document what you can see, access, operate, measure, photograph, or capture on video. If something cannot be tested or accessed, document the limitation clearly.
  • Document overall condition with clear photos, video, and written notes.
  • Address job-specific client concerns when they are included in the Field Notes.
  • Focus on functional condition; document cosmetic issues when they affect operation or are otherwise relevant.
  • Test and demonstrate key systems and features when accessible.
  • Fully complete the current approved V-PPI Inspector Form.
  • Capture readable photos of all completed forms and written notes.

Required Documentation Media

Capture all listed media unless an item is unavailable at the time of inspection. Missing items must be explained.

Exterior

Front
Rear
Right front
Left front
Left side
Right side
Right rear
Left rear

Interior

Driver seat area
Rear seats
Trunk / cargo area
Interior ceiling / headliner
Instrument panel
OBD port

Identification & Verification

Instrument cluster with odometer visible
VIN dash placard
VIN door placard
License plate

Engine Bay & Fluids

Engine bay overview
Brake fluid reservoir
Coolant reservoir
Engine oil level — dipstick or vehicle display
Emissions label
Visually measurable fluids

Tires & Labels

Tire & loading information label
Tire size — all four tires
Tread depth — all four tires
DOT code — all four tires

Diagnostic Scan Data

Full-system scan / all accessible modules
Freeze-frame information when available
Emissions readiness
MIL / warning-light status

Video Capture

Engine cold start & operation
360° exterior walkaround
Any observed problem or abnormal condition
Limited road evaluation when authorized and performed

Functional Feature Verification

Capture video demonstrating operation of major powered features when equipped and accessible.

Power liftgate / trunk
Sunroof / moonroof
Power windows — at least one full cycle
Driver power seat adjustment
Door lock / unlock function
Electronic parking brake engagement / release
Convertible top, if equipped
Power sliding doors, if equipped
If a feature is inoperative or cannot be tested, document the condition or limitation and capture supporting video when practical.

Client-Requested Inspection Focus

Some assignments include specific areas the client wants documented. Treat these as unverified requests, not established findings.

Follow any specific documentation instruction included in the assignment. For example:

Example:
Photograph all accessible shocks and struts. Document visible leakage and any observable suspension noise.

Inspect and document only what is visible, observable, accessible, or testable at the time of inspection.

How to Write Inspection Notes

Written notes must remain factual, observational, and non-speculative.

Good: “Raw exhaust odor observed at engine compartment during idle.”
Good: “Front brake pad material visually appeared 4 mm or less.”
Good: “Unable to verify rear HVAC operation due to ambient temperature conditions.”
Avoid: “Engine likely failing.”
Avoid: “Transmission probably needs replacement.”
A diagnostic trouble code is an observed data point, not a diagnosis. Record the code or available scan information without declaring the failed component or root cause unless that condition is directly observable.

V-PPI Inspector Form

The V-PPI Inspector Form is the primary structured inspection document. Complete every applicable field based only on direct observations made during the inspection.

✔ Acceptable
Acceptable visible or operational condition observed at the time of inspection.
✖ Concern Observed
Defect, abnormal condition, or operational concern observed.
■ Unable to Verify
Could not verify because of access, environment, vehicle condition, configuration, or another limitation.
Strikethrough — Not Applicable
Use when the vehicle is not equipped with the feature or the item does not apply.
Do not leave applicable inspection fields blank. Any item marked or requires a factual written note.

Inspection Limits

This inspection is visual, observational, and non-invasive.

Inspectors are not expected to:

  • Disassemble components
  • Remove wheels
  • Diagnose internal failures
  • Perform invasive testing
  • Force or recreate conditions
  • Speculate about hidden conditions
  • Certify hidden damage, repair quality, or future reliability

If something cannot be verified because of access, vehicle condition, environmental conditions, seller limitations, or vehicle configuration, mark it as unable to verify and document the limitation factually.

Limited Road Evaluation

When specifically authorized and conditions allow, a limited road evaluation may be performed to observe basic vehicle operation under normal driving conditions. Document observations and limitations factually.

Upload & Final Review

Required Uploads

  • Inspection photos
  • Inspection videos
  • Completed V-PPI Inspector Form
  • Photos of Field Notes or handwritten notes
  • BlueDriver or other approved scan reports when applicable
  • Supporting media for abnormal conditions

Before Marking the Inspection Complete

All applicable V-PPI fields are marked
Required written notes are complete
Required photos are captured
Required videos are captured
Any job-specific requested documentation is complete
Limitations are explained
Forms and written notes are readable
All required media has been uploaded
If access, seller restrictions, safety concerns, or another field condition prevents completion as expected, contact DNS Engineering before attempting work outside the inspection scope.

DNS Engineering Limited Company
inspect@dnsengineering.ltd

DNS Engineering Limited Company — Inspector Field Requirements