Prepare for ACCP Level II by studying how a written procedure controls what you may accept, reject, or defer — not just how each NDT method works. Work through realistic inspection scenarios, practice extracting parameters from procedure text, and build a reporting habit in which every call is traceable to a stated criterion. Readiness means you can explain, for any indication, which procedure clause governed your decision and how you recorded it. One verification step first: ASNT's current certification page names ASNT NDT Level II and ASNT 9712 Level II as its central Level II programs, so confirm the exact program name and status you are applying under directly with ASNT before building your study plan.
What a Level II authorization actually permits — and where your responsibility stops
A Level II technician may work independently: reading and understanding inspection procedures, performing the inspection, and producing complete, accurate documentation of results. Responsibility for writing procedures and supervising others rests with Level III personnel.
This division of labor defines what you must master. Level I technicians follow specific instructions under supervision, so their study centers on executing steps correctly. Level II adds interpretation: you must understand why a procedure requires certain settings, techniques, or extents of examination, and you must be able to notice when a real-world condition does not match what the procedure anticipated.
The boundary matters for study planning. Do not spend preparation time practicing procedure writing or audit design — those are Level III functions per ASNT's own role descriptions. Instead, train yourself to read a procedure critically: identify its essential variables, its acceptance criteria, and its reporting requirements, because those are the three things you will apply on every job.
| Role question | Level I | Level II | Level III |
|---|---|---|---|
| Who works under supervision? | Yes, on specified tasks | No — independent field work | No |
| Who reads and applies a written procedure? | Follows given instructions | Reads, understands, and applies it | Applies and authors it |
| Who performs the inspection and records results? | Yes, supervised | Yes, independently | May, but typically oversees |
| Who writes procedures and trains personnel? | No | No | Yes — writing, auditing, training, managing |
Indication versus discontinuity: the distinction that governs every call you make
An indication is what the technique shows you; a discontinuity is the physical interruption or inhomogeneity it may represent. Level II evaluation means interpreting indications against a procedure before calling a discontinuity real, relevant, and acceptable or rejectable.
Conflating these terms produces weak reports and weak exam answers. A magnetic particle or liquid penetrant indication might arise from a crack, from a shallow surface irregularity, or from something non-relevant such as a change in permeability at a heat-affected zone. The indication is the observation; classifying it requires the interpretive steps your procedure defines, which may include re-examination at a different sensitivity, surface preparation, or comparison with a reference standard.
Study each method with this chain in mind: detect the indication, interpret its origin, evaluate its relevance and size against stated criteria, and report the disposition. When you review a practice question, ask which link in that chain it is actually testing. A question about dwell time tests detection; a question about whether a linear surface mark exceeds a length limit tests evaluation. Tagging your knowledge this way makes recall under pressure much more reliable than memorizing definitions in isolation.
- Detection: does the technique reveal the indication at all (sensitivity, surface condition, technique selection)?
- Interpretation: what is the probable source — crack, porosity, geometric feature, non-relevant pattern?
- Evaluation: does the relevant discontinuity meet the procedure's acceptance criteria?
- Reporting: is the disposition recorded with location, extent, and the criterion applied?
Worked scenario: a wall-thickness reading sitting on the acceptance boundary
When an ultrasonic thickness reading falls at or near a minimum acceptable value, the defensible move is to re-verify the reading and report it against the stated criterion — never to round in the favorable direction or exercise personal discretion.
Scenario: an ultrasonic thickness survey on a pipe section shows a reading of 4.9 mm where the procedure's minimum retained thickness is 5.0 mm. A neighboring couplant spot reads 5.1 mm. The plausible mistake is to average the two readings mentally, decide the area is 'really' 5.0 mm, and record it as acceptable. That decision invents an averaging rule the procedure never authorized, and it places a potentially below-minimum wall into service without flagging it.
The better decision: confirm the low reading by re-checking surface preparation and couplant, take additional readings per the procedure's grid or scan plan around the thin spot, and report the lowest verified value against the criterion. If the procedure defines how to treat local thin areas, apply that clause; if it does not, report the finding and refer the disposition to the appropriate authority rather than deciding yourself. This matters because minimum-thickness limits often feed directly into pressure-integrity calculations — a smoothed reading hides information someone downstream may need.
Worked scenario: a linear MT indication the procedure language does not cleanly classify
When an indication's appearance is ambiguous — for example, linear but faint and near a geometric transition — the correct path is re-examination and honest reporting of uncertainty, not forcing the observation into whichever category produces an easy answer.
Scenario: during wet magnetic particle testing of a welded bracket, you see a faint, straight indication about 6 mm long running parallel to the weld toe, within a zone where machining marks are common. The procedure rejects 'crack-like linear indications' but you cannot yet tell crack from scratch. The tempting shortcut is to declare it a surface scratch from grinding, wipe it, and move on. The mistake is skipping the interpretive steps the procedure itself prescribes.
The better decision: follow the procedure's ambiguity path — lightly blend and re-examine the area, or re-magnetize in the required field direction, and check whether the indication persists with the same sharpness. If it persists, treat it as relevant and evaluate it against the crack-like criterion. If it disappears after genuine surface blending, record what was done and the outcome. This matters because an ambiguously classified crack is precisely the discontinuity most likely to propagate, and your report is the only trace of that ambiguity.
Documentation: building a report habit that answers the reviewer before questions are asked
A Level II record must let a reviewer reconstruct what was examined, how, what was found, and which criterion produced each disposition. Study documentation as a reconstruction test: if a stranger cannot follow your report, it is incomplete.
ASNT describes Level II work as ensuring complete and accurate documentation, and that phrasing gives you a concrete standard. Complete means every element the procedure requires is present: identification of the item and area, technique and essential parameters, personnel, and results. Accurate means values are as observed — including uncertain or re-checked findings — not as preferred. A report that shows only accept/reject stamps tells a reviewer nothing about coverage.
Practice by writing reports for your scenario work, then audit your own report the way a Level III auditor would: can you locate the exact clause that authorized each acceptance? Are re-checks and surface blending noted? Are indications described by location, orientation, and size rather than vague terms like 'minor'? Repeating this audit loop turns documentation from a chore into a skill you can demonstrate in scenario-based exam items and in the field.
- Self-check rubric for any practice report: 1 point for item/area identification, 1 for technique and parameters, 1 for findings with sizes and locations, 1 for the criterion applied to each disposition, 1 for notes on any re-examination or deviation. Aim for 5/5 on every practice report before your exam window.
- Red-flag words to eliminate from your own writing: 'minor', 'looks fine', 'within spec' (without citing which spec), and unexplained dashes where a value belongs.
A procedure-extraction exercise you can run this week
Take any complete written NDT procedure you can legitimately access and extract its decision content into a one-page sheet: essential parameters, acceptance criteria, ambiguity clauses, and reporting requirements. This trains the exact reading skill Level II work demands.
Exercise: choose one procedure for a method you are studying. On one page, record (a) every parameter the procedure states numerically, (b) every acceptance or rejection criterion with its clause reference, (c) what the procedure says to do when a result is ambiguous or equipment cannot meet a setting, and (d) what the report must contain. Then close the procedure and rewrite your sheet from memory; reopen and correct it.
Expected observations on a first pass: you will reliably capture the numeric parameters but miss the ambiguity clauses and reporting requirements, because procedures front-load technique detail. That gap is the study target — repeat with two or three procedures across different methods until extraction from memory takes one clean page. Scoring 4 of 4 categories complete from memory is a reasonable personal milestone for this exercise; it measures your extraction skill, not your exam outcome.
An adaptable preparation sequence and readiness checks before you sit the exam
Sequence preparation as: core method concepts, then procedure-driven application, then scenario practice with reports, then mixed review. Readiness is behavioral — you can trace every decision to a clause and produce a complete report unaided.
A realistic adaptable sequence: weeks one and two, build or refresh core concepts for each method in your scope, using the indication chain (detect, interpret, evaluate, report) as your organizer. Weeks three and four, run the procedure-extraction exercise and add flashcards only for criteria, definitions, and terms you repeatedly miss. Weeks five and six, work scenario sets and write a full report for each, scoring it with the rubric above. Final days, mix methods and roles so you are switching between concept questions and scenario judgment, the way any assessment combining general and specific content will require.
Readiness checks to finish with: you can state, from memory, the Level II role boundary; you can classify a fresh indication through the full chain and name the governing clause type; you can produce a rubric-perfect report in one sitting; and you can explain your worst scenario decision out loud without notes. Treat any weak check as a targeted review item, not a general reason to reread everything. For program names, application steps, eligibility documentation, and current exam administration details, rely on ASNT's official certification pages rather than secondhand summaries — including confirmation of which central Level II credential you are actually pursuing.
- Check 1: Explain the Level I / II / III responsibility split in three sentences without notes.
- Check 2: Walk a new indication through detect → interpret → evaluate → report, naming what evidence each step needs.
- Check 3: Score 5/5 on the documentation rubric for two consecutive practice reports.
- Check 4: Complete a procedure-extraction sheet from memory hitting all four categories.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.