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 the gap is not theft. It is accounting failure. A worker picks up fifty metres of cable from the warehouse. The warehouse logs forty. The worker installs forty-five and reports fifty. Nobody reconciles the three numbers because they live in three different places — a warehouse sign-out sheet, a truck inventory count, and a work report. By the time anyone notices the discrepancy, the project has moved on and the trail is cold.

The conventional response is periodic inventory audits. Count everything, compare to the records, write off the difference, and promise to do better next quarter. This is damage measurement, not damage prevention. The shrinkage happened weeks ago. The audit tells you how much you lost, not where, when, or why.

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 shows up, signs a clipboard, and loads materials onto a truck. The clipboard records a name, a date, and a rough description of what was taken. It does not record exact quantities with any reliability. It does not verify that the person signing is authorized to take those materials. It does not check whether the materials match a work order. And it is a piece of paper, which means it is lost, illegible, or filed in a box by the end of the week.

Worker to installation. The worker drives to the site and installs the materials. What they actually install may differ from what they picked up — they used less cable than expected, or they needed extra junction boxes from a second trip. The difference between what was issued and what was installed is where most shrinkage hides. Not stolen. Just unrecorded.

Installation to report. The worker submits a report at the end of the day. If the report is disconnected from the pickup record and the inventory system, the worker is reporting from memory. How much cable did I use today? Probably about fifty metres. The "probably" is where the accounting fails.

Closing the Chain with QR Authorization

Our approach ties every handoff to a verifiable, timestamped, immutable record — starting at the warehouse.

Work orders generate QR pickup codes. When a work order is created with resource targets — fifty metres of cable, ten junction boxes — the system generates a QR authorization code. The code contains the authorized user IDs, the resource targets, and an expiration timestamp. Only users assigned to the work order can see the QR code.

The worker scans to pick up. At the warehouse, the worker opens the scanner and scans the QR code. The system validates three things before the transfer completes: the authorization code is valid and not expired, the scanner is an authorized recipient or a warehouse staff member with pickup facilitation rights, and the requested stock is available at the source site. If all three checks pass, the transfer transaction is created automatically — recording what was transferred, from where, to whom, with a GPS location and a timestamp. No clipboard.

Partial pickups are tracked. If the warehouse only has sixty of the requested hundred units, the worker takes sixty. The system updates the pickup remaining to forty. The same QR code remains valid for a second trip when stock is replenished. Every partial pickup is a separate transaction with its own timestamp and quantity.

Staff-assisted pickups preserve the chain. A warehouse staff member with the right permission can scan the QR code on behalf of the worker. The transaction records both who performed the scan and on whose behalf — so even an assisted pickup has a clear chain of custody.

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 consumed from — which stock items were depleted. Submitting the report automatically creates consumption transactions that deduct inventory from the worker's assigned stock.

The system flags mismatches. If the worker reports installing fifty metres of cable but only consumed thirty metres from stock, the system raises a warning. It does not block the submission — there may be legitimate reasons for the discrepancy — but it flags it for review. The QC validator sees the mismatch during the validation step and can investigate before approving the report.

Reports lock after validation. Once a report is validated and payment is released, the report becomes read-only. Corrections require a new report with an explanation. The original report and its consumption transactions remain in the system permanently. Nobody can retroactively adjust the numbers to hide a discrepancy.

The Immutable Ledger

Every inventory transaction in the system — pickups, consumption, adjustments, transfers between sites — is immutable. Transactions cannot be edited or deleted. If a correction is needed, a new adjustment transaction is created with a required reason code. The original transaction remains, and the adjustment transaction references it.

This is not a design choice made for theoretical purity. It is the specific property that makes the chain of custody trustworthy. If anyone could edit a transaction after the fact, the entire audit trail would be unreliable. By making transactions append-only, the system guarantees that what happened stays recorded exactly as it happened.

The practical consequence is that every piece of material in the system has a complete history: when it arrived at the warehouse, who picked it up and when, which work order authorized the pickup, which report consumed it, and which validator approved the consumption. If a discrepancy surfaces during an audit, the answer is not "we will investigate" — the answer is a query.

What This Changes

The shift from clipboard-based tracking to system-enforced chain of custody does not eliminate shrinkage entirely. Workers can still report inaccurate quantities. Materials can still be damaged or wasted in ways that are difficult to track. But it eliminates the category of shrinkage that comes from the chain simply not being recorded — which, in most organizations, is the majority of the gap.

It also changes the conversation with auditors and clients. Instead of "we count everything quarterly and write off the difference," the answer becomes "every material movement is recorded with a timestamp, a location, an authorization code, and an immutable transaction. Here is the export." That is a different level of accountability, and in procurement-heavy operations, it is increasingly the expected one.

Summary

Material shrinkage in field operations is mostly accounting failure, not theft — the gap between what was issued, what was installed, and what was reported, recorded in three different places with no automatic link between them.
The chain of custody breaks at every handoff: warehouse to worker, worker to installation, installation to report. Each break is a place where quantities drift and records diverge.
QR authorization codes on work orders tie the pickup to the plan. The system validates authorization, availability, and identity before any transfer completes. Every pickup is a timestamped, GPS-located transaction — no clipboard.
Reports document installation and automatically create consumption transactions. The system flags mismatches between pickup quantities and reported consumption for validator review.
Every inventory transaction is immutable — no edits, no deletes. Corrections create new adjustment transactions with required reason codes. The original record stays.
The result is a complete, queryable history for every piece of material: arrival, pickup, authorization, consumption, validation. Audit answers are queries, not investigations.