What is the contract management process in procurement, step by step?
Short answer
In procurement, the contract management process follows one contract from the request through drafting, award and signature to performance, changes and renewal or closeout, with an owner at each step.
Key takeaways
- The contract management process in procurement has ten practical steps: request, plan, draft with the sourcing documents, evaluate and negotiate, approve and award, sign and record, hand over, manage performance, control changes, and renew or close out.
- Contract management starts before the tender, not after signature. In a competitive tender, the draft contract is part of the tender documents, so its terms, KPIs and renewal options are set before suppliers bid.
- The handover after signature is the weakest point. Prices, terms and the contract reference must reach the ordering system, and the obligations must reach the person who will check them.
- Public buyers have fixed dates in the process: in the EU a standstill of at least 10 days before signature and an award notice within 30 days; in the UK a contract details notice within 30 days and, above £5 million, a copy of the contract within 90 days.
- Renewal is decided from the notice date, not the end date. A contract with a 90-day notice period and a six-month re-tender needs a decision about nine months before it ends.
What is the contract management process in procurement?
The contract management process in procurement is the set of steps that takes one contract from the first request to its end: request, planning, drafting, award, signature, handover, performance, changes, and renewal or closeout. Each step has an owner, produces a record and hands it to the next step.
The contract management guide explains what the discipline covers and the stages of the contract lifecycle. This page follows one contract through a procurement team’s work, step by step: who acts, what goes in, what comes out and where the contract passes to sourcing or to ordering and payment. The US National Contract Management Association’s standard uses three phases, pre-award, award and post-award; the steps below sit inside those three phases.
A typical case. The facilities manager says the building security contract ends next year. From that sentence, procurement opens a contract request, plans the new contract, runs a tender with the draft contract in the pack, awards it, signs it, loads the prices into the ordering system, reviews the guards’ performance every quarter, approves a change when a new entrance opens, and decides in time whether to renew. That chain is the process.
What are the steps of the contract management procurement process?
- Request the contract. The business owner states the need, the budget, the start date and the expected term. Procurement first checks whether an existing contract or framework agreement already covers the need. A framework agreement is a contract that sets terms with one or more suppliers for later orders, called call-offs.
- Plan the contract. Before going to market, decide the contract type (fixed price, rates, or a framework), the term and any renewal options, the main KPIs (measures of performance with a target), payment terms and the exit rules. Choose the template.
- Draft the contract with the sourcing documents. In a tender, the draft contract goes into the request for proposal or tender pack, so suppliers price against known terms. In direct negotiations, the draft or the supplier’s paper is reviewed against the template and the clause rules.
- Evaluate and negotiate. Bids are scored on the published criteria. Any change to standard terms is logged with its reason and the person who accepted it. In EU open and restricted procedures, the terms are not negotiated after bids arrive.
- Approve and award. The award and the final contract are approved under the delegation of authority, by value and risk, with legal and finance where required. Public buyers notify bidders and respect the standstill period before signing.
- Sign and record. Both parties sign. The signed copy goes into one repository, and the contract record is completed: parties, owner, value, currency, start and end dates, renewal options, notice period, payment terms, KPIs.
- Hand over to operations. A kick-off meeting with the supplier and the business owner confirms contacts, reporting and the first deliverables. Prices and items are loaded into the ordering system or catalogue, and each purchase order carries the contract reference. The obligations of both sides go into an obligations register.
- Manage performance and obligations. The contract manager tracks deliverables, KPIs and service credits, holds regular reviews, and checks invoices against contract prices. The buyer’s own obligations, such as forecasts and approvals, are tracked too.
- Control changes. Every change in scope, price or term follows a written procedure, is approved at the right level and is recorded with the contract. Public contracts also check whether the change is allowed without a new tender.
- Renew, re-tender or close out. Ahead of the notice date, the owner decides on evidence whether to renew, renegotiate, re-tender or exit. At the end, closeout confirms deliverables accepted, final invoices paid, credits claimed, guarantees released, assets and data returned and the file archived.
The number of steps differs between organisations and software vendors; search results for this question list six, seven or eight. What matters is that no record is lost between two steps. Steps 2 to 5 overlap with sourcing; steps 7 to 10 run beside ordering and payment.
Who leads each step, and what does it hand to the next?
| Step | Who usually leads | Input | Output | Handed to |
|---|---|---|---|---|
| 1. Request | Business owner | A need, a budget, an end date of an old contract | Contract request with owner, value and term | Procurement |
| 2. Plan | Buyer or category manager | The request, spend data, market information | Contract strategy: type, term, options, KPIs, template | Sourcing and legal |
| 3. Draft | Buyer with legal | Template and clause library | Draft contract inside the tender pack | Bidders |
| 4. Evaluate and negotiate | Evaluation panel, buyer | Bids, criteria | Scores, deviation log, preferred supplier | Approvers |
| 5. Approve and award | Approver under the delegation of authority | Award recommendation, final draft | Approval, award notices | Supplier and unsuccessful bidders |
| 6. Sign and record | Authorised signatories, contract administrator | Approved final contract | Signed copy, contract record | Contract manager |
| 7. Hand over | Contract manager | Contract record | Kick-off notes, prices in the ordering system, obligations register | Requesters, buyers, accounts payable |
| 8. Manage performance | Contract manager with the business owner | KPI reports, invoices, deliveries | Review minutes, service credits, scorecards | Supplier, business owner |
| 9. Control changes | Contract manager, approver | Change request | Signed amendment, updated record | All users of the contract |
| 10. Renew or close out | Business owner and procurement | Performance evidence, notice date, market prices | Renewal, new tender or closeout checklist | Archive, or step 1 of the next contract |
The contract record created at step 6 is the thread through the process: every later step reads it or updates it.
Two roles are often confused. The buyer or category manager usually leads the steps up to signature; the contract manager leads after signature. In a small team, the same person does both, which is fine as long as the handover at step 7 still happens: someone has to load the prices and set up the obligations register.
Legal usually owns the templates, the clause rules and disputes; finance approves commitments and checks payment terms; accounts payable applies the contract prices when invoices arrive. In US federal contracts, only a contracting officer has authority to enter into, administer or terminate contracts, so every change at step 9 goes through that officer.
How does the process connect to sourcing and procure-to-pay?
Before signature, contract management and sourcing run together. The sourcing team runs the competition; the contract terms are part of what suppliers bid on. The steps of a tender are explained in the strategic sourcing process and the RFP process. The CIPS procurement and supply cycle shows the same order: specification, market analysis, tender and evaluation come before contract award and implementation, then delivery, performance and supplier relationship management.
After signature, the contract feeds procure-to-pay. Each purchase order should reference the contract it draws on, and the contract prices should be in the system that creates the order. Then the three-way match can compare the invoice with the order and the receipt at the contract price. When the link is missing, an invoice for 120 per hour on a contract signed at 110 is paid without anyone noticing.
The full route, from the first need to payment, is set out in the procurement process; the split between source-to-contract and procure-to-pay is compared in source-to-pay vs procure-to-pay.
Which dates and duties apply to public buyers?
Public procurement adds fixed dates and notices to several steps. The table lists the main ones in the EU, the UK and the US federal government. It is a summary: each rule has exceptions and conditions, so check the current text before relying on it.
| Step | EU (Directive 2014/24/EU and Remedies Directive) | UK (Procurement Act 2023) | US federal (FAR) |
|---|---|---|---|
| Plan | The estimated value includes all options and renewals set out in the documents | Above £5 million, at least three KPIs set before the contract is entered into, then published (unless KPIs cannot measure performance) | Only contracting officers can bind the government |
| Approve and award | Standstill of at least 10 calendar days after the award decision is sent electronically | Standstill of eight working days after the contract award notice | Award under the contracting officer’s authority |
| Sign and record | Contract award notice within 30 days of signature; copies of contracts kept for their duration from €1 million (supplies, services) or €10 million (works) | Contract details notice within 30 days; copy of the contract within 90 days above £5 million | Signed by the contracting officer |
| Manage performance | No review cycle set by the Directive; procedure documentation kept at least three years from award | KPI performance assessed at least once every 12 months | Performance evaluations at least yearly and at completion, above the simplified acquisition threshold |
| Control changes | Changes allowed without a new tender only within the limits of Article 72 | Changes allowed only within section 74 and Schedule 8; a change notice for larger changes | Changes made by the contracting officer |
| Close out | No closeout notice set by the Directive | Contract termination notice within 30 days of the end | Firm-fixed-price files closed within 6 months of physical completion, others within 20 or 36 months |
Public buyers have dates at award, signature, performance and end; a process that tracks only the expiry date misses most of them.
Renewals deserve care in public contracts. A renewal or extension is allowed only if the original procurement documents provided for it as an option; otherwise it is a change to the contract, limited by the rules on modifications, or a new tender is needed. That is one more reason to set the options at step 2, before going to market.
What does the process look like on a real timeline?
An illustrative example with invented dates: an IT support contract with a three-year term from 1 January 2027 to 31 December 2029, renewing automatically for one year unless either party gives 90 days’ notice. The organisation’s tenders for this kind of service take about six months.
| Date | Step | What happens |
|---|---|---|
| Mid-2026 | 1 to 5 | Request, plan, tender with the draft contract, evaluation, award and standstill |
| December 2026 | 6 and 7 | Signature, contract record, kick-off, rates loaded into the ordering system |
| Every quarter from April 2027 | 8 | Performance review against the KPIs: response time, resolution time, user satisfaction |
| Any time | 9 | A new office opens: change request, approved amendment adding the site |
| By early April 2029 | 10 | Decision on evidence: renew or re-tender; a re-tender starts now to finish in time |
| 2 October 2029 | 10 | Last day to give 90 days’ notice before 31 December 2029 |
| 31 December 2029 and after | 10 | End of term, or start of the renewal year; closeout of the old contract if it ends |
Counting back from the end date, the notice date falls on 2 October and a six-month re-tender must start around early April: the real decision comes about nine months before expiry.
The same logic works for any contract: write the notice date in the contract record at step 6, subtract the time the next tender takes, and set the alert there. If the alert is set on the end date, the contract renews by itself before anyone acts.
Where does the contract management process usually break?
Most failures happen at the handoffs between steps, not inside them. These are the common ones, with the control that prevents each.
- Signed but not recorded. The signed copy stays in an email inbox, so nobody else knows the contract exists. Control: no purchase order against a supplier without a contract reference, for categories that require one.
- Prices never reach ordering. The contract has new rates, but the catalogue still shows the old ones. Control: the handover at step 7 is a checklist item with a named person and a date.
- The owner leaves. The business owner changes job and the contract has no one to review performance or decide renewal. Control: the owner is a field in the contract record, checked at each quarterly review.
- Changes agreed by email. The supplier adds work after a phone call and invoices it later. Control: no change is paid before a signed amendment exists.
- Closeout skipped. The work ends, but retentions, guarantees and open orders stay open, and late invoices are still paid. Control: a closeout checklist, signed by the contract manager.
Software helps when the number of contracts makes these controls hard to run by hand: a repository, alerts on notice dates, approval workflows and a link to the ordering system. How to compare tools is covered in how to choose the best contract management software.
Questions
How many steps are there in the contract management process?
There is no fixed number. This guide uses ten practical steps; NCMA’s standard groups the work into three phases, pre-award, award and post-award, and vendors often list six to eight stages. The count matters less than a named owner and a complete record at each step.
Who owns the contract management process: procurement or legal?
Usually both, at different steps. Procurement leads the request, the planning, the tender and the commercial terms; legal owns templates, clause deviations and disputes; a contract manager, often in procurement, runs the contract after signature. The business owner stays accountable for the result.
What is the difference between the procurement process and the contract management process?
The procurement process covers the whole route from need to payment, for every purchase. The contract management process follows one contract inside that route, from its request to its closeout. It overlaps with sourcing before signature and runs beside ordering and payment after it.
What is contract closeout?
Closeout is the formal end of a contract. It confirms that deliverables were accepted, final invoices paid, credits claimed, guarantees released or called, assets and data returned and the file archived. In US federal contracts, firm-fixed-price files should be closed within six months of physical completion.
New guides on the contract management line
One short email when a guide on this line is added or revised. Nothing else.
Coming soon: sign-up opens with the first email.