Factory & company fleets
Before the lorry leaves: a practical factory dispatch checklist
The useful question is not simply which truck is free. It is whether the whole job is ready to move, with a named person responsible for the next decision.
FLEET OPERATIONS / FIELD GUIDES
Better decisions between the jobs.
Factory dispatch, freight readiness and passenger-trip review. One practical operating decision at a time.
Freight coordination
A shipment plan is not ready just because the CBM fits
Volume answers one planning question. It does not tell you whether the selected orders, documents and release decision all refer to the same shipment.
Passenger & charter fleets
Trip completed, money unchecked: separating fares, receipts and driver costs
A completed transfer tells operations that the journey ended. It does not tell accounts how much was received, which expenses were approved or whether a payment is due.
Fleet handoffs and exceptions
Keep a Cancelled Freight Job Separate from the Vehicle Movement
Record the cancellation request, verification, dispatcher decision, live situation, driver acknowledgement and outcome as separate facts before authorising any new movement.
Fleet handoffs and exceptions
Check Odometer Readings Before Recording Trip Distance
Link traceable start and end observations to the same vehicle, movement and unit before deriving an observed odometer difference.
Fleet handoffs and exceptions
Keep a Freight Document Correction Linked to Its Original
Control which internal document revision dispatch may rely on, without replacing the earlier issued copy or treating file receipt as delivery evidence.
Fleet handoffs and exceptions
Resolve Delivery-Proof Discrepancies Before Closing a Freight Job
Keep one freight job open while the disputed delivery fact, proof reference, verification owner and confirmed correction are made explicit.
Fleet handoffs and exceptions
Hand Over Open Dispatch Exceptions at Shift Change
A shift handover is complete only when every live exception has a known state, a next action, a review point, and an explicitly accepting owner—or is honestly marked unaccepted.
Fleet handoffs and exceptions
Keep Driver Reassignment Clear After Job Acceptance
Use one job record, preserve each allocation attempt, and treat driver acceptance as a distinct response to a specific instruction. Reassignment is not a replacement of history; it is a controlled next decision.
Fleet handoffs and exceptions
Keep Empty Vehicle Repositioning Separate from a Freight Delivery
Record the empty movement, its authority and its arrival separately; retain the freight job until its own cargo and completion evidence exist.
Fleet handoffs and exceptions
Record a Failed Pickup Before Sending Another Vehicle
Preserve the attended but no-load attempt as a factual event, keep the freight job visible, confirm the stated blocker, then make a separate redispatch decision.
Fleet handoffs and exceptions
Keep Customer References Separate from the Dispatch Job
Use one stable dispatch-job reference as the operational anchor, then crosswalk each verified customer reference by issuer, exact supplied value, covered job part and evidence.
Fleet handoffs and exceptions
Link a Carrier Leg to the Original Freight Job
Create a job-to-carrier-leg reference map. Preserve the original freight job, define the handover boundary, record the carrier’s own reference and issuer, then keep the leg outcome separate from final delivery.
Fleet handoffs and exceptions
Link a Goods Return Request to Its Original Delivery
Keep the completed delivery, the customer request, any authorised reverse-movement decision, the proposed collection, custody evidence and receiving acknowledgement as distinct linked records.
Fleet handoffs and exceptions
Keep Collected and Remaining Pieces Clear After a Partial Pickup
Use one job, one explicit unit basis, and separate pickup-attempt records so later collections are not counted twice.
Fleet handoffs and exceptions
Handle a Receiving Window Change Before Dispatch
When a receiving window changes, preserve the original plan, attach the new confirmation, identify the person deciding whether the revised plan can proceed, and ensure the driver has one current instruction. This guide addresses one dispatch exception rather than complete freight readiness, routing, GPS tracking, booking, pricing, or passenger transport.
Fleet handoffs and exceptions
Record Freight Waiting Time Without Assuming a Charge
Capture observable timestamps, uncertainty, evidence references and overlap rules before anyone interprets the interval commercially.
Fleet handoffs and exceptions
Track Returnable Pallets Separately from the Goods They Carry
Use a separate internal custody ledger for reusable transport assets, with an explicit unit basis, handover parties, time, condition and unresolved differences.
Fleet handoffs and exceptions
Keep a Pickup Appointment Separate from Goods Readiness
A pickup appointment confirms an agreed visit interval and contact arrangement. Goods readiness records what the consignor has actually declared ready for the identified job and collection point at a stated time. Keep both facts visible; neither establishes the other.
Fleet handoffs and exceptions
Keep Each Stop Outcome Separate on a Multi-Stop Freight Job
Record each receiving-stop result on its stated unit basis, then reconcile every stop before considering closure of the parent freight job.
Fleet handoffs and exceptions
Verify a Delivery Address Change Before Updating a Freight Job
Record the request as an exception, preserve the original address, identify the decision owner, and update the usable instruction only after an observable decision.
A practical first step
Start with the handoff
that slows your team down.
BOSSFLOW FLEET / GET IN TOUCH
Your fleet.
One practical conversation.
Factory lorries, freight trucks or passenger fleets: tell us your fleet size, how jobs are assigned and which handoff needs attention.
Focused on fleet dispatch and transport operations systems. Services are provided by BossFlow Systems; implementation is scoped separately.