Start with a diagnostic
Before building a schedule, find out where you stand. Sit practice questions across the five Body of Knowledge domains without revising first and without opening anything. The score matters less than the shape of the result: two domains are usually well behind the rest, and those two decide how your plan is weighted.
- Calculations: minimum thickness, corrosion rate, remaining life, MAWP.
- Welding: procedure qualification and weld examination.
- NDE: radiography, ultrasonics, magnetic particle, penetrant.
- General practice: inspection programmes, roles, records.
- Specific practice: damage mechanisms, repairs, re-rating.
Balance study modes
The exam asks two different things of you, so a plan with a single activity leaves half the paper unprepared. Rotate three: learn the material, practise questions under correction, sit timed sessions. On InspectAhead those are the Learn, Practice and Mock Exam modes, where Learn uses spaced repetition to bring a notion back as you are about to lose it.
Weight the rotation towards your diagnostic rather than the topics you enjoy: the domain you find interesting is rarely the one costing you points. Revisit the weighting at review checkpoints, not every day.
- Learn: guided material and spaced-repetition cards for the rules you keep losing.
- Practice: corrected question sets on the domains your diagnostic flagged.
- Mock exams: a timed session to test stamina and section discipline.
Review and adapt
Close each cycle with a review
Close every cycle with a review instead of a new topic. Re-sit questions on the domain you have just worked, compare with your baseline, and shift the weighting only if the change holds across two sessions. One good session is noise.
Checkpoint on the report, not a feeling
Use the report by domain from a timed mock as the checkpoint, not a feeling of readiness. In signed-in practice, a correct answer you marked as a guess counts for less than a confident one in the mastery estimate. With a paid pass, the AI coach sets out what to prioritise next.
Treat the index as directional
The preparation index in the app, on a scale of 0 to 100, is experimental and internal: it compares your sessions with each other and forecasts nothing.
Retake or delayed exam#
If your sitting is postponed, do not stop and do not restart from the beginning. Drop to a maintenance rotation: short recall sessions on the domains you already hold, one timed section at longer intervals, calculations kept warm by hand. After an unsuccessful attempt, the useful work is diagnostic again: note while it is fresh where you ran out of time and which items you could not place in a code, then check the current eligibility and re-sit rules with API (api.org) and Prometric.
Frequently asked questions
How long should an API 570 study plan be?#
No honest universal answer exists: it depends on your diagnostic, the hours you can protect and how much of this code work is already in your job. Build the plan around review checkpoints rather than a number of weeks.
Can I follow this plan without paying?#
The method costs nothing, and so does the first diagnostic: sample questions are free and a free account gives limited access. Full access to the bank, the timed mock exams and the AI coach requires a paid pass.
Should I read the codes cover to cover?#
No. Read for structure first, so you know which document answers which kind of question, then read in depth where your diagnostic says you are weak. The open-book section tests navigation, learned by searching.
When should I book the exam?#
Take the exam windows, fees and eligibility rules from API (api.org) and Prometric, not from a study guide. Our part is showing what your results say, not when you are ready.