September 8, 2026 · 7 min read
TL;DR: Kick-off appears in nine answer options in this bank and is keyed once. The pattern behind that split is clean enough to use as a rule. Kick-off is keyed when the question asks what a meeting is called. It is a distractor when the question asks what you should do next, because a kick-off announces authority and a plan that both have to exist already. If the stem is asking for your next action and one option says hold the kick-off, that option is usually there to catch you.
Most candidates have run a kick-off. That familiarity is exactly what the item writers exploit, because a kick-off feels like a decisive, well-organised, obviously-correct thing to do, and it reads as the right answer long before you check whether the project is ready to have one.
When the question is definitional rather than procedural.
The single keyed instance in this bank does not ask what to do. It describes a situation and asks you to name it: before any work begins, the project manager gathers the sponsor, the project team, the stakeholders and key contractors to formally announce that the project has been approved. What kind of meeting is this? Keyed is the kick-off meeting, and the explanation names three details in the stem that fix the answer. It happens before any work begins, it gathers those four groups together, and its purpose is to announce approval.
The explanation then says why that combination matters. Everyone hears the same statement of purpose, scope and authority at the same time, so the project starts from one shared understanding instead of several. That is the whole function of the event, and it is also why it cannot be your next action in most scenarios: you cannot announce a purpose, a scope and an authority you have not yet established.
Because a kick-off is downstream of something the scenario has usually not finished.
The bank makes this point three times with different upstream items missing.
In one record, initiating is complete and planning is about to begin. What do you do first? Holding the kick-off is offered. Keyed is reviewing the project charter, because the charter produced during initiating supplies the high-level authority and project information the team needs, and reviewing it grounds the planning that follows. The kick-off is not wrong forever; it is wrong now.
In a second, senior leadership asks you to take the first steps toward launching a project for a new self-service kiosk. One option is to hold a kick-off at once and start pulling resources together. Keyed is gathering the high-level requirements, scope, milestones and risks for a project charter. The explanation is blunt about the sequence: until something formally exists and someone is empowered to spend on it, everything else is unfunded speculation.
In a third, an automotive team has finished the design phase, the customer has accepted every deliverable, and development is next. Two options offer a kick-off or a planning meeting for the development phase. Keyed is a phase gate review to confirm the deliverables are complete and decide whether to continue, and the explanation states the ordering directly: that decision has to be taken before anyone kicks off or plans the phase that follows.
Three different scenarios, one shape. The kick-off distractor is placed at exactly the moment when something else must be settled first.
It looks like a reasonable option sitting one step ahead of where the stem left you.
| What the stem is asking | Kick-off option offered | What is actually keyed |
|---|---|---|
| What kind of meeting is this? | Kick-off meeting | Kick-off meeting |
| Initiating is done, what comes first in planning? | Hold the kick-off meeting | Review the project charter |
| First steps toward launching a new project | Hold a kick-off at once and pull resources | Gather scope, milestones and risks for the charter |
| Design phase accepted, development is next | Kick off the development phase | Hold a phase gate review |
| Iteration missed the product owner's expectations | Run a kick-off workshop on the agile tools | Communicate the vision and each iteration's objectives |
| Scope keeps changing, stakeholders unhappy | Kick off every phase to share the plan | Build a prioritised backlog with iteration reviews |
| When to hold the first status meeting | Shortly after the kick-off | Once the team has demonstrated real progress |
The last two rows are worth sitting with, because they show the distractor working in adaptive contexts too. In the record about the iteration that missed expectations, the kick-off workshop is offered as training on agile tools and techniques. Keyed instead is ensuring the project vision and each iteration's objectives were communicated, because the team and the product owner were working to different pictures of what the iteration was for. Tooling was never the gap.
Common trap: a kick-off feels like the answer whenever a scenario involves confusion, misalignment or a fresh start, so candidates reach for it as a general-purpose fix. In this bank it is offered that way and is not keyed once. Look at what is missing in the stem. If the charter has not been reviewed, if the phase gate has not happened, if the vision has never been communicated, the kick-off is not the remedy, it is the thing that would have carried the remedy had the remedy existed. Every wrong answer here gets explained on that basis rather than just marked wrong.
Yes, and the bank tests it from the opposite direction.
One record describes a kick-off you have scheduled to announce the project, present the plan and build consensus, with time reserved to explain roles and allow discussion. The agenda went out weeks ago. Just before the event, some team members want out. Keyed is to insist they attend on the scheduled date. The explanation says the kick-off is where the team builds shared understanding of the plan, roles and goals, so attendance matters, and that treating it as optional or repeatedly rescheduling around individuals undermines its purpose and momentum.
Notice this does not contradict the pattern above. Once the kick-off is genuinely due, it carries real weight and you protect it. The distractors are about holding one prematurely, not about taking it lightly when it is properly scheduled.
Is the kick-off meeting ever the correct answer on the PMP exam? Yes, but almost only when the question is definitional. In this bank the one keyed instance describes a meeting held before work begins that gathers sponsor, team, stakeholders and contractors to announce the project has been approved, and asks what kind of meeting that is. When the question instead asks what you should do next, kick-off is a distractor in every case measured.
Why is holding a kick-off meeting wrong when the project has just been authorised? Because something has to exist to kick off. In the bank's records, the correct next step at that point is reviewing the charter or gathering the high-level scope, requirements, milestones and risks that produce it. A kick-off announces a plan and an authority that must already be in place.
Should you hold a kick-off at the start of every phase? The bank offers phase kick-offs as a distractor twice. In one record the correct answer at a phase boundary is a phase gate review to confirm the deliverables are complete and decide whether to continue, because that decision has to be taken before anyone kicks off the next phase.
What is the difference between a kick-off meeting and the first status meeting? A kick-off establishes shared understanding of purpose, scope, roles and authority before work starts. A status meeting reports actual progress against the plan, so it needs progress to report. The bank keys holding the first status meeting once the team has demonstrated real work, and names holding it immediately after kick-off as the trap, since a status meeting with nothing to examine is just a second kick-off.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained, not just marked wrong. Start the free 20-question sample to see how often the confident-looking option is the one placed there to catch you. No card, no signup required to try it.
Is the kick-off meeting ever the correct answer on the PMP exam?
Yes, but almost only when the question is definitional. In this bank the one keyed instance describes a meeting held before work begins that gathers sponsor, team, stakeholders and contractors to announce the project has been approved, and asks what kind of meeting that is. When the question instead asks what you should do next, kick-off is a distractor in every case measured.
Why is holding a kick-off meeting wrong when the project has just been authorised?
Because something has to exist to kick off. In the bank's records, the correct next step at that point is reviewing the charter or gathering the high-level scope, requirements, milestones and risks that produce it. A kick-off announces a plan and an authority that must already be in place.
Should you hold a kick-off at the start of every phase?
The bank offers phase kick-offs as a distractor twice. In one record the correct answer at a phase boundary is a phase gate review to confirm the deliverables are complete and decide whether to continue, because that decision has to be taken before anyone kicks off the next phase.
What is the difference between a kick-off meeting and the first status meeting?
A kick-off establishes shared understanding of purpose, scope, roles and authority before work starts. A status meeting reports actual progress against the plan, so it needs progress to report. The bank keys holding the first status meeting once the team has demonstrated real work, and names holding it immediately after kick-off as the trap, since a status meeting with nothing to examine is just a second kick-off.