← All posts
field inspectionoffline-firstcomputer visionfiber networksutilities4 min read

Why Your Field App Should Read Serial Numbers Without a Signal

By the Forge team ·

Crews work in basements, cabinets, and dead zones, yet reading a serial number off a cable still tends to demand a cloud round-trip. We tested fully offline, on-device text reading and saw 98-99% accuracy on short equipment codes.


The reality of field work: signal you can't count on

Your crews don't work in offices. They work in cable cabinets, basement risers, underground chambers, plant rooms, and the kind of remote sites where one bar of signal is a good day. That's just the nature of inspecting fiber, utility, and infrastructure assets, the equipment you need to check is exactly where the network isn't.

So when a field app depends on a cloud connection to do its job, it inherits every dead zone your crews walk into. The app stalls, the technician waits, and a five-second task turns into a frustrating two-minute one, repeated dozens of times a shift. Multiply that across a workforce and across a year, and 'the app is slow on site' becomes a real operational cost.

The everyday task that keeps needing the cloud

Here's a task your teams do constantly: reading a code off a piece of equipment. A serial number stamped on a unit. A marking printed along a cable. A label on a component in a cabinet. Capturing that text accurately is the backbone of asset tracking, warranty checks, and audit trails.

Today, a lot of field apps handle this by sending the photo up to a cloud service to be read, then waiting for the answer to come back. That's an upload-and-poll round trip: snap the photo, push it over the network, wait for processing, wait for the result. It works fine on office wifi. In a basement, it's the single slowest moment in the whole inspection, and it puts you at the mercy of a third-party cloud just to read a few characters.

Reading a few characters off a cable shouldn't depend on a third-party cloud.

Offline, on the device: 98-99% accuracy on short codes

We wanted to know whether that round trip is actually necessary for this specific task. So we tested reading text directly on the phone, no connection, nothing leaving the device, using a compact on-device model format that runs on the handset's own processor.

On short alphanumeric strings, the kind of serial numbers and equipment codes crews read every day, such as 'SN: A4F-2291-X', on-device reading reached 98-99% accuracy in our testing. That's strong enough to be genuinely useful for the everyday job of capturing a code in the field, with no signal required.

To be clear about scope: that figure is for short codes and serials, not general document or form reading. Long paragraphs, dense forms, and degraded text are a different problem. But short equipment codes are precisely what field crews need, and that's where the result lands.

98-99% accuracy on short equipment codes, fully offline, in our testing.

A tiny footprint that ships inside your app

A capability is only useful in the field if it actually fits on the phone. The recommended on-device approach is fully offline on both iOS and Android, with a bundled footprint of only around 5-10MB.

That's small enough to ship inside your existing field app without bloating downloads or eating storage. There's no separate install, no model to fetch over a flaky connection, and no setup step for the technician. It's simply there, working, the moment they open the app, on the train, in the chamber, or three floors underground.

Faster, more reliable inspections, and data that stays put

Removing the cloud round trip changes the feel of the job. The read happens the instant the photo is framed, so a technician can capture a code, confirm it, and move on without waiting on a network they can't trust. Inspections get faster and, just as importantly, more predictable, the app behaves the same whether there's full signal or none at all.

It also changes where your data lives during the read. Because the text recognition runs on the device, the image doesn't have to leave the phone to be interpreted. That's a cleaner story for data control and a smaller dependency surface, one less external service standing between your crew and a finished inspection.

And because the output maps directly to the formats your systems already expect, it slots into existing workflows with minimal adapter code, so this is fast to wire into a real app, not a months-long integration.

How Forge can bring offline reading to your field app

This is what we mean when we say Forge is built for field inspection. Off-the-shelf cloud vision tools are powerful, but many of them are cloud-first by design, and a cloud-first tool struggles in exactly the places your crews spend their days. Offline-first reading is a capability those tools tend to leave on the table.

Forge lets your team build and deploy custom computer-vision capabilities, including offline, on-device reading of serials, cable markings, and component labels, without data scientists or outside consultants. You bring the equipment and the codes your crews actually read; we help you turn that into something that runs on their phones.

To be straight with you: offline on-device reading is a capability we've tested and that Forge can deliver, framed here as a tested result rather than a finished, off-the-shelf feature. If your crews work where the signal doesn't, this is worth a conversation.

How we measured this. The 98-99% figure comes from our own focused testing on short alphanumeric strings such as serial numbers and equipment codes. It is not a general document- or form-reading benchmark, and accuracy on longer or lower-quality text will differ.

Build your own AI. No code required.

Train a computer-vision model on your own faults and put it in your team's hands, no data scientists, no consultants.

See Forge in action, book a demo