September 7, 2026 · 6 min read
TL;DR: The steering committee appears in 17 of the bank's answer options: 2 keyed, 15 wrong. Both keyed instances hand it a decision that is genuinely its own, backed by analysis. The fifteen wrong ones use it as a venue, an audience, or a referee, and every time there is somebody closer who should have been asked first.
A steering committee is a real governance body with real authority, so the option never looks absurd. That is exactly why it works as a distractor. It is the respectable-looking way to not deal with something.
Twice, and the two cases are different in kind.
As a signing authority. One item asks who can sign the project charter, choose three, and the answers are the sponsor, the steering committee, and the PMO. Each of those has the authority to authorise a project and empower a project manager. The project manager is the one who cannot, because the charter is what grants them their authority.
As a decision-maker, on evidence. A project inside an operations function hits scope changes and delays to critical tasks. The options are a team meeting to decide whether the changes should be included, initiating a change request to modify scope and timelines, conducting an impact analysis and presenting the results to the steering committee for approval, or reporting the concerns in the weekly PMO report.
Keyed is the impact analysis plus the steering committee. Changes of this size are approved by the body that governs the project, and they are approved on evidence. The analysis quantifies what the changes and delays do to objectives, timelines, and resources; putting it to the committee gets a decision from the people entitled to make it.
Look at what the two closest distractors omit. The team meeting has the wrong people deciding. The change request drafted first skips the analysis the decision rests on. Neither is wrong because it avoids the steering committee. They are wrong because they either misplace the authority or skip the evidence.
That is the whole rule: the committee is keyed when it is holding a decision that is genuinely its, and you arrive with the analysis it needs.
When somebody closer owns the problem. In every one of the distractors, the stem has already named that person.
| Scenario | Steering committee option | Keyed instead |
|---|---|---|
| Team assigned at 50% keeps getting pulled to day jobs | Talk to the committee and arrange for more resources | Negotiate written assignments with the functional managers |
| Functional manager says they were not properly engaged | Escalate so your point of view is heard | Demonstrate integrity, build trust, see it from their side |
| Developer hits ambiguity in acceptance criteria | Call a committee meeting to discuss the feature | Collaborate with the product owner to resolve it |
| Two-year research project closing | Convene the committee to announce completion | Confirm the planned knowledge transfer is carried out |
The resource item is the clearest. Members assigned at 50% availability are being pulled back into their day jobs and the project is slipping. Asking the steering committee for more resources adds people to a project that cannot hold the ones it already has. The keyed answer negotiates with the functional managers who control those people, turning a vague "50%" into written assignments with stated scheduling priorities, so the next competing demand has something to argue against.
Common trap: escalating to the steering committee so your point of view is heard. That phrase, or something close to it, is offered in the bank and it is a tell. A functional manager complains they were not properly engaged and that the programme is now missing requirements; you believe you captured everything; your programme manager asks you to handle it from a win-win perspective. Escalating loses to demonstrating integrity, building mutual trust, and looking at the situation from the manager's point of view. Win-win is not splitting the difference and it is not arbitration. It requires enough character to hear a criticism without defending it. An escalation that exists to get your view on the record is the opposite of that, and this bank keys against it.
Governing is a decision the committee owns arriving with the analysis it needs. Escalating is a decision you own arriving in somebody else's meeting.
The closing item makes the distinction almost physical. A two-year research initiative is wrapping up, and one option convenes the steering committee to announce the project is complete. It loses to confirming the planned knowledge transfer activities are carried out, because closure is where a project's knowledge either transfers or evaporates. Two years of findings are at stake, and the announcement can follow. The committee has nothing to decide here, so summoning it is ceremony.
Before you pick a steering committee option, ask what decision you are putting in front of it and whether you have the analysis to support one. If the honest answer is "I want backup," it is a distractor.
When is the steering committee the keyed answer on the PMP exam? When a decision genuinely belongs to it and you have the analysis to support one. One bank item keys conducting an impact analysis and presenting the results to the steering committee for approval; the analysis is what makes it keyed.
Can a steering committee sign the project charter? Yes. One bank item lists the sponsor, the steering committee and the PMO as parties that can sign, because each has the authority to authorise a project and empower the project manager. The project manager cannot sign their own charter.
Why is escalating to the steering committee usually wrong? Because the scenario almost always names someone closer who owns the problem: a functional manager holding the resources, a product owner holding the acceptance criteria, or the person you are in conflict with.
Is a steering committee the same as a change control board? Not necessarily. A change control board evaluates and approves changes to baselines; a steering committee is a broader governance body that can authorise a project, approve major changes, and hold the project to its business case.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: The Escalation Ladder: 27 Keyed Answers, 227 Distractors and Project Governance: Who Decides What, and Where Your Authority Ends. Governance is mapped on the Business Environment study page.
When is the steering committee the keyed answer on the PMP exam?
When a decision genuinely belongs to it and you have the analysis to support one. One bank item keys conducting an impact analysis and presenting the results to the steering committee for approval; the analysis is what makes it keyed.
Can a steering committee sign the project charter?
Yes. One bank item lists the sponsor, the steering committee and the PMO as parties that can sign, because each has the authority to authorise a project and empower the project manager. The project manager cannot sign their own charter.
Why is escalating to the steering committee usually wrong?
Because the scenario almost always names someone closer who owns the problem: a functional manager holding the resources, a product owner holding the acceptance criteria, or the person you are in conflict with.