A visual inspector spots blistering on a vessel shell. What happens next, on most sites, is an email: a couple of photos, a paragraph of description, a guess at the location, sent to whoever coordinates NDE. From there the finding enters a queue with no status, no link back to the equipment record, and no guarantee the UT crew shows up at the right spot.
What the email actually loses
The email handoff feels fast because writing it is fast. The cost lands later, in four places.
- Location precision. "North side, about ten feet up, near the manway" sends a rope-access team to the wrong quadrant. The inspector knew the exact spot; the email could not carry it.
- The evidence trail. The photos live in a sent-items folder. When the NDE report comes back, nobody joins it to the original finding, so the equipment record shows a UT survey with no stated reason and a visual finding with no stated resolution.
- Status. Between the send and the survey there is no state. Was it received, scoped, scheduled, done? The inspector's only tool is a follow-up email, and follow-up emails are how findings age silently into the next turnaround.
- Priority logic. An inbox sorts by arrival time. A finding queue should sort by severity, equipment criticality, and due date. The two orderings agree only by accident.
The structured alternative
The mechanics of a clean handoff are not complicated. They require that the finding, the request, and the result all live on the same equipment record.
- The finding is captured in place. Photos, dimensions, and a location pinned against the component, not described in prose. If the inspector tagged the spot on the vessel's drawing or its scan, the NDE crew inherits that pin.
- The NDE request is raised from the finding. One action on the finding itself: requested method, extent, and priority. The request carries every photo and measurement automatically, because it is a child of the finding, not a retelling of it.
- Routing follows rules, not memory. The request lands with the NDE coordinator with severity and equipment criticality already attached, and it sits in a visible queue with a state: raised, scoped, scheduled, in progress, reported.
- The result closes the loop. When the UT grid or shear-wave report is filed, it attaches to the request, which attaches to the finding. The equipment record now reads as a sentence: blistering observed, UT requested, thickness confirmed above minimum, finding closed.
The compounding effect
Sites that make this switch notice the second-order effects more than the first. NDE crews stop burning hours relocating findings. Coordinators can answer "what is open on this unit" without reconciling an inbox against a spreadsheet. And when the same vessel shows blistering again three years later, the new inspector opens the record and sees the whole prior chain, not a rumor that "we looked at this once."
The uncomfortable audit question is always the same: show me how this finding became this survey. If the answer runs through a mailbox, the trail is only as durable as somebody's inbox retention policy.
In intelliSPEC, an intelliINSPECT finding raises the NDE request directly and the intelliNDT result closes it, all on the same equipment record. If your current handoff runs on email, bring a real example to a demo and trace it end to end.
