September 8, 2026 · 8 min read
TL;DR: The statement of work appears in sixteen options in this bank and is keyed three times. Its failures are almost all failures of timing, not of meaning. The procurement SOW is written before a tender goes out, as one of the things a vendor has to be told in order to bid, so any option that offers it after proposals have been evaluated or after an agreement has been signed is placed there to catch a candidate who knows the term but not its position in the sequence. The other reliable split is ownership: a statement of work comes from the customer, a project scope statement comes from your team.
This is a topic where knowing the definition is not enough to score. Every distractor here names a real artifact that genuinely exists and genuinely belongs to the project. It is simply being offered at the wrong moment.
Who writes it.
The bank asks this directly and the keyed answer is the ownership one: the statement of work is prepared by the customer, while the project scope statement is developed by the project management team. The explanation adds that the SOW is typically supplied by the customer or sponsor to describe what is needed, and the project scope statement is produced by the project management team during planning.
The three distractors are each a different plausible-sounding rule, and it is worth naming them because they are the shapes candidates invent for themselves. That the SOW takes a functional view while the scope statement is physical or technical. That the scope statement is usually written first. That a scope statement can become a contract document but a SOW cannot. The bank notes these reverse the views, the sequence, or which document can be contractual.
The scope statement's own contents get tested separately, and the SOW appears as a distractor there too. Asked what the project scope statement must contain, keyed is the scope description, deliverables, acceptance criteria and exclusions. The option pairing the scope management plan with the statement of work and the traceability matrix is wrong on all three counts. The bank's explanation makes a point about exclusions worth keeping: unstated exclusions are where late disputes come from.
Before the tender, as an input to it.
The clearest record has a steering committee approving the outsourcing of automation technology the company has never used and for which the team has no resources. What next? Keyed is creating the procurement statement of work and the source selection criteria.
The explanation is worth reading carefully because it teaches how to read the stem rather than just the answer. Notice what the stem has already settled: the company lacks the technology, the team has no resources, and the steering committee has approved outsourcing. That is the make-or-buy decision, taken by the body entitled to take it. So the distractor offering a make-or-buy analysis to confirm the decision revisits a closed question and delays the procurement. What comes next is preparing what a vendor has to be told in order to bid.
Now flip it. Another record has a project manager who has already settled source selection criteria, advertised the opportunity, evaluated proposals and selected a seller. What next? Developing the procurement management plan and the procurement statement of work is offered. Keyed is administering the agreement and monitoring seller performance. The explanation says the tendering stage is behind the project manager rather than ahead of them, and that the plan and the SOW belong to sourcing strategy, earlier still.
Same artifact, two records, opposite verdicts, and the only thing that changed is where the stem left you.
It tracks the tendering sequence almost exactly.
| What the stem has already established | SOW option offered | What is actually keyed |
|---|---|---|
| Steering committee approved outsourcing | Create the procurement SOW and selection criteria | Create the procurement SOW and selection criteria |
| Seller selected, agreement signed | The procurement SOW is the output | Agreements with the selected sellers |
| Tender complete, seller selected | Develop the procurement plan and SOW | Administer the agreement and monitor performance |
| Urgent contracted work, severe time pressure | Include a detailed contract SOW | Incentives to motivate fast delivery |
| Team morale has dipped during execution | Consult the statement of work | Consult team performance assessments |
| Writing the project scope statement | Scope plan, SOW and traceability matrix | Scope description, deliverables, acceptance criteria, exclusions |
| Describe what a business case is | A more detailed statement of work | A documented economic feasibility study |
The urgent-contract record is the one that surprises people. A firm needs outside work performed as fast as possible, and one option is a detailed contract statement of work. Keyed is incentives. The explanation accepts the premise rather than fighting it: because this is an emergency, there is rarely enough time to prepare a detailed statement of work or to vet subcontractors, so the practical approach is a cost-reimbursable contract with incentives that motivate the contractor to deliver quickly without inflating the scope.
That is a genuinely uncomfortable answer for a candidate trained to believe documentation is always right, and it is exactly why it is tested.
Common trap: treating any recognised artifact name as a safe answer. The statement of work is a real document that this project really needs, which is what makes it such an effective distractor in the two post-tender records and in the team-morale record, where consulting the SOW to understand a dip in team mood is offered alongside the charter and the cost baseline. Keyed there is team performance assessments, and the explanation notes that the charter, cost baseline and statement of work do not address team dynamics at all. Before you pick a document, ask what question it answers and whether that is the question being asked. This bank names the losing document in its explanations rather than only marking the choice wrong.
The sequence itself is the frame these questions hang on, and three positions come up repeatedly.
Sourcing strategy comes first and produces the procurement management plan, the procurement statement of work and the source selection criteria. This is where you decide what to buy, on what terms, and how you will judge the responses.
Tendering comes second: advertise, obtain seller responses, evaluate proposals, select a seller. Its output is the agreements with the selected sellers. The bank keys this directly in a record about a competitive tender between two bidders for a turnkey installation where the agreement has just been signed, and names both the SOW and the procurement management plan as things produced earlier as inputs to running the tender.
Administration comes third: monitoring performance against the agreement, handling claims, and eventually closed procurements. The bank places closed procurements at the other end of the life cycle, once work under the agreement is finished.
Fix that three-step shape and most SOW questions resolve without any further reasoning, because the question is nearly always just asking which step you are standing in.
What is the difference between a statement of work and a project scope statement? The bank tests this pairing head-on and keys the ownership answer: the statement of work is prepared by the customer or sponsor to describe what is needed, while the project scope statement is developed by the project management team during planning. Options that reverse the sequence, split them by functional versus technical view, or claim only one can be contractual are all wrong.
When is creating the procurement statement of work the correct next step? Once the make-or-buy decision has been taken by whoever is entitled to take it, and before the tender runs. In the bank's automation record the steering committee has already approved outsourcing, so re-running the make-or-buy analysis revisits a closed question, and what comes next is preparing the procurement statement of work and the source selection criteria.
Is a detailed statement of work always the right thing to include in a contract? No, and the bank has a record where it is the distractor. Under genuine time pressure there is rarely time to prepare a detailed statement of work or to vet subcontractors, and the keyed answer is incentives that motivate the contractor to deliver quickly without inflating the scope.
Why is the procurement statement of work wrong as an output of awarding a contract? Because it was produced earlier. The bank keys agreements with the selected sellers as the output of the tendering stage, and names the procurement statement of work and the procurement management plan as products of the earlier sourcing strategy work that fed the tender rather than results of it.
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, which is the only way sequencing questions like these actually teach you anything. Start the free 20-question sample — no card, no signup required to try it.
What is the difference between a statement of work and a project scope statement?
The bank tests this pairing head-on and keys the ownership answer: the statement of work is prepared by the customer or sponsor to describe what is needed, while the project scope statement is developed by the project management team during planning. Options that reverse the sequence, split them by functional versus technical view, or claim only one can be contractual are all wrong.
When is creating the procurement statement of work the correct next step?
Once the make-or-buy decision has been taken by whoever is entitled to take it, and before the tender runs. In the bank's automation record the steering committee has already approved outsourcing, so re-running the make-or-buy analysis revisits a closed question, and what comes next is preparing the procurement statement of work and the source selection criteria.
Is a detailed statement of work always the right thing to include in a contract?
No, and the bank has a record where it is the distractor. Under genuine time pressure there is rarely time to prepare a detailed statement of work or to vet subcontractors, and the keyed answer is incentives that motivate the contractor to deliver quickly without inflating the scope.
Why is the procurement statement of work wrong as an output of awarding a contract?
Because it was produced earlier. The bank keys agreements with the selected sellers as the output of the tendering stage, and names the procurement statement of work and the procurement management plan as products of the earlier sourcing strategy work that fed the tender rather than results of it.