← All insights

Real-Time Load Location Tracking for Indian Shippers

In my work with shippers, I define what “real time” should mean for load location in India, using official freight and logistics-cost data, and how I get updates without GPS installs.

By Sridhanwanth · Updated 2026-09-11

In my work with shippers, “real time” is a marketing phrase until I define the decision it supports. For most desks I sit with, it doesn't mean a ping every second. It means a trustworthy location often enough to plan labour, answer a buyer, and escalate a true stall, not a driver who is simply busy.

• 9.09% — logistics cost vs non-services output (agri, mining, manufacturing) (DPIIT / NCAER 2023-24)
• 4,661 BTKM — India freight movement cited in NITI transport scenarios (NITI Aayog)
• NLP 2022 — policy aim: keep logistics costs globally competitive (National Logistics Policy)

Location is an operations input

Load location drives dock slots, overtime, demurrage, and inventory in transit. DPIIT’s study breaks logistics cost into transport, warehousing, and other components, information delay shows up as detention and buffer stock, even when the official GDP ratio has improved versus older 13-14% quotes.

Getting location without installing anything

Vehicle-number tracking compresses time-to-visibility from days (device fitment) to minutes (RC known at indent). I pair it with basic RC / insurance / permit checks before loading and I cover onboarding risk as well as in-transit uncertainty.

Where Lorryman fits

We've built Lorryman so shippers can track any truck carrying their goods across India and know where the load is, without GPS hardware and without depending on the driver for every update.

Define the decision, then define the ping

I've seen this pattern up close. A buyer asking “where is my container?” needs a different refresh than a yard manager holding a labour gang. If I don't name the decision, vendors will sell animation. Real time for Indian shippers is usually: frequent enough to catch a stall before a dock window collapses, trusted enough to send to a customer without a second confirmation call, and available whether or not the driver is on the network. That bar is operational, not cinematic.

Load location is an input to overtime, demurrage, production sequencing, and inventory-in-transit accounting. DPIIT/NCAER’s logistics-cost composition, transport, warehousing, and the rest, is a reminder that information delay shows up as buffer stock and detention even when headline ratios improve. I can celebrate a better national percentage and still bleed at a single plant because one inbound RM truck was a ghost for eleven hours.

What “the load” means legally and practically

The load is the consignment on a vehicle identified by an RC and, often, an e-way bill. If the vehicle changes after a breakdown, the load has a new identity I must track. Hardware left on the first chassis will look green while the goods sit on the second. Real-time load tracking therefore includes an assignment discipline: the number on the trip record must be the number that physically loaded. That sounds basic. It's the most common data-quality failure in Indian control towers.

NLP 2022 talks about service quality and competitive cost. Service quality for a shipper includes a truthful ETA. A truthful ETA is a location history plus a corridor assumption, not a driver performing optimism. When I publish ETAs from a board, I also create an audit trail for claims and post-mortems. Phone ETAs evaporate. Board ETAs can be reviewed on Monday.

How often is often enough?

For most FTL industrial lanes, knowing movement versus dwell every meaningful driving hour already changes behaviour. For high-value or high-risk cargo, tighten the watch. For milk runs inside a metro, I may want denser updates. I don't copy a consumer cab app’s refresh rate onto a Jaipur-Chennai hired lorry and then declare the category a failure when physics and networks disagree. I match cadence to the cost of being wrong.

I share the view. If only one coordinator can see location, I still have a bottleneck. Plant, logistics, and customer-service should read the same trip. Arguments drop when the object is shared. I find Lorryman useful when that shared object can be created from a vehicle number at indent, not after a week of device scheduling.

A 30-day measurement you can take to leadership

I count location calls on a lane. I count customer ETA complaints. I count dock waits caused by “we thought it was 40 km away.” After tracking is live, count them again. If the numbers don't move, I have an adoption problem, not a product problem, people aren't looking at the board before they dial. If they move, I have a budget conversation that's no longer theoretical. Real time that doesn't change a KPI is decoration.

India’s freight mix still leans on road. Real-time load tracking is how a road-heavy economy stops treating every consignment as a rumour. I start with the loads whose delay is most expensive. I expand when the rumour mill is quieter.

Name the decision before you name the refresh

I've seen this pattern up close. A buyer asking where a container sits needs a different cadence than a yard manager holding a labour gang for an inbound coil. If I don't name the decision, vendors will sell animation. Real time for Indian shippers is usually this: frequent enough to catch a stall before a dock window collapses, trusted enough to send to a customer without a second confirmation call, and available whether or not the driver is on the network. That bar is operational, not cinematic. Load location is an input to overtime, demurrage, production sequencing, and inventory-in-transit accounting. I can celebrate a better national logistics-cost percentage and still bleed at one plant because an RM truck was a ghost for eleven hours. I name the decision on the lane. Then buy the ping that serves it. Cinema that doesn't change a dock slot is decoration with a map skin.

I write the decisions down. Dock labour: do we call the gang now or in three hours? Production: will this RM make the first shift or do we change over? Customer-service: what sentence do we send without lying? Finance: is this consignment still in transit or is it sitting in a night-halt yard inflating working capital? Each decision has a cost of being wrong. I match refresh to that cost. A milk run inside a metro can justify denser updates. An FTL industrial lane from a plant in Pantnagar to a warehouse in Bhiwandi already changes behaviour if I can tell movement from dwell every meaningful driving hour. I don't copy a consumer cab app onto a long-haul hired lorry and then declare the category a failure when networks and physics disagree. I match cadence to rupees, not to a demo. If the demo needs a ping every few seconds to look alive, it's selling anxiety, not a dock decision.

The load’s name on the road is the RC

The load is the consignment on a vehicle identified by a registration certificate and, on taxable movement, an e-way bill. If the vehicle changes after a breakdown, the load has a new identity I must track. Hardware left on the first chassis will look green while the goods sit on the second. Real-time load tracking therefore includes an assignment discipline: the number on the trip record must be the number that physically loaded. That sounds basic. It's the most common data-quality failure in Indian control towers. Brokers send a photograph. Gate security sees another plate. Coordinators update the e-way bill and forget the trip. The board then tracks a ghost. Stop. When the plate changes, the trip changes. Type the new RC before anyone debates last hour’s pin. Identity isn't a clerical afterthought. It's the load’s name.

The National Logistics Policy talks about service quality and competitive cost. Service quality for a shipper includes a truthful ETA. A truthful ETA is a location history plus a corridor assumption, not a driver performing optimism because a buyer is shouting. When I publish ETAs from a board, I also create an audit trail for claims and Monday post-mortems. Phone ETAs evaporate. Board ETAs can be reviewed. That review is how plants stop staffing from folklore. It's also how I separate a true check-post dwell from a story. If the “real time” can't survive an RC swap at 2 a.m., it's not load tracking. It's vehicle tracking of the wrong vehicle. Hired freight will keep swapping chassis. The cadence and the identity rules must assume that, the way I already assume e-way bills at dispatch. Assumption here is cheaper than a Monday reconstruction from chat screenshots.

Cadence that matches the cost of being wrong

For most FTL industrial lanes, knowing movement versus dwell every meaningful driving hour already changes overtime and dock planning. For high-value or high-risk cargo, tighten the watch. For perishable or mandi lots heading to a buyer who will sell onward the same evening, a stall I see late is a price I already lost. I don't run one refresh religion for the whole company. I run a rule per lane class. I write it next to the board so a Saturday coordinator doesn't invent policy. When in doubt, ask what decision will be made with the next update. If nobody can name one, I'm collecting pings for comfort. Comfort isn't a KPI. A plant that overstaffs because it thought a truck was close is paying for a wrong cadence, not for a missing satellite. I fix the rule. Then measure whether labour windows moved.

I share the view or I still have a bottleneck. If only one coordinator can see location, the plant will call drivers and sales will invent a parallel story. Stores, logistics, and customer-service should read the same trip. Arguments drop when the object is shared. I don't share noise, don't flood a distributor with every minor halt. I share progress, long stalls, and RC changes. I find Lorryman useful when that shared object can be created from a vehicle number at indent, not after a week of device scheduling. Same-day hired trucks don't wait for scheduling. The load leaves. Either I have a picture from the RC or I have a rumour. Real time that starts after fitment isn't real time. It's a delayed hardware project wearing a live-map vocabulary. I call it that in the steering pack so nobody funds a workshop and names it real time.

Thirty days of counting, not decorating

I count location calls on a lane before I go live. I count customer ETA complaints. I count dock waits caused by “we thought it was forty kilometres away.” After tracking is live, count them again. If the numbers don't move, I have an adoption problem, not a product problem, people aren't looking at the board before they dial labour or a buyer. If they move, I have a budget conversation that's no longer theoretical. Real time that doesn't change a KPI is decoration. I put the three counts on one page for leadership. I don't bring a screenshot of a pretty truck. Bring the overtime line and the complaint log. India’s freight mix still leans on road. Real-time load tracking is how a road-heavy operation stops treating every consignment as a rumour. I start with the loads whose delay is most expensive. I expand when the rumour mill is quieter.

Week four should also test identity hygiene. How many trips had an RC change? How many of those changes hit the board the same hour? How many still showed the old vehicle while cargo moved? That last number is the integrity score. A beautiful cadence on the wrong registration is worse than a slower cadence on the right one, because it creates confident error. Confident error staffs the wrong shift. I assign someone to audit a sample of gate-out plates against trip records every Friday. Dull work. It's the difference between a live map and a live lie. Plants that skip the audit eventually declare that “real time doesn't work on transporters.” Transporters were not the failure. The name of the load was. I fix the name. Then the ping means something. Until then I'm measuring the wrong truck with impressive punctuality.

What to do when the vehicle changes at 2 a.m.

I write the night path before I need it. Transporter or broker sends a new RC. Duty desk updates the trip immediately. Plant and customer-service see the new identity without a morning meeting. Old hardware, if any existed, is ignored. Calls go to the new driver for instructions only, gate, labour, unloading bay, not for a pin to replace the board. If the e-way bill must change, do that as a paired action, not as a separate clerical island. Two systems with two numbers is how ghosts are born. One trip object with one registration is how a 2 a.m. replacement stays a trip instead of becoming a missing load. Practice this path on a weekday afternoon once, so the night desk isn't inventing it in panic. Panic isn't a cadence. It's the absence of one.

Real time, in the end, is a management choice about which rumours I'll still tolerate. If I tolerate “driver said” as an input to labour, I'll keep paying surprise. If I tolerate a board that only logistics can see, I'll keep parallel stories. If I tolerate RC drift, I'll track the wrong truck with great punctuality. I refuse those three. I keep human judgement for breakdowns and delivery politics. Let the ping serve named decisions. Then “real-time load location tracking” stops being a brochure phrase and becomes a desk habit: indent has a number, the number is the load, the board is shared, the counts move. That habit is available on hired trucks the morning the RC exists. I don't need a workshop to start it. I need the discipline to treat the registration as the name of the goods until those goods are off the deck.

Labour, MRP, and the buyer are different clocks

I don't force one clock on three users. Labour contractors think in gang hours. MRP thinks in shifts and safety stock. Buyers think in their own unloading windows and onward sales. A single trip board can serve all three if I translate, not if I spam. The plant needs stall versus progress against the shift. The buyer needs a calm sentence they can staff against. Finance needs to know whether inventory is moving or becoming a parked working-capital tax. I teach coordinators those translations. A raw ping isn't a sentence. The board is the source; the sentence is the service. When those clocks disagree, and they will, at check-posts and during night halts, the shared history is how I explain the disagreement without inventing a fourth clock on WhatsApp. Four clocks is how Indian desks go mad. One object, three translations, is how they stay adult.

If leadership still asks for a ping every minute on a hired N3, take them to the decision list. I ask which decision changes at minute seventeen versus minute forty. If none does, I'm buying anxiety reduction for a steering committee, not operations. Anxiety reduction is a legitimate purchase only if I admit it. Most plants can't afford that honesty, so they should buy operational cadence instead. Operational cadence on market trucks starts with the vehicle number, not with a fitment calendar. That's the Indian constraint. I honour it and real time becomes a working phrase. Ignore it and I'll run a beautiful owned-fleet map beside a hired-lane rumour mill, and I'll call the combination a “control tower.” It won't be. It will be two clocks that never agree, and a buyer who still calls I at 11 p.m. because the sentence wasn't backed by a trip.

Track trucks without GPS on Lorryman