Make the relief-driver handoff explicit
Use a sample run that includes a relief driver or a vehicle reassignment. Identify when the outgoing driver’s assignment ends, who is responsible for any intervening movement and how the incoming driver confirms the truck and device.
The test concerns road-vehicle records. Animal welfare, loading procedures, plant receiving and biosecurity remain separate operating responsibilities; a driver-log system does not certify them.
Poultry transport evaluation worksheet
| Handoff point | What to establish |
|---|---|
| Outgoing driver finishes | Last vehicle assignment and unresolved record issues |
| Truck remains at pickup or plant | Who is responsible for any movement and work |
| Relief driver starts | Correct named account, selected vehicle and connection |
| Office reviews the run | Each driver’s record can be identified without sharing credentials |
Bring the actual truck configuration
The Factor PT30 manual documents login and vehicle selection. Ask for a parked handoff demonstration using the exact proposed app and device; do not assume that a common truck implies a shared driver history.
Confirm engine, connector and mobile-device fit individually. Review commodity-related or other exceptions with the carrier’s responsible person. A poultry movement is not automatically exempt for every vehicle, route or driver task.
For the broader fleet discussion, see livestock. Use the ELD rollout checklist to assign training and review responsibilities, and check ELD applicability for the actual operation.
Poultry transport questions
Should the relief driver keep the outgoing driver logged in?
Use the carrier’s proper named-account and handoff process. The next movement must be attributed to the actual driver.
Does this ELD discussion cover poultry condition or biosecurity certification?
No. Those require their own procedures and records, separate from the driver-log evaluation.