Review each vehicle and operating pattern
List the actual vehicles, drivers and routes before selecting equipment. A parcel business may use different vehicle classes and work patterns; the business category alone does not determine which units need an ELD.
For vehicles within the intended ELD scope, describe loading, successive delivery stops, returns and closeout work. Keep parcel scans and delivery confirmation separate from the driver-log evaluation.
Parcel delivery evaluation worksheet
| Fleet-matrix column | Information to collect |
|---|---|
| Vehicle and engine | Actual model, engine and relevant vehicle characteristics |
| Connection | Diagnostic connector and proposed device/cable |
| Operation | Route, driver duties and applicable recordkeeping decision |
| Mobile device | Phone/tablet, operating system and app version |
| Acceptance owner | Person responsible for the representative trial |
Bring the actual truck configuration
Ask Factor ELD to review the matrix before recommending a fleet-wide kit. For a supported configuration, use the vehicle selection and log review described in the PT30 manual as trial tasks.
Have the carrier assess any short-haul or other exception independently. A local route, small package or returning vehicle does not provide the complete answer.
For the broader fleet discussion, see delivery. Use the ELD rollout checklist to assign training and review responsibilities, and check ELD applicability for the actual operation.
Parcel delivery questions
Does every parcel van need the same ELD setup?
No. Assess the actual vehicle, operation and supported connection before selecting equipment.
Can the ELD replace package scanning?
Package-level delivery evidence is a separate capability that must be verified independently.