How Is an NDT Work Order Managed?

The NDT work order must freeze the inspection scope and method, verify the suitable personnel and instruments before assignment, collect the field evidence under a single identity and not close the report before the technical review is completed.

Traceability is not writing a few serial numbers at the end of the report. It is being able to show in the same chain from whom the request came, which part or weld area was inspected with which procedure version, who performed the job with which competency, which instrument was used and how the result was approved.

Which scope should be frozen when the work order is opened?

Short answer: the customer request, inspection object, acceptance criterion, method, technique and the procedure version to be applied must be clear before the field assignment. An ambiguous “NDT will be performed” task is not sufficient for the correct personnel and instrument selection.

The order card should contain at least the customer and facility, project or order link, part/weld identity, location, distinguishing information on material and geometry, inspection scope, method and technique to be applied, reference documents, acceptance criterion, planned time and field safety notes. The inspection percentage or a numerical acceptance limit should be recorded only if it actually exists in the contract, code or approved procedure; the system must not generate a default number.

ISO/IEC 17020:2026 updates the framework for inspection bodies to operate competently, impartially and consistently, and counts data/information control among the change headings. This standard alone does not select a method for a specific weld. The technical result is this: the work order must link the organization's approved procedure and the contract scope with its version; it must not use the standard's name as an automatic method decision.

Why must changes not overwrite the old record?

If the scope changes before the field, the old and new value, the justification, the requester, the technical approver and the time stamp must be preserved. After the field has started, a change in part identity, method or acceptance criterion may require a new revision and re-evaluation. A silent update makes it ambiguous under which conditions the data was collected, even if the final report looks correct.

How is the personnel assignment verified?

Short answer: the person merely being “NDT personnel” is not enough; the method, technical responsibility, sector/scope in the work order and the organization's authorization rule must match valid records.

ISO 9712:2021 defines personnel qualification and certification requirements for industrial NDT methods including UT, RT, MT, PT and VT. The existence of a certificate record does not mean automatic suitability for every job. The assignment gate must check the relevant fields such as method, level, sector or product scope, validity, vision qualification record and employer authorization according to the scheme the organization applies.

ILAC P15 draws attention to defining the duties, responsibilities and authorities of positions affecting the management, performance, recording or reporting of inspection. For this reason, the roles of performer, supervisor, technical reviewer and report approver must not be squeezed into a single free-text field. If one person can take on more than one role, the basis for this in the organization's procedure and the audit trail must remain visible.

At which gates should instrument suitability be checked?

Short answer: instrument and accessory suitability must be verified not only when writing the report, but at assignment and at the field start. Identity, status and the relevant verification/calibration record must be linked to the order.

• Assignment gate: the instrument group, probe, reference block or consumable requirement suitable for the method and technique is determined.
• Field opening: the unique identity, usage status and the organization's current acceptance rule of the selected physical instrument are checked.
• Application record: the probe/accessories used, settings, surface and environmental conditions and the required intermediate checks are kept in a form appropriate to the method.
• Impact review: if an instrument is later found unsuitable, the work orders affected by it must be queryable.

The IAEA's NDT quality assurance guides address periodic calibration programs for inspection equipment and personnel training/qualification programs in the same record system context. The software decision that follows is not to give each instrument an arbitrary fixed period; it is to link the organization's approved instrument control rule, the validity evidence and the work order usage history.

How should the field record be linked to the report?

Short answer: every measurement, finding, photograph or raw file must be recorded with the work order and inspection area identity; when copied to the report, its source link must not be broken.

According to IAEA Training Course Series 48, the NDT report must carry the information needed for the acceptance decision, repair of the nonconformity and the ability to repeat the inspection. The same guide requires that records be able to show the procedure used, the data recording/analysis technique and the results in the future. Therefore the final PDF alone is not the whole record.

Method-specific fields should be opened with a versioned form template. For UT, the scanning arrangement, probe and setting records; for PT or MT, the materials and process conditions used; for VT, the access and observation context; for RT, additionally the authorized radiation safety process may be required. These examples are added on top of the common work order backbone; the methods are not forcibly merged in the same free form.

In offline field work, it is necessary not to confuse the instrument clock with the server clock, to store the user and instrument that created the record, and to resolve synchronization conflicts visibly. A later edit must not delete the old value; it must answer the questions of who, when, changed what, and why.

When should the report be closed?

Short answer: without the mandatory field fields, the scope completion check, the finding-evidence link and the technical review, the work order must not be “completed”. Signing or sending to the customer is the next controlled step after these.

1. Field personnel finish the application and run the missing record check.
2. The system compares the planned scope with the actual areas and the cancellation reasons.
3. The authorized technical role examines the consistency of procedure, personnel, instruments, raw data and results.
4. If a correction is required, the record returns to a justified revision; the previous version is preserved.
5. The approved report version is published with the work order identity and subsequent revisions become new versions.

TÜRKAK announced the transition policy for ISO/IEC 17020:2026 in its 15 June 2026 announcement. Accredited or applicant organizations must verify their own current transition timeline and scope with TÜRKAK documents. The safe approach in software terms is to keep procedure and checklist revisions dated; not to silently change the basis of old work orders with the new version.

Applicable work order checklist

Short answer: in the pilot application, pass a single real work order through the following gates and verify that you can recall the evidence of every decision.

• Is the inspection object and area clear with a unique identity?
• Are the method, technique, procedure version and the source of the acceptance criterion known?
• Was the assigned person's method and role suitability checked from valid records?
• Were the physical instrument, probe/accessory and validity evidence verified before the field?
• Are the raw data and findings linked to the order and the inspection area?
• Do scope changes, cancellations and re-inspection reasons leave a trace?
• Are the technical reviewer and approver roles and time stamps visible?
• Can every version of the published report reach the same evidence chain backwards?

How does VizyonTech meet this flow?

VizyonTech's features page; it defines work orders and tasks, resource management, task tracking and work order structures adaptable to the organization's existing templates among publicly available product capabilities. In NDT practice, these modules must be configured according to the organization's approved method, competency, instrument and technical review rules; the software alone is not proof of accreditation or conformity to a standard.

In the product evaluation, request a demo with a real UT or PT order: revise the scope, test the assignment gate with a personnel or instrument record whose validity is unsuitable, synchronize the offline field evidence and recall the report revision history. To compare the overall architecture, to the destructive and non-destructive testing software guide; for method-based fields to the VT, PT, MT, UT and RT report management guide .

Sources

• ISO — ISO/IEC 17020:2026, requirements for inspection bodies
• ISO — ISO 9712:2021, qualification and certification of NDT personnel
• TÜRKAK — TS EN ISO/IEC 17020 transition policy announcement
• ILAC/TÜRKAK — ILAC P15:05/2020, application of ISO/IEC 17020
• IAEA — Training Course Series 48, Eddy Current Testing
• IAEA — Training Guidelines in Non-destructive Testing
• VizyonTech — Modules and features