NRCan NDTCB NDT Level 2: Studying for Judgment, Not Recall

Prepare for NRCan NDTCB NDT Level 2 by studying three linked ideas: the scope of Level 2 authority relative to Level 1 and Level 3, the separation between detecting and recording an indication versus evaluating it against the governing document, and the discipline of working only inside the written procedure in force. Drill the boundary with scenarios, keep a self-check rubric, and treat every practice decision as a documentation question as much as a technical one.

What a Level 2 certificant may and may not decide

Level 2 sits between Level 1 and Level 3. You set up equipment, perform tests, interpret and record results, and can supervise Level 1 work, but procedure preparation and approval rest with Level 3.

This three-level structure matters because every exam-style question about a judgment call has a hidden second question: whose responsibility is this? Setting up a UT instrument and scanning a weld is Level 2 work. Writing or revising the written procedure, approving a technique change, or interpreting an unfamiliar code requirement belongs to Level 3. When you practise, label each step of a scenario with its level.

A useful drill: write out a full inspection workflow from job setup to final report, then mark each step L1, L2, or L3. Expected observation: nearly everything from calibration through reporting is L2, while procedure authoring, technique justification, and acceptance-criteria selection are not yours. If your marking shows you evaluating results against a criterion you chose yourself, you have drawn the boundary in the wrong place, and that error carries into real work and into scenario answers alike.

Interpretation versus evaluation: two words that change your report

Interpretation is determining what an indication is, its location, size, and character. Evaluation is comparing that finding against acceptance criteria in the governing document. Level 2 does both, but each needs separate evidence.

These terms are often used interchangeably in conversation, and that blurring causes problems on paper. Interpretation answers: is this indication relevant, what type of discontinuity does it suggest, where is it, and how long or deep is it? Evaluation answers: does that finding meet the acceptance requirements of the referencing specification or contract? The first is a technical characterization; the second is a comparison against a document you did not write.

Practise the separation by splitting a past finding into two report lines. Line one: indication, method, technique, location, extent, character. Line two: applicable document and clause referenced, acceptance decision, disposition path. Expected observation: if you cannot fill line two without hunting for the governing document, your study has overemphasized detection skills and underemphasized the paper trail that makes a Level 2 report defensible. Both lines belong in your practice notes for every method you study.

Discontinuity or defect: why the vocabulary decision matters

A discontinuity is any interruption in the structure; a defect is a discontinuity that the applicable acceptance criteria reject. Calling every indication a defect is an evaluation made without, or before, consulting the governing document.

This distinction is small on the page and large in practice. A slag line, a porosity cluster, a lamination, or a surface crack is a discontinuity regardless of context. Whether it is a defect depends entirely on the acceptance criteria in the code, specification, or contract that governs that particular job. The same porosity can be acceptable on one weldment and rejectable on another, so the finding itself cannot carry the verdict.

Build the habit with a simple two-column exercise. Take ten written findings and sort each into 'characterization' language versus 'disposition' language. Expected observation: phrases like 'rounded indication, 2 mm, mid-thickness' belong in characterization, while 'reject, repair required' belongs only after naming the clause that rejects it. If a sentence mixes them, rewrite it. This habit keeps your scenario answers, and your eventual reports, aligned with the way the work is actually structured.

Scenario 1: a UT indication on a butt weld

An ultrasonic Level 2 finds a mid-weld indication. The common mistake is rejecting it against criteria remembered from a different code. The better decision: characterize it fully, then compare it only to the job's governing document.

Worked scenario: you are performing UT on a full-penetration butt weld, and your search unit finds an indication with a reflector depth near mid-wall and a length of roughly 8 mm in your labelled worked example. The tempting shortcut is to say 'over the length limit, reject' using a limit you recall from training material written for another code. That skips the interpretive work and imports criteria from a document that may not govern this job at all.

The better decision sequence: first interpret, identifying the indication class, depth, length, and amplitude behavior, and record it per the procedure's reporting requirements. Second, open the applicable specification for this contract and evaluate the recorded parameters against its stated criteria, citing the clause. Third, report. Why it matters: the same recorded indication can be acceptable or rejectable under different governing documents, so your report's credibility rests on the interpretation-then-evaluation order, not on memorized numbers. Rehearse this sequence until it is reflexive.

Scenario 2: surface methods and the relevant-indication question

A magnetic particle examination shows a broad, fuzzy line of particles. The mistake is reporting it as a crack. The better decision: re-check surface condition and technique, then classify the indication before any disposition.

Worked scenario: during MT on an as-welded surface, particles build along a wide, diffuse band near the weld toe rather than forming a sharp, well-defined line. Reading it as a crack and calling for repair feels decisive, but diffuse, broad accumulation can reflect surface condition, grinding marks, or permeability variation rather than a relevant indication. The initial observation alone does not settle the classification.

The better decision: verify surface preparation meets the procedure, check your field, and re-examine; if the pattern stays diffuse and lacks definition, characterize it cautiously and, where the procedure allows, consider a supplementary surface method such as PT or a visual check to assist interpretation, then record what you did and what you observed. Why it matters: mislabeling a non-relevant pattern as a crack triggers unnecessary repair, while dismissing a real crack does the opposite. The discipline is not boldness; it is verification before classification, with each step written down.

Procedure discipline, calibration records, and defensible documentation

A Level 2 works inside the written procedure in force: the approved technique, the required equipment checks, and the reporting format are fixed. Deviations and equipment checks must be recorded so results remain traceable.

Every method you study has the same documentation skeleton: equipment and setup used, reference standards or calibration steps performed and when, the procedure revision applied, findings, and the signature trail. Learn each method's specifics inside that skeleton rather than as free-floating facts. For example, an instrument's calibration check is not just a technical step; it is the record that lets anyone later trust the readings you reported that day.

Practical exercise: take any written procedure available to you, or write a one-page outline for your primary method, and list which items a Level 2 must follow exactly, which require a documented decision, and which must go back to a Level 3. Expected observations: technique parameters and acceptance criteria are follow-exactly items; an unclear indication or an equipment anomaly is a documented decision; changing the technique itself is an escalation. If you find yourself treating a technique parameter as negotiable, rewrite your note until the escalation is explicit.

An adaptable preparation sequence and readiness rubric

Study in four passes across your available weeks: method fundamentals, the Level 2 responsibility boundary, scenario practice with full report lines, and a self-check rubric. Adapt the pace to your timeline, not to a fixed schedule.

Pass one, fundamentals: for each method in your scope, outline equipment, setup, techniques, and common discontinuity appearances. Pass two, the boundary: annotate that outline with L1, L2, and L3 labels and the documentation required at each step. Pass three, scenarios: work written cases for each method using the two report-line format from earlier sections, always ending at the governing document. Pass four, review your own errors and redo the cases you characterized or dispositioned incorrectly.

Self-check rubric with learning-milestone targets: for each practice scenario, award a point for correct characterization language, a point for correct separation of interpretation from evaluation, a point for citing the governing document rather than recalled numbers, and a point for correct level-of-responsibility decisions. Eight of eight across two consecutive scenarios suggests the concepts are settling; lower scores identify which pass to repeat. These scores measure study progress only and predict nothing about the actual assessment. Administrative details such as certification requirements and eligibility belong to NRCan's NDTCB, linked below, and should be confirmed there rather than inferred from any study guide.

References and further reading

Use these references to explore the concepts and check the latest information from the relevant organizations.

• ndtcanada.ca
• nrcan.gc.ca

Continue your preparation

• Nrcan Ndtcb Ndt Certification Level 2
• Study Guides