NDT Credential Dates vs Customer Site Access Dates

An inspector's assignment file can contain a method qualification record, a training completion document, a customer induction record and a site-access credential. Several may display an expiry date, but the dates do not describe the same permission or evidence. Start by identifying who issued each document, what it is intended to establish and which organization decides whether it satisfies the proposed task. Do not select the earliest visible date and paste it into every record. That shortcut loses the distinction between a qualification question and a customer-access question.

The free certificate manager organizes entered certification information and relevant expiry dates. It does not convert a site pass into an NDT credential or verify that a person may enter a particular facility. Use it for the evidence categories the actual record supports, and maintain a separate assignment checklist for access and induction requirements through the appropriate project process. A single organized view can reference both tracks, but their underlying documents, dates and responsible decisions should remain distinct.

A document describing NDT qualification can address a method, level, scope or employer program. A customer-access record may address entry, induction or another site-specific arrangement. Neither should be substituted for the other. A current access pass does not establish competence for an examination, while a method credential does not automatically establish permission to enter every customer location. Keep those statements narrow and factual. The actual requirements for the assignment come from the relevant employer, client and project sources, not from a general assumption about how all NDT work is organized.

ASNT's explanation of employer-based programs provides context for understanding that an employer's qualification program has its own requirements. Use that context to ask who determines the person's work scope for this assignment. Separately, ask the customer or site contact who confirms access readiness. The same manager may coordinate both conversations, but the decisions remain different. Keeping the distinction explicit helps prevent an administrative clearance message from being repeated as though it were a technical authorization.

Create one track for qualification evidence and another for customer access or induction. For each entry, record the document purpose, source reference, stated date, applicable location or scope and the party responsible for resolving questions. Use the actual wording without exaggerating what the document proves. If a record has no stated expiry, leave that fact visible and obtain the applicable review guidance rather than inventing a date. A planning review date can be useful, but it should be labeled separately from the expiry shown on a credential. Resolve ambiguous date notation with the source owner before entering it. A value such as 03/04 can be read differently in different document conventions; copying it without clarification can shift an action by a month while appearing perfectly precise.

Add the planned assignment window as a third reference, not as a replacement for either document date. Compare the start, anticipated finish and any likely extension with the relevant records. This exposes a common planning error: everything appears current on the first day, but a site-access or qualification question arises before the work ends. Record the conflict and its owner. The worksheet identifies a need for review; it does not decide that work may continue or that a date can be extended to accommodate the project.

Enter the credential's supported expiry date in its own record. Do not change it to a customer badge date simply to obtain an earlier reminder. That would make the certification record inaccurate and confuse later review. If the customer-access deadline is earlier, maintain an appropriately labeled external action for that separate requirement. Keep the source document and the planning action linked in your own process so the reason for the earlier task remains understandable. The certificate manager's notification workflow is based on entered credential information, not a universal multi-purpose site-access scheduling system.

Similarly, do not move a credential expiry later because the customer has extended a site pass. An access decision does not supply new evidence for the method qualification. When a credential is renewed or amended, update its record from the actual relevant evidence and retain the appropriate history through your document process. The tool does not automatically verify the issuer's decision or determine employer authorization. A clean record means the entered facts have a traceable source, not that every downstream assignment has been approved.

A date printed on a card or shown in a customer system may need interpretation from the issuing organization. Ask whether it relates to an induction, a specific project, a facility, a visit window or another defined arrangement. Confirm the scope rather than assuming that one current record covers all locations associated with the customer. Keep the response in the assignment file or the appropriate controlled process. Avoid inventing a general rule about customer sites when the actual access arrangement is specific to a contract or location.

Also identify the practical lead time for resolving the issue. The site may need information or an appointment before a new access arrangement can be confirmed, but the actual process should come from the responsible contact. Record the required action, its owner and the confirmed timing. Do not rely on a certificate expiry reminder to trigger an unrelated access task. If the assignment date is approaching and the response remains unresolved, make that status visible to the project coordinator rather than presenting the person as fully mobilization-ready because their method credential is current.

The qualification and access tracks can have different states. One may be current while the other needs clarification; both may appear current while the proposed task falls outside the documented scope; or both may require action. Describe those states as evidence conditions, not as automatic permission decisions. The next step is to obtain the appropriate responsible review for the actual assignment. A spreadsheet cell colored green cannot establish technical authorization, and a badge displayed in a profile cannot demonstrate that all project-specific requirements have been met.

Use the qualification evidence planner to organize method, level, role and route questions where useful. Keep customer-access questions in the separate site coordination track. The planner does not contact the issuer, validate the credential or decide site entry. The value of combining the two tracks in an assignment worksheet is that a coordinator can see what remains unanswered and who must respond. It is not a substitute for either organization's actual decision process.

Consider a fictional inspector proposed for work from April 10 through April 20. The relevant qualification record shows a supported June 30 expiry, while a customer induction record shows April 15. The coordinator keeps June 30 in the qualification record and records April 15 in the access track. The date comparison reveals an access question during the planned assignment. The coordinator asks the customer contact how the induction arrangement must be handled for the proposed work period and keeps the response pending until it is actually confirmed.

Now reverse the fictional dates. The customer-access record extends through June, but the qualification record needs attention during April. Renewing or confirming the customer-access arrangement would not resolve that separate qualification question. The responsible employer or receiving reviewer must address the applicable work-scope evidence. The example does not prescribe a renewal period or a universal rule about site entry. It shows why combining the dates into one field creates a misleading picture: a single value cannot accurately explain two different documents and two different decisions.

An assignment coordinator usually needs to know what evidence exists, whether a review is pending and who can resolve it. That does not mean every participant needs a complete personnel file or a copy of every access credential. Share the information required for the specific coordination task through the approved process. Keep sensitive personal details out of broad planning notes and public-facing profile text. The free tools can organize references and questions, but they should not become a reason to distribute more information than the decision actually needs.

Record a useful reference instead of duplicating documents unnecessarily. A worksheet can identify the issuer, document purpose, applicable scope and location of the approved evidence without embedding private identification data. If the customer requires a specific document submission, use its legitimate process and confirm who receives it. Do not assume that entering a date in NDT Connect submits evidence to the customer or grants anyone access to a private account. Manual coordination remains part of the workflow, and its record should make the actual submission and review status clear.

A move to another facility can change the access question even when the method work appears unchanged. A change in examination role or technique can change the qualification question even when the site pass remains current. Reopen the affected track rather than repeating the whole checklist mechanically or assuming nothing has changed. Record the new location, task or responsibility and identify which previous confirmations still apply. Ask the responsible parties to resolve uncertainty; do not infer cross-site or cross-scope recognition from a familiar company name on the document.

If the contract period is extended, compare both tracks with the revised work window. The contract offer comparison can help organize written time and cash assumptions for a real engagement, but it does not check credentials or customer access. Keep a manual link between the commercial extension and the readiness worksheet. That link prevents an accepted longer schedule from being mistaken for completion of the evidence reviews needed to support it. The resulting plan should identify practical dependencies before travel or work commitments are made.

When preparing the report, describe the actual inspector and the supported qualification or authorization reference relevant to the examination. Do not use a customer badge number as though it were a method qualification. Conversely, do not add unnecessary site-access details merely to make the report look more comprehensive. Follow the actual reporting requirement and retain separate administrative evidence where it belongs. The distinction matters because a report reader may interpret a number next to an inspector's name as evidence of technical scope unless its purpose is clear.

The reporting workspace does not automatically pull and validate these details from the certificate manager. Transfer appropriate references deliberately and check them against the actual examination record. A typed name or an issued status is not an electronic signature or independent qualification verification. Keep the responsible review evidence in its proper context. If an administrative record later changes, that does not automatically require rewriting a historical report; assess the relevance and use the applicable correction process where a factual error affects the report. Preserve the distinction between current readiness and past examination evidence.

A completed access task should be closed from the customer's actual confirmation or relevant updated record. A completed qualification task should be closed from the applicable issuer, employer or receiving review evidence. Do not mark both complete when only one response arrives. Record the date, source and scope of the confirmation so a later coordinator can understand what was actually resolved. If a response is limited or conditional, preserve that limitation rather than shortening the note to approved. Clear closure reduces the chance that a future assignment inherits an overstated readiness claim.

Review notification ownership as part of the handoff. The person monitoring certificate reminders may not be the person coordinating customer access. Make the separate responsibilities explicit, especially when staff change or an inspector works away from the usual office. The certificate tool can support its configured reminders, but it does not guarantee that the right person acts on every unrelated project date. Keep a manual review routine appropriate to the assignment and ensure unresolved items have a named destination. An organized date list is useful only when it leads to the correct responsible action.

After the assignment, keep the two-track worksheet structure for future planning, but reassess the actual documents and scope each time. Do not copy the prior job's access confirmation into a new location or assume a current credential covers every future task. Reuse the questions: what does the document establish, which date belongs to it, what work window is proposed and who decides whether it meets the requirement? Those questions remain useful even when the customer, method or engagement arrangement changes.

The finished record should make the next review straightforward. A coordinator can see the qualification evidence, the separate access evidence, their applicable dates and the status of any project-specific questions. The person maintaining the certificate manager can keep its entries accurate without trying to turn it into an invented universal access-control system. That is the practical benefit of two date tracks: each record retains its meaning, each action reaches the right owner, and the assignment plan becomes clearer without claiming that a calendar or reminder automatically authorizes inspection work.