The Shrinkage Problem

Every organization that manages physical inventory in the field has a shrinkage number. It is the gap between what the system says you should have and what you actually have. In infrastructure operations (utilities, telecom, construction) that number tends to land between two and eight percent of total material cost, depending on who you ask and how honestly they are counting.

Most of that gap is accounting. A worker picks up fifty metres of cable from the warehouse. The warehouse logs forty. The worker installs forty-five and reports fifty. The three numbers live in three places (a sign-out sheet, a truck count and a work report), and by the time anyone notices, the project has moved on and the details are gone.

Periodic inventory audits are one response: count everything, compare with the records and write off the difference. An audit measures the loss after it has happened. It shows how much went, and where, when and why stay open.

Where the Chain Breaks

Material moves through a field operation in a predictable sequence: procurement delivers to a warehouse, a worker picks up from the warehouse, the worker installs at a site, and a report documents what was used. The chain of custody breaks at every handoff.

Warehouse to worker. The worker signs a clipboard and loads materials onto a truck. The clipboard records a name, a date and a rough description. Exact quantities, the worker's authority to take the materials and the work order they belong to stay off the sheet, and the sheet itself can go missing.

Worker to installation. The worker installs the materials at the site. What goes in can differ from what was picked up: less cable than expected, or extra junction boxes from a second trip. That difference between issued and installed is where most shrinkage hides, unrecorded.

Installation to report. The worker reports at the end of the day. A report apart from the pickup record and the inventory leaves the worker reporting from memory: about fifty metres of cable, probably. The "probably" is where the accounting fails.

Closing the Chain with QR Authorization

Aptli ties every handoff to a timestamped, immutable record, starting at the warehouse.

Work orders carry material lines. A work order lists what the work needs, such as fifty metres of cable and ten junction boxes. A hold reserves that stock at a site until the crew collects it.

A trip gets one code. The crew member picks the lines they are collecting across their open work orders, and Aptli issues one QR code for the trip.

The counter scans it. Staff at the counter scan the code, see who is collecting and what, and hand the trip over. Each line writes a transaction recording what moved, from where, to whom, when, and who handed it over. No clipboard.

Partial pickups are tracked. If the site holds sixty of the hundred units, the crew takes sixty and the line shows forty still to collect. Each partial pickup is its own transaction.

From Pickup to Installation to Report

The QR pickup is the first link. The report is the second.

Reports document what was installed. When the worker submits a report, they record work completed, which resources were used and in what quantities, and which stock items were depleted. Submitting the report automatically creates consumption transactions that deduct inventory from the worker's assigned stock.

Changes wait for a decision. When a report uses more or less than the work order planned, the change waits for someone with the right to authorise it or refuse it with a reason. The stock moves once it is authorised, and the validator sees the change beside the report.

Validation holds. A validated report keeps its validated status, and a correction goes in a new report with an explanation. The original report and its consumption transactions stay on the record.

The Immutable Ledger

Every inventory transaction (pickups, consumption, adjustments, transfers between sites) is immutable. A transaction stays as written. A correction is a new adjustment with a required reason, and it references the original.

That property is what makes the chain of custody trustworthy. An audit trail holds only while its entries stay as written, and append-only transactions keep what happened exactly as it happened.

The result is a complete history for every piece of material: when it arrived at the warehouse, who picked it up and when, which work order it was for, which report consumed it and which validator approved the consumption. A discrepancy found in an audit is answered with a query.

What This Changes

A recorded chain of custody closes the shrinkage that comes from unrecorded handoffs. What remains is the accuracy of each report and material lost to damage or waste, and both show on the record where someone can act on them.

The conversation with auditors and clients changes too. The answer becomes: every material movement is recorded with a timestamp, the person who handed it over and an immutable transaction, and here is the export. In procurement-heavy operations that level of accountability is increasingly the expectation.

Summary

Most material shrinkage in field operations is accounting: what was issued, installed and reported sits in three places with no link between them.
The chain of custody runs through three handoffs: warehouse to worker, worker to installation, installation to report.
One QR code per trip ties the pickup to the plan. Staff at the counter scan it, and every pickup writes a timestamped transaction.
Reports record installation and create consumption transactions. A change from the planned quantities waits for someone to authorise it.
Every inventory transaction is immutable. A correction is a new adjustment with a required reason, and the original stays.
Every piece of material has a complete, queryable history: arrival, pickup, work order, consumption, validation. Audit questions are answered with a query.