Why a lorry surprises the gate

A lorry arrives at the site gate. The man at the barrier has no idea it was coming.

Somewhere in the office, three people knew. An order was placed a fortnight ago. A dispatch was confirmed yesterday on a phone call. A vehicle number came through on WhatsApp this morning. None of it reached the barrier, and the barrier is where the decision has to be made.

What happens when the gate knows nothing#

The man at the gate is in no position to refuse. He has no list, so he has no basis, and a driver who has come a long way is not going to accept "I have not been told" as an answer. Behind him a supervisor wants the material. So the default is always yes.

Everything that follows comes from that yes.

The wrong material is unloaded. Nobody at the gate can compare the load against an order, because there is no order in front of him. The mismatch is discovered at issue, weeks later, by which time it has been signed for.

A load meant for another site is accepted. Same vendor, similar material, two projects. The driver takes the nearer gate. The receiving site's stock is overstated and another site's is short, and both discover it at stock-taking.

A short load is signed as full. With no expected quantity, the only figure available is the one printed on the vendor's paper. Counting against the challan is not verification; it is transcription, which is precisely the fault that hollows out a goods receipt note.

The vehicle waits. Nobody can authorise unloading, or the crane is committed elsewhere, or the storekeeper has gone to another block. Detention and demand charges start running against the account, and the argument about who pays them happens months later with no record of when the vehicle actually arrived.

Nothing reaches the office. The load is in. The entry is in a register in a cabin. Accounts finds out when the invoice arrives, which is the wrong direction for information to travel.

The specific ways the information fails to arrive#

It is tempting to say the office should simply tell the gate. Offices do try. The failures are worth naming, because each one defeats a different fix.

Dispatch confirmed on a phone call. The purchase officer knows. He is on another call when the lorry arrives, and there is no artefact anywhere that says a load was expected today.

The vehicle number changes at the last moment. A truck breaks down, a transporter substitutes another, the number shared in the morning is not the number at the barrier. A gate instructed to check the number now has grounds to refuse a load that is entirely legitimate, which teaches everyone to stop checking the number.

A partial dispatch against a large order. The order is for a quantity the vendor will deliver over several vehicles. The gate has no way to know whether this load is the first, the fourth or a duplicate — and no running balance against which to see it.

Deliveries outside working hours. Late at night, on a Sunday, during the one hour the storekeeper is at the bank. The people who can check are absent, and the people present can only open the barrier.

Free material, samples and replacements. No order exists at all. A replacement for a rejected load is often sent with paper that references nothing, and a gate process that requires an order number cannot record it.

Direct-to-site purchases. A supervisor buys locally in cash for an urgent kaam. The material is real, the need was real, and no purchase order will ever exist. If the gate can only record what the office ordered, this load enters the site invisibly.

What the gate actually needs#

Not a system. A short, specific set of facts, available at the barrier, without a phone call.

Today's expected deliveries. For each one: vendor, material, expected quantity, order reference, and the vehicle number if it is known — marked as indicative, not as a gate condition. The gate's job is to notice a mismatch and raise it, not to enforce a number that legitimately changes.

A running balance against each open order. So that the fourth lorry against an order is visibly the fourth, and a quantity that would take the order past its total is visible as it happens, not at invoice stage.

A way to record the unexpected. This is the part most designs get wrong. A gate that can only record expected loads will turn away legitimate material or, far more often, let it in without a record. The correct behaviour is to accept and record it as unexpected — vendor, material, quantity counted, photograph, who authorised entry — and let the office resolve what it belongs to afterwards. An unmatched entry that exists can be investigated. A load that was never written down cannot.

A way to record a refusal. Rejected loads leave no trace in most sites, which means the order still looks fulfilled and the vendor's version of events is the only one that survives.

Onward travel by itself. The entry should reach the store and the office without anybody re-typing it. The register in the cabin is a real record — the practical shape of one is in a gate register people keep — but a record that stays in the cabin protects nothing until the day of the dispute.

The paper the driver carries is not the record#

The driver hands over a delivery challan. It is a useful document and it is the vendor's document: it states what the vendor says he sent, in the vendor's units, signed by the vendor's man. Its purpose and its limits are set out in what is a delivery challan.

Your record is the one your side writes, at the barrier, from what your side counted. Signing the driver's copy is an acknowledgment of receipt of a vehicle, not agreement with its contents, and the difference between those two things is the whole reason to write anything down at all. The same discipline runs through running a site store: count first, write your own figure, note the difference on both copies before the lorry leaves.

Two things we found in our own gate#

Our gate screen recorded that a vehicle had come in, and that was all it recorded. The entry wrote no material receipt, so there was nothing on our side for a supplier's billed quantity to be compared against. Nobody had switched the comparison off. There was simply never a figure of our own to compare with, and a comparison that never runs raises no alarm.

The second was the register itself. The physical book in the cabin held things our software had never held: the receiving officer's name, the challan number, the rate, the slump reading, the cube results. When we read that book in and matched it against what had reached us through the phone, the book turned out to be the better record. It had been kept faithfully for years by somebody nobody was asking.

The short version#

A lorry surprises the gate because the information that it was coming stayed in the office. The man at the barrier then has no basis to refuse, so he accepts everything.

Give the gate today's expected loads with quantities and an order balance; allow it to record what was not expected and what was turned away; and let the entry travel to the store and the office on its own. The barrier is the first place your side can state a fact about a delivery. It is also the last place it is cheap to state.