How to remove the CPC-A apprentice status and get to a clean CPC

You studied for months, sat the four-hour exam, passed it, and then your certification came back with a letter you weren't expecting: CPC-A, not CPC. That little A stands for apprentice, and for a lot of new coders it lands like a demotion they didn't know was coming.

Here's the short version, so you can stop worrying and start planning. You remove the A by documenting real coding experience to AAPC and having it verified. Most people get there one of two ways: enough time actually working as a coder, or a shorter stretch of work combined with AAPC-approved training that offsets part of the requirement. Once your experience is verified, AAPC drops the A and you hold a clean CPC. That's the whole arc. The rest of this is how each piece works, and how to handle the apprentice year without letting it stall your job search.

What the -A actually means (and what it doesn't)

The A is not a lower score or a lesser exam. You sat exactly the same CPC exam as everyone else and you passed it to the same standard. The apprentice designation exists for one reason: AAPC hands out the plain CPC to people who have both passed the exam and documented on-the-job coding experience. If you pass before you've logged that experience, which is the normal situation for someone breaking into the field, you get certified now and carry the A until the experience catches up.

So read CPC-A as "certified, still building the hours," not "certified with an asterisk against your ability." That distinction matters, because how you talk about the A shapes how employers read it. If you treat it as an embarrassment, they will too. If you treat it as the expected starting point it actually is, it reads as exactly that. I touched on this in what the CPC certification is and who it's for, and it's worth internalizing before you write a single job application.

The two documented paths to dropping the A

There are two routes to removing the apprentice designation, and they're really the same idea at different mixes: prove you've done the work.

The first is straight experience. You work as a coder, accumulate the coding experience AAPC requires, and submit it for verification. This is the default path for anyone who lands a coding role and simply puts in the time.

The second is experience combined with approved education. AAPC lets certain training count toward the requirement so that a shorter period of real work will satisfy it. Its own Practicode program, a bank of real, de-identified charts you code for practice, is the best-known route here, and relevant coursework can factor in as well. The point of this path is to shorten the on-the-job portion for people who don't yet have a coding job but want to demonstrate equivalent, verifiable practice.

Now the honest caveat, and I'd rather give it to you straight than have you plan around a number that's wrong. AAPC sets the exact thresholds itself: how many years the straight path takes, how much of that the education path offsets, what even counts as qualifying work. Those figures change over time. I'm not going to quote you a specific one here and risk it being out of date the week you read this. Before you build a timeline, open AAPC's own apprentice-removal page (it's in your member dashboard and on aapc.com) and confirm the current requirement in writing. Treat that page as the source of truth. A forum thread isn't one, and neither is a course sales page; both are full of stale numbers.

How to actually submit it to AAPC

The mechanics are simpler than the requirement itself. Once you believe you've met the standard, you document it and send it to AAPC through your member account. In practice that means:

• Verification of your experience. AAPC wants proof of the coding work you're claiming, typically confirmed by an employer or supervisor rather than just your own say-so. If your role involves coding but isn't titled "coder," keep a clear record of the coding duties you actually perform.
• Your training records, if you're using the education path. Completion of Practicode or qualifying coursework is documented and submitted alongside the experience you do have.
• Submission through your AAPC profile, where the credential status is updated once everything checks out.

The takeaway: start the paperwork trail on day one of your first coding-adjacent job. The people who struggle to remove the A usually aren't short on experience, they're short on documentation of it, scrambling months later to get a former manager to verify duties nobody wrote down at the time.

Does the -A hurt your job search?

Less than the forums will tell you, if you handle it right. A meaningful slice of entry-level coding postings are written with CPC-A holders in mind, because employers know the apprentice period is where new coders get their first real hours. Those are the jobs that turn your A into a plain CPC. Applying to them isn't settling; it's the on-ramp working as designed.

Where the A does cost you is when you aim only at postings that explicitly demand an experienced, non-apprentice CPC and then read the rejection as being about your competence. It usually isn't. Aim at the roles built for your stage, be plain that you're a CPC-A actively working toward removal, and let the first job supply the experience the second one will want. The wider sequence of exam, apprentice period, and first hire is laid out in how to become a medical coder, and it's worth reading in order so the A lands where it belongs in the plan.

It also helps to understand what the day-to-day actually asks of you, so you can speak to it in an interview even before you've done it for pay. I wrote up what a medical coder does all day for exactly that reason.

What to do while you're still a CPC-A

Don't just wait out the clock. The apprentice period is the cheapest time you'll ever have to get genuinely fast and accurate, because the stakes are lower and the learning curve is steepest. A few things worth doing:

• Keep your books sharp. The speed you built for the exam decays if you stop using it. Stay fluent in the manuals so your first coding job doesn't start with re-learning navigation.
• Log everything codable you touch. Every chart, every claim, every audit correction. This is both how you improve and how you build the documentation trail you'll submit later.
• Consider Practicode if you're stuck without a job. If the classic chicken-and-egg problem has you unable to get experience because you have no experience, the education path exists precisely to break that loop.
• Stay a member in good standing. Your CPC, apprentice or not, depends on maintaining AAPC membership and your continuing education. Don't let the credential you just earned lapse while you're focused on the A.

The honest bottom line

CPC-A isn't a problem to be ashamed of. It's a stage to move through, and the move is mechanical: get verifiable coding experience (or shorten that stretch with approved training), keep careful records of it, and submit it to AAPC. The only real mistakes are treating the A as a verdict on your ability and failing to document the experience so you can prove it when you have it. Confirm the current thresholds on AAPC's official apprentice page, aim your job search at the roles built for your stage, and the A comes off on schedule.

If you're reading this before you've passed, still deciding whether the CPC is even your right first credential or how much the AAPC actually governs here, start with what the AAPC is and what it controls. And if the exam itself is still ahead of you, the cleanest way to shorten the apprentice road later is to pass convincingly now, with enough timed, full-length practice that exam day is a formality. That's what we built the Medical Billing & Coding Study Guide and its simulator around: real exam-format questions and full-length timed mocks, every answer explained, so you walk in ready and walk out with the shortest possible path to a clean CPC.