Start With the Scoreboard, Not the Trap List
Almost every "hardest topics" page for PRINCE2 7 Foundation opens with the seven processes. That is the wrong place to start, and the official syllabus says so.
The PeopleCert PRINCE2 7 Foundation syllabus publishes an exam specification with five learning outcomes and a fixed weighting for each. Here it is, with the approximate question count you get when you apply those percentages to a 60-mark paper:
| Learning outcome | Weight | Approx. questions |
|---|---|---|
| 1. Key concepts relating to projects and PRINCE2 | 3% | about 2 |
| 2. How the principles underpin the method | 8% | about 5 |
| 3. The importance of people in successful projects | 14% | about 8 |
| 4. The PRINCE2 practices | 60% | about 36 |
| 5. The PRINCE2 processes | 15% | about 9 |
PeopleCert publishes the percentages, not a guaranteed count per outcome, so treat the right-hand column as planning arithmetic rather than a promise. Even so, the shape of the paper is unambiguous:
- The practices are the exam. Sixty percent of marks sit in business case, organizing, plans, quality, risk, issues, and progress.
- People outweighs principles. The people element is worth 14 percent; the seven principles are worth 8 percent.
- Processes are a supporting act. Fifteen percent, or roughly nine questions.
- Key concepts are almost a rounding error. Three percent, or about two questions.
If you have been drilling the seven processes and skimming the practices, you have been studying a 15 percent topic at the expense of a 60 percent one. Fix that before you touch a single trap.
free PRINCE2 Foundation practicePractice questions with detailed explanations
The Exam Facts That Change Your Tactics
These come from the PeopleCert PRINCE2 7 Foundation syllabus and the PeopleCert PRINCE2 Project Management Foundation (Version 7) page. Each one should change something about how you prepare.
| Fact | Detail | What it means for you |
|---|---|---|
| Questions | 60, each worth 1 mark | One minute per question, no exceptions |
| Time | 60 minutes | Pacing is a skill you must rehearse |
| Pass mark | 36 marks (60%) | You can miss 24 and still pass |
| Materials | Closed book | The official manual is not permitted |
| Negative marking | None | Never leave a question blank |
| Level of thinking | Bloom's levels 1 and 2 | Recall and understanding, not judgment calls |
| Question styles | Standard, missing word, list, negative | Four formats to rehearse, not one |
| Language accommodation | 25% extra time (75 minutes) if you sit the exam outside your native or working language | Check eligibility before you book |
| Languages | Exam available in 14 languages | Confirm your language is offered |
| Results | Official results in 2 business days | Plan the Practitioner booking around it |
Two of these deserve emphasis because candidates routinely get them wrong.
Bloom's levels 1 and 2 only. Foundation asks you to recall and understand. It does not ask you to weigh a messy scenario and choose the best of two defensible options, which is Practitioner's job. If a practice question feels like a judgment call with no clean answer, it is probably not a realistic Foundation item.
No negative marking. A blank scores the same as a wrong answer: zero. Guessing is free. Candidates still fail by leaving four or five unanswered items when the clock runs out, which is a pacing failure, not a knowledge failure.
Version Check: Is Your Material Actually PRINCE2 7?
PRINCE2 7 launched in September 2023. PeopleCert then retired the older exams: for PRINCE2 6th edition Foundation and Practitioner in English and most languages, the last day to buy a voucher was 30 June 2024 and the last day to sit an exam was 31 December 2024. A few translations ran longer, to 30 June 2025 at the latest. Nothing you sit today is 6th edition.
The problem is that a great deal of free material online was written before 2023 and never revised. Run this five-point check on anything you study from:
- Practices, not themes. PRINCE2 7 renamed the seven themes to practices. Material that says "the progress theme" is pre-2023.
- Issues, not change. The change theme became the issues practice. The scope widened; it is no longer just change control.
- Five integrated elements. PRINCE2 7 has five: principles, people, practices, processes, and the project context. Material listing four elements is stale.
- Seven aspects of project performance. PRINCE2 7 added sustainability to the 6th edition's six, giving benefits, cost, time, quality, scope, sustainability, and risk. Anything that says six aspects is out of date.
- A 60 percent pass mark. The 6th edition Foundation pass mark was 55 percent (33 of 60). Practice sets still quoting 33/60 were built for a retired exam.
If a page fails two of these five, close it. It will teach you distractors.
Trap 1: Reciting 6th Edition Principle Names
The seven principles did not change in meaning, but three changed in wording, and PRINCE2 7 exam items use the current wording.
| Current PRINCE2 7 name | Older wording you may have memorized |
|---|---|
| Ensure continued business justification | Continued business justification |
| Learn from experience | Learn from experience |
| Define roles, responsibilities and relationships | Defined roles and responsibilities |
| Manage by stages | Manage by stages |
| Manage by exception | Manage by exception |
| Focus on products | Focus on products |
| Tailor to suit the project | Tailor to suit the project environment |
Three single-word edits do all the work. Ensure was added to the business justification principle, relationships was added to the roles principle to reinforce the new people element, and environment was dropped from the tailoring principle. Those are exactly the differences a missing-word question is built around.
The deeper principles trap is treating them as slogans. Principles are rules that decide whether a project is being run the PRINCE2 way, so study each one with the decision it changes and the plausible-sounding answer it rules out.
| Principle | Correct behavior | Trap answer |
|---|---|---|
| Ensure continued business justification | Recheck viability at every stage boundary | Continue because the budget was already approved |
| Learn from experience | Seek lessons before and during the project | Capture lessons only in the closing process |
| Define roles, responsibilities and relationships | Name who decides what, and who talks to whom | Let the team share accountability informally |
| Manage by stages | Plan and authorize one management stage at a time | Approve one detailed plan for the whole project |
| Manage by exception | Escalate a forecast tolerance breach | Escalate every variance to the project board |
| Focus on products | Define products and quality criteria before activities | Start planning from an activity list |
| Tailor to suit the project | Adjust how the method is applied | Drop principles because the project is small |
That last row is the single most common principles trap. Tailoring changes the application of PRINCE2. It never removes the principles.
Trap 2: Answering a Practice Question With a Process
This is where the 60 percent outcome meets the 15 percent outcome, and it is the highest-value distinction on the paper.
- Practices are what you manage continuously. Business case, organizing, plans, quality, risk, issues, progress.
- Processes are when management work happens. Starting up a project, directing a project, initiating a project, controlling a stage, managing product delivery, managing a stage boundary, closing a project.
A practice runs across the whole project. A process occupies a slot in the project's flow. When a question asks how uncertainty is identified, assessed and controlled, that is the risk practice. When it asks what happens before the project board authorizes the next stage, that is managing a stage boundary.
Build the map once, on one sheet:
| Practice | Its PID approach | Its other key management products |
|---|---|---|
| Business case | Benefits management approach, sustainability management approach | Business case, project brief |
| Organizing | Commercial management approach | Project management team structure, role descriptions |
| Plans | None of its own | Plan, project product description, work package description |
| Quality | Quality management approach | Quality register, product register, product description |
| Risk | Risk management approach | Risk register |
| Issues | Issue management approach | Issue register, issue report |
| Progress | Digital and data management approach | Daily log, lessons log, and six of the seven reports |
The syllabus files every report except the issue report under progress; the issue report belongs to the issues practice. The people element then adds two more approaches to the PID: change management and communication management. Count them all and you get the nine PID management approaches named in the Foundation syllabus.
Trap 3: The Management Product Map, Where Most Marks Are Lost
Because the practices carry 60 percent of the marks and most practice items ask about a management product's purpose, this is the highest-yield hour of study in your whole plan.
PRINCE2 7 restructured management products, and old material will actively mislead you here. The 6th edition listed 26 separate products with standalone registers and logs. PRINCE2 7 consolidates them into three groups.
Group 1: the nine PID management approaches. Benefits, change, commercial, communication, digital and data, issue, quality, risk, and sustainability. Every one is part of the project initiation documentation. If a question describes how the project will handle something, the answer is usually an approach.
Group 2: the six project log records. Daily log, lessons log, issue register, risk register, quality register, and product register. These are living records, updated as work happens, and PRINCE2 7 groups them under the single term project log. The product register is new in PRINCE2 7 and replaces the old configuration item records and product status account.
Group 3: the seven reports. Checkpoint report, highlight report, end stage report, end project report, exception report, issue report, and lessons report. These are snapshots that communicate status to someone.
Everything else is a baseline in its own right: the PID, project brief, business case, plan, product description, project product description, and work package description.
Two renames catch people out. PRINCE2 7 says work package description, not work package. And the old change control approach is now the issue management approach.
The fastest decision rule for any product question:
- Does it describe how we will manage something? It is a PID approach.
- Is it updated continuously as work happens? It is a project log record.
- Does it communicate status to someone at a point in time? It is a report.
- Is it an approved reference point under change control? It is a baseline.
Then the classic report pairing: a checkpoint report goes from the team manager up to the project manager; a highlight report goes from the project manager up to the project board. Direction of travel is the whole answer.
Trap 4: Starting Up a Project vs. Initiating a Project
Both happen early, and the exam loves the boundary between them.
Starting up a project answers: is this worth initiating? It is pre-project. It produces enough information, principally the project brief, for the project board to decide whether to authorize initiation.
Initiating a project answers: how will this project be controlled? It builds the project initiation documentation with its management approaches and baselined controls.
The memory rule: starting up makes the case for spending effort on initiation; initiating creates the control baseline for delivering the project.
If a question mentions a project brief, an outline business case, or initial viability, look at starting up. If it mentions the PID, a management approach, or baselined controls, look at initiating. If it mentions authorizing either of those, the answer is directing a project, because that is the only process the project board performs.
Trap 5: Giving the Project Manager the Board's Accountability
PRINCE2 distributes accountability deliberately, and your workplace habits will mislead you. In many organizations the project manager informally owns everything. In PRINCE2 they do not.
| Role | Core accountability |
|---|---|
| Executive | Owns the business case and business justification; chairs the project board |
| Senior user | Represents those who will use the products and realize the benefits |
| Senior supplier | Represents those providing resources and technical integrity |
| Project manager | Runs the project day to day within delegated tolerances |
| Team manager | Delivers assigned work packages, where the role is used |
| Project assurance | Checks the project independently on behalf of the three project interests |
| Project support | Provides administrative and tooling support |
Three traps live in that table. First, an answer that moves business justification from the executive to the project manager: the project manager maintains the business case, but the executive owns it. Second, treating senior user and senior supplier as interchangeable: user interests and supplier interests are different, which is the whole point of the three project interests of business, user, and supplier. Third, letting project assurance and project support blur: assurance checks independently, support administers.
Trap 6: Risk, Issue, and Exception Are Three Different Things
A risk is uncertain: it may or may not happen. An issue has happened, or is happening, and needs management attention now. An exception is a forecast breach of an agreed tolerance, which is what triggers escalation to the next management level.
- "A supplier might miss a delivery date" is a risk.
- "The supplier missed the delivery date" is an issue.
- "The supplier missed it and the stage will now finish three weeks past its time tolerance" is an exception.
Two refinements that PRINCE2 7 will test you on.
Risk includes opportunity. The syllabus defines a risk as a threat or an opportunity based on uncertainty. An answer that treats every risk as a threat is incomplete.
Issues are broader than change requests. PeopleCert's own guidance describes PRINCE2 7 issues as anything that could affect the project, and names problems, concerns, business opportunities, requests for change, and off-specifications. The tightest distinctions:
- Request for change: someone wants to alter an approved baseline.
- Off-specification: something that should be delivered is not, or is forecast not to be, to its agreed specification.
- Problem or concern: anything else needing resolution or escalation.
The classifying question is not "is this bad?" It is "does someone want the baseline changed, or has the baseline not been met?"
One more pair, since it is easy money: a dis-benefit is an expected negative outcome, so it is not a risk. It is planned for, not uncertain.
Trap 7: Treating People as a Chapter to Skim
People is worth 14 percent, nearly double the principles. It is an integrated element of PRINCE2 7, not an appendix.
The syllabus asks you to define the organizational ecosystem, the project ecosystem, change management, stakeholder, culture, collaboration and co-creation, leadership, and management. It asks you to explain the difference between leadership and management, and between people within the project and people affected by the project. It names two PID approaches as people products: the change management approach and the communication management approach.
Exam items rarely say "people element". They describe resistance to adoption, unclear responsibilities, stakeholder conflict, or a communication breakdown. When they do, be suspicious of any answer that only updates a document while ignoring engagement.
The syllabus also has an explicit outcome on how people aspects integrate with the rest of the method, so study people through the other practices rather than in isolation:
- Business case: benefits depend on adoption, which is change management.
- Organizing: roles, responsibilities, and relationships must be explicit.
- Plans: work depends on capability and availability, not just duration.
- Quality: users and suppliers can define acceptable quality differently.
- Risk: stakeholder resistance is a delivery risk, and decision bias is named in the risk syllabus.
- Progress: reporting is a communication act before it is a control act.
Trap 8: Hunting for a Sustainability Chapter That Does Not Exist
Sustainability is genuinely new in PRINCE2 7, which makes candidates over-study it. At Foundation it is narrow and precise.
The syllabus names sustainability in exactly two places: the sustainability management approach, a PID product under the business case practice, and delivery sustainability, part of the guidance for effective management of plans. Separately, sustainability is the seventh aspect of project performance, alongside benefits, cost, time, quality, scope, and risk.
That is your whole Foundation-level sustainability syllabus. You are not being asked to be an environmental, social, and governance specialist. You are being asked to know where sustainability attaches to the method.
The wrong answer pattern is "ignore sustainability because the project is on time and on budget", because PRINCE2 7 measures performance across seven aspects, not two. The opposite over-correction is just as wrong: inventing a sustainability practice or a sustainability process. Neither exists.
The same restraint applies to digital and data. It appears as one PID approach, the digital and data management approach, sitting under the progress practice. Learn its purpose and move on.
Trap 9: Losing Marks to the Question Style, Not the Content
The syllabus names four question styles. Each fails candidates in a different way, and each is worth rehearsing separately.
Standard. A question stem and four options, one correct. The trap is a distractor that swaps a single word, usually a register for a report, or one role for another.
Missing word. A sentence with a blank and four candidate words. These reward exact terminology, which is why paraphrasing every practice, process, and product purpose in fewer than ten words is such an efficient revision technique.
List. Four numbered statements and four combinations; you pick the two correct statements. Work the statements, not the combinations. Mark each of the four as true or false first, then find the option matching your marks. Candidates lose these by reading the combinations first and pattern-matching.
Negative. A standard question with a negatively worded stem, always bolding the word NOT. The syllabus says these are used only as an exception, where knowing what does not happen is part of the learning outcome. Their entire difficulty is that you read past the NOT under time pressure. When you see a bolded NOT, say it to yourself before reading the options.
Pacing: One Minute per Question, Three Passes
Sixty questions and sixty minutes leaves exactly one minute each, including reading. Rehearse this pattern in every timed set:
Pass 1 (about 35 minutes). Answer everything you know immediately. Flag anything that does not resolve within 20 seconds and move on. Do not argue with a hard question on the first pass.
Pass 2 (about 20 minutes). Return to flagged items. Adjacent questions often supply the term you could not retrieve. Eliminate options that violate a principle, then choose between what is left.
Pass 3 (about 5 minutes). Sweep for blanks. There is no negative marking, so an educated guess is strictly better than an empty answer. Finish this sweep before the clock forces it.
If you sit the exam outside your native or working language and qualify for the 25 percent accommodation, you have 75 minutes and 15 minutes of genuine slack. Confirm eligibility with PeopleCert when you book, not on exam day.
The 10-Day Trap-Fix Plan, Weighted to the Syllabus
This plan deliberately allocates time in proportion to the exam weights, which means most of it goes to the practices.
Days 1 to 2: the practices and their products. Build the practice-to-product map from Trap 3 by hand. For each of the seven practices, write its purpose in under ten words, its PID approach, and its records and reports. Answer 40 practice-focused questions.
Days 3 to 4: the management product map. Drill the nine PID approaches, the six project log records, and the seven reports until you can sort any named product into its group in under three seconds. Add the baselines last.
Day 5: people. Cover the ecosystem terms, leadership versus management, change management, stakeholder engagement, communication, and effective teams. Connect each to a practice.
Day 6: processes. Purpose, objectives, and context for all seven. Focus your effort on the starting up versus initiating boundary and on which process the project board performs.
Day 7: principles and key concepts. Current names, the decision each principle changes, the five integrated elements, the seven performance aspects, and the three delivery approaches: linear-sequential, iterative-incremental, and hybrid.
Day 8: question styles. One short set of each style. Practise the list-question technique of marking statements before options.
Days 9 to 10: timed mixed sets. Two full 60-question sets in 60 minutes. Review every miss with the log below. If more than a third of your misses are management products, spend the next block there rather than booking the exam.
How To Log a Missed Question
"I forgot" is not a diagnosis. Write one of these instead, and count them:
- I confused a practice with a process.
- I put a management product in the wrong group.
- I moved accountability to the wrong role.
- I chose a workplace habit over PRINCE2 terminology.
- I treated a risk as an issue, or an issue as an exception.
- I used a 6th edition name.
- I misread a list question or missed a bolded NOT.
- I ran out of time and guessed blind.
After two timed sets you will have a ranked list of your own failure modes. That list, not a generic trap article, is your final study guide.
If You Fail: What Take2 Does and Does Not Cover
PeopleCert publishes no mandatory waiting period before retaking PRINCE2 Foundation.
PeopleCert sells a resit service called Take2, and its rules matter because they are easy to get wrong:
- It must be bought before you sit, but not necessarily at checkout. PeopleCert lets you add it from your candidate profile up to 15 minutes before your session.
- It can never be added after a fail. That is the rule candidates get wrong most often.
- It provides one additional attempt, not unlimited retakes.
- You have six months from your original exam date to book and sit the resit.
- Take2 resits are delivered exclusively through online proctoring.
- A PeopleCert Plus membership includes a Take2 with every eligible exam, so compare the membership price against a standalone Take2 before buying either.
If you fail a second time, you buy a new voucher at full price. Treat Take2 as insurance you decide on at booking, and be aware that PeopleCert bundles the Foundation exam voucher with official materials such as the eBook and learning resource kit, with prices that vary by region, tax, and promotion. Check the live checkout price for your country before you commit.
After You Pass: The Three-Year Clock
PeopleCert lists PRINCE2 Project Management Foundation (Version 7) as subject to renewal every three years. Older articles claiming the Foundation certificate is valid for life describe the pre-2023 policy and are wrong now.
You have three routes to stay current:
- Log 60 continuing professional development points, 20 in each of the three years, through a PeopleCert Plus membership.
- Pass another exam in the same product suite, PeopleCert's Project, Programme and Portfolio Management group, before your renewal date. Every certification you hold in that suite then shares the newer expiry date.
- Retake the Foundation exam.
Foundation is also only one accepted prerequisite for PRINCE2 Practitioner. PeopleCert equally accepts PMP, CAPM, the APM's PMQ or PPQ, and IPMA Levels A to D. If Practitioner is your plan, note that official results arrive within two business days, so you can book the next step quickly.
Final Readiness Checklist
You are ready when you can do all of this without notes:
- Sort any named management product into approach, record, report, or baseline in under three seconds.
- Name all nine PID management approaches and all six project log records.
- State the purpose of each of the seven practices in under ten words.
- Explain starting up a project versus initiating a project, and name the only process the project board performs.
- Give the current wording of all seven principles, including relationships.
- Distinguish risk, issue, and exception, and classify a request for change against an off-specification.
- Name the seven aspects of project performance, including sustainability, and the five integrated elements.
- Work a list question by marking statements before options, and spot a bolded NOT every time.
- Score above 75 to 80 percent on timed 60-question sets with five minutes to spare.
PRINCE2 7 Foundation is a passable exam with a narrow margin. It rewards precise terminology and punishes workplace intuition. The candidate who passes comfortably is not the one who read the most pages; it is the one who put their study hours where the syllabus put the marks.
Buy on Amazon
Take courses on Udemy
