LEARN. PRACTICE. GROW.Understand the concept
Procurement starts with a need and evaluation criteria. Price is one dimension: compare technical capability, lifetime costs, dependencies, support, and risks. A fixed-price contract provides a baseline for defined scope, but additional requests still require analysis. Time-and-materials arrangements require attention to consumed effort, agreed limits, and delivered value. The project should involve procurement and people authorized to make commitments.
Apply and decide
Before delivery, agree objective acceptance evidence. During execution, track milestones, issues, and changes with the supplier. If a deliverable is missing, establish the deviation from the agreement and pursue a resolution plan through applicable governance. Do not promise payments, penalties, or additional work without authority. Distinguish technical completion from contractual acceptance and business acceptance.
Guided application
In a fictional fixed-price contract, a new retention requirement can change storage, licenses, and testing. Fixed price for agreed scope does not mean unlimited included changes. In another time-and-materials contract, compare consumed effort, deliverables, limits, and remaining forecast before authorizing continuation. The manager should involve procurement and those authorized to make commitments; exercises do not interpret real legal clauses. When a supplier and internal team disagree, use evidence about dependencies and acceptance criteria. A service that starts may still lack contracted training or reconciliation, and those deviations need an explicit decision.
Reconcile contractual deliverables
At closure, compare what was received with every agreed condition. Code, documentation, and transfer can be separate deliverables even when one represents most effort. If items are missing, identify ownership, treatment, and acceptance decisions under the agreement. Do not delete conditions from records to present clean closure. A change may be negotiated by competent authority while preserving history and consequences, without pretending original work was delivered.
Comparing offers and separating acceptances
Compare offers using the same volume, period, and included services. For 800 jobs monthly over three months, an offer of EUR 1,000 monthly with 500 jobs included and EUR 2 per additional job costs EUR 4,800. Another offer of EUR 1,450 monthly up to 850 jobs, plus a one-time EUR 200 integration fee, costs EUR 4,550. The difference is EUR 250 before considering nonfinancial requirements. Contractual acceptance of delivered servers may coexist with an outstanding operational recovery test. Check what each agreement requires. A supplier metric excluding half the relevant volume needs supplementary evidence. If the agreement allows partial payment, route the evidenced portion through competent approval and address the discrepancy separately without inventing a universal rule.
A supplier delivers servers, but documented recovery was in scope and has not been demonstrated. Record the gap, involve procurement and the acceptance owner, and agree the missing demonstration before treating the milestone as accepted.
Common pitfalls
Confusing fixed price with unlimited scope; promising commitments without authority.
Related topics: Quality, data, and benefits · Autonomy, collaboration, and adaptive teams
Acceptance depends on agreed criteria and evidence; an invoice does not demonstrate the outcome.
Reference: PMP Examination Content Outline · PMP ECO July 2026; DR PMP 2026.5