PMP 3-Month Study Plan: Week-by-Week Schedule (Working PMs)

When I first sat down to prepare for the PMP exam while holding a full-time job, the biggest question was not "what do I study" but "when on earth do I study it." I had a delivery role, a young family, and a calendar that looked like a Tetris board on the wrong setting. The standard advice of "study for 150 hours" felt useless without a structure. I needed a plan, not a vibe.

What I ended up building, and what I now recommend to every working professional I mentor, is a tight 12-week programme that assumes 6-8 hours a week. That is one hour on weekday mornings, two hours on a weekend day, and a longer Sunday block. It is not heroic. It is realistic, and that is exactly why it works.

In this guide I will walk you through the same week-by-week schedule I have refined across dozens of candidates. You will see what to read, what to practise, when to start mocks, and how to time your final brain dump. Treat it as a default plan, not a sacred text. Adjust where your life demands it, but do not skip the structure.

I have watched candidates try the four-week sprint, and I have watched them fail. The PMP is not a knowledge exam in the way university finals are. It is a behavioural and situational exam dressed up as a project management test. You are being asked, again and again, what a senior PM would actually do in a messy room with incomplete information. That kind of judgment does not get installed in a fortnight.

Twelve weeks works because it gives you three distinct phases. In the first month, you build the vocabulary and the mental model. In the second month, you load the depth - knowledge areas, agile ceremonies, hybrid choices. In the third month, you stress-test your thinking against full-length mocks and patch the holes before they cost you in the test centre.

A 12-week window also matches how adults actually learn while working. You hit a topic, sleep on it, see it again next week in a different context, and your brain finally encodes it. Cramming skips the consolidation phase, which is where real understanding lives.

Six to eight hours a week is the sweet spot. Less than five and the material decays faster than you can rebuild it. More than ten and you burn out before week eight.

Here is the rhythm I recommend, and the one I used myself.

Mornings beat evenings for this exam. After a workday, your situational judgment is shot, and PMP questions punish tired thinking. Move your study to the start of the day even if it hurts for the first fortnight.

Before we go week by week, here is the shape of the whole plan.

• Month 1 - Foundation. Decode the ECO, install the PMP mindset, read through PMBOK 7 once, finish the spine of your training course.
• Month 2 - Depth. Drill knowledge areas, master agile and hybrid behaviours, start topic-specific quizzes, build your error log.
• Month 3 - Performance. Full-length mocks weekly, weak-area reinforcement, brain dump practice, exam day rehearsal.

The single most common mistake I see is candidates spending eight weeks on month one and then panicking through months two and three. Protect the calendar. Move on even when you do not feel finished.

If a week slips, do not extend the plan. Cut the lowest-value activity that week and stay on schedule. The exam date is the anchor.

The first month is about scaffolding. If you try to memorise inputs and outputs in week one, you will quit by week three.

Start with the PMI Examination Content Outline. Print it. Read it three times. Highlight every task statement that includes a verb you would expect from a senior PM - facilitate, empower, resolve, support, mentor. These verbs are the PMP mindset in disguise, and they predict the right answer in roughly seven out of ten situational questions.

Next, pick one core training course and commit. Do not graze across four. I usually point candidates at Andrew Ramdayal's 35-hour course on Udemy or the PM PrepCast, but the specific choice matters less than finishing one. By the end of month one you should have completed at least 60 percent of your chosen course and read PMBOK 7 cover to cover, even if some of it felt abstract.

The PMBOK 7 read is not for memorisation. It is for vocabulary and the twelve principles. Highlight the principles. They are the answer key to a surprising number of People domain questions.

Month two is where most candidates either consolidate or collapse. The shift in this month is from input to output. You stop just consuming content and start producing answers.

The work splits into three streams that run in parallel:

• Knowledge area drilling.Risk, procurement, quality, schedule, cost, communications, stakeholders, scope, integration. One area per week, with 30-50 topic-specific questions at the end of the week.
• Agile and hybrid fluency. Scrum events, Kanban flow, SAFe at a high level, servant leadership behaviours, hybrid tailoring decisions.
• Mindset reinforcement. Re-read the twelve principles every Sunday. They drift out of your head fast.

I tell candidates that month two should produce at least 600 practice questions completed, all logged in an error tracker. Without the error log, you are just exercising; you are not actually learning from mistakes.

By the end of month two you should know which two or three knowledge areas are your weak spots, and your mock performance should be hovering in the 65-70 percent range on topic quizzes.

Month three is the performance phase. I treat it the way an athlete treats taper week, except for four weeks instead of one.

You will run one full 180-question mock every weekend. You will do targeted weak-area drills midweek. You will practise your brain dump until you can write it in under three minutes. And in the final week, you will deliberately do less, not more.

The temptation in month three is to keep adding content. Resist it. By this point the gap between you and a pass is not what you do not know - it is how reliably you can apply what you already know under timed conditions. New content disrupts that. Drilling consolidates it.

I will break down each of these weeks in detail below.

Week one is administrative as much as it is academic, and that is fine.

•  Read the PMI Examination Content Outline three times. Highlight the verbs.
•  Choose your one primary course. Buy it. Start it.
•  Choose your one question bank. PM Exam Simulator or PrepCast Simulator are my defaults.
•  Set up an error log. A simple spreadsheet with columns for question ID, topic, your answer, correct answer, and why you were wrong is enough.
•  Block your study calendar for the next 12 weeks. Recurring invites. Treat them like work meetings.

Aim to complete 6-8 hours of video this week and 20 questions to calibrate where you stand. Do not panic at your score. The week one baseline is meaningless. It only matters where you finish.

The People domain weights 42 percent of the exam, so I open with it.

Across these three weeks you cover stakeholder engagement, team formation, conflict resolution, servant leadership, emotional intelligence, virtual teams, and team performance management. In parallel, you work through the predictive lifecycle - scope, schedule, cost, integration - because most People domain questions are dressed in predictive clothing.

By the end of week four you should have:

•  Finished roughly 80 percent of your primary course.
•  Completed about 250 practice questions.
•  A mock test score in the 60-65 percent range on a short 50-question diagnostic.

If your People domain score is below 60 percent at this point, you have not internalised servant leadership behaviours. Go back to the twelve principles and re-anchor.

The Process domain is the largest single domain at 50 percent and absorbs everything you have learned about the technical side of project management. This is where I push candidates hardest.

Week five is risk and quality. Week six is procurement, schedule and cost. Week seven is communications, integration and the agile lifecycle as a whole - Scrum events, Kanban metrics, story points, velocity, burn-down and burn-up charts.

 The exam does not test agile and predictive separately. It tests your judgment about which approach fits which situation, and how to blend them. Train for that.

By the end of week seven, you should hit 70 percent on a 90-question topic-mix mock. If you are stuck at 60, your error log is doing nothing, or you are not reviewing it. Block 30 minutes every Saturday morning just to read your error log out loud. It is unglamorous, and it works.

Business is only 8 percent of the exam, but candidates love to under-prepare it and then lose four to six easy questions on benefits realisation, compliance, and organisational change.

In these two weeks I cover business value, benefits management, organisational change management, regulatory and compliance considerations, and the tailoring decisions that sit at the heart of hybrid delivery. The hybrid questions are subtle. They almost never tell you the project is hybrid. You have to infer it from clues like "the team needs predictability for the auditors but the requirements keep shifting." Train your eye for those.

Targets by end of week nine:

•  100 percent of the course completed.
• Around 800 practice questions done.
•  A full 180-question mock attempted at least once, even if rough.
•  Error log up to date and reviewed weekly.

Now we shift into performance mode. One full 180-question mock each weekend, under timed conditions, with the two breaks built in exactly as you will see them on test day.

After each mock, spend at least three hours reviewing - not just the questions you got wrong, but the ones you got right by guessing. Mark those in your error log too. They are landmines.

Midweek work is targeted. If your last mock showed weakness in risk, you spend Tuesday and Thursday doing 30 risk-only questions each, with a slow review. No new content. No new courses. Just patching.

A reasonable trajectory is week 10 mock at 70 percent and week 11 mock at 75 percent. If you are above 75 percent on a reputable simulator like PM Exam Simulator, you are ready. If you are below 65 percent, push the exam by two weeks. Do not gamble at this stage.

The final week is taper week. Volume goes down. Recall practice goes up.

Here is my week 12 prescription:

•  Monday: 60 minutes, brain dump practice. Aim for under three minutes.
•  Tuesday: 60 minutes, twelve principles plus formulas review.
•  Wednesday: 50 questions, mixed topics, slow review.
•  Thursday: Light. Re-read your error log highlights.
•  Friday: Off. Walk. Eat well. Sleep early.
•  Saturday or exam day morning: light review only, no new content.

Confirm your Pearson VUE booking. If you are taking it online, run their system test 48 hours before. Clear your desk. Lay out your ID. Sleep matters more than one extra mock at this point.

 The single highest-leverage activity in week 12 is sleep, not study. A rested brain finds the right answer on situational questions. A tired one rationalises the wrong one.

I keep my whole prep in one spreadsheet with four tabs.

That is it. No fancy app. No subscription. The error log alone is worth more than any premium tracker. Reviewing it weekly is the single highest-ROI activity in the whole 12 weeks.

I also recommend Pocket Prep on your phone for queue-and-coffee moments. Twenty questions in fifteen minutes adds up over three months.

After mentoring a fair number of PMP candidates, I have seen the same five plan-killers repeatedly.

1. Course-hopping.Buying three courses, finishing none. Pick one. Finish it.
2. No error log. Doing thousands of questions and never reviewing wrong answers. Pure motion, zero learning.
3. Skipping mocks until the last week.You have no idea where you are. You will be shocked, and you will not have time to fix it.
4. Cramming month one for too long.Foundations bleed into depth which bleeds into performance. Move on by the end of week four no matter what.
5. Pushing past 10 hours a week.Burnout in week eight is the most common reason candidates push their exam. Stay disciplined at 6-8.

If you can avoid those five, the 12-week plan does the heavy lifting for you.