NDT Experience Log: Record Work Evidence Without Guesswork

Identify the intended use of the log

Before choosing columns, ask who will review the record and for what purpose. An employer development record, a certification application, and an employment reference may ask different questions. Keep a factual underlying log, then prepare a separate summary for the specific review. This avoids rewriting the history every time the intended application changes.

Obtain the relevant program guidance from the responsible authority. ASNT's Level III application page describes signed experience documentation for the methods being claimed [1]. BINDT publishes an industrial NDT experience log within its PCN document collection [2]. These are examples of program-specific evidence routes, not interchangeable instructions for every employer or credential.

Write the intended method, scope, role, and review route at the top of the working record. If these are still undecided, label the log as a general factual work record. Do not assume that collecting entries alone guarantees that a future issuer will accept them or credit the total in the way you expect.

Record activities close to when they occur

Make entries while the work and supporting references are still available. Record the date or period, employer or authorized work context, method, activity description, role, relevant duration or unit, and the person who can review the entry. This is an administrative description of the work, not a substitute for the technical inspection report.

Use enough detail to distinguish activities without copying confidential project content. A controlled job reference and a concise role description may be more appropriate than including customer findings or proprietary procedure text. The authorized reviewer can consult the underlying records where needed through the employer's process.

Avoid entries such as NDT all week when a later reviewer needs method-specific evidence. Equally, do not manufacture detailed daily entries from a vague recollection years later. If a historical entry is reconstructed from available records, label the reconstruction and identify the sources supporting it.

Keep the original unit and the credited unit separate

Record time or activity in the unit supported by the source. If the source shows hours, preserve hours. If an employer statement describes days or a period of employment, preserve that wording. Any conversion for a particular program belongs in a separate calculation with its rule and reviewer identified.

Do not assume a universal relationship between paid hours, time on site, and qualifying experience. Travel, administration, training, supervised practice, and inspection duties may be treated differently by the applicable program. Record the activities honestly and ask the responsible authority how they should be evaluated rather than maximizing a total by assumption.

When a calculation is required, show the inputs and the basis. A transparent conversion is easier to check than a final number with no explanation. Keep the original values so a later reviewer can apply a different program's rules without attempting to reverse-engineer the earlier calculation.

Prevent overlapping entries from inflating the history

A day can involve several methods or responsibilities. Describe those activities in a way that makes any overlap visible. Do not enter a full shift against each method simply because each appeared somewhere in the assignment. The log should reflect the evidence and the program's accepted treatment of mixed activities.

Use a stable activity or job reference to connect related entries. If a weekly summary draws from daily records, label it as a summary and avoid counting both layers as additional experience. The same principle applies when a supervisor letter summarizes work already present in the log.

Review totals against the underlying period for obvious inconsistencies. This is a data-quality check, not a new qualification rule. A total that exceeds the available time may reveal duplicate entries, an incorrect unit, or a summary counted twice. Resolve the cause rather than reducing the number without explanation.

Make supervisor review meaningful

Identify the person authorized to confirm the activity under the relevant process and what that person is confirming. A signature should have a defined scope: the described work, the period, the role, or another specific fact. Do not ask someone to approve a general experience total they cannot reasonably support.

Provide the supporting references the reviewer needs and allow them to correct inaccuracies. If the reviewer can confirm only part of an entry, retain that limitation. A qualified and honest partial statement is more useful than a broad signature obtained merely to complete a form.

Record when the review occurred. Work date and verification date are different facts. A later confirmation can support earlier activity when accepted by the relevant process, but it should not be backdated to make the review appear contemporaneous. Preserve the actual sequence so another reviewer can understand the evidence trail.

Work through a fictional mixed-activity week

Imagine a fictional trainee, Cameron, whose week includes two methods, classroom learning, and travel. The timesheet shows paid time, while the job references and supervisor notes identify the actual activities. Cameron creates separate factual entries and keeps the classroom learning in the training record rather than silently labeling the entire paid week as inspection experience.

The supervisor reviews the descriptions and corrects one entry that overstated Cameron's role. The log retains the corrected description and the review date. For a later application, the responsible reviewer determines which entries and units can support the applicable experience requirement.

The example does not establish a required allocation formula. Its lesson is to preserve enough factual detail that a reviewer can make the program-specific decision. A single inflated total would be simpler to type but harder to defend, correct, or reuse honestly.

Handle gaps without inventing continuity

A missing period should remain visible. Identify whether the gap is missing documentation, an interruption in relevant work, or uncertainty about what activity occurred. These conditions may lead to different questions under a particular program. Do not fill every calendar interval merely to make the timeline look uninterrupted.

Search authorized sources such as employer records, approved job references, or signed statements where appropriate. Record which source supports each recovered fact. If the evidence remains incomplete, state that limitation in the application summary and ask the receiving authority about acceptable alternatives.

Avoid assuming that a prior credential proves every day of experience during its validity. A credential and a work history describe different things. The log should be built from relevant activity evidence, with the credential used only for the role it actually plays in the applicable review.

Correct entries without hiding the original issue

When an error is found, record the corrected value, reason, source, editor, and review where needed. A simple controlled correction note can be sufficient. The purpose is to explain a material change rather than leave two conflicting totals in circulation or silently rewrite a previously reviewed history.

Distinguish a transcription error from a change in interpretation. Correcting a mistyped date differs from applying a new program's crediting rule. Keep the factual record stable where possible and place the new interpretation in the application-specific summary. This protects the history from being reshaped to suit each submission.

If an error affected an application already submitted, follow the issuer's correction process. Do not assume that updating your local spreadsheet updates the submitted claim. Preserve what was submitted, the correction request, and the response so the final record remains understandable.

Protect employer and customer information

Keep the level of detail proportionate to the purpose. The FTC's security guidance encourages limiting unnecessary personal information [3]. In an experience log, the same practical discipline helps avoid including private customer contacts, sensitive identifiers, or unrelated employee information where a controlled reference would suffice.

Ask the employer which evidence you may retain personally and which must remain in its controlled systems. Do not copy inspection databases or proprietary reports merely because they could help prove experience. An authorized summary or direct confirmation may provide the needed facts without disclosing the underlying material.

When changing employers, request the appropriate statements before access ends where feasible. Keep the custodian's contact route and the evidence index. A portable, authorized summary is more useful than a collection of files that cannot legitimately be shared with the next reviewer.

Prepare an application summary from the factual log

Select the entries relevant to the specific program, period, method, and role. Identify the source records and the calculation basis where one is used. Keep unsupported entries out of the claimed total or label them for review according to the application process. Do not treat the act of summarizing as approval of eligibility.

Have the appropriate person review the summary for completeness and consistency. Compare dates, method labels, units, and supporting signatures. Check that the same experience has not been counted twice through both detailed entries and an employer summary. Preserve the final submitted version with its application reference.

If the issuer requests clarification, respond to the specific question and retain the correspondence. The response may improve the underlying log's usefulness, but it should not erase the distinction between raw evidence and the program's decision about that evidence.

Review a reporting period before it becomes a large total

Choose a practical reporting period suited to the work and the applicable process, then review entries while the source references remain easy to locate. This is a management choice rather than a universal logging interval. The review should check whether the descriptions, dates, units, and supporting references are coherent. A monthly total copied from a timesheet can hide errors that are obvious when individual activities are examined alongside their original context.

For a fictional mixed week, an employee records classroom learning on one day, relevant work on two days, a combined assignment on another day, and travel on the final day. Keep the factual activity descriptions separate before asking how any program would credit them. Do not start with the paid-week total and allocate all of it to the method that is short of claimed experience. The credit question follows the evidence; it should not determine how the history is written.

Ask the reviewer to identify exceptions explicitly. A missing project reference, an uncertain method allocation, or an entry outside the signer's knowledge may need clarification. The remaining well-supported entries need not become inaccurate merely because one item is unresolved. Mark the questionable item separately and avoid adding it to a claimed total until the relevant process permits its treatment. This produces a usable partial record while preserving the limits of what has been confirmed.

At closeout, retain the reviewed version and the outstanding-action list. If an entry changes later, connect the correction to that version rather than overwriting the total without explanation. An application reviewer may need to understand why a later summary differs from a previously signed log. A concise correction trail can answer that question without requiring the supervisor to remember every activity months or years after the work occurred.

Keep source references useful when project access ends

Experience logs often outlive the systems used for the original assignment. Before access ends, ask the employer what references or summaries may be retained and who can confirm the relevant activity later. The answer may be an internal project identifier and an authorized statement rather than copies of technical reports. Preserve enough context for a custodian to find the underlying record without removing controlled customer information from its proper location.

Use a source-reference note that identifies the record class, responsible organization, relevant period, and authorized verification contact. Keep private contact details proportionate to the purpose and update the organizational route when a named supervisor leaves. A personal telephone number in an old notebook is a fragile verification plan. Where possible, identify the employer's continuing records function so the history can remain traceable even when individual staff members change.

If a supervisor becomes unavailable before reviewing the entries, record that circumstance and ask the responsible authority what alternative evidence or review is acceptable. Another person should confirm only what they can support through knowledge or authorized records. Do not transfer a signature from a related document or ask a replacement supervisor to approve the whole total without examining its basis. The factual log remains useful even while its confirmation status is unresolved.

Prepare later summaries from the preserved references and reviewed entries, with a clear statement of their limits. If the receiving program needs more detail than the employer can release, arrange a focused clarification through the authorized parties. Keep the resulting statement linked to the relevant log entries. The goal is a credible, reviewable account of experience that survives normal employment and system changes while respecting the ownership of the underlying work records.

Keep experience tracking distinct from certificate reminders

NDT Connect's certificate manager organizes credential details and dates supplied through profiles. It does not provide an automatic experience-credit decision or submit a log to a certification body. Maintain the detailed activity record in the approved process that supports the relevant employer or issuer review.

A certificate expiry reminder can prompt a review of the evidence needed for renewal, but it cannot reconstruct missing work history. Collect and review experience records as the work occurs rather than waiting for an approaching date to trigger a search through years of emails.

The useful end product is a factual history with clear units, traceable sources, honest limits, and an identifiable reviewer. That gives future decision makers a better basis for assessing experience while protecting the technician from having to defend totals whose origin nobody can explain.