Execute Vehicle Assignment and Handover Protocols
Standard operating procedure for vehicle handover, physical inspection checklists, and baseline odometer sign-off.
1. Overview & Business Value#
This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for Execute Vehicle Assignment and Handover Protocols within SmartERP.

Standard operating procedure for vehicle handover, physical inspection checklists, and baseline odometer sign-off.
2. Prerequisites & Security Access Groups#
- Required Modules:
fleet, smarterp_fleet_operations, smarterp_fleet_insurance - Security Groups:
Fleet Operator(Technical ID:fleet.group_fleet_user)Fleet Administrator / Transport Manager(Technical ID:fleet.group_fleet_manager)
- Master Data Dependencies: Vehicle asset cards, license plate registry, fuel cards, driver profiles, scheduled maintenance intervals, and third-party insurance policies.
3. Step-by-Step Configuration & Execution#
Step 1: Navigating to the Interface#
- Log into your SmartERP instance at
https://smarterp.et/odoo. - Open the main App Switcher (grid icon in the top-left corner).
- Navigate to Fleet → Vehicles.
Step 2: Operational Data Parameters & Controls#
Ensure all mandatory parameters comply with enterprise operational standards:
- Authorized Operator: Action executed under assigned RBAC permissions (Fleet Manager, Dispatch Officer, Maintenance Supervisor).
- Relational Integrity: Linked to upstream master records, approval requests, or transactional ledgers.
- Statutory & Quality Controls: Verified against Ethiopian statutory regulations and corporate governance standards.
Step 3: Operational Execution & State Progression#
- State Progression Gate: Advance record from Draft through Audited to Confirmed / Certified.
- Integrated System Impact: Automatically updates real-time operational states and posts financial/inventory journal moves.
- Audit Verification: System registers tamper-evident audit records logging user ID, timestamp, and cryptographic transaction digests.
Purpose of Formal Vehicle Handover#
When assigning a fleet asset to a new driver or transferring a vehicle between operating branches, a formal handover protocol prevents disputes regarding pre-existing body damage, missing tools, or fuel discrepancies.
Procedure: Completing a Handover Inspection#
- Navigate to Fleet > Operations > Vehicle Assignments and click New Assignment.
- Select Vehicle and Assigned Driver.
- Complete the digital Handover Checklist:
- Body condition: Note any existing dents, scratches, or windshield cracks.
- Fluid levels: Engine oil, coolant, brake fluid, windshield washer.
- Safety kit: Fire extinguisher (check pressure gauge), spare tire, jack, wheel spanner, warning triangles.
- Odometer Reading: Confirm physical gauge reading against digital entry.
- Fuel Level: Record gauge reading (e.g., 3/4 full).
- Both the Dispatcher and Driver sign digitally on the mobile tablet.
- Click Confirm Assignment. The driver is now officially recorded as the custodian of the vehicle.
4. Advanced Configuration Points#
- Automated Actions & Scheduled Tasks (Crons):
Fleet: Trigger preventive maintenance intervals(fleet.ir_cron_service_interval): Runs daily to alert transport officers when vehicles approach service kilometer thresholdsInsurance: Alert expiring third-party liability policies(fleet.ir_cron_insurance_alert): Runs weekly to flag insurance policies expiring within 30 days
- Custom Print Templates & Reports:
- Vehicle Preventive Maintenance Work Order
- Fleet Fuel Consumption & Mileage Analysis (km/L)
- Third-Party Liability & Comprehensive Insurance Schedule
- Driver Incident & Vehicle Lifecycle Cost Ledger
- Multi-Company Rules: Record-level security isolation under Company 1 (
Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.
5. Comprehensive Troubleshooting Matrix#
| Error Symptom / Exception | Probable Root Cause | Corrective Action / Resolution |
|---|---|---|
Service Due Warning: Odometer exceeds threshold | Vehicle operating past scheduled oil change or brake inspection kilometer mark. | Ground vehicle and schedule immediate maintenance in Fleet → Services. |
Policy Expired Block: Vehicle grounded | Mandatory statutory third-party liability insurance has elapsed. | Renew insurance policy with underwriter and update expiration date on vehicle card before release. |
Fuel Anomaly Warning: Consumption exceeds normal rate | Logged fuel volume exceeds vehicle fuel tank capacity or normal kilometer ratio. | Audit driver logbook, inspect fuel card receipts, and perform fuel tank sensor diagnostic. |
Last updated: 2026-11-15