NDT Records Across Multiple Locations: Ownership and Control

Identify the organizational boundaries first

List the locations, legal or operating organizations, employer relationships, and quality-program owners involved. Two branches using the same brand may not have identical qualification arrangements. A central records view should make those boundaries visible rather than assuming that common ownership makes every personnel decision interchangeable.

Identify the purpose of the shared view. It may support resource planning, evidence retrieval, internal review, or a consistent update process. Those are different tasks. Decide which one the central record is intended to answer before asking every location to upload its entire personnel archive.

ASNT's employer-based accreditation application asks applicants to identify the locations in scope [1]. That provides a useful reminder that location coverage should be explicit. This guide does not determine accreditation scope or whether a particular employer record applies at another facility; those decisions remain with the relevant program owners.

Separate common facts from local decisions

A certification-body credential can be a common factual record associated with a person. A local employer qualification decision, site-specific requirement, or customer acceptance may need a separate record. The central view should connect these layers without collapsing them into a single qualified everywhere status.

Use stable person and credential references across locations where the organization can do so appropriately. Then attach the relevant local review records with their owners and scope. This allows one updated credential fact to be found centrally while preserving the distinct decisions made by different facilities.

Do not duplicate the same source document into many uncontrolled folders merely to make each branch self-contained. Where approved systems allow it, use a controlled shared source and local references. If copies are necessary, identify the custodian and update process so branches know which version is current.

Define ownership for every significant field

Assign a primary owner for identity, issuer credential details, employer records, local scope decisions, and operational availability. These may be different people. A branch administrator might maintain contact information while a designated reviewer controls qualification conclusions. The central system should not blur those responsibilities because it permits broad editing.

Document who can propose a correction, who reviews it, and who updates the active value. A location that discovers an incorrect date should have a clear route to the record owner. It should not need to create a competing spreadsheet or overwrite another branch's reviewed record without explanation.

Provide a backup owner for essential tasks. Multisite systems often fail when a central coordinator becomes unavailable and local teams cannot obtain evidence. A controlled successor arrangement should give authorized staff enough access to continue the work without shared passwords or informal transfers of private files.

Agree on a common data dictionary

Define the meaning of issuer, credential type, method, scope, expiry, review state, and location applicability. Different branches may use the same word for different things. For example, approved could mean evidence received at one site and technical review completed at another. A central dashboard cannot resolve that ambiguity by choosing a single color.

Keep local vocabulary mapped to the common definitions where needed. Preserve the source wording when a method or scope label cannot be safely standardized. A controlled dictionary should support clear comparisons while allowing legitimate differences in program or customer requirements.

Review changes to the dictionary through the appropriate owners. If a central administrator renames a status, consider whether the new wording changes what users infer about personnel readiness. Treat semantic changes as process changes, not merely visual cleanup.

Control how records move between locations

When a person is proposed for work at another site, identify the intended role, period, and local requirements. Share the relevant evidence through the approved process and let the receiving location record its review. Moving a personnel file does not automatically create a new employer or site decision.

Preserve the home location's historical record while adding the receiving site's review outcome. If the person changes employer or program context, identify that change explicitly. Avoid editing the old record's issuer or location to make it appear as if the original decision was made by the new organization.

Record who maintains updates during the assignment. A renewal, corrected scope, or change in availability may need to reach both the central owner and local planner. Agree on that communication path before the transfer rather than relying on the technician to notify every system independently.

Work through a fictional two-branch transfer

Imagine a fictional NDT company with a central credential index and two branches. One branch proposes a technician to support the other for a defined assignment. The central record contains a current certification-body credential, while the receiving branch has a separate local review process for the intended work.

The coordinator shares the relevant credential and employer evidence, with the source locations and review dates. The receiving reviewer identifies one scope question and records it as open. The central system does not change the person to approved at both sites simply because the transfer appears on a staffing calendar.

After the question is resolved, the receiving location records the decision and its limits. The central view can show that a review exists for that assignment while preserving the original branch's record. If the assignment later changes, the affected local decision can be revisited without rewriting the person's entire credential history.

Check accreditation claims at the right level

If a company or issuer claims accreditation, identify the organization, program, scope, and locations to which the claim applies. ANAB's directory distinguishes accreditation status and scope categories for personnel certification bodies [2]. Use the relevant accreditation source rather than assuming a corporate logo proves coverage for every activity or office.

Keep accreditation evidence separate from individual credential status. A branch may need both kinds of information, but they answer different questions. Do not let a central company certificate automatically fill every person's qualification row or imply that every subcontractor under the brand is covered.

Where the scope is unclear, ask the relevant accreditation or program owner. Record the clarification and its limits. The central record should help users understand coverage, not extend it through a convenient internal label such as group certified.

Manage updates without creating competing truths

Choose a controlled active source for each common fact and define how branches receive changes. If a date is corrected centrally, the affected local views should be updated or notified through a reliable process. A branch copy that remains stale can undermine an otherwise accurate central record.

Keep a change note for material updates: what changed, the supporting source, the editor, and which local decisions may be affected. Not every change requires a new qualification review, but a scope or issuer change may need attention beyond the central database field.

Do not resolve conflicts by choosing whichever branch updated its spreadsheet most recently. Compare the evidence and authority behind the values. A later edit can still be wrong, while an older record may preserve the relevant historical period. The reconciliation should be evidence-based and documented.

Tailor access to the location's task

A local planner may need a limited summary, while the program reviewer needs controlled supporting evidence. Define those access needs explicitly. A central system that exposes every personnel file to every branch may create unnecessary disclosure without improving the local decision.

NIST's small-business information-security guidance addresses protecting information and planning recovery [3]. Apply those general principles to shared access and backup ownership. The exact permissions should reflect the services and processes actually available to your organization, not assumed features of a software product.

Review access when staff move, leave, or take on new responsibilities. A person transferring between locations may need different access without losing all ability to retrieve their authorized records. Coordinate the change with the relevant system owner rather than relying on ad hoc folder sharing.

Review central and local records together

Sample a person who works at more than one location and trace the shared credential fact to each local decision. Check whether the issuer, scope, dates, and review limits remain consistent. This reveals whether the system preserves the intended distinction between common evidence and local applicability.

Include a record with a recent update or transfer in the sample. Ask each location which version it uses and what triggered its latest review. If the answers differ, investigate the communication path rather than simply telling everyone to use the central dashboard without understanding why the divergence occurred.

Track findings to the owner who can resolve them. A vocabulary problem needs a definition change; a missing notification needs a communication fix; a local qualification question needs the responsible reviewer. Treating every discrepancy as a data-entry error can leave the real process weakness untouched.

A branch rename or corporate reorganization deserves a focused records check. Confirm whether the change affects only the displayed name or also the employer, program owner, evidence custodian, or scope of an existing decision. Preserve the earlier issuer wording on historical documents and record any official clarification rather than editing old certificates to match a new brand. Update the central index and local contacts so requests reach the correct owner. This review does not decide legal succession; it identifies the record relationships that the responsible organizational owners need to clarify.

Resolve conflicting edits through field ownership

A central record can receive different updates from two branches at nearly the same time. One branch may report a renewed credential while another is correcting an employer review note. Establish which owner controls each fact before treating the newest edit as authoritative. A date supplied from issuer evidence and a site-specific review condition can both be correct, but they belong to different fields and may have different supporting records.

Use a discrepancy record when two locations supply conflicting values for the same field. Identify both values, their sources, the time received, the affected personnel record, and the designated owner who will reconcile them. Keep the conflict visible in the appropriate review process instead of repeatedly overwriting the central value. The goal is to settle the factual question through evidence and to prevent a local spreadsheet from restoring a superseded value during the next update.

Imagine a fictional branch A receives a corrected credential document while branch B is still using an earlier downloaded copy. The central owner compares the sources and obtains clarification if needed. Once the current value is established, the owner updates the common record and identifies the local summaries that depend on it. Branch B records the correction in its own controlled view rather than changing its separate employer decision without assessing whether that decision is affected.

Record the reconciliation outcome and communicate only the material change to the relevant owners. A corrected personal spelling may need a display update, while a changed scope may require a substantive local review. Do not broadcast the entire personnel file to every branch for every correction. Field ownership and targeted updates help a shared system remain accurate while preserving the distinction between common evidence and decisions made for a particular location.

Test continuity when a branch changes structure

A branch opening, consolidation, or closure can affect record custody even when the personnel continue doing similar work. Identify the new custodian, the employer and program context, the locations of historical evidence, and the owners of open qualification actions. Do not assume that changing a folder name transfers every review responsibility or that a corporate reorganization changes the issuer printed on historical records.

Prepare a transition map for the affected record families. Show where common credential facts will remain, where local employer decisions will be retained, and who will answer questions about earlier assignments. Keep historical location references understandable after the operational branch name changes. A later audit may ask about a period when the old branch existed, so replacing every old name with the current one can make the history harder to interpret.

Test one person with work at several locations. The successor should locate the shared issuer evidence, identify which local decisions applied to each assignment, and find the relevant program owner without contacting a departed coordinator through a personal channel. Any missing ownership or access becomes a transition action. This is a records continuity exercise; it does not determine whether one branch's qualification decisions automatically apply to another organizational arrangement.

Close the transition only after the receiving owners accept their records responsibilities and the operational users know where current information is maintained. Retain a narrow transition note with unresolved questions and their owners. A central view can remain simple while this supporting map preserves the organization-specific detail needed for review. The result is continuity of evidence and responsibility through a structural change, without rewriting historical decisions to fit the new organization chart.

Use NDT Connect without assuming a multisite approval system

NDT Connect supports profile-based personnel and company record information and a certificate manager for recorded dates. It does not automatically decide which employer record applies across locations, provide a complete multisite approval hierarchy, or lock work assignments based on local qualification decisions.

Maintain the necessary governance and local review records in your controlled process. Keep platform entries accurate and avoid broad public claims that imply all locations or personnel share identical qualification coverage. The information should describe the evidence actually held and the organization responsible for it.

A useful multisite record system has one clear source for common facts, visible local decisions, and a dependable path for changes. That arrangement lets branches cooperate without turning a shared database into an unsupported claim that every person is qualified for every location's work.