Negotiate Agreements and Manage Suppliers

Introduction

This lesson covers the second half of task 5 of the Process domain in the July 2026 PMP Examination Content Outline (Process carries 41% of the exam): participate in agreement negotiations, execute the procurement management plan, evaluate vendor performance, manage suppliers and contracts, and verify that the objectives of the agreement are met. The previous lesson covered planning and contract types. Here the contract is chosen and the real work starts: getting a fair agreement signed and then making sure the seller delivers.

Exam questions in this area are rarely about law. They ask what a project manager should do first when a vendor misses a milestone, how to handle a change the vendor requests, how to prepare for a negotiation, or when a procurement can be closed. After this lesson you will be able to prepare and conduct a negotiation, run a bidder selection with a weighted score, manage a seller through performance reviews, handle claims and changes, and close the agreement correctly.

Learning objectives

• Prepare a negotiation strategy using BATNA, interests, and tradeable items.
• Evaluate proposals with a weighted scoring model and a total cost view.
• Explain the role of the project manager, procurement department, and legal in managing a contract.
• Monitor seller performance with service levels, milestones, and earned value data.
• Handle contract changes, disputes, and claims in the right order.
• Verify that procurement objectives are met and close an agreement properly.
• Apply ethical rules and agile practices to supplier relationships.

1. From plan to signed agreement

Between the procurement plan and the first day of delivery there are four steps: issue the procurement documents, answer bidders' questions, evaluate offers, and negotiate and sign the agreement.

Bidder conference. When several sellers are bidding, a bidder conference (or an anonymous question and answer log) gives everyone the same information at the same time. Any answer given to one bidder is shared with all of them. This is both a fairness rule and a practical one: it avoids proposals built on different assumptions.

Proposal evaluation. The criteria and weights are set before proposals arrive. A weighted scoring model gives each criterion a weight and each proposal a score from 1 to 5, then multiplies and adds.

Example: weighted scoring

A retailer is choosing a payment platform provider. Criteria and weights: technical fit 35%, security and compliance 25%, price (total cost over 3 years) 25%, references and financial stability 15%.

Calculation for Vendor A: 0.35 x 4 = 1.40; 0.25 x 5 = 1.25; 0.25 x 3 = 0.75; 0.15 x 4 = 0.60; total 4.00. Vendor B: 1.75 + 0.75 + 1.00 + 0.60 = 4.10. Vendor C: 1.05 + 1.00 + 1.25 + 0.45 = 3.75. Vendor B wins on score, but the team should note its weaker security score and negotiate security commitments into the contract (audit rights, incident notification time) instead of ignoring the gap.

Other selection tools are independent estimates (the buyer estimates the cost to check the bids), a screening system (minimum requirements that disqualify a vendor), and a seller rating system based on past performance. Always compare total cost of ownership (purchase, integration, support, exit) rather than the purchase price alone.

2. Negotiating agreements

Negotiation is a planned conversation to reach a binding agreement that both parties can live with. The project manager usually participates and brings the knowledge of the work, while the procurement department or an authorized contract officer leads and signs. A project manager should not agree to terms outside their authority.

Preparation

1. Define interests, not just positions. A position is "we want a lower price". The interest may be a predictable budget, a faster start, or less risk of vendor lock-in. Interests open more solutions.
2. Know your BATNA (best alternative to a negotiated agreement): what you will do if no deal is reached, such as the second-ranked bidder or building in-house. A strong BATNA gives you the confidence to walk away. Estimate the seller's BATNA too.
3. Set limits: the target outcome, the acceptable range, and the walk-away point.
4. List tradeable items that cost one side little and are worth a lot to the other: payment terms, contract length, volume commitments, reference rights, milestone dates, scope options.
5. Agree on the team and roles: who leads, who takes notes, who has authority, who brings legal and technical expertise.
6. Plan the agenda: scope and deliverables, price and payment, schedule, acceptance, warranty, IP, data protection, change and termination.

Typical negotiation tactics and how to respond

Collaborative (win-win) negotiation, based on interests and objective criteria, builds a relationship for a contract that may last years. Competing (win-lose) approaches may be acceptable for a one-off commodity purchase but are risky with a strategic supplier you depend on.

Worked example: negotiating a managed-service contract

Statement. A logistics company must renew a warehouse management software contract. The vendor proposes EUR 20,000 per month for 12 months. The current price is EUR 17,000. The buyer has a second quote at EUR 18,500 per month from another vendor, but switching would cost about EUR 60,000 in migration and 4 months of disruption. The buyer would like price stability and a service level of 99.9% availability. How should the project manager prepare?

Reasoning, step by step.

1. BATNA. Switching: EUR 18,500 x 12 = 222,000 plus 60,000 migration = 282,000 in year one. The vendor's offer is 240,000. Staying is cheaper in year one, so the buyer's BATNA is weaker than it looks. Do not bluff about leaving.
2. Seller's BATNA. The vendor loses a customer paying 204,000 per year (17,000 x 12) if the buyer leaves, and it knows migration is costly for the buyer too.
3. Interests. The buyer wants predictability and availability; the vendor wants revenue growth and long-term commitment. A longer term is something the vendor values.
4. Package. Offer a 36-month term in exchange for EUR 18,000 per month fixed for 3 years (economic price adjustment capped at 3% per year), 99.9% availability with service credits (for example 5% of the monthly fee for each 0.1% below target), and a right to terminate for repeated service failures.
5. Check value. 36 months at 18,000 = 648,000 versus renewing yearly at 20,000 with likely increases. The buyer saves at least 72,000 over three years against the first offer repeated three times.

Solution. Prepare interests, a BATNA analysis based on total cost, and a package trade: a longer term for a lower fixed price and enforceable service levels.

Why other approaches are weaker. Threatening to leave without a credible alternative damages credibility. Accepting the first price keeps the buyer exposed. Negotiating only the price ignores service levels, which cause the real business impact.

3. Executing the procurement management plan

After signature, the project manager manages the seller against the agreement. The agreement, not verbal promises, governs. Key activities:

• Kick-off with the seller: roles, communication channels, reporting cadence, escalation path, tools, and the definition of acceptance.
• Integrate the seller's work into the schedule, risk register, quality plan, and communication plan. A seller's late delivery is a project risk, tracked like any other.
• Authorize the seller's work at the right time according to the agreement (notice to proceed, purchase orders, payment milestones).
• Manage payments: invoices are checked against accepted deliverables or agreed rates before payment. Paying for work not delivered weakens the buyer's position.
• Keep records: correspondence, change requests, meeting minutes, inspection results. In a dispute, documented facts matter.
• Use the right channel: formal communication about the contract (notices, change requests, claims, acceptance) is written. Technical day-to-day conversation may be informal, but anything that changes scope, price, or schedule must go through change control.

4. Evaluating vendor performance

Performance is measured against what the agreement says. Common tools:

Example: seller performance with earned value

The seller builds a module under a fixed price of EUR 300,000 with a planned value at the status date of EUR 150,000. The accepted work is worth EUR 120,000 (earned value) and the seller reports EUR 140,000 spent. SPI = 120,000 / 150,000 = 0.80. The seller is behind schedule: it has earned only 80 cents of planned work for each planned euro. Cost performance for a fixed-price contract is the seller's concern (the buyer pays EUR 300,000), but the delay is the buyer's concern because it threatens the project schedule. The project manager asks for a recovery plan, checks whether the delay hits the critical path, and records the risk.

Rule of thumb. For fixed price the buyer follows schedule and quality closely. For cost-reimbursable and T&M the buyer must also follow cost closely, since the buyer pays the actual cost.

What to do when the seller underperforms

1. Check the facts against the agreement (what is required, what was delivered, what changed).
2. Talk to the seller's manager and identify the root cause (staffing, unclear requirements, buyer delays).
3. Agree on a corrective action plan with dates.
4. Escalate through the defined path (project sponsor, procurement, legal) if the plan fails.
5. Apply contract remedies (service credits, withholding payment, cure period, termination) only through the contract terms and with procurement and legal advice.

Do not start by terminating the contract or by threatening legal action. Termination is the last resort, because it costs time and may leave the project without a supplier.

5. Managing changes, claims, and disputes

Changes to a contract follow a formal process, just like changes to a project. A change is evaluated for scope, cost, schedule, risk, and quality, approved by the right authority, and then written into an amendment. A verbal instruction to the seller ("just add that report") is a classic exam trap: it creates an undocumented change and often a later claim.

Claims are requests or demands by a seller (or buyer) for compensation, time, or a right, usually because of an alleged change or breach. The usual order of resolution is:

1. Negotiation between the parties.
2. Mediation by a neutral person who helps but does not decide.
3. Arbitration where a neutral decides, often binding.
4. Litigation in court, the most expensive and slowest.

Alternative dispute resolution is preferred because it protects the relationship and cost. Contract documents often define the order and the jurisdiction.

Buyer-caused problems. Late approvals, late access to systems, or unclear requirements by the buyer can justify a seller's claim. A good project manager manages the buyer's side of the obligations too.

Table: contract changes and who decides

6. Verifying objectives and closing the agreement

Procurement closure confirms that all work and deliverables were accepted and that all obligations were met. Steps:

1. Procurement audit: review the procurement process and the contract performance to capture lessons learned (what worked in the selection, what clauses should be standard).
2. Verify acceptance: all deliverables are formally accepted against the acceptance criteria. The buyer issues formal written notice of completion.
3. Settle open items: final payments, retained amounts (retention), warranty periods, open claims, return of buyer property and data, and removal of seller access to systems.
4. Transfer knowledge and rights: documentation, source code, licences, support contacts, IP transfer as agreed.
5. Update records: archive the contract file and update the seller performance record, which feeds future source selection.
6. Verify business objectives: did the procurement deliver the benefits that justified it (cost, speed, capability, risk transfer)? Compare to the business case, not only to the deliverable list.

An agreement can end by completion, by mutual agreement, or by termination for convenience or cause. Termination triggers the exit plan: transition of services, handover, and payment for work accepted.

7. Agile and hybrid supplier management

With agile suppliers, the project manager works as a partner more than as an inspector:

• Treat the seller's team as part of the team: invite to planning, reviews, and retrospectives.
• Use the iteration review as the acceptance point, with the product owner accepting stories against the definition of done.
• Monitor value with burn-up charts, velocity, and defect trends instead of only milestone dates.
• Keep the right to reprioritize the backlog at each iteration and to stop after an iteration under the contract's exit rights.
• Track the contract cap (not-to-exceed) against the burn rate so the budget is not exhausted before the highest-value items are delivered.
• Agree on transparency rules: shared backlog, shared board, access to demos.

For hybrid projects, a vendor may run in sprints while the contract and the milestone payments follow a predictive structure. Align them: for example, payment tied to a release, each release made of several sprints accepted by the product owner.

8. Ethics, compliance, and sustainability in supplier management

• Do not accept gifts, entertainment, or favours that could influence a decision. Follow the organization's gift policy and declare conflicts of interest.
• Treat all bidders equally; confidential information from one bid must not leak to another.
• Respect confidentiality and data protection clauses; verify that sellers handle personal data as required (for example, data processing agreements under GDPR).
• Check subcontractors: the seller remains responsible, but the buyer should know who handles sensitive data or critical work.
• Monitor sustainability and labour commitments in the contract (emissions reporting, energy use, ethical sourcing) and audit them when required.
• Report suspected fraud or corruption through the organization's channel; do not investigate alone.

9. Common pitfalls and exam tips

Pitfalls

• Negotiating only on price and ignoring service levels, liability, and exit terms.
• Negotiating without knowing the BATNA or the walk-away point.
• Agreeing verbally to scope changes.
• Treating the seller as an adversary and hiding information needed for delivery.
• Paying invoices before checking acceptance.
• Waiting until the end to review performance.
• Closing the project without closing contracts, access rights, and warranties.
• Escalating to termination or legal action before trying to resolve the issue.

Exam tips

• If a seller asks for a change, the answer is a change request through change control, not immediate work.
• When a vendor is late, first analyze the cause and the impact on the critical path, then discuss a corrective plan, before escalating or terminating.
• Preparation before negotiation: interests, BATNA, limits, tradeable items.
• The project manager needs authorization before committing the organization to contract terms; legal and procurement sign.
• Dispute order: negotiation, mediation, arbitration, litigation.
• Procurement closure needs formal acceptance and a lessons-learned audit.
• In agile contracts, the right answer typically keeps collaboration and transparent value tracking, with exit rights, not blame.

10. Mini case study

Situation. A hospital is installing a patient scheduling system delivered by a vendor under a fixed price of EUR 480,000 with five milestones. At milestone 3 the vendor is three weeks late, saying that hospital IT took too long to provide test data. The hospital's clinical director asks the vendor to add a new reminder feature verbally "while you are here". The vendor now sends an invoice for milestone 3 plus EUR 25,000 for the reminder feature, and warns that milestone 4 may slip further. The contract includes a change clause and a 5% payment retention until final acceptance.

Questions. What should the project manager do?

Commented solution.

1. Separate the issues. Delay at milestone 3, the extra feature, and the invoice are three different matters.
2. Delay: compare the log of data requests with delivery dates. If hospital IT was late, part of the delay may be a legitimate claim for a time extension; if not, the vendor is responsible. Analyze the impact on the critical path and ask the vendor for a recovery plan for milestone 4.
3. Extra feature: the verbal request is not valid under the change clause. Remind stakeholders that changes go through change control. Prepare a change request, get a written quote, assess the impact on schedule and cost, and have the change control board decide. If approved, amend the contract.
4. Invoice: pay milestone 3 only if the deliverable meets the acceptance criteria (less any retention). Hold the EUR 25,000 until a change is approved; involve procurement and legal on the disputed amount.
5. Relationship: meet the vendor's manager to agree on data delivery dates from the hospital side and a joint plan, then record decisions in writing.
6. Learning: add a rule that no instruction to the vendor is given outside the project manager and the change process, and track the hospital's own obligations as dependencies.

Why not terminate? The vendor may not be solely at fault and the replacement cost is high. Why not just pay everything to keep peace? It rewards an undocumented change and sets a precedent. Why not refuse all discussion? A time extension claim may be valid.

Key terms

• BATNA: best alternative to a negotiated agreement; the basis of negotiating power.
• Weighted scoring model: objective bid evaluation using pre-set criteria and weights.
• Service level agreement (SLA): measurable service commitments, often with credits.
• Retention: part of the payment held until final acceptance.
• Change clause: contract rule defining how changes are requested and priced.
• Claim: request for compensation or rights, linked to a change or a breach.
• Mediation and arbitration: alternative dispute resolution methods.
• Procurement audit: structured review of the procurement process for lessons learned.
• Termination for cause or convenience: ending a contract with or without breach.
• Total cost of ownership: all costs over the life of the purchase.

Summary checklist

• I can prepare a negotiation with interests, BATNA, limits, and tradeable items.
• I can score proposals with a weighted model and compare total cost.
• I know the project manager's role versus procurement and legal.
• I can monitor a seller with milestones, SLAs, and earned value.
• I handle contract changes through formal change control.
• I know the dispute resolution order and avoid early termination.
• I can close a procurement with acceptance, audit, and open-item settlement.
• I can adapt supplier management to agile and hybrid work and keep ethics rules.

Official sources

• PMI, PMP Examination Content Outline (July 2026): https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
• PMI, PMP certification: https://www.pmi.org/certifications/project-management-pmp (opens in a new tab)
• PMI, PMP exam change: https://www.pmi.org/blog/pmp-exam-change (opens in a new tab)