Skip to main content

Field notes

Field notes for industrial inspection teams. Written from the record.

Practical writing for inspection, NDE, integrity, turnarounds, compliance, rollout, and security teams.

Request a topic
Open resources

The shelf

Every note, searchable by workflow, standard, or role.

Buyer guidance

Inspection program KPIs worth tracking

Most inspection dashboards track activity, not health. Eight measures that reveal backlog risk, data quality, and whether findings actually close.

Jul 14, 2026 · 6 min read
Buyer guidance

Grounded AI for inspection: answers with citations

Generic chatbots guess. Grounded retrieval answers from your own inspection records and cites them, so every claim can be checked before it is trusted.

Jul 13, 2026 · 6 min read
Buyer guidance

What audit-ready actually means in software

Every vendor claims audit-ready. The term has testable content: attribution, immutability, completeness on demand, and evidence that opens from the record.

Jul 11, 2026 · 6 min read
Buyer guidance

Migrating inspection history, audit trail intact

Decades of readings in spreadsheets and PDFs are an asset, not a liability, if the migration preserves identity, units, and provenance.

Jul 10, 2026 · 6 min read
Buyer guidance

SSO for field apps: identity without friction

Single sign-on for inspection software has to survive gloves, shared devices, and offline sessions. What IT should require and what the field can tolerate.

Jul 09, 2026 · 5 min read
Buyer guidance

Training field crews on new inspection software

Classroom sessions do not make field adoption. What works: route-based training, peer champions, offline-first confidence, and killing the paper copy.

Jul 08, 2026 · 5 min read
Buyer guidance

Why shared drives fail audits

Folder trees of PDFs pass casual review and fail real audits. The gaps are structural: no completeness check, no attribution, no reliable retrieval.

Jul 07, 2026 · 5 min read
Buyer guidance

When Excel stops scaling for inspection data

Spreadsheets carry inspection programs further than anyone admits, until they fail in specific ways: identity drift, formula rot, and single-owner risk.

Jul 06, 2026 · 5 min read
Buyer guidance

The business case: four ROI drivers that hold up

Inspection software business cases fail on inflated claims. Four drivers survive finance review: admin time, re-inspection, turnaround days, audit prep.

Jul 04, 2026 · 6 min read
Buyer guidance

How inspection software pricing actually works

Per-user, per-site, and facility licensing explained: what drives inspection software cost, where the hidden line items are, and how to compare quotes.

Jul 03, 2026 · 6 min read
Buyer guidance

Roll out one unit first. Then the site.

Why a single-unit pilot beats a site-wide launch for inspection software: scope, success criteria, and the signals that say expand or stop.

Jul 02, 2026 · 5 min read
Turnaround & reliability

Closeout packages, assembled as the work happens

Closeout is where turnaround schedules quietly die. The fix is structural: build the package during execution instead of after it.

Jul 02, 2026 · 5 min read
Buyer guidance

Scoring vendors on inspection data migration

A practical scorecard for comparing how inspection software vendors handle legacy data: identity mapping, provenance, verification, and ownership.

Jul 01, 2026 · 6 min read
Buyer guidance

A security review checklist for inspection software

A practical security review checklist for inspection software: identity, RBAC, tenant isolation, audit immutability, export rights, and residency.

Jun 27, 2026 · 6 min read
Buyer guidance

IDMS vs CMMS: different jobs, one thread

The CMMS manages work, the IDMS manages condition. Sites get in trouble forcing one to do the other's job. The real design question is the thread between them.

Jun 24, 2026 · 5 min read
Buyer guidance

Twelve questions for any inspection software demo

Demos are optimized to look good. These twelve questions, asked of any vendor, surface the differences that show up in year two instead of on the screen.

Jun 20, 2026 · 6 min read
Buyer guidance

What an IDMS is, and when you need one

What an inspection data management system actually does, and the signs a site has outgrown spreadsheets and shared drives.

Jun 18, 2026 · 6 min read
Standards in practice

What API 510 actually asks of your inspection records

The pressure vessel code is specific about what an inspection record must carry. Most programs fail the record, not the inspection.

Jun 18, 2026 · 6 min read
Turnaround & reliability

Turnaround KPIs the record can actually prove

Most turnaround KPIs are assembled by hand after the fact. A KPI you cannot trace to records is an opinion with a decimal point.

Jun 16, 2026 · 5 min read
Turnaround & reliability

Relief valve overhaul records in a turnaround

Hundreds of valves, one shop, one window. The overhaul record that satisfies the auditor is built valve by valve during the outage, not reconstructed after it.

Jun 13, 2026 · 5 min read
Turnaround & reliability

Post-turnaround baselines: reset the record

After repairs and replacements, old thickness data describes equipment that no longer exists. The weeks after startup are when the record resets.

Jun 11, 2026 · 5 min read
Turnaround & reliability

Discovery work: keeping scope growth honest

Discovery scope is inevitable in a turnaround. What is optional is losing control of it. A disciplined finding-to-decision path keeps growth honest.

Jun 09, 2026 · 5 min read
Turnaround & reliability

Managing NDE subcontractor data during outages

Subcontracted NDE produces the evidence your integrity decisions rest on. Set the data contract before mobilization or spend closeout chasing it.

Jun 06, 2026 · 6 min read
Turnaround & reliability

Exchanger bundle inspection in a turnaround window

Bundle inspection is a race against the pull schedule. The record-keeping choices you make before the pull decide whether the data survives it.

Jun 04, 2026 · 6 min read
Turnaround & reliability

Punch lists that close themselves

A punch list maintained as a spreadsheet is stale the moment it prints. Derive it from the record instead, and it closes as the work does.

Jun 02, 2026 · 5 min read
Turnaround & reliability

Scoping turnaround inspection work from history

The best predictor of what a turnaround will find is what the last three found. How to mine equipment history into a defensible inspection scope.

May 31, 2026 · 6 min read
Turnaround & reliability

Turnaround readiness gates: the inspection view

Readiness gates check scaffolding and materials but often take inspection readiness on faith. What the inspection function should certify at each gate.

May 27, 2026 · 5 min read
Field workflow

Inspection scheduling: due dates that defend themselves

An inspection due date is a conclusion, not a calendar entry. It should carry its basis, recalculate when inputs change, and survive an auditor's why.

May 22, 2026 · 5 min read
Field workflow

A requirements checklist for mobile inspection apps

The demo always works on office wifi. A field-tested checklist for evaluating mobile inspection software: offline behavior, data model, capture, and audit trail.

May 19, 2026 · 6 min read
Field workflow

Findings triage: from anomaly to work order

The distance between observing a defect and raising a work order is where inspection programs earn or lose their credibility. A triage pipeline, step by step.

May 15, 2026 · 5 min read
Field workflow

Building an equipment register that survives

Every inspection record hangs off an equipment identity. Registers decay through renames, spreadsheet forks, and turnover. Here is what durable looks like.

May 12, 2026 · 6 min read
Field workflow

What makes a field signature defensible

A signature is a claim about who approved what, when, based on which evidence. Most field sign-off practices cannot back that claim up.

May 08, 2026 · 5 min read
Field workflow

Shift handoffs that do not lose inspection data

Inspection data goes missing at shift change more than anywhere else. What a handoff looks like when the record, not the conversation, carries the state.

May 05, 2026 · 5 min read
Field workflow

Drone and rope-access data in the equipment record

Aerial and rope-access inspections produce excellent data that rarely reaches the equipment record. The fix is treating access as a method, not a silo.

May 02, 2026 · 5 min read
Field workflow

From visual finding to NDE request, without email

The handoff from a visual finding to a follow-up NDE request is where evidence and context go missing. A structured request path fixes it.

Apr 29, 2026 · 5 min read
Field workflow

UT thickness data: from gauge to defensible record

A thickness reading is only as good as its chain of custody. How CML identity, calibration context, and same-shift sync turn gauge output into evidence.

Apr 26, 2026 · 5 min read
Field workflow

Digital inspection forms vs paper: the real gains

The pitch for digital forms is usually speed. The real gains are validation at capture, structure you can query, and records that never fork.

Apr 25, 2026 · 6 min read
Field workflow

Making inspection photos auditable evidence

A camera roll full of rust photos proves nothing. What separates a snapshot from evidence: identity, context, timestamp, and chain of custody.

Apr 21, 2026 · 5 min read
Field workflow

Voice capture in the field: hands stay on the work

Gloved hands, live gauges, and confined spaces make typing the wrong input method. What voice capture changes about field data quality, and its limits.

Apr 17, 2026 · 5 min read
Field workflow

Why offline-first matters in inspection apps

Inspection work happens in tank interiors, remote right-of-ways, and steel canyons with zero signal. Software that assumes connectivity fails the field.

Apr 13, 2026 · 5 min read
Standards in practice

DICONDE, explained for integrity teams

DICONDE is the ASTM standard that keeps radiographic and UT images readable and traceable for decades. What it is, and why integrity teams should care.

Apr 09, 2026 · 5 min read
Standards in practice

Relief valve inspection intervals under API 576

API 576 ties relief valve intervals to service history, not a fixed clock. Defending an interval means producing the as-received record behind it.

Apr 05, 2026 · 6 min read
Standards in practice

Deadlegs: where piping programs quietly fail

Deadlegs corrode on their own schedule, not the circuit's. Why they escape thickness programs and how to bring them back under control.

Apr 01, 2026 · 5 min read
Standards in practice

Corrosion under insulation: an inspection strategy

CUI hides under jacketing that looks fine and attacks equipment that reads healthy. A strategy for prioritizing, inspecting, and recording it.

Mar 28, 2026 · 6 min read
Standards in practice

Coating hold points AMPP inspectors actually check

Coating failures trace back to skipped hold points, not bad paint. The checkpoints an AMPP certified inspector will not let a crew talk past.

Mar 24, 2026 · 6 min read
Standards in practice

NFPA 25 records: proving fire system inspection

NFPA 25 sets the inspection, testing, and maintenance clock for water-based fire systems. The record is what proves the clock was kept.

Mar 20, 2026 · 5 min read
Standards in practice

OSHA PSM mechanical integrity: the paper trail

The mechanical integrity element of OSHA PSM is won or lost on documentation. What the citation history says auditors actually look for.

Mar 16, 2026 · 6 min read
Standards in practice

Circuitization: grouping piping the defensible way

A piping circuit is a corrosion argument, not a drawing convenience. The grouping rules that survive audit, and the boundaries that break programs.

Mar 14, 2026 · 6 min read
Standards in practice

ASME PCC-2 repairs and the inspection record

A repair is only as good as the file it leaves behind. What PCC-2 methods require of documentation, and why temporary repairs are where records fail.

Mar 10, 2026 · 6 min read
Standards in practice

Remaining life: the calculation auditors check

Actual minus required, divided by rate. Three inputs, each with its own failure mode, and the half-life rule that turns the result into an interval.

Mar 06, 2026 · 6 min read
Standards in practice

Corrosion rates: short-term vs long-term math

Two rates, one rule: the interval stands on the more conservative result. The arithmetic, why the two diverge, and how measurement noise fools both.

Mar 02, 2026 · 5 min read
Standards in practice

CML selection: how many locations are enough

CML count is not a coverage contest. How to place condition monitoring locations by mechanism, defend the density, and prune without losing history.

Feb 26, 2026 · 6 min read
Standards in practice

When to run an API 579 fitness-for-service

Fitness-for-service is the disciplined answer when equipment no longer meets its original acceptance basis. When to trigger it, and what each level costs.

Feb 22, 2026 · 6 min read
Standards in practice

Damage mechanisms: putting API 571 to work

API 571 is a library, not a checklist. How to turn mechanism descriptions into susceptibility calls, monitoring choices, and a defensible record.

Feb 18, 2026 · 6 min read
Standards in practice

Implementing risk-based inspection in seven steps

RBI succeeds or fails on sequence. The seven steps from data collection to evergreening, and the record each step has to leave behind.

Feb 14, 2026 · 7 min read
Standards in practice

API 580 vs API 581: what each one governs

One sets the rules for a credible RBI program, the other supplies the math. Where API 580 ends, where API 581 begins, and what auditors check in each.

Feb 10, 2026 · 5 min read
Standards in practice

API 653 tank inspection intervals, explained

Tank intervals hinge on the bottom you cannot see. How API 653 external, ultrasonic, and internal clocks are actually set and defended.

Feb 06, 2026 · 6 min read
Standards in practice

API 570 piping inspection: what the record must carry

Piping circuits fail audits on the record, not the fieldwork. What API 570 expects a defensible piping file to contain, CML by CML.

Feb 02, 2026 · 6 min read

Editorial lanes

Four lanes. One bar: it must help a reader decide.

FIELD 01

Field workflow

What actually happens at the asset: visual findings, NDE requests, photos, signatures, and handoffs.

STD 02

Standards in practice

How API, ASME, AMPP, NFPA, OSHA, and site procedures shape the record teams defend later.

TURN 03

Turnaround and reliability

Readiness gates, CML history, RBI inputs, repair decisions, and closeout evidence in one operating thread.

BUYER 04

Security and rollout

Identity, data migration, procurement, support, and the path from first workflow to facility rollout.

Answers

Field Notes questions

What does Field Notes cover?

Four lanes: field workflow (what happens at the asset), standards in practice (how API, ASME, AMPP, NFPA, and OSHA language shapes software), turnaround and reliability, and buyer guidance on security, rollout, and data migration.

Who is Field Notes written for?

Inspection leads, NDE technicians, reliability and integrity engineers, turnaround planners, and the IT and procurement people evaluating inspection software.

How is this different from a typical vendor blog?

One editorial bar: an article publishes only if it helps a reader run a workflow, apply a standard, or make a buying decision. No filler and no generic thought leadership.

Looking for a topic that is not here yet?

Ask for material by workflow, standard, or buying role. We will point you to the right page or review it live.

Request a topicOpen resources