What Happens During a Certification Audit?

An audit notification is not an accusation. It is the certification body saying: prove the three or four claims your application made. Everything that happens between the notification email and the outcome is organised around those claims — your education, your experience, and any required training hours — and your job during the audit is simply to turn each claim into a document someone else can check.

This walkthrough is for candidates already selected. Why audits exist, how selection works and how common they are is covered in how certification audits work; the record-keeping habits that make an audit trivial belong to how to prepare for a certification audit. Here we stay inside the audit itself, using PMI's well-known Project Management Professional (PMP) audit as the running example because it is the audit most candidates will ever meet.

Step 1: the notification, and what it freezes

The audit begins with a notification through the certification body's official channel — for PMI, tied to your pmi.org account and application. Read it twice, because it is the authoritative document for your specific audit: it names what evidence is required, how to submit it, and your deadline. Those specifics vary and change, so treat the notification and the provider's current certification handbook as the source of truth over any blog post, this one included.

Two practical effects kick in immediately:

• Your progress pauses. You will not move forward to payment or exam scheduling (or, in an audit triggered at another stage, to certification) until the audit closes. If you had a study timetable pegged to an exam date, expect it to shift.
• The clock starts. Audits run on a deadline stated in your notification. Missing it is itself an outcome — audits can close against you for non-response, not only for bad evidence — so the first thing to diarise is the date.

Step 2: mapping the requests to your application

Audit requests mirror the application's claim types. For a PMP application, the claims are: a degree or secondary diploma, 36 or 60 months of project leadership experience (depending on your education path), and 35 contact hours of project management education. The evidence requested maps one-to-one:

1. Education claim → proof of your qualification. Typically a copy of the diploma or degree certificate you cited. If your certificate is in another language or under a former name, deal with that mismatch now, not in a follow-up round.
2. Training claim → proof of your contact hours. Certificates of completion from the training provider(s) you listed, supporting the hour counts on the application.
3. Experience claim → third-party verification. This is the step candidates fear and the reason audits take real calendar time: the managers, supervisors or colleagues you named on the application are asked to confirm your experience descriptions — classically by signing off the very entries you wrote. You are now dependent on other people's inboxes and diaries.

Notice what is not on the list: nobody asks you to re-prove your competence, resit anything or write new essays. The audit checks that what you already wrote is true.

Step 3: the verification round-trip

The experience verification is where audits are won smoothly or lost slowly, so run it like a small project:

• Contact every verifier before the forms do. A thirty-second heads-up ("PMI is auditing my PMP application; you'll receive my project summary for Project X to confirm and sign") converts a puzzling request into a two-minute favour.
• Send them what they are confirming. A verifier should see the exact description and dates they are endorsing. If your write-up was accurate — the standard argued for in our guide to common certification application mistakes — this is painless.
• Have a fallback for the unreachable. A supervisor who has left the company or a firm that no longer exists is a solvable problem, but the solution is provider-specific: ask the certification body, through the contact route in your notification, what alternative verification it accepts. Do not substitute a different signatory on your own initiative.
• Track completion. Chase politely at the halfway point of your deadline, not the day before it.

While gathering documents, resist the urge to "improve" anything. If you discover a genuine error in what you submitted — a wrong date, an overcounted month — disclose it through the audit channel rather than papering over it; the process for correcting a mistake on a certification application is a companion read.