I'm planning to sit for the PCC in early September and wanted to see if my timeline is reasonable based on others' experience. I have about 6 years in project controls (scheduling and cost) but haven't done formal study since finishing my BS. Right now I'm blocking out 1 hour on weekdays and 2-3 hours each weekend day.
The AACEI competency areas I'm least confident in are risk management and earned value methodology - I do EV daily but learned it on the job rather than from the formal ANSI 748 perspective. I've been working through the Skills and Knowledge of Cost Engineering publication, which is dense but seems to be the primary source the exam draws from.
For anyone who's taken it recently: how much of the exam is calculation-heavy versus conceptual? My background is stronger on the conceptual side but I don't want to under-prepare on the math. I saw posts saying roughly 30-35% involves calculations but those were a few years old.
12 weeks is workable with your experience level. I passed on my first attempt after about 10 weeks but I have a pure scheduling background. The calculation percentage sounds about right from what I saw - EV metrics, indices, forecasting formulas. Nothing exotic but you need to be fast.
Risk quantification - Monte Carlo outputs and interpreting confidence levels - came up more than I expected. If that's a weak area I'd spend dedicated time there, maybe 8-10 hours beyond your normal rotation through the domains.
The ANSI 748 framing is worth the time. I failed my first attempt at 71% partly because I was applying EV concepts correctly but wasn't matching the terminology the exam expected. Second attempt I scored 82% after drilling on that alignment specifically.
The calculation portions aren't timed separately so don't panic if they take longer. I flagged the heavier math questions and came back after clearing the conceptual ones. Finished with about 22 minutes to spare overall.
Honestly I almost talked myself out of even sitting for it. Six years in the field and I figured the exam would just confirm what I already knew, but the first practice set I took humbled me fast. The terminology and the formal formulas are a different animal than day to day project controls work, and I kept second guessing whether 12 weeks was enough on a part time schedule. Your timeline is fine by the way. I had roughly the same hours and it worked, I just wish I'd started doing real questions sooner instead of only reading.
What pulled me out of the slump was grinding through actual problems until the patterns clicked, especially the scheduling and earned value stuff since that's where I bled the most points early on. I leaned on this free pcc scheduling time management set a ton in the back half. There were a couple weeks where I genuinely thought about pushing my date, didn't, and ended up passing on the first try. Don't read your low practice scores as a verdict. They're just telling you where to spend the next hour.
Twelve weeks is totally doable with your background, honestly I'd say you're in a better spot than most. The scheduling and cost experience means you're not starting from zero on the concepts, which is where people lose the most time. One thing that made a huge difference for me was working through free pcc scheduling time management questions and really stopping on every wrong answer to understand the reasoning behind it, not just noting the right one and moving on. That habit alone probably saved me from a lot of pattern-matching traps on the actual exam.
Your weekday hour is fine for reviewing material but I'd use the weekend blocks for full practice sets where you're forcing yourself to explain why each distractor is wrong. It's slower at first. Worth it. By week 8 or 9 you'll start seeing the question logic repeat in different packaging and that's when everything clicks.
Quick update from me since I posted a few weeks back in a similar thread -- I'm about 8 weeks out now and just hit 74% on a timed mock covering scheduling and cost. Wasn't where I wanted to be at first but it's trending up. I found the free pcc scheduling time management questions really useful for drilling the weaker areas, especially since I kept second-guessing myself on earned value formulas under time pressure.
Sitting in mid-September, same window as you. With 6 years in project controls you've probably got the intuition already, it's more about learning the PMI framing. Your hour-per-weekday plan sounds realistic if you stay consistent -- I'd just make sure you're doing timed practice sets by week 8 or so, not just reading.
Twelve weeks felt impossibly short to me when I started, and honestly around week six I nearly bailed because the cost engineering side was kicking my butt. I've got similar experience to you, scheduling-heavy, and I assumed that would carry me through. It didn't. The PCC expects you to really know earned value and forecasting mechanics at a depth that day-to-day work doesn't always give you.
But here's the thing -- your schedule is actually fine if you stay consistent. The 2-3 hour weekend blocks are where you'll do most of the real learning, so protect those. I'd say don't panic if week 8 or 9 feels like you're going backwards, that happened to me too and I passed with room to spare. Just don't skip the practice exams thinking you'll circle back to them.
Twelve weeks is doable, especially with your background — six years in scheduling and cost means you're not starting from zero on the hard stuff. I'm a working dad with a pretty packed schedule and I passed studying around 45 minutes most weeknights and a longer session on Sundays. The key for me was consistency over heroics. I didn't try to cram on Friday nights, I just kept the daily habit going.
One thing that tripped me up early was change management, which sounds obvious but it showed up in ways I wasn't expecting. I spent extra time on practice sets like pcc/questions/change management 5 and it helped me see how those scenarios are framed on the actual exam. Your timeline is realistic — just don't let a rough week throw you off. Missing two days isn't a crisis, it's Tuesday.