Record NDT Scope Changes After Mobilization

A useful field change record states the original requirement and the proposed replacement or addition. A note saying extra work requested leaves too many questions unanswered. Identify the component, examination area, method or stage affected, and describe what is being added, removed or changed. Keep the original request reference available. This creates a precise question for the people who must assess the change, instead of forcing them to infer its meaning from a general site conversation or a later invoice description.

Capture the request when the difference becomes apparent, using the project’s actual communication process. The record can initially show that the request is under review. It does not need to pretend that every decision is already complete. A clear proposed change is valuable even when execution cannot yet proceed. The bid clarification guide addresses questions before award; this ledger follows changes encountered after mobilization, when the crew, equipment and work sequence may already be committed to a different plan.

A client representative may point out another area of concern without authorizing additional examination. An examiner may identify a limitation without being authorized to change the agreed method. Record who raised the issue, what was actually communicated and what decision is being requested. Avoid converting a suggestion into an instruction through the wording of the ledger. If the source is verbal, follow the project’s process for confirmation rather than creating a quotation or approval statement that the speaker has not provided.

An observation can still require urgent action through the applicable site or technical process. The change ledger does not replace those communication routes or justify delaying a consequential notification. Record the relationship to the relevant action without inventing a universal response time. Keep the purpose of the ledger clear: it preserves the scope difference and the decisions needed to handle it. It does not grant permission to continue work, change an examination technique or release equipment simply because someone has entered a new row.

A field change can require separate technical, operational and commercial decisions. The person coordinating access may not control the examination procedure. The person approving expenditure may not be authorized to accept a changed technical basis. Identify the actual roles required for the specific change and record their decisions through the established process. Do not use one approved checkbox to imply that every necessary decision has been made. Where authority is unclear, make that uncertainty an explicit action rather than assigning it to the nearest available person.

NASA’s configuration management guidance describes proposal, evaluation, authorized change and implementation tracking within its own program framework. The relevant planning idea is to preserve the difference between a proposed change and an implemented one. An ordinary NDT service project should use its real contract and technical authority structure, not claim NASA compliance from this worksheet. The ledger is useful because it makes each required decision visible, including decisions that remain outside the report preparer’s authority.

Determine whether the requested change affects the applicable procedure, examination technique, acceptance basis, qualification or equipment configuration. Do not assume that a method is interchangeable simply because both methods can be described as NDT. The responsible technical person must assess the proposed approach against the actual project requirements. Record the relevant instruction or procedure reference and the affected scope. A commercial agreement to perform more work does not by itself establish that the revised technical approach is suitable or authorized.

If a new document revision is supplied at site, establish which work it applies to and whether earlier results need review. Avoid silently replacing the report’s procedure reference for all examinations when only later events used the revised instruction. Preserve the effective boundary between events. The record should let a reviewer understand what basis applied at the time the work occurred. It should not retrospectively imply that an earlier examination followed a document that had not yet been issued or made applicable.

A request for more coverage needs a location definition that the crew and the reviewer can use. Record component identifiers, drawing references and the relevant examination boundaries. If a customer points to a physical area, connect that instruction with a controlled sketch or another appropriate location record. Do not rely only on a phrase such as the other side. A precise location delta helps prevent accidental overlap, omissions and later disagreement about whether the requested additional work was actually performed.

Preserve the distinction between a new component and an expanded area on an existing component. They may affect report structure and quantities differently. If the location cannot be identified reliably, resolve that issue before representing the change as executable scope. A temporary site marking can be helpful but may disappear before the report is reviewed. Record enough supporting context to make the changed boundary understandable after demobilization without inventing coordinates or dimensions that were never established in the field.

A small additional examination area may require a different access arrangement, preparation step or work sequence. Record those dependencies as questions for the responsible site participants. Do not promise immediate completion based only on the apparent size of the added area. The original mobilization may not include the personnel, equipment or access needed for the revised task. A useful ledger distinguishes the requested completion expectation from the execution plan that has actually been confirmed.

Consider whether the change affects other ongoing work. An examination required before coating or assembly may have a different practical window from one that can be performed later. Record the relevant sequence relationship without inventing a general hold point. If the responsible process establishes a hold or a release condition, reference that decision explicitly. The reporting tool does not coordinate site permits, issue access authorization or manage a live dispatch schedule. Those arrangements remain part of the project’s operational controls.

Document whether the change creates an unresolved question about additional time, travel, standby, consumables or other agreed commercial items. Use the actual quote and contract terms rather than inventing a standard rate. A crew member’s acknowledgement of a technical request should not be rewritten as agreement to a new price. Similarly, an approved cost variation should not be presented as technical acceptance of the examined item. Keeping the decisions separate helps both parties understand what has been agreed and what still needs clarification.

The quote comparison tool can organize real supplier scope and exclusions, and the contract comparison tool can compare entered terms and time assumptions. They do not calculate contractual entitlement or authorize changes. Use them as planning aids where useful, then record the actual decision reference in the ledger. If work proceeds under an authorized arrangement while a commercial question remains open, preserve that exact state instead of marking the entire change approved without qualification.

Identify when the change became applicable to the work and which events it affects. The relevant boundary might be a specific instruction, work package revision or examination sequence. A date alone may be insufficient when several activities occurred during the same shift. Record the practical event relationship without claiming greater timestamp precision than the evidence supports. This helps distinguish work performed under the original scope from work performed under the revised instruction and prevents a later reviewer from assigning the wrong basis to an earlier result.

NASA’s requirements management guidance discusses maintaining requirement relationships and communicating approved changes in its systems engineering process. For this field ledger, the useful application is to identify the affected instruction and make the change available to the people who need it. Do not assume that approval alone means the crew received or implemented the instruction. Record the actual communication and execution evidence through the project’s process, with any unresolved handoff clearly identified.

Consider a fictional team mobilized to examine six identified welds. At site, the customer requests an additional weld W-107, while access to W-104 is unavailable. The coordinator creates two ledger entries because an addition and a deferral are different changes. For W-107, the team records the requested method, location reference and required technical and commercial decisions. For W-104, it records the access limitation and asks whether the original requirement remains open. It does not assume that adding one weld cancels the missing examination of another.

After the appropriate decisions, W-107 is examined under the documented applicable instruction. W-104 remains unexamined with a recorded follow-up action. The report and closeout matrix show both facts. The total number of performed examinations may resemble the original quantity, but the component coverage is different. This hypothetical example does not prescribe who can approve a change or how it should be priced. It demonstrates why a numerical balance cannot replace an explicit record of which work was added, deferred and actually performed.

Not every proposed change becomes authorized work. A request may be rejected, withdrawn, superseded or left unresolved. Keep its final state and the reason or decision reference appropriate to the project. Do not delete it merely because the work did not occur if the record is needed to explain field planning or a later scope question. A rejected method change, for example, may explain why the original examination approach remained in use despite a conversation recorded elsewhere in the project file.

Avoid language that implies the examination was unnecessary or the component acceptable simply because a request was withdrawn. The decision may have been commercial, operational or administrative. Describe what the record actually establishes. If a new request supersedes an earlier one, link the two so the crew does not act on both. The ledger should reduce contradictory instructions, not become an unfiltered list of every suggestion with no indication of which instructions are current and which have ceased to apply.

Once the changed work is performed, add the actual examination and report references to the ledger. Compare the implemented boundary with the authorized delta. A change can be approved but only partly executed, or performed differently because a new limitation emerged. Record that difference and route it through the appropriate process. Do not close the ledger entry solely because the crew demobilized or a report was generated. The evidence should show what happened to the specific change, including any remaining unresolved part.

Check that personnel and equipment references correspond to the changed event where those details are required. If an additional technique used different resources, the report should not inherit the original setup automatically. Keep the level of detail proportionate to the actual requirements. The ledger is not a duplicate technical report; it points to the records that demonstrate implementation. That distinction keeps it usable while preserving the connection between the instruction, the performed work and the evidence delivered to the customer.

Use the free digital reporting workspace to record the performed scope, applicable references and necessary limitations. Cite the controlled change record where it helps explain the difference from the original request. Do not replace the entire original scope description with the final one in a way that hides unresolved or removed items. The customer should be able to distinguish original work, authorized additions and remaining exceptions without reading every field conversation in the project archive.

Review the conclusion and quantity summary after adding the changed work. A statement such as all requested welds examined may be false if one original location remains open even though an extra weld was completed. The scope intake record supplies the baseline for this check. Where a distributed report needs correction, use the applicable amendment process. A new local PDF does not automatically notify recipients or withdraw an earlier version, and the free tool does not perform those communications on your behalf.

When another crew takes over, identify the active changes that affect its work and the instructions that have been superseded. A late approval recorded in one coordinator’s notebook may not reach the people preparing the next examination. Use the actual handover process to communicate the affected locations, applicable references and unresolved decisions. Record that communication where the project requires it, without treating a routine receipt as technical approval. This is especially useful when the physical marking remains unchanged but the required examination stage or reporting boundary has changed since the previous shift.

At demobilization or the agreed reporting cutoff, review open change entries with the responsible project participants. Confirm which were implemented, which remain pending and which no longer apply. Keep technical, access and commercial questions separate where they have different outcomes. A ledger can truthfully show that an examination addition was completed while a cost clarification remains unresolved. Avoid forcing every entry into a single closed state merely to make the administrative list look finished.

The worksheet below is designed to capture the delta, decision path and implementation reference in one place. Use actual document identifiers and responsible roles rather than the fictional example values. A good record lets a later reviewer answer why the performed scope differs from the initial request and what evidence supports that difference. It also helps the next mobilization start from the real remaining work, rather than repeating an old instruction or overlooking a deferred examination that disappeared from an informal site conversation.