Build a Turnaround Deferred Examination Handover List

At the end of a turnaround, an inspection package can contain many completed reports while still leaving specific examination obligations unresolved. Some work may not have been started, some may lack usable acquisition, and some may be waiting for interpretation or a corrected document. Build the deferred-examination list from the agreed scope and actual evidence, rather than from memory or the number of PDFs delivered. The purpose is to give the owner a clear account of what remains and who must decide the next step. The list itself does not authorize deferral or permit equipment operation.

The free digital NDT reporting workspace can document completed examination scope and explicit limitations, while the downloadable worksheet organizes the remaining work across reports. It is a manual coordination record, not an automatic work-order system or approval queue. Keep the owner's existing maintenance, engineering and authorization processes as the source of actual decisions. This guide focuses on making incomplete work actionable at handover. Its fictional examples do not establish acceptable inspection omissions, deferral periods or operating conditions for any asset.

Identify the scope document, work order or inspection plan that defines the expected examinations. Record its revision and any approved changes made during the turnaround. A work list assembled only from completed reports can overlook an item for which no report was ever created. Compare each required examination with the evidence available and identify the actual state. If the scope changed, retain the instruction that changed it rather than simply deleting the original item from the list. The owner should be able to distinguish an approved scope change from work that remains incomplete.

NASA's requirements management guidance describes traceability to requirement sources and controlled treatment of changes. Used here as general management context, that principle supports linking each open examination to its source obligation and decision record. It does not impose NASA project requirements on an industrial turnaround. Apply the owner's actual change process. If the source of an examination request is unclear, resolve that question explicitly. Do not assume an item is optional because it lacks a convenient reference, or mandatory because it appeared in an informal planning spreadsheet.

Distinguish work not started, work attempted without usable completion, acquired data awaiting interpretation, results awaiting technical disposition and completed work awaiting documentation. These states have different consequences and may have different owners. Use the project's approved terminology, but define it clearly enough that people outside the inspection team can understand the next action. A single deferred label can conceal whether the problem requires another site visit or only retrieval of an existing signed record. The list should make that difference visible at the row level.

Do not treat document status as examination status. A draft report may describe completed fieldwork, while an issued report may deliberately cover only part of the requested scope. Similarly, a completed work-order checkbox does not prove that the required technical evidence exists. Reconcile the actual records and preserve the relevant boundaries. If the status cannot be established, mark the uncertainty and identify the person who can resolve it. Choosing the most favorable status to make a closeout dashboard look complete creates a problem for the team that inherits the remaining work.

Each open item needs an asset and location reference precise enough to support follow-up. Include the equipment, component, weld or area identifier used by the owner, together with the relevant drawing or scope reference. A broad entry such as finish UT does not explain where the gap exists or what has already been completed. Describe the remaining examination boundary using the information available from the work records. Keep it separate from any proposed follow-up scope that has not yet been authorized.

If only part of a planned examination remains, identify the completed and incomplete portions without implying that they are technically equivalent. A missed length, inaccessible surface or unreviewed data segment may need different treatment. Do not use a rough percentage as the only description of the gap. The responsible reviewer needs a physical and evidential reference to decide what action is appropriate. Where the boundary is uncertain, retain that uncertainty rather than inventing an exact range. The next team should know what must be clarified before it can plan or execute the remaining work.

Describe why the examination is incomplete using supported facts. Access may have been unavailable, equipment may have been unsuitable, the component may not have reached the required stage, or evidence may still be under review. Record the actual circumstance and its source. A reason explains the gap; it does not authorize it. Avoid wording that implies a delay was accepted merely because it was unavoidable from the inspection team's perspective. The owner or responsible authority must determine the permitted treatment through the applicable process.

Keep a proposed resolution distinguishable from an approved one. A crew may suggest returning during another access window, but that suggestion does not establish that the timing is acceptable or that access will be available. Record the proposal, its dependencies and the decision needed. If a different examination approach is considered, identify it as subject to technical review. The free procedure generator can help organize inputs for a draft, but it does not approve a substitute method or decide whether the remaining examination can be postponed.

Identify who must decide the treatment of the gap and who will carry out the resulting action. These roles may differ. An inspection coordinator may arrange a return visit, while an engineer or owner representative decides the required scope and timing. A document controller may retrieve a missing final report without being responsible for the technical disposition. Use actual project roles and confirmed contacts through the approved system. Do not assign responsibility to someone merely because their name appears on the most recent email in the chain.

Make the next request specific. Ask for a defined applicability decision, a missing evidence reference or an authorized examination arrangement, rather than a vague request to close the item. Record any agreed target date as a coordination commitment, not as an automatically valid deferral period. If no date has been approved, state that the timing decision is open. The worksheet does not send notifications or create tasks automatically. Transfer the required action into the owner's established system and keep the reference so that the list and the actual follow-up process remain connected.

List the conditions that must be resolved before the remaining work can proceed. These may concern the component's stage, access arrangements, required information, personnel or equipment, depending on the actual project. Describe the dependency without providing an unauthorized work instruction. The purpose is to prevent a return visit from being scheduled while the same obstacle remains. Confirm which party controls the dependency and what evidence will show it is ready. A statement that access is expected is weaker than a confirmed arrangement and should be labeled accordingly.

Use the free equipment tracker and certificate manager to organize the supporting records for a future assignment, while keeping the actual suitability and authorization decisions with the responsible process. Their entries do not automatically reserve an instrument or approve a person for the task. The quote planner can compare user-entered costs for different return-work scenarios, but cost does not determine whether an examination can be omitted. Keep commercial assumptions in their own record and link them only where they help coordinate an authorized technical action.

Before arranging another examination, check whether the apparent gap is actually a missing document or an unresolved retrieval problem. The required data may exist in a source record that has not been connected to the closeout package. Conversely, a report title may suggest completion even though the document does not contain the required result. Trace the evidence carefully. A missing PDF should not automatically trigger repeat work, and a familiar filename should not automatically close an examination obligation. Establish what was performed and what can be supported by the available records.

The National Archives' metadata guidance for permanent electronic records illustrates the importance of descriptive information that keeps records identifiable. Its requirements concern federal record transfers, not every private turnaround. The practical lesson for this worksheet is narrower: preserve the identifiers, dates and relationships needed to retrieve the evidence. If a source file is found, confirm that it belongs to the correct asset, event and scope before closing the row. File availability and technical sufficiency remain separate questions.

Read the reports associated with deferred items and check that their scopes and conclusions remain consistent with the list. A report should not say the full requested examination was completed while the handover register identifies a missing area. If the report is an authorized interim deliverable, describe its boundary and the outstanding work clearly. Do not hide a material limitation only in the separate action list, especially when the report may later be circulated without that attachment. The recipient should understand the report's actual scope from the document itself.

If a discrepancy is found in an issued report, preserve its version and use the supported draft-revision process together with the project's correction procedure. Do not quietly replace the PDF in a shared folder and assume everyone will notice. Record which open item prompted the correction and which revised document resolves the wording. The issue action in the reporting tool preserves a document state; it does not approve deferral, operating risk or a change in inspection obligations. Keep those decisions identifiable in their actual source records.

Consider a fictional turnaround with three open-looking items. Item A is a weld segment that could not be examined because the planned access was unavailable. Item B has acquired data awaiting the responsible interpretation. Item C has completed examination evidence, but the final report was omitted from the delivery folder. A single list marked three deferred inspections would misdescribe the work. The coordinator separates the rows by actual state, identifies the evidence for each and assigns the relevant decision and action owners. Only Item A clearly requires resolution of a field-examination gap.

In the same fictional case, the final report for Item C is retrieved and checked against the expected scope before the documentation row is closed. Item B remains open for interpretation, and Item A remains subject to the owner's decision about the required follow-up. No deferral duration or operating permission is supplied by the example. It demonstrates how accurate status descriptions prevent unnecessary repeat work and prevent unfinished technical work from disappearing behind an administrative completion label. The actual project process determines what may be accepted, changed or scheduled next.

Define what evidence will close a row before marking it complete. A return examination may need a reviewed report covering the specified gap. An interpretation item may need a responsible evaluation record. A documentation item may need the correct final document and a verified link in the package index. Avoid closing an item solely because a message says done. Identify the actual deliverable or decision and confirm that it addresses the original obligation. If the approved treatment changes the scope instead, retain the change reference and its authority.

Preserve the closure history rather than deleting completed rows from the working record without an archive. The owner may later need to understand why an examination was delayed or how a missing record was resolved. Use a clear final status and evidence reference, with dates appropriate to the actual events. If an item is reopened because new information changes the decision, retain that transition and the reason. The worksheet is a coordination aid, so the authoritative action and decision records should remain in the organization's approved systems with the necessary access and retention arrangements.

Before the turnaround team disperses, ask the receiving coordinator to follow one open item from the list to its scope reference, current evidence and next required decision. If the chain depends on an undocumented conversation, improve the record while the participants are still available. Confirm that the intended recipient can retrieve the referenced files and understands the status terms. A long list is not necessarily a useful list; clear boundaries, owners and closure evidence matter more than the number of columns. Keep sensitive project details in the approved location rather than a public support or discussion channel.

Use the downloadable worksheet as a starting structure and replace its fictional entries with actual reviewed information. Link the relevant digital reports and supporting free-tool records deliberately, since the tools do not synchronize or assign follow-up work automatically. At final closeout, preserve both the completed examination evidence and the history of unresolved or changed obligations. A reliable deferred-examination list makes unfinished work visible and actionable while leaving approval, technical adequacy and operating decisions with the people and processes authorized to make them.