“Placement” is a word everyone in logistics uses and nobody explains. It means a vehicle, with a driver, made available to a network at a stated place and time to do a stated run. One vehicle, one day, one lane: that is one placement, and it is the unit almost everything else is counted in.
Here is what a day of it looks like, and why the boring part — writing the day down — decides whether the month ends in an argument.
Two kinds of placement
Regular placement is a vehicle attached to a lane on a continuing understanding: the same truck, the same origin and destination, the same reporting time, day after day. The network plans its capacity around it and the owner plans a month’s running around it.
Ad-hoc placement is a vehicle asked for when it is needed: a sale week, a festival build-up, a lane where volume suddenly needs one more trip, or a stand-in for a vehicle that has gone off the road, arranged for a day or a few days at a time.
Both are legitimate and most operations run a mix. The mistake is to treat them as the same thing. A regular placement is planned on the assumption that the vehicle turns up every day; an ad-hoc one is arranged on being available at short notice. Blurring the two is where both sides start to feel cheated.
The morning confirmation
A placement day usually begins before the vehicles do.
Someone on the ground has to confirm, early, which vehicle and which driver is going on which lane today: that the driver has reported, the vehicle is fit to go, the papers have not expired overnight, and the reporting time at the centre still stands. Where there is a cut-off — and in first mile there almost always is — this happens well before it.
It sounds like a formality until it is skipped. The failure is never “a vehicle did not turn up”. It is “everyone assumed the other side had checked”. A confirmation at a fixed hour, in one place both sides can see, removes most of that.
Three things are worth confirming, in this order: the vehicle number, the driver, the lane. If any has changed from yesterday, say so rather than let it be discovered at the gate.
When a vehicle drops
It will happen. A tyre goes, a driver falls ill, a vehicle is held at a check post, a permit turns out to have expired.
What matters is the next hour. A good vendor is looking for a replacement of the same size before the reporting time passes, and telling the hub the moment they know rather than the moment they have solved it. A network that hears early can move load, change the sequence or accept a later departure. A network that hears at the reporting time can only wait.
So the question to ask a vendor is not “do vehicles ever drop?” They do, everywhere. It is how quickly it is known, and whether the replacement comes from people the vendor knows or from a broker three calls away. The day also needs a decision on what the drop means for counting: covered by a replacement, or not covered at all? That belongs in the record on the day.
What a good ad-hoc request looks like
Ad-hoc work fails for a dull reason: the request is incomplete. A request that can be filled says the date, the reporting time, the exact reporting point, the vehicle size, the open or closed body, and roughly what the load is. If it is a return trip, say so.
The more of that is missing, the more the vendor is guessing, and a guess at eight in the evening for a vehicle needed at six in the morning is how the wrong size ends up at the gate.
Why the day-wise record protects both sides
At the end of the month someone raises a bill. If it is a single number — so many vehicle-days at so much — checking it means remembering a month. Nobody remembers a month.
A day-wise record is the list behind that number: for each date, the vehicle, the lane and whether it ran. It is unglamorous and it settles nearly everything.
It protects the network, because a claimed day that did not happen shows up as a line with nothing behind it, and a disputed date can be settled on its own instead of holding up the whole invoice.
It protects the vehicle owner just as much, and this is the part owners miss. A day the vehicle reported and was not loaded is only arguable if it was written down at the time. An overnight trip that belongs to Tuesday rather than Wednesday can only be shown if both sides recorded the same convention. Without a record, the owner argues from memory against someone else’s spreadsheet.
Write it the same day
The single rule that makes all of this work: enter the day on the day.
Not on Friday for the week. Not at month end from trip sheets in a bag. The same day: the date, the vehicle number, the lane, whether it ran, and one line if something was unusual — detention, a replacement vehicle, a cancelled trip.
It takes two minutes per vehicle and removes most of the reasons a month goes wrong. A placement is easy to promise. A record is what makes it possible to prove.