How DockLedger takes a truck yard off paper without a server

Walk into a goods depot and you'll find the same stack of paper everywhere: the incoming vehicle register, the unload memo pad, a photocopied discrepancy form headed for the computer department, and the gate-out book. None of it talks to the others, and by the time management asks what's still pending, the answer lives in somebody's memory. DockLedger replaces that stack with one app a yard supervisor runs from a phone.

It models the paper, not a warehouse system

The design starts from the actual artifacts on the desk rather than from generic warehouse-software features. A truck visit runs gate-in to gate-out: vehicle number, transporter, DO number, origin plant, tonnage, then a dock, a supervisor with a mobile number, and a labour gang. Status moves At Gate, On Dock, Working, Completed, Gate Out.

The unload memo is a digital version of the printed receipt and inspection report, line by line — description, quantity, old or damaged quantity, totals for bags, loose tubes and flaps, nags, plus who unloaded, who re-checked, who inspected, and the driver's details. Anyone who has filled the paper version recognizes the screen immediately, which is most of what adoption means in a yard.

When the memo doesn't match the invoice, the discrepancy becomes a tracked record instead of a scribble: shortage, damage, interchange, or dirty and old stock, linked to its truck visit, owned by a department, and moved through Open, Reported, Follow-up, Closed with dates and notes.

Everything happens on the device

Here is the part that matters mechanically: there is no server. Records are stored on-device with SwiftData. No account, no login, no internet, no subscription — and no IT project to start using it.

That's not a privacy slogan in this case so much as an operational requirement. Yards have thick walls, metal roofs, and dead spots between the gate and the dock. An app that pauses to sync at the gate is an app that goes back in a drawer while somebody grabs the register again.

A supervisor standing at a gate with a truck waiting does not have thirty seconds to spend on a spinner, and any app that needs them has already lost to the paper it replaced.

Because every write is local, entry is immediate. Tap, save, next truck. The responsiveness isn't an optimization we tuned; it's what you get when nothing is waiting on a network.

The report is a read, not a job

The question every depot in-charge asks is what's pending and what's closed. DockLedger answers it from data already on the phone: a daily or monthly summary by issue type, trucks received and dispatched, and the oldest open issues with their age. It shares as clean formatted text through the share sheet in one tap, so it lands in whatever chat or mail thread the depot already uses.

Outbound gets the same treatment. The loading-plan register tracks plan number, destination, vehicle length and load factor, from Planned to Dispatched.

Paper doesn't lose to software because software is smarter. It loses when software is faster at the gate and honest about what it can do offline. That's the bar we're building against across our apps, and it's the one DockLedger was designed to clear.