Reconcile Excel Dates Before Issuing an NDT Report

Before changing a date format, establish what the field describes. An inspection date, instrument calibration date, worksheet preparation date and report issue date belong to different events. A spreadsheet may place them beside each other without explaining the distinction. Ask which event the receiving customer needs to recognize and where the evidence of that event is retained. A date that looks consistent across the page can still be wrong when it has been copied from the preparation record into the inspection field. Write the field meaning beside its source reference before addressing its appearance.

Keep separate entries when the work spans more than one event. A technician might acquire readings on one day, repeat a small area later and complete the report after review. Replacing all three dates with the most recent date hides that history. The report can identify its overall inspection context while individual rows or notes retain the relevant examination dates. Decide this representation with the responsible project party. The objective is a reader who can connect a result to the correct work, equipment evidence and governing information without reconstructing the timeline from filenames.

Keep an unchanged copy of the workbook received for reporting and record its filename, revision or other agreed identity. Work on a separate preparation copy. If a date appears questionable, note the sheet, cell and visible value before editing anything. A screenshot may help communicate what was displayed, but it should accompany a usable reference to the underlying workbook. Do not rename the prepared copy so that it becomes indistinguishable from the original. A later reviewer needs to know whether the discrepancy came from the supplied source, a preparation step or a report entry.

The reconciliation worksheet should preserve both the source representation and the proposed report representation. Avoid a single corrected-date column that erases the question. Add the person or document that resolved the meaning and a short explanation when a change matters. This is a practical review record, not an assertion that every report requires a separate form. For a simple file with clear dates, a short documented check may be sufficient. For a workbook assembled from several contractors, the same structure helps prevent inconsistent decisions being made independently on different sheets.

Microsoft explains that spreadsheet cell values require interpretation according to their stored type. A human-readable date may therefore depend on workbook formatting rather than a complete date string stored in the cell. This matters when moving data between applications. A reporting import can preserve a stored number while presenting something that no longer resembles the date visible in Excel. Treat the discrepancy as a question about representation; do not immediately replace the number with a guessed calendar date.

The free NDT reporting importer reads supported table values and warns that dates or units expressed only through numeric formatting are not reconstructed. It does not promise to recreate the workbook display. If a date appears as a number in the preview, return to the source and confirm its meaning there. Enter a verified date representation into the report only after that check. The reporting workspace is a place to assemble reviewed information; it is not a date-conversion authority. A successful upload says the supported content was read, not that every date has been interpreted correctly.

Microsoft documents two Excel date systems, 1900 and 1904, and explains that the same date has different serial values in those systems. That is enough reason to reject a conversion based only on the size of a number. Confirm the workbook setting and the origin of the relevant data. A table copied from another workbook deserves particular attention. Do not assume that a current computer, a familiar file extension or the person who sent the file tells you which convention was used when those values were created.

If the date system cannot be established, keep the item unresolved and ask the source owner for a confirmed date or a revised extract. Applying an offset to a whole column can create a second error when some cells are already text, were converted previously or describe a different event. Separate the affected cells from the rest of the worksheet before testing a correction. Record which source evidence supports the chosen interpretation. A coherent-looking sequence of dates is useful as a warning check, but it is not proof that the conversion is correct.

A value such as 04/05/2026 does not, by itself, tell every reader whether the intended date is in April or May. For a US recipient working with an international supplier, this is a realistic handover question. Ask the author or examine an authoritative source record that identifies the event unambiguously. Do not resolve the question by the customer’s location, the sender’s address or a computer’s language setting. Those clues can help frame a question, but they cannot establish what happened on a particular date. Retain the original string while clarification is pending.

After the meaning is confirmed, choose an agreed display that makes the full year and ordering clear. An explicit year-month-day entry can be useful in a data table, while a written month may suit a narrative report. Consistency should follow confirmation rather than substitute for it. If the source contains a two-digit year, establish the intended full year through evidence instead of applying an undocumented century assumption. A report author should not silently turn a formatting preference into a historical fact. The worksheet can record the confirmed date and the basis without copying unnecessary personal information.

Some examination records need more than a calendar date. A repeat reading, an equipment change during a shift or a dataset collected across midnight may depend on the sequence of events. Determine whether the source includes a time and whether the project requires it in the final record. Do not discard the time merely because a destination column is called date. Where the report needs only the day, preserve the more detailed source reference separately so the relationship can be checked if a later question arises about which event a result belongs to.

When a supplied record contains a time-zone label or offset, keep that context with the timestamp. Do not convert between local time and another time basis without an agreed reason and a verified conversion. A timestamp without a zone does not authorize the report author to invent one. Ask the source owner when the ambiguity could change event ordering or the assigned date. The report may need a concise note explaining which time basis was supplied. This is especially useful when data acquisition and remote review occur in different places, even though only one of those events represents the examination.

Compare the confirmed examination date with the equipment records identified for that work. The equipment tracker can help organize the instrument and supporting references, but an entry does not establish that a particular examination was valid. If the date reconciliation changes which certificate or equipment state appears relevant, raise that consequence with the responsible technical reviewer. Do not move a calibration date to make the records fit. A missing or conflicting document should remain visible until the appropriate evidence and decision are available.

The calibration reminder tool organizes due dates entered by the user. Its reminders do not verify a historical inspection date or extend a calibration interval. Keep the date being reconciled separate from the dates used to schedule future actions. This distinction prevents a report cleanup from accidentally becoming an equipment-management change. If a confirmed source correction also affects a register, update that record through the organization’s normal process and retain the reason. The report should reference the resulting evidence rather than imply that software formatting resolved the technical question.

Choose representative rows that expose the kinds of dates present in the workbook. Include an ordinary row, an ambiguous day-month string, a value that imports numerically, a blank date and any row associated with repeat work. Compare the original workbook, import preview and proposed report entry side by side. The purpose is to discover whether the preparation approach preserves meaning across these cases. Checking only the first row can miss a second date convention introduced farther down the sheet or a special entry copied from an earlier report.

Once the approach is agreed, apply it to the remaining affected rows and reconcile their count. Maintain a separate list of unresolved items instead of mixing them with confirmed dates. A blank should stay distinguishable from a value intentionally omitted from the deliverable. If a field is required for issue, an unresolved date should prompt the responsible person to decide what can be communicated. The report editor does not perform that decision. Avoid filling a required field with today’s date simply to make the form look complete or to move past a local review step.

Consider a fictional fabrication closeout containing a twelve-row examination table. Most rows show written month names. One row displays 04/05/2026, and another appears as a number after import even though the original workbook displays a date. The coordinator retains the supplied workbook, records both cell references and marks the two items unresolved. The remaining rows are checked against the source rather than presumed correct. No part of this example represents an actual customer, a completed inspection or a required reporting format.

The supplier confirms from its examination log that the ambiguous row means 4 May 2026. For the numeric row, the supplier provides a verified date extract and identifies the workbook setting used for that entry. The coordinator enters the confirmed dates, keeps the original representations in the reconciliation worksheet and links each clarification to its row. A later repeat examination retains its own date instead of inheriting the original event date. The completed report is then reviewed for consistency with the requested scope and supporting equipment references; the clarification itself does not establish technical acceptability.

After entering confirmed dates in the free digital reporting workspace, download the PDF and read the actual exported fields and table cells. Check the full year, order, separators and relationship to the row identity. A correctly entered date is not enough if the surrounding heading makes it appear to be a different event. Look at the report inspection date alongside any row-level examination dates and the source-template reference. Ask whether a recipient unfamiliar with the workbook can understand why different dates appear.

Keep the draft state while a material date question remains unresolved. A saved number or polished PDF is not evidence that the chronology has been checked. If the report has already been issued and a correction is necessary, use the organization’s amendment process and the report amendment guide to preserve the earlier record. Do not quietly replace an already distributed PDF. A date correction may be administrative, or it may change which examination evidence is relevant; that assessment belongs with the responsible reviewer.

A later workbook may contain a different date without explaining whether the underlying event changed or an earlier entry was corrected. Compare the affected rows using their examination identity, not their row number alone. Ask the supplier to identify the reason for the difference and the evidence supporting it. Do not assume the latest file is authoritative simply because it arrived last. An updated template can accidentally carry a new preparation date into historical results. The useful question is what changed in the record and why that change should govern the proposed report.

Keep a short difference list for the dates that matter to the deliverable. Record the previous value, replacement value, affected event and clarification reference. Where the revision adds a new examination, give that event its own place in the report instead of overwriting the earlier examination date. Where it corrects a transcription error, preserve the correction relationship through the appropriate control process. If the supplier cannot explain a material discrepancy, show the open question to the person responsible for issue. This review avoids both unnecessary rejection of a useful update and uncritical acceptance of a newly introduced error.

The final check should answer four practical questions: which fields were reviewed, which discrepancies were found, what resolved them and which items remain open. Keep the evidence trail concise enough that another person will actually use it. A source file reference and a clear clarification record are often more useful than a large unlabelled collection of screenshots. Record the report identity produced from the checked information so that the preparation work can be connected to the delivered version. Follow the applicable project arrangements for retaining the original and the reviewed extract.

Use the worksheet again when a later supplier revision changes the relevant data, rather than assuming the earlier reconciliation covers every future workbook. Check only the affected scope and related dependencies, but make that boundary explicit. The intended outcome is a defensible date for each reported event, with unresolved information still recognizable. That supports traceable reporting without turning the author into the source of invented dates. It also gives the supplier a precise question to answer when the next file contains the same ambiguity, reducing repeated clarification work.