Remote NDT Review Software: Viewing, Control and Records
Remote collaboration can connect a field team with specialist help, but a video session does not automatically become an approved inspection review. Define who can see and control what, what decision the session supports, and which evidence will remain afterward.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the remote collaboration task
Start with the purpose of the connection. A remote colleague may provide product familiarization, help investigate a software issue, observe an examination or perform a defined technical review. Those activities have different authority and evidence needs. Write the intended task before selecting software so the team can evaluate the functions that matter without assuming that every live session carries the same approval status.
Identify the expected output in plain language. It might be a support recommendation, a list of unresolved questions, a documented review decision or a training observation. The organization should decide who is authorized to produce that output under its applicable process. The software can facilitate communication, but joining a session does not establish a participant's competence, authority or permission to accept an inspection result.
Separate immediate collaboration from later data review. A live session may help the field team obtain the right context or understand a problem, while a formal review still requires the retained source package. The buyer should know whether the proposed software supports one activity, the other or both. This distinction prevents a convenient conferencing feature from being sold internally as a complete inspection approval system.
Distinguish screen sharing, context video and remote control
Evident's Remote Collaboration Service description lists screen sharing, video, annotation and remote control functions. Waygate's remote collaboration overview describes remote expert assistance through live communication and shared inspection information. These manufacturer sources show that collaboration can involve several different functions. Confirm which functions exist in the exact quoted product, instrument configuration and software version.
A shared instrument screen, a camera view of the physical arrangement and access to a native dataset provide different information. The remote participant may need more than one to understand the task. Ask the responsible technical reviewer which views and context are necessary. Do not assume that a clear video of the instrument screen provides every piece of evidence available in the source record or at the inspection location.
Remote control adds another responsibility. If the proposed software permits a remote participant to change instrument functions, define whether that capability is required and who may use it. The organization should approve the control arrangement through its technical and site processes. This article does not provide remote operating instructions or authorize adjustment of inspection parameters; it provides purchasing questions about capability, permission and records.
Identify the supported equipment and software combination
Request a configuration statement listing the instrument, installed options, collaboration application, receiving device and relevant versions. A product family may support different functions across models or releases. The buyer needs confirmation for the unit and entitlement being purchased. A demonstration on a supplier's latest instrument should not be assumed to apply unchanged to an older unit in the organization's fleet.
Include the remote participant's environment. Determine whether the participant needs a browser, installed application, account, license or another approved tool. Ask the supplier to demonstrate access under the intended role rather than using a privileged support account. The accepted workflow should be practical for the people who will actually join sessions, including any customer reviewer who has different access permissions from the provider's internal staff.
Record network and service dependencies without turning them into unsupported availability promises. The supplier should identify the conditions needed for the proposed function, and the organization should assess them in its intended environment. A successful demonstration on an office network establishes useful evidence for that setup, but it does not guarantee an identical experience at every customer site or in every remote location.
Define who grants access and who retains control
Create a responsibility record for starting a session, inviting participants, granting any control capability and ending access. Keep these responsibilities separate from technical approval of the inspection. A coordinator may arrange the meeting while an authorized field user retains control of the equipment and a qualified reviewer evaluates evidence. The software should support the intended arrangement, or the organization should identify the limitations it must manage.
Ask whether viewing and control permissions can be distinguished in the proposed workflow. Demonstrate the roles with fictional or approved sample data and the manufacturer's supported process. Record what the local user sees when another participant gains or loses a capability. The buyer should understand the actual behavior before relying on a statement that remote access is configurable.
Check what happens when the session ends or a participant leaves. The intended users should be able to tell whether sharing or control remains active. The organization's approved procedure determines the appropriate actions; purchasing verifies that the software's behavior is understood and documented. Avoid assuming that closing one visible window necessarily ends every related connection or permission in a multi-application arrangement.
Evaluate whether the remote view supports the intended question
Ask the reviewer to perform a defined sample task through the remote view and state what information is available or missing. The task might involve identifying a sample file, locating an annotation or confirming that the relevant configuration context is visible. The technical authority should choose the exercise. A visually attractive stream is not sufficient evidence if it omits a field or source relationship necessary for the actual decision.
Distinguish observation from measurement or analysis. A remote display may help someone understand a situation while the technical review requires access to the saved data in an appropriate application. The reviewer should determine the limits of the shared representation. Purchasing should not assume that video quality, screen size or a live connection independently establishes suitability for every form of NDT interpretation.
Record any context supplied through a separate camera or document. The remote participant may need to understand component identity, location or the physical arrangement in addition to the instrument view. Keep those relationships clear in the session record. A conversation that refers to this component or that location can become ambiguous later unless the retained evidence identifies what the participants were discussing.
Test ordinary connection problems with controlled data
Include a controlled interruption case in the evaluation if the intended workflow depends on continuous communication. The supplier and organization's responsible personnel should define a suitable sample exercise that does not affect live inspection work. Observe how the local and remote users are informed, what information remains available and how the session is resumed through the supported process.
Do not assume that a frozen image represents the current instrument state. Ask what indicators or procedures help participants recognize an interruption or delay in the shared view. The appropriate response to a communication problem belongs to the organization's approved workflow. The purchasing decision should establish that users can understand the condition and that a failed connection does not silently masquerade as a completed review.
Define a fallback for the collaboration task. The team may defer a decision, transfer an approved source package for later review or use another authorized communication method. The fallback should preserve the technical and record requirements rather than merely restore conversation. A phone call can be useful for coordination while being insufficient for a task that requires reviewable inspection evidence.
Determine what is recorded and what remains temporary
Ask the supplier which session objects can be retained: participant information, chat, annotations, screenshots, recordings or other records. Do not assume that a feature shown during a meeting is stored afterward. A temporary annotation may help communication without becoming part of the inspection record. The organization should decide what evidence it needs and verify that the purchased workflow can retain it appropriately.
Distinguish a session recording from the source inspection data. A recording can document a discussion or presentation, but it may not preserve the functions or metadata needed for later technical analysis. Conversely, the source file may retain the inspection evidence without recording the reasoning expressed during the conversation. The accepted process may need both a source reference and a concise decision record rather than relying on one object to serve every purpose.
Obtain the required organizational and customer permissions before retaining or sharing real session material. Use nonconfidential sample information during the purchasing test. The purpose is to establish the agreed record workflow, not to collect unrelated personal or customer data. The buyer should know where retained session material goes, who can access it and how it is connected to the relevant inspection record.
Preserve recommendations and approvals accurately
Create a concise session outcome record with the task, participants and roles, equipment or dataset references, advice given, unresolved questions and next owner. If the session results in a formal technical decision, record the authorized reviewer and the applicable approval reference under the organization's process. Do not convert a casual suggestion or training remark into an approval simply because it was made by an experienced participant.
Use wording that distinguishes advice, observation and acceptance. For example, a remote specialist may recommend obtaining additional evidence rather than approving the existing result. The field team should retain that distinction so a later reader does not interpret the session as complete technical clearance. A clear outcome record can be short while still preserving the decision's meaning and limitations.
If the discussion leads to a change in equipment configuration or software workflow, connect it to the appropriate change record. The collaboration session may provide context or support, but the organization's authorization process still determines whether the change is accepted. Keep the source evidence and the resulting decision linked rather than relying on a meeting title as the only explanation for a later configuration difference.
Include the customer review boundary in the agreement
If a customer will participate remotely, agree what participation means before the session. The customer may witness a demonstration, ask questions or perform a defined review under the contract. Those roles should be explicit. A customer's presence in a call does not automatically establish acceptance of every result or waive requirements that were not addressed in the session.
Identify the evidence the customer will receive afterward. It may include an issued report, source package, session note or another agreed object. Confirm the receiving software and access arrangement where the deliverable requires it. The buyer should not promise that the customer can independently revisit a measurement merely because the customer could watch the original display during the live call.
Document any limitation that affects the customer's decision. If the remote view is incomplete, the connection is interrupted or the necessary source record is not available, record the remaining action. A useful collaboration tool helps expose and resolve such gaps. It should not create pressure to mark a review complete merely because a scheduled meeting has ended.
Evaluate licenses, support and practical deployment
Ask which participants require accounts or paid entitlements and which functions are included in the quoted package. Confirm the terms for the actual service rather than relying on an old promotion or a general platform description. Product familiarization, remote support and formal review may use different access arrangements. The purchasing comparison should show the complete cost and responsibility for the intended use.
Include the local and remote users in a practical trial. A feature can be technically available while being difficult to use within the team's normal environment. Record any required preparation, supported device or customer approval needed for a session. The objective is to understand the workflow the organization will maintain, not merely to reproduce a supplier's demonstration under ideal conditions.
Ask how support issues and version changes are handled. The instrument, collaboration service and receiving application may change independently. Retain the accepted combination and identify who reviews later changes that affect the workflow. The software change guide provides an administrative structure for that evidence without assuming that every update requires repeating every earlier test.
Work through a hypothetical remote review trial
A fictional inspection provider wants a remote specialist to help review selected ultrasonic evidence during a project. Its first demonstration successfully shares the instrument screen, but the specialist cannot see the component reference needed to understand the location. The team adds a controlled context record to the planned workflow and repeats the relevant sample task. The issue is information completeness, not a claim that the collaboration product is defective.
In the same hypothetical trial, a temporary annotation disappears when the session ends. The organization had expected it to remain in the customer package, so the team revises the evidence plan to retain an approved outcome note and source reference. This example does not describe a named product's behavior. It illustrates why buyers should verify what remains after a call instead of assuming that live collaboration automatically creates a durable record.
The final acceptance states the supported viewing functions, permitted control arrangement, required context, interruption response and retained evidence. It also identifies the reviewer authorized to make the technical decision. That package can support useful remote assistance while keeping the organization's inspection responsibilities clear. It avoids treating connectivity as a substitute for competence, appropriate evidence or an identifiable approval process.
Keep equipment administration separate from the session system
NDT Connect's free equipment tracker holds instrument identity, calibration due date, status and notes. It does not provide live instrument streaming, remote control, conferencing or session recording. A note can refer to an external software acceptance or support record, but it should not imply that the tracker stores the underlying session evidence or verifies a remote review decision.
Maintain the instrument's current administrative record while retaining relevant collaboration evidence in the selected controlled system. If a session concerns an out-of-service condition, repair question or software change, link it to that existing workflow. The outcome should be visible to the person responsible for the equipment without requiring them to search through an unrelated conversation archive to determine what action remains open.
A complete buying decision answers four practical questions: what the remote participant can observe, what actions they may take, how the team handles an incomplete connection, and what evidence survives the session. When those answers are demonstrated for the intended configuration and assigned to responsible people, remote collaboration becomes a defined part of the inspection workflow rather than an ambiguous promise of expert access.
Frequently Asked Questions
Is screen sharing the same as remote instrument control?
No. They are different capabilities with different permission and responsibility needs. Verify the functions included in the proposed configuration.
Does a recorded video replace native inspection data?
Not automatically. The required evidence depends on the review task; a session recording may lack functions and metadata available in the source dataset.
Does a remote expert joining a call approve the result?
No. Record the participant’s role and distinguish advice from an authorized technical decision under the organization’s applicable process.
References & Standards Cited
- Evident: Connect Remote Collaboration Service functions View source ↗
- Waygate Technologies: remote collaboration in NDT View source ↗
Related on NDT Connect
Join NDT Connect — free
The free marketplace for the NDT industry — connect inspectors and the companies that need them.
Free to join · Compare provider qualifications and confirm availability directly · Browse providers
By NDT Connect Editorial · Updated
Source-based editorial guidance. Read our editorial policy and disclosures.