Remote Lock Monitoring That Records Every Open, Close and Attempt
A mechanical seal tells you a number at the destination and nothing on the way there. A GPS smart lock reports its own state continuously, and KO Fleetz logs every open and close with a time, a coordinate and the identity of whoever authorised it.
The seal number was different on arrival. That is the entire evidence file.
The way most fleets secure a container is a numbered bolt seal and a manifest line. The loader writes the number down, the consignee reads it off at the far end, and if the two match everybody signs. If they do not match, you have learned exactly one thing: it happened somewhere between the two, at some point in the last eleven hours.
Keys have the same shape of problem. Padlock keys get copied, spares live in the glovebox, and the depot's master key has been on the same hook since before the current supervisor started. Nobody can tell you who opened a door last Tuesday because the lock has never been able to say.
Then there is the ordinary friction. A truck sits at a customer gate for forty minutes because the person holding the authority to open it is on another site and not answering. The load is late for a reason that has nothing to do with the road, and the only fix anyone has is a phone call chain.
Give the lock a voice and a clock
A KO Fleetz smart lock is a reporting device, not just a hasp. It publishes its state — locked, unlocked, in transit, tampered — on change and on a heartbeat, and each state change is written with the GPS fix, the vehicle, the trip and the credential that caused it. An open is no longer an inference drawn from a broken seal. It is a record.
Authority moves to the platform rather than to the keyring. A supervisor can release a door from a desk, a driver can be granted a single-use unlock that expires at the end of the delivery window, and a site can be given rights to a specific consignment on a specific day. Where coverage is unreliable, a time-bounded offline code lets the door open without the lock needing a network at that moment, and the event still uploads on reconnection.
What the lock deliberately does not do is shout about normal work. An opening inside your own depot fence during a rostered loading window is logged and left alone, because a system that pages a supervisor for every legitimate door movement gets its notifications switched off inside a fortnight. Nor does the lock pretend to be armour: it secures and reports the locking point, and someone attacking the hinges, the roof or the bodywork is a physical security problem that a padlock of any intelligence does not solve.
Capabilities
What KO Fleetz remote lock monitoring gives your team
State change log
KO Fleetz stores every lock, unlock and close with the time it happened and the trip it happened on, giving you an ordered history instead of a seal number at each end.
Remote unlock authorisation
A supervisor releases a door from the platform without anyone driving a key across town. The command records who issued it and whether the lock confirmed it.
Position-stamped door events
Each opening carries the coordinate where it occurred, so a door that moved on a service road reads differently from one that moved on a customer's dock.
Tamper and forced-open detection
The lock reports shackle interference, housing removal and openings it never authorised, rather than only reporting the commands it accepted.
Expiring one-time codes
Issue an unlock that works once, for one door, inside one window. It stops being a key the moment the delivery window closes.
Lock power and link health
Battery charge and last contact are tracked per lock, because a device that has gone quiet is a security question, not a blank row in a report.
Targeted escalation
Route unexpected openings by depot, route or consignment value, so a night event reaches the person on shift and not an inbox read at nine the next morning.
Custody handover record
KO Fleetz captures each transfer between loader, driver and receiver against the lock event that accompanied it, so responsibility has a boundary you can point at.
How it works
How KO Fleetz does it
Step 1: Fit the lock and bind it to the vehicle
The lock is paired to a vehicle or a container in the platform. From that moment its events inherit the trip, the driver and the route it is travelling on.
Step 2: Write the access rules
Decide who may open what, from where, and inside which window. Depot staff, drivers and customer sites each get their own scope, not one shared credential.
Step 3: Run the trip
The lock reports state changes as they happen and buffers them when coverage drops. Openings that match the rules are logged quietly; the rest raise an alert.
Step 4: Review the exceptions
Each flagged opening is closed out as authorised, mistaken or genuine. Those decisions sharpen the rules, so next month's alert list is shorter and more meaningful.
Outcomes
What changes
- History per door, not a seal number per leg
- Event-level
- Authorisation travels instead of a driver
- No key run
- Every unlock carries the credential behind it
- Named
- Routine depot openings never page anyone
- Quieter
Frequently asked questions
Yes. Any padlock can be defeated with enough time and the right tool, and we would not ask you to believe otherwise. The difference is what happens next. A cut mechanical seal is discovered at the destination, hours later and hundreds of kilometres away. A cut smart lock stops reporting or reports tamper immediately, and the alert carries the coordinate where it happened. You are trading an unbreakable claim for a fast, located one, which is generally the trade worth making.
The lock keeps working. State changes are stored on the device and uploaded when the link returns, so the history stays complete even though it arrives late. For opening a door in a dead zone, KO Fleetz can issue a time-bounded code that the lock validates locally without needing to reach the server. The honest limitation is alerting: an event that cannot upload cannot notify anyone until the device finds coverage again.
No, and this is worth asking before you buy anything. Locks are specified so that a flat battery does not turn a container into a sealed box: depending on the model, that means an external jump point, a mechanical override held under key control, or both. KO Fleetz's job is to make the situation rare rather than survivable. Charge level is reported per lock, and a lock trending toward flat appears as a task before it becomes an incident on a dock.
In practice most fleets keep a controlled mechanical fallback, and we would rather that decision be deliberate than discovered during a bad night. What changes is the default. Routine access is granted electronically, scoped to a door, a window and a person, and every use is recorded. The fallback becomes an exception that itself gets logged, instead of the everyday method nobody can audit.
This page is about the lock as a device: its state, the commands sent to it, its tamper reporting and its health. Cargo Security is about the consignment travelling behind the lock, and it uses these events as one input alongside route rules, stop analysis and proof of delivery. If you want to know when a door moved and who authorised it, that is here. If you want to know whether the load stayed intact from bay to signature, start with Cargo Security.
They should, and we recommend telling them plainly. A lock that records openings is not a trap; it is the thing that ends the argument in the driver's favour when a consignee claims a shortage that never happened. Fleets that introduce this as covert surveillance get resistance and tampering. Fleets that introduce it as evidence which protects everyone in the chain get cooperation, and the data is better because of it.
Put a lock on the bench and watch it report
Bring one container and one route with a history you cannot explain. We will show you the event trail the lock would have written.