Identify the truck behind the box body
List the actual road vehicles and how they operate. A box body does not identify one engine, connector or regulatory case. Include the relevant vehicle characteristics and driver duties in the carrier’s applicability review.
For trucks within the proposed ELD scope, choose a representative day with loading, delivery and return work. Keep cargo scanning and proof of delivery as separate requirements unless a supported integration is confirmed.
Box truck fleets evaluation worksheet
| Matrix field | Information to provide |
|---|---|
| Vehicle identity | Year, model and relevant vehicle details |
| Engine and connector | Exact engine and diagnostic connection |
| Mobile device | Phone/tablet and operating-system version |
| Operation | Route, driver work and recordkeeping decision |
| Pilot | Named driver and representative acceptance checks |
Bring the actual truck configuration
Ask Factor ELD to review the matrix before recommending hardware. The PT30 manual supplies a vehicle-selection and log-review workflow for that product, not a guarantee for every box truck.
Record which configurations have passed a real-vehicle check and which are unresolved. A successful demonstration on another truck is not a substitute for that distinction.
For the broader fleet discussion, see mixed fleets. Use the ELD rollout checklist to assign training and review responsibilities, and check ELD applicability for the actual operation.
Box truck fleets questions
Does every box truck have the same ELD connector?
No. Confirm the exact engine, connector and supported cable/device combination.
Does the body style determine whether an ELD is required?
No. Have the carrier assess the actual vehicle and operation against the applicable requirements.