William Kelly, a surveyor tasked with mapping the rugged limestone shorelines of the Great Lakes, carried a government-issued logbook that weighed nearly five pounds. It was bound in thick calfskin and filled with high-grade rag paper intended to survive a century of archival storage.
He also carried a heavy brass theodolite, a box of charcoal, and a three-foot chain. But when Kelly was actually waist-deep in the cedar swamps of Michigan, the calfskin logbook stayed in a waterproof oilskin wrap inside his pack. Instead, Kelly carried a small shard of roofing slate and a fragment of chalk.
He would scratch the day’s bearings and distances onto the slate while standing in the muck, copy them onto a scrap of paper tucked into the sweatband of his hat, and only at night-by the light of a fading fire and with the luxury of a flat rock for a desk-would he transfer the “official” truth into the heavy logbook.
, the calfskin logbook has been replaced by enterprise resource planning systems and sophisticated asset management platforms, but the shard of slate is still very much in use. It has simply evolved into a glass rectangle that fits in a pocket.
Miller reached the first machine, a excavator with a bucket large enough to hide a small car. He didn’t reach for the laptop. He didn’t even think about the eleven mandatory fields waiting for him in the “Asset Verification” module of the company’s core system.
Instead, he pulled out his personal phone. He snapped a photo of the serial plate, another of the hour meter, and a third wide-angle shot of the machine’s profile against a stack of concrete culverts.
Field Note: Unit 402, serial ends in 88, matching the lease, but the cab glass is cracked and the left track is at 20% life. Two others match. Leaving now.
By the time Miller climbed back into the air-conditioned cab of his truck, the “authoritative” record of those three million dollars’ worth of collateral lived in his camera roll, nestled comfortably between a photo of his daughter’s birthday cake and a picture of a grocery list.
We often talk about this as a “mobile access gap.” The IT department looks at Miller and sees a problem to be solved with a better mobile app, a more robust offline mode, or perhaps a lecture on data security. They see a failure of the official system to reach the edge of the organization.
But what is actually happening is far more profound: it is a substitution. A general-purpose tool with a near-zero adoption cost is holding the authoritative record of physical reality, and it will keep holding it regardless of what the official system eventually offers.
The institutional systems we build are not competing against each other; they are competing against the camera roll. And the camera roll is winning because it works while you are standing up.
📊
The Latency of Truth
“Device-Switching Latency” impact
68%
A survey of field operations across the industrial sector found that 68% of “data accuracy” issues were not caused by human error, but by what researchers called “device-switching latency.”
In plain human terms: if a person has to walk back to their truck or find a flat surface to record a number, they will lose roughly ten percent of the truth for every fifty feet they walk.
The brain is a high-speed processor that hates waiting for a login screen. By the time the laptop has woken up and the user has navigated through three sub-menus to find the “Asset Modification” screen, the vivid detail of the cracked cab glass has been smoothed over by the brain’s desire to just finish the task and get out of the heat.
I find myself doing this constantly. I will criticize a colleague for not updating a project board, and then three minutes later, I will record a vital piece of client feedback on the back of a receipt because opening the project management app feels like starting a car in mid-winter. It’s an act of friction-avoidance that we all participate in.
“If you ask a baker to weigh every gram of flour on a digital scale during a Saturday morning rush, they will eventually start measuring by the handful. The bread won’t wait for the Wi-Fi.”
– Drew J., Third-shift Baker
The dough is alive, the oven is hot, and the handful is “close enough” to be true. In the world of equipment finance, the “handful” is the photo in the camera roll.
The System of Delayed Memory
This creates a massive disconnect for the people who manage the back office. The operations and servicing leaders at equipment finance lenders-the people responsible for thousands of active contracts-are often making decisions based on a “system of record” that is actually a “system of delayed memory.”
The contract says one thing, the customer says another, and the truth is sitting in a field rep’s pocket, un-ingested and un-indexed.
When the billing doesn’t match the equipment on-site, or when a delinquency starts to creep up because the collateral has been moved or damaged, the legacy servicing systems usually require a “vendor ticket” or a massive manual workaround to fix. The “in-life” changes that define a lease or a loan are treated as exceptions rather than the rule. But in reality, the exception is the day nothing changes.
The challenge for modern equipment finance software is not to replace the camera roll, but to respect it. This is why the shift toward API-first architecture in portfolio servicing is so critical.
An API-first system doesn’t demand that every piece of data be birthed inside its own clunky interface. It acknowledges that data is born in the gravel yard, in the note-taking app, and in the “snap” of a smartphone camera.
The Sponge Principle
If the architecture is open, you can build a bridge. You can create a workflow where Miller’s photo is sucked into the system via a simple email or a lightweight web-hook, and the eleven mandatory fields are populated by the back office-or an AI assistant-at a later time. The system of record should be a sponge, not a gatekeeper.
It should be able to absorb the “shard of slate” and turn it into a governed, audited, and synchronized record without forcing the surveyor to walk back to the fire.
Servicing the Physical World
This is the reality of servicing a live portfolio. It is a messy, physical, gravel-strewn process. The lenders who thrive are not the ones with the most comprehensive “origination-to-end-of-term” monoliths; they are the ones who have a servicing engine that can stay in sync with the physical world.
They are the ones who understand that their contract records, collateral data, and customer information must be fluid enough to accommodate the way humans actually work.