Vehicle File Checklist

Standard Operating Procedure: Vehicle Documentation Lifecycle & Compliance Audit

1. Document Control Block

---

2. Executive Summary & Scope

This SOP defines the mandatory requirements for the curation, maintenance, and verification of vehicle-specific documentation within the Template Registry. The scope covers all owned and leased assets, ensuring adherence to DOT, ISO 39001, and local jurisdictional motor vehicle statutes. Non-compliance risks significant fiscal penalties and operational liability.

---

3. Prerequisites & Tool Requirements

• Software Access: ERP/Fleet Management System (FMS) with "Manager" level write-access; Cloud Document Repository (Read/Write).
• Equipment: Secure document scanner (600 DPI min); encrypted hardware token for digital signatures.
• Certification: Personnel must maintain active "Fleet Compliance Officer" certification (TR-CERT-88).
• PPE: N/A (Admin/Back-office focus).

---

4. Roles & Responsibilities (RACI Matrix)

---

5. Step-by-Step Operational Procedure

Phase I: Intake & Identification

• Assign unique Asset ID (VIN mapping) in FMS.
• Verify physical Title/MCO presence and state of origin.
• Scan and upload bill of sale to the secure repository.

Phase II: Regulatory Documentation

• Validate registration card is current and matches the facility address.
• Confirm Proof of Insurance (COI) reflects the specific VIN.
• Inspect annual state inspection sticker and upload certificate of compliance.

Phase III: Maintenance & Usage Logs

• Attach the Preventive Maintenance (PM) schedule to the digital file.
• Verify Driver Qualification (DQ) file is linked to the vehicle assignment.
• Ensure telematics data logs are synchronized with the file repository.

Phase IV: Finalization

• Perform metadata tagging (Year, Make, Model, Status).
• Apply "Locked" status to the file directory in the ERP.

---

6. Quality Assurance & Verification Criteria

• Completeness: 100% of required fields populated (no null entries).
• Accuracy: VIN string match against physical plate/frame tag.
• Audit Threshold: 0% tolerance for missing insurance or expired registration.
• Acceptance Benchmark: Document file must pass the "3-Click Audit" (Asset location, registration, and insurance must be retrievable within 3 clicks in the FMS).

---

7. Practical Troubleshooting Scenarios

Scenario A: VIN Mismatch during Audit

• Observation: Electronic registry VIN does not match physical chassis engraving.
• Correction: Halt all operations for the asset. Tag as "Out of Service." Initiate a physical verification form (TR-FORM-9) and alert Legal Counsel for potential title re-issuance.

Scenario B: Insurance Expiration Identified

• Observation: System alert indicates COI expiration within 48 hours.
• Correction: Immediate email notification to the Insurance Broker and the Fleet Manager. If no proof of renewal is received by T-minus 12 hours, the vehicle is restricted from the dispatch board via ERP override.

Scenario C: Corrupt Digital File Upload

• Observation: Document scanned but file shows 0 bytes or format error.
• Correction: Delete the corrupted file immediately to prevent record contamination. Request re-scan from the original source; if source is unavailable, flag as "Compliance Incident" and initiate a manual manual affidavit of documentation.

---

Approved by: Julian Vance Chief Operations Architect, Template Registry