Offline Field Data Capture: The Record Written Where the Work Happened
A steel tank interior, a turnaround deck and a remote right-of-way have no signal, so the record either gets written on the device at the point of examination or it gets reconstructed hours later from memory. Offline field data capture holds the record locally until a network returns. Auditors are trained to tell the two apart.
Offline capture is the capability inspection companies ask about first, and the one vendors describe most loosely. Ask how a tool behaves when the tablet loses signal on the way into a vessel and the answer gets vague, because most tools degrade to a read-only cache: you can look at the job, you cannot complete it. The distinction matters more than any feature list. A record created at the point of examination carries the examiner's identity, the device clock, the component it belongs to and the photograph taken beside it. A record typed up in a truck at nine that evening carries a memory of all four. Both look identical in the finished PDF. They are not identical to an auditor who asks when the reading was taken, and they are not identical to the engineer who later has to trust the number.
Source: US FDA data integrity guidance and the ALCOA / ALCOA+ framework used by FDA, MHRA and WHO (attributable, legible, contemporaneously recorded, original, accurate, plus complete, consistent, enduring, available); 10 CFR 50 Appendix B, Criterion XVII, quality assurance records; 29 CFR 1910.119(j)(4)(iv), OSHA process safety management inspection and test documentation; NFPA 70 (National Electrical Code) Article 500 hazardous location classification and the definition of intrinsic safety; 29 CFR 1910.307, hazardous (classified) locations. Statements about Atlantis describe our own offline-first build.
| Field condition | Why connectivity fails | What the technician does instead | Record risk it creates | What genuine offline capture changes |
|---|---|---|---|---|
| Tank, vessel, column or boiler interior | The steel shell attenuates radio frequency energy and the man-way is the only aperture; this is physics, not carrier coverage | Writes readings on a glove, a permit or a photocopied shell map | Transcription errors, rounded values, timestamps that record typing rather than examination | Local-first storage with device-clock timestamps at the point of examination |
| Turnaround deck and scaffold at height | Several thousand contractors saturate available spectrum; contractor devices are excluded from site Wi-Fi | Photographs on a personal phone, notes in a messaging app | Images separated from the record, no binding to the weld or component | In-app camera writing directly into the job against a component identifier |
| Class I Division 1 classified area | Only intrinsically safe equipment is permitted; a consumer tablet is a potential ignition source | Paper only, or no record taken until leaving the area | A paper record with no chain into the report and no examiner attribution | Paper parity — a printed form matching the digital one field for field, plus intrinsically safe hardware where it is justified |
| Remote pipeline right-of-way, wellpad or terminal | No cellular coverage across large parts of the route | Batch entry that evening from a truck or motel | Contemporaneity lost for an entire day of work across several examiners | Queue-and-forward sync that transmits when coverage returns, keeping original capture times |
| Subsea, vault, culvert or underground plant | Physical shielding, and the examiner is often not the person reviewing | Video or data reviewed and recorded later by someone else | The recorded observer is not the person who made the observation | Explicit examiner and reviewer attribution on separate fields of the same record |
| Client site where personal devices are prohibited | Site security policy rather than signal | Dictation to the office by phone, or handwritten notes handed over | Third-hand data entry, with two people between the reading and the record | An approved offline device with no network dependency during the shift |
Where the signal actually dies
A steel tank interior is a shielded enclosure. The shell attenuates radio frequency energy, the man-way is the only meaningful aperture, and a technician thirty feet in on a shell course has no cellular service and no Wi-Fi by physics rather than by policy. The same applies inside vessels, columns, boilers, hulls, and the lower levels of concrete structures. No carrier upgrade changes this, and no vendor claim about coverage survives its first confined-space entry with a permit and a hole watch.
Turnaround decks fail differently. Coverage exists but is unusable: several thousand contractors on one site saturate the available spectrum, guest networks are not extended to contractors, and many owners prohibit personal devices on the unit entirely. The technician at the top of a scaffold has bars on the screen and nothing moving through them. Software assuming intermittent-but-present connectivity behaves worse here than software assuming none, because it retries, times out, and locks the form mid-entry while somebody waits on a rope.
Then there is geography. Pipeline rights-of-way, wellpads, remote terminals, offshore platforms with metered satellite links, vaults and underground plant. Across all of them the shared property is that the moment of examination and the moment of connectivity are separated by hours. Everything on this page follows from that separation, and every design decision in a field tool is really a decision about what happens inside that gap and who ends up carrying the consequences.
The reconstruction problem
Watch what actually happens when a tool cannot capture offline. Readings go onto a glove, a scrap of paper, the back of a permit, or into a phone's notes app. Indication locations get marked in pen on a photocopied weld map. Then, hours later, in a truck or a site office or at a motel desk, one person types up a full day of work for a whole crew, from notes taken by several people in bad light while wearing gloves. Nobody in that chain is being careless.
The degradation is specific and predictable. Exact thickness readings get rounded to convenient numbers. Indication positions drift by inches. Instrument settings, gain, calibration block references and couplant condition are recalled rather than recorded. Surface condition and temperature go in as whatever the weather was that day. Times of examination become the time of typing. None of this is dishonest. It is what fatigue does to numbers, and it is the mechanism by which competent field work turns into a weak record.
Transcription then adds a second, independent error source. Every handwritten value is read once and typed once, usually by someone who was not present at the examination and cannot query an ambiguous digit. A five-crew turnaround day can push a thousand readings through that funnel. The failure is invisible in the finished PDF, which looks exactly like a report produced from a contemporaneous record — and that is precisely why auditors developed methods for telling the two apart.
Contemporaneous is a defined property, not a figure of speech
The regulated-industry vocabulary for this is ALCOA. The US FDA's data integrity guidance anchors trustworthy records to five attributes: attributable, legible, contemporaneously recorded, original, and accurate. The expanded ALCOA+ formulation used by MHRA, WHO and others adds complete, consistent, enduring and available. The framework comes from life sciences rather than from NDT, and it transfers directly, because both disciplines are making the same argument — that a record can be trusted after the event it describes.
Contemporaneous means recorded at the time of the activity. A reading typed at 21:40 for an examination performed at 10:15 is not contemporaneous, however accurate it happens to be. Attributable means the record identifies who produced it, which is the same requirement 10 CFR 50 Appendix B, Criterion XVII expresses when it demands that inspection and test records identify the inspector or data recorder, the type of observation, the results, the acceptability, and the action taken in connection with any deficiencies noted.
Auditors detect reconstruction by pattern. A day of examinations sharing one timestamp. Uniform handwriting across records supposedly produced by four different technicians. Sequential entries at impossibly regular intervals. Readings that are all round numbers when the instrument resolves to three decimal places. None of these prove anything alone, and all of them expand the sample. A device-clock timestamp written at the point of examination and attributed to the examiner who performed it ends that line of questioning immediately.
Conflict resolution on sync, which nobody demonstrates
Two technicians work one tank. Both take the job onto a device in the morning, both go offline, both add readings against overlapping component lists, and both come back into coverage at four in the afternoon. Somebody's data is now at risk. This scenario is entirely ordinary in field NDT, and it is the scenario vendors skip in demonstrations, because it is the hardest part of the engineering and the least impressive thing to put on a screen during a sales call.
Last-write-wins is the common implementation and the wrong one. The second device to reach the network silently overwrites the first, and the loss surfaces weeks later when a component has no readings against it and nobody can say why. The correct model treats measurements as append-only rows keyed to the component and the examiner, so two offline sets merge rather than collide. Genuine conflicts — the same component read twice with different values — belong in an explicit queue for a Level II or Level III to resolve, with both original entries preserved and both examiners named.
Ask any vendor to show you the conflict queue. Not a slide about sync architecture — the actual screen where two contradictory offline entries are presented side by side and a qualified person chooses between them. If that screen does not exist, the product resolves conflicts by discarding data, and it will do so silently on your jobs. This is the single most useful question in a field capture evaluation, and it takes thirty seconds to ask.
Photographs and sketches are records, not attachments
A photograph in a camera roll is evidence of nothing. A photograph captured inside the job, bound to a component identifier, stamped with the device clock and attributed to the examiner is part of the inspection record. The difference is not storage, it is the join. Field tools that open the system camera and ask the technician to attach files later have already lost the binding, because the attaching happens during the same tired evening as the transcription, by the same person, from the same imperfect memory.
Sketches carry the same requirement. Weld maps, tank shell course layouts, condition monitoring location grids and nozzle schedules are how location is communicated, and location is what makes a reading actionable to an engineer. Annotation drawn over a captured photograph, or over a loaded drawing, keeps the mark and the measurement inside one object. A technician marking a paper map that is scanned separately has produced two records that somebody downstream must be trusted to correlate correctly.
Media also changes sync design. Measurement rows are small and must move first; photographs and video are large and can follow. A field tool that blocks the upload of a completed job until a hundred megabytes of images have crossed a marginal link will be worked around by technicians, and the workaround is always paper. Sync ordering looks like an implementation detail and is actually the decision that determines whether the system gets used at all.
What offline has to mean before it is worth anything
Offline is used loosely enough to be meaningless in a feature list, so define it by capability instead. Can the technician create a new job record with no network? Edit and complete an existing one? Capture photographs and sketches into it? Apply acceptance criteria and record a disposition? Sign it? A product answering no to any of these has a cache, not offline capture, and the cache fails at the exact moment the man-way closes behind the crew.
Reference data has to travel too. Acceptance criteria, procedure revisions, technique sheets, component registers, prior readings for comparison, and the current calibration status of the instrument in hand all need to be resident on the device before the crew leaves the trailer. Prior readings matter most: a corrosion rate calculation needs the last inspection's numbers at the same location, and a technician who cannot see them offline is recording a disposition without the comparison the code expects them to make.
This is why we treat field capture as the foundation of the reporting stack rather than as a mobile add-on bolted to a desktop product. Our NDT inspection software is built local-first, and the same architectural point drives the evaluation criteria in our review of the best NDT reporting software for 2026. A reporting tool producing beautiful PDFs from data typed the following morning has optimised the visible half of the problem and left the half that gets audited alone.
In classified areas the device itself is regulated
In classified areas the hardware is a compliance object. NFPA 70 Article 500 classifies locations by the presence of flammable gases, vapours and combustible dusts, and Class I Division 1 covers areas where ignitable concentrations can exist under normal operating conditions. Equipment in those areas must be incapable of releasing enough electrical or thermal energy to ignite the atmosphere, which is what intrinsically safe certification establishes. A consumer tablet is a potential ignition source, and no protective case changes its classification or the site's decision about it.
The operational consequence is that some field capture happens on intrinsically safe devices with modest screens and slow processors, and some does not happen on a device at all. A field tool therefore needs paper parity: a printable form matching the digital form field for field, so a record started on paper inside a classified area transfers into the system without being reinvented. Parity also means the paper form carries the component identifiers and the examiner attribution the digital record would have captured automatically.
Method choice shapes what gets captured. Ultrasonic work produces dense numeric data, grids of thickness readings that must land against a condition monitoring location, while radiography produces images, densities and shot records with entirely different field requirements — a contrast we set out in our comparison of RT and UT for weld inspection. Both need the instrument serial number and its calibration state captured at the point of use, which is the link straight into equipment calibration tracking.
The audit moment where this pays for itself
Return to the traceback. An auditor holds a completed report and asks a simple question: when was this reading taken, and by whom? A contemporaneous record answers on one screen — examiner, device timestamp, component identifier, instrument serial number, the photograph captured alongside it. A reconstruction answers with a report date, and the auditor's next question is how the report date relates to the examination date, which is the point at which firms start explaining rather than showing.
The same record does operational work long before any audit. Engineering trusts numbers captured at the point of examination more than numbers typed later, and that trust shortens the loop between an inspection finding and a repair decision. Corrosion rates computed from contemporaneous readings hold up under review; rates computed from rounded transcriptions produce remaining-life numbers nobody wants to sign their name against. Field capture is a data quality investment that happens to also be a compliance one.
It closes the commercial loop as well. A job whose field record has synced, been reviewed and been signed is a job that can be invoiced, which is why our QuickBooks integration draws from the job record rather than from a separate billing sheet: no complete record, no invoice, no disputed line items three weeks later. Atlantis builds this offline-first — affordable, accessible and fully customisable to your methods and your forms. Ask for a demo or a quote, and bring your worst-connectivity site.
What counts as genuinely offline field capture?
Create, edit, complete, photograph, sketch, apply acceptance criteria and sign — all with no network, then sync when one returns. Anything less is a read-only cache. The real test is whether a technician can start a job they have never opened before while standing inside a vessel, because a turnaround produces that situation several times a day. Ask a vendor to demonstrate it in airplane mode.
What happens if two technicians edit the same job offline?
In a well-built system, measurements are append-only rows keyed to the component and the examiner, so two offline sets merge instead of colliding, and genuine contradictions land in a conflict queue for a Level II or Level III to resolve with both originals preserved. In a poorly built one, the second device to reach the network silently overwrites the first. Ask to see the conflict queue.
Can we use a standard tablet inside a classified area?
No. NFPA 70 Article 500 classifies hazardous locations by the presence of flammable gases, vapours and combustible dusts, and equipment used where ignitable concentrations can exist must be incapable of releasing enough electrical or thermal energy to ignite the atmosphere. That is what intrinsically safe certification establishes, and a protective case does not confer it. Plan for intrinsically safe hardware or paper parity.
Is a record typed up that evening acceptable?
It is a reconstruction, and auditors are trained to recognise one. The FDA's data integrity guidance names contemporaneous recording as an attribute of a trustworthy record, alongside attributable, legible, original and accurate. A report produced from evening transcription can be perfectly accurate and still fail the contemporaneity test, which widens the audit sample rather than closing it. The finished PDF looks identical either way.
Do photographs taken offline keep their attribution?
Only if they are captured inside the job rather than through the system camera and attached later. A photograph bound at capture to the component identifier, the device clock and the examiner is part of the record. A file dragged in from a camera roll the following morning is an attachment whose provenance the auditor has to take on trust. Insist on in-app capture bound to the component.
Why does prior inspection data need to be on the device?
Because dispositions depend on comparison. A corrosion rate needs the previous reading at the same condition monitoring location, and a technician who cannot see it offline is estimating remaining life from a single point. Reference data — acceptance criteria, procedure revisions, component registers, prior readings and the instrument's calibration status — must be resident before the crew leaves the trailer. Sync down matters as much as sync up.
Built for any business that runs on operations
Most companies do not fail at their craft. They lose time, margin and goodwill in the gaps between the tools they use to run the place — a quoting spreadsheet that does not talk to the job sheet, a job sheet that does not reach accounts, and a compliance folder nobody can search when a client asks. Atlantis closes those gaps by putting the whole operation on one platform, so information is entered once and everything downstream stays in step.
What you can run on it
- Sales and CRM — leads, quotes, follow-ups and the pipeline that tells you what next month looks like.
- Projects and job costing — plan the work, track the hours and materials against it, and see the margin while the job is still live rather than at final account.
- Field and service teams — dispatch, schedules, mobile capture that works with no signal, and sign-off from site.
- Inventory and purchasing — stock, suppliers, reorder points and goods receipt, joined to the jobs that consume them.
- People — records, qualifications and licences with renewal reminders, timesheets, leave and payroll.
- Quality and documents — procedures and forms under revision control, with the audit trail an inspection or accreditation body actually asks for.
- Accounts — invoicing, expenses, multi-currency and the reporting your accountant stops chasing you for.
Affordable, accessible, fully customizable — and we mean each word
Affordable because the whole suite is included rather than sold to you a module at a time, and because implementation is done by people who have run operations rather than by a chain of subcontractors. Accessible because it runs in a browser and on a phone, works for a small team on day one, and does not need a specialist on staff to keep it alive. Fully customizable because your process is the thing that makes you competitive — the software should bend to it, not the other way round.
Industries we configure for
Service businesses and contractors, manufacturing and fabrication, trading and distribution, laboratories and testing houses, engineering consultancies, construction and facilities, and asset owners across energy, marine, aerospace and infrastructure. Inspection and testing is where we started, and it remains the sector we go deepest in — but the platform underneath is general-purpose, and most of what it does has nothing to do with inspection at all.
What happens when you get in touch
A short conversation, not a sales sequence. We ask how the business runs today and where it hurts, show you the platform doing that work, and send a written quote shaped to your region, your team size and the scope you actually need. No obligation, nothing to install first, and no pressure to decide on the call. Reach out and tell us what you are trying to fix.
Related: business management platform · inspection management software · choosing the right category of software · modules · by industry · asset integrity platform. Book a free consultation.