Reconcile Results Across NDT Inspection Worksheets

A repeated component number does not establish a duplicated examination result. The rows may describe different locations, methods, dates, preparation stages or repair cycles. Begin by identifying the event represented by each row. Use the component, examination area, method, event reference and relevant process state to decide whether the records describe the same thing. Only then compare their values and interpretations. Removing repeated component numbers before this check can erase legitimate evidence and make a report appear more consistent by hiding its actual history.

Keep the reconciliation question narrow. You are establishing which source rows belong in a particular report and how unresolved differences should be represented. This is different from migrating an entire inspection database or redesigning a company’s asset identifiers. The inspection data migration guide covers broader system transfers. For one workbook, a short event comparison matrix can be enough, provided it retains the source locations and a reason for every decision that affects the final report.

Keep an identifiable copy of the workbook as received through the project’s record process. Record its source and relevant version context before sorting, filtering or correcting cells. A reconciliation workspace can then contain the review notes without changing the only available source. Microsoft’s duplicate-removal guidance notes that its removal action deletes duplicate data and recommends preserving the original information. That software behavior is a good reason to investigate repeated inspection rows before using a cleanup command.

Do not assume that a workbook named final is the latest authorized source. Compare its transmittal, author and intended reporting use with the other available files. Two people may have edited different copies after receiving the same starting sheet. A later file modification time can reflect copying or formatting rather than new examination evidence. Preserve those distinctions in the review record. The chosen source should be supported by the project’s actual document process, not by whichever filename sounds most definitive.

Identify which worksheets contain field entries, reviewed results, summaries, calculations or historical records. A summary tab may repeat values intentionally while a repair tab records a separate event. Document that role before combining rows. Check with the source owner when a worksheet’s purpose is unclear. Hidden, filtered or visually grouped information can affect what a person sees in the original application, so do not treat one visible table as proof that the workbook contains no other relevant records.

The browser importer presents supported extracted tables for review; it does not determine the authority of a worksheet or perform cross-tab reconciliation for you. Review the source workbook in its appropriate application when its structure matters. Microsoft’s Open XML cell-value documentation distinguishes stored values and cell types, including shared strings. A successful extraction therefore gives you data to examine, not a guarantee that every displayed convention or business meaning has been carried into the report.

Build a comparison key from the fields needed to distinguish the examination events in this assignment. A weld identifier alone may be insufficient if the same weld was examined before and after repair. A component and date may still be ambiguous if two separate zones were tested during one shift. Choose the smallest set that preserves the meaningful distinctions and document it in the reconciliation notes. Do not invent missing event identifiers simply to make a lookup formula return one match.

Preserve identifiers as text when that is their actual meaning. A leading zero, suffix or separator can distinguish two records that look similar after spreadsheet conversion. Verify suspected matches against drawings, field records or another controlled source. If the match remains uncertain, retain both source references and mark the relationship unresolved. The practical objective is not to reduce the workbook to a predetermined row count. It is to avoid assigning a result to the wrong event or losing a legitimate examination history.

Separate exact repeated entries, intentional summary copies, distinct examination events and conflicting descriptions of the same event. Each case requires a different response. An exact copy may be excluded from the report’s presentation while its origin remains recorded. A summary copy may point back to the detailed evidence. A distinct event needs its own representation. A contradiction requires source review. Calling all four cases duplicates encourages the preparer to apply a single deletion rule to information with very different significance.

Keep the classification provisional until the evidence supports it. Two rows with identical values may still describe different events, while two rows with different values may be a detailed result and its rounded display. Inspect their definitions and sources. Do not average values, select the most favorable result or choose the last row as a default resolution. Those shortcuts can conceal a real disagreement. Where the difference has technical significance, the appropriate reviewer must determine what the evidence establishes and how it should be reported.

Before treating two numbers as conflicting, check their units and quantity definitions. One tab may contain an individual reading while another reports an aggregate or a derived value. A rounded presentation value may differ from the retained source without representing a new measurement. Record the distinction rather than forcing both cells into the same display. If conversion or calculation is needed, obtain the checked result through the controlled process and retain its basis. The reporting tool does not resolve those technical relationships automatically.

Text fields deserve the same attention. A status of complete might refer to data acquisition on one sheet and completed review on another. Accepted, released and closed can also refer to different responsibilities. Compare the field definitions before declaring agreement. If the workbook uses ambiguous labels, ask the owner to explain their intended meaning and preserve that clarification. A consolidated report should not inherit a misleading status simply because the wording was repeated consistently across several source tabs.

For each genuine conflict, record the workbook identity, sheet name and cell or row reference for both entries. Then locate the field record, acquisition reference or review instruction that can resolve the difference. A broad note saying checked with inspector is often too weak to explain a later question. Record the actual source relationship and the responsible decision in the level of detail appropriate to the project. Preserve original values in the reconciliation record even when only the resolved result appears in the report.

Distinguish a transcription correction from a reinterpretation of examination evidence. Correcting a copied identifier may require confirmation of the source entry. Changing a technical disposition may require a different authority and review process. Do not treat both as ordinary spreadsheet cleanup. When the authorized reviewer cannot yet resolve the contradiction, keep the affected report result open or otherwise communicate the limitation under the project’s instructions. The presence of a spreadsheet formula or a highlighted cell does not supply the missing technical authority.

In a fictional workbook, the Daily tab contains an examination of weld W-018 before repair. The Summary tab repeats that event but contains a different result description. The Retest tab records W-018 after a documented repair and uses a separate event reference. The coordinator initially sees three rows with the same weld identifier. After checking the event context, the team identifies one unresolved disagreement about the original event and one legitimate follow-up event. It does not collapse all three rows into one preferred result.

The responsible reviewer resolves the Daily-versus-Summary difference using the retained examination and review records. The final report represents the original and follow-up events separately, with the repair relationship visible. The reconciliation matrix records why the Summary copy was not treated as additional examination work. This scenario is hypothetical; it does not prescribe repair acceptance or retest coverage. Its purpose is to show that event identity must be established before duplicate removal, quantity totals or a consolidated technical conclusion can be trusted.

A summary worksheet may populate its results through formulas that reference other tabs. The importer leaves formula cells blank rather than executing them or treating saved output as a newly verified result. A blank imported summary therefore does not mean that the underlying examination was not performed. Review the source formula and its inputs in the appropriate controlled environment, then obtain the checked information needed for the report. Do not fill the blank by choosing whichever detailed row happens to look closest.

A formula can also reference an old range or omit a recently added row. Reconciliation should examine the intended relationship between source and summary, not merely whether the workbook opens without an error. Keep the calculation responsibility with the organization’s established process. The report can reference a checked summary without pretending that the browser importer recalculated it. If the summary cannot be supported, use the appropriate reviewed source entries or state the unresolved limitation rather than manufacturing a plausible total.

Once the event relationships are established, decide which rows contribute to the report’s stated counts. A duplicate presentation copy should not inflate the number of examinations. A repeat event may legitimately count as additional work but should not be mistaken for an additional physical component. State what each total represents. Component count, examination-event count and accepted-result count are different quantities. Keeping them separate prevents a clean-looking summary from obscuring the amount and state of the actual work performed.

Compare the reconciled set with the requested scope. The absence of a duplicate does not prove that every requested item has a result. An omitted location may have no matching row anywhere in the workbook. Use the scope intake record or the agreed item list as the external reference. This final cross-check catches missing work that a comparison confined to the available worksheet rows cannot discover. Reconciliation needs both internal consistency and an explicit boundary for what should have been represented.

For every material resolution, keep the original source references, the selected interpretation, the supporting evidence and the responsible decision reference. The final report can remain concise while the reconciliation matrix preserves the reasoning needed for a later question. Avoid a vague cleaned flag that says nothing about what changed. If a difference was purely presentational, say so. If it affected identity, scope or technical disposition, make the nature of that change visible in the appropriate project record.

Do not copy private review correspondence wholesale into a client-facing result table. A controlled reference and a clear outcome may be enough, subject to the project’s requirements. Keep access to the supporting evidence available through the agreed record process. The procedure draft tool can help organize proposed reconciliation responsibilities for technical review, but it does not assign authority or approve the resulting decisions. The organization must establish who can resolve each kind of discrepancy before those decisions are presented as final.

Use the free digital reporting workspace to assemble the reviewed tables and explanatory notes. Choose or enter the rows deliberately after reconciliation, preserving event references and any required limitation. The import preview is an opportunity to compare the selected grid with the source, not a substitute for the preceding review. Check the final PDF for missing rows, repeated presentation copies and ambiguous labels. A well-formatted export can still be wrong if the selection was based on an unresolved workbook conflict.

Keep the external reconciliation matrix with the supporting package when required. The app does not automatically attach the original workbook, grant shared company access or verify the source decisions. Explain what is included in the PDF and what is supplied separately. The report buyer-review guide provides broader package questions. Here the key check is whether a recipient can distinguish the physical component, its separate examination events and the source evidence supporting each reported result.

Before finalizing the consolidated table, choose a record that includes a repair, a changed identifier or an unresolved source note. Walk it through the proposed comparison key and inclusion rule. If the rule drops its history or joins it to a different event, revise the rule before applying it more widely. A straightforward unchanged component is a poor test of whether the reconciliation handles the workbook’s real complexity. Keep the difficult example in the review notes so another preparer can understand the boundary of the chosen approach without reconstructing every earlier discussion.

A late workbook can change the evidence set without making every previous decision obsolete. Identify which events it affects and compare those source relationships deliberately. Do not replace the entire reconciled table merely because the new file has a later date. Preserve the prior decision references and document the additional evidence. If the late information changes an issued result, follow the applicable report amendment process and identify the affected report version rather than quietly editing a local working copy.

The worksheet below is intended for the unresolved pairs and meaningful inclusion decisions, not as a mandatory duplicate of every source row. Use it to answer what each record represents, why the apparent conflict exists and who resolved it. A completed matrix should allow another preparer to repeat the selection logic from the retained evidence. That is more valuable than a workbook with fewer rows but no explanation of which events were removed, retained, corrected or still awaiting an authorized decision.