Contract management is the discipline of administering an agreement between a buyer and a seller across its full life, from drafting through performance monitoring to formal closure.
For project managers the important point is that contract management is an operational responsibility, not a legal one. Lawyers draft and negotiate the document. The project manager lives inside it: tracking deliverables against the statement of work, verifying invoices, controlling changes, documenting performance and closing the agreement out. A contract that is negotiated well and administered badly produces the same outcome as a bad contract.
This guide covers the contract lifecycle, the main contract types and how they allocate risk, the clauses that most affect delivery, and the mechanics of change control and closure.
A note before starting: this is a project management guide, not legal advice. Contract law varies by jurisdiction, and specific wording should always be reviewed by a qualified legal adviser.
Where contract management sits
Contract management is a component of the wider procurement management process, not a synonym for it. The distinction is worth holding.
| Activity | Description | Primary owner |
|---|---|---|
| Plan procurement | Decide what to buy and how | Project manager |
| Conduct procurement | Solicit, evaluate, select, award | Procurement function |
| Control procurement | Administer the contract during performance | Project manager |
| Close procurement | Verify completion, settle, close formally | Project manager |
The project manager’s heaviest involvement is in the third and fourth rows. This is also where most value is lost, because control and closure are administrative work that competes for attention with delivery.
The contract lifecycle
Stage 1: Pre-award definition
The contract can only be as clear as the requirement behind it. Two documents do most of the work here.
The statement of work defines what is being purchased. It should be traceable back to the project’s scope statement, because any gap between the two becomes a gap the buyer pays to fill later. The most common defect in a statement of work is describing activity rather than outcome: “provide three developers for six months” transfers no delivery obligation at all, whereas “deliver an integrated payments module meeting the attached acceptance criteria” does.
Acceptance criteria define what finished means. These must be objective and testable. Terms such as reasonable, industry standard or to the buyer’s satisfaction are unenforceable in practice because they cannot be measured, and they place the dispute at the end of the contract rather than resolving it at the start.
Solicitation follows, using the appropriate instrument. The three standard bid documents serve different purposes: an RFI gathers information where the requirement is not yet defined, an RFQ obtains pricing where the requirement is fully specified, and an RFP requests a proposed solution where the buyer knows the problem but not the answer.
Evaluation should use weighted source selection criteria agreed and documented before proposals are opened. Criteria set after bids arrive are, in practice, criteria fitted to a preferred bidder.
Stage 2: Award and contract type selection
The contract type determines how cost risk is distributed between buyer and seller. This is the single most consequential decision in the process.
| Type | Buyer pays | Cost risk sits with | Appropriate when |
|---|---|---|---|
| Firm fixed price (FFP) | A set price regardless of seller cost | Seller | Scope is fully defined and stable |
| Fixed price incentive fee (FPIF) | Set price plus a fee adjusted by cost performance | Shared | Scope is defined but cost is uncertain |
| Fixed price with economic price adjustment | Fixed price with defined indexation | Shared | Long duration, volatile input prices |
| Cost plus fixed fee (CPFF) | Allowable costs plus a fixed fee | Buyer | Scope cannot be defined in advance |
| Cost plus incentive fee (CPIF) | Allowable costs plus a variable fee | Buyer, partly shared | Research or development work |
| Cost plus award fee (CPAF) | Allowable costs plus a discretionary fee | Buyer | Performance quality matters more than cost |
| Time and materials (T&M) | Agreed rates for hours and materials used | Buyer | Small or urgent work, staff augmentation |
Two practical observations follow from this table.
Fixed price does not eliminate buyer risk. It converts cost risk into scope risk. A seller committed to a fixed price with an ambiguous statement of work will manage its margin through the change process, and the buyer ends up paying anyway, at a worse rate and with more friction.
Time and materials contracts should always carry a not-to-exceed ceiling and a defined review point. Without one, the arrangement has no cost control mechanism at all.
Selecting a type is a risk allocation decision, so it belongs in your risk management analysis rather than being treated as a purchasing formality.
Worked example: FPIF and the point of total assumption
Fixed price incentive fee contracts share cost variance between the parties according to a defined ratio, up to a ceiling price. The mechanics are commonly examined and frequently misunderstood.
Contract terms:
- Target cost: $100,000
- Target fee: $10,000
- Target price: $110,000
- Ceiling price: $125,000
- Share ratio: 70/30 (buyer 70%, seller 30%)
Case 1: the seller underruns. Actual cost comes in at $95,000, a $5,000 saving. The seller keeps 30% of the saving, so the fee rises to $11,500 and the final price is $106,500.
Case 2: the seller overruns. Actual cost reaches $110,000, a $10,000 overrun. The seller absorbs 30%, so the fee falls to $7,000 and the final price is $117,000, still below the ceiling.
The point of total assumption is the cost level at which the seller begins absorbing every additional dollar, because the ceiling price has been reached.
PTA = ((Ceiling price − Target price) ÷ Buyer share ratio) + Target cost
PTA = (($125,000 − $110,000) ÷ 0.70) + $100,000 = $121,428.57
Beyond that cost, the seller’s share of further overrun is 100%. This matters operationally, not just arithmetically: a seller approaching the PTA has a strong financial incentive to reduce quality, submit change requests aggressively, or seek to exit. A buyer’s project manager who tracks seller cost performance can anticipate that behaviour rather than being surprised by it.
Reliable cost estimates on the buyer side are what make these structures usable, since target costs set without an independent view are simply the seller’s number with extra steps.
Stage 3: Contract administration
This is the longest stage and the one most often neglected. Five activities define it.
Performance monitoring against defined measures. Deliverable dates, service levels and quality thresholds should be tracked on the same cadence as the rest of the project. Contractual performance data belongs in the standard work performance report rather than in a separate document that only procurement reads.
Invoice verification against evidence. Every invoice should be checked against delivered work, agreed rates and the payment schedule before approval. Approving payment for work not yet accepted weakens the buyer’s position permanently, because payment is generally treated as evidence of satisfaction.
Acceptance and rejection in writing. Deliverables must be formally accepted or formally rejected against the stated criteria, within the timeframe the contract specifies. Many contracts contain a deemed acceptance clause, under which a deliverable is treated as accepted if the buyer does not respond within a set period. Silence is therefore not a neutral position. Acceptance testing links directly to the project’s quality management process, and the criteria applied should be the same ones.
Ongoing relationship management. Contract administration is the formal layer; vendor management is the working relationship underneath it. Both are necessary. A project manager who relies only on the contract will find that the seller performs to the letter of it, which is rarely what the project needs.
Record keeping. Correspondence, decisions, meeting minutes, defect reports and performance data should be retained systematically throughout. In any later dispute, the contemporaneous record decides the outcome. Documents created after a disagreement begins carry very little weight.
Stage 4: Change control
Contract changes are not project changes. A change to the agreement requires a formal contract amendment or variation, executed by whoever holds signing authority, and that is almost never the project manager.
The correct sequence is:
- Change is identified and its impact on cost, schedule and scope assessed
- A change request is raised and evaluated through the project’s change management process
- If approved, a contract amendment is drafted and signed by authorised signatories on both sides
- Baselines are updated only after the amendment is executed
The failure mode here is constructive change: instructions given informally by project staff that a seller reasonably interprets as authorisation to do additional work. The seller performs, invoices, and is frequently entitled to payment. Preventing this requires a single named point of contractual authority on the buyer side, and clear instruction to the project team that nobody else may direct the seller.
Clauses project managers need to understand
The project manager does not draft these, but should be able to locate and interpret them, because each has direct operational consequences.
| Clause | Operational effect |
|---|---|
| Statement of work | Defines the delivery obligation; the reference point for every dispute |
| Acceptance criteria and procedure | Determines what counts as complete, and the response window |
| Payment terms and milestones | Sets when money moves and against what evidence |
| Liquidated damages | Pre-agreed sum payable for defined delays, avoiding proof of loss |
| Warranty period | Obligation to remedy defects after acceptance, and for how long |
| Intellectual property | Determines who owns deliverables, code and derived materials |
| Limitation of liability | Caps the seller’s total exposure, often at contract value |
| Indemnity | Allocates responsibility for third-party claims |
| Termination for convenience | Allows the buyer to exit, usually with compensation for work done |
| Termination for cause | Allows exit on defined breach, with specified notice and remedy periods |
| Dispute resolution | Sets the escalation route, forum and governing law |
Two of these deserve particular attention during delivery.
Limitation of liability is often capped at the contract value, which means a supplier delivering a $200,000 component into a $10 million programme may carry $200,000 of exposure for a failure that costs far more. That imbalance is a project risk and should be recorded as one.
Termination for cause almost always requires a documented notice and cure process. A buyer who has not maintained a written record of breach and remedy requests will find the clause unusable at the point it is needed.
Claims and disputes
Most contractual disputes originate in one of three places: ambiguous scope, undocumented changes, or unrecorded delay.
The practical guidance is procedural rather than legal.
Raise issues in writing early and in the form the contract specifies. Many agreements impose notice periods, and a claim submitted outside the window may be barred regardless of merit.
Keep commercial escalation separate from the working relationship. Disputes handled at the delivery level tend to poison day-to-day cooperation, which the project still depends on. Standard conflict resolution practice applies: escalate the commercial disagreement into the appropriate forum and let the delivery teams continue working.
Follow the contractual escalation sequence in order. Most contracts specify negotiation, then mediation or expert determination, then arbitration or litigation. Skipping a step usually results in being sent back to complete it.
Contract closure
Closure is a formal act, not the natural end of activity. An unclosed contract leaves open obligations, unreleased retentions and unresolved liabilities that can surface long after the project team disperses.
A closure checklist should confirm:
- All deliverables received and formally accepted against criteria
- All invoices received, verified, and settled
- Retentions and performance bonds released or scheduled for release
- Warranty period start date recorded and owner assigned
- Intellectual property, source code, credentials and documentation transferred
- Access rights and system permissions revoked
- Outstanding claims resolved or formally documented as open
- Supplier performance evaluated and recorded for future selection
- Formal notice of closure issued and acknowledged in writing
Where the contract was significant or problematic, a compliance-focused project audit at closure is worth the effort. Its main output is not the pass or fail judgement but the evidence of what worked, which feeds directly into how the next agreement is structured.
Common failure modes
| Failure | Cause | Countermeasure |
|---|---|---|
| Scope disputes mid-delivery | Statement of work written as activity, not outcome | Define deliverables with testable acceptance criteria |
| Unbudgeted change costs | Informal instructions treated as authorisation | Single named contractual authority on the buyer side |
| Weak position in dispute | No contemporaneous record | Maintain written correspondence and decision logs throughout |
| Deemed acceptance of defective work | Missed response window | Track acceptance deadlines as schedule activities |
| Contract left open after delivery | Closure treated as administrative | Formal closure checklist with an assigned owner |
| Wrong contract type | Type selected by habit or policy default | Select based on scope certainty and risk allocation |
Common questions
What is the difference between contract management and procurement management? Procurement management covers the whole acquisition process, including deciding what to buy and selecting a supplier. Contract management is the administration of the resulting agreement. Contract management is a subset, concentrated in the performance and closure stages.
Can a project manager sign a contract or amendment? Usually not. Signing authority is defined by organisational delegation, and project managers rarely hold it for external agreements. This is a control, not a slight: separating delivery authority from commitment authority prevents informal changes from becoming binding obligations.
Which contract type is best? There is no general answer, because the choice is a risk allocation decision. Fixed price suits well-defined stable scope. Cost reimbursable suits work that cannot be specified in advance. Selecting fixed price for undefined scope is the most common and most expensive error, because it converts cost risk into change requests.
What is a constructive change? Work performed by the seller in response to informal buyer conduct or instruction, without a formal amendment. It frequently creates a valid entitlement to payment. It is prevented by controlling who may direct the supplier, not by contract wording alone.
How long should contract records be retained? Longer than the project. Retention periods are set by the contract, organisational policy and applicable law, and typically extend years past closure to cover warranty and limitation periods. Confirm the requirement rather than assuming it.
Summary
Contract management for project managers is administration, not drafting. The contract type allocates cost risk, and selecting it for undefined scope pushes that risk into the change process rather than removing it. During delivery, the controlling activities are formal acceptance against testable criteria, invoice verification against evidence, a single point of contractual authority, and continuous written records.
Changes require executed amendments before baselines move. Closure is a formal act with a checklist, not the point at which activity stops.
Internal links used (10)
| # | Anchor text | URL |
|---|---|---|
| 1 | procurement management | https://pmstudyguide.com/procurement-management/ |
| 2 | scope statement | https://pmstudyguide.com/scope-statement/ |
| 3 | bid documents | https://pmstudyguide.com/bid-documents/ |
| 4 | source selection criteria | https://pmstudyguide.com/source-selection-criteria/ |
| 5 | risk management | https://pmstudyguide.com/risk-management-strategies/ |
| 6 | cost estimates | https://pmstudyguide.com/cost-estimates/ |
| 7 | work performance report | https://pmstudyguide.com/work-performance-report/ |
| 8 | quality management | https://pmstudyguide.com/quality-management/ |
| 9 | vendor management | https://pmstudyguide.com/vendor-management/ |
| 10 | change request | https://pmstudyguide.com/change-request/ |
Bonus links also included in the body: change management process, conflict resolution and project auditing.
