Purpose of the lesson
Develop and apply a contract-management process that monitors supplier deliverables against agreed quality, quantity, place and time requirements and supports controlled payment approval.
Practical outcome
By the end of this lesson, you must be able to:
- Extract measurable requirements from a contract or SLA.
- Develop a contract-management process.
- Allocate monitoring responsibilities.
- Collect and validate performance evidence.
- Evaluate deliverables against agreed criteria.
- Calculate and report performance results.
- Identify exceptions and potential claims.
- Define and apply a payment-approval process.
- Maintain accurate contract records.
1. Gather the contract documents
Obtain:
- Signed contract
- Service-level agreement
- Specifications
- Pricing schedule
- Purchase orders
- Delivery or service schedule
- Contract implementation plan
- Approved amendments
- Supplier invoices
- Delivery notes
- Inspection and acceptance records
- Performance reports
- Customer complaints
- Claims and credit notes
- Previous meeting minutes
- Applicable organisational procedures
Confirm that you are using the latest approved versions.
2. Create a contract summary
Extract the essential information from the contract.
| Contract field | Information to record |
|---|---|
| Contract reference | Unique contract number |
| Supplier | Contracted supplier |
| Contract owner | Responsible organisational representative |
| Start and end dates | Contract period |
| Scope | Goods, services and deliverables |
| Prices | Agreed rates and payment terms |
| Service levels | Measurable performance commitments |
| Reporting | Required reports and frequency |
| Remedies | Credits, deductions or corrective actions |
| Change control | Procedure for authorised amendments |
| Escalation | Responsible parties and escalation levels |
| Renewal or exit | Notice periods and closure requirements |
Do not interpret the contract from memory. Record the actual approved requirements and relevant clause references.
3. Develop the contract-management process
Create a controlled workflow.
Confirm contract requirements
↓
Assign responsibilities
↓
Schedule deliverables and reviews
↓
Collect performance evidence
↓
Compare performance with criteria
↓
Record results and exceptions
↓
Approve, query or adjust payment
↓
Implement corrective action
↓
Report and retain records
Your process should define:
- What must be monitored
- How it will be measured
- Who will collect the information
- How often monitoring will occur
- What evidence is acceptable
- Who may approve performance and payment
- How exceptions will be escalated
- Where records will be stored
4. Prepare a deliverables register
List every recurring and once-off deliverable.
| Deliverable | Requirement | Due date | Evidence | Responsible party | Status |
|---|---|---|---|---|---|
| Monthly stock delivery | 1,000 units | 25th monthly | Delivery note | Supplier | Pending |
| Performance report | Monthly report | 3rd working day | Approved report | Supplier | Pending |
| Quality certificate | Per delivery | At receipt | Certificate | Supplier | Pending |
Include milestone dates, reporting obligations and customer or operational acceptance requirements.
5. Define performance criteria
Assess contract performance against four core dimensions.
Quality
Confirm whether the goods or services meet:
- Specifications
- Inspection requirements
- Defect tolerances
- Workmanship standards
- Regulatory requirements
- Packaging standards
- Customer acceptance criteria
A quality measure may be:
Quality acceptance rate = Accepted units ÷ Inspected units × 100
Quantity
Confirm whether the supplier delivered:
- The ordered quantity
- The correct unit of measure
- Complete orders
- No unauthorised excess quantities
- No unresolved short deliveries
Use:
Quantity variance = Actual quantity − Contracted or ordered quantity
Place
Verify that delivery or service occurred at:
- The correct facility
- The agreed delivery point
- The correct customer location
- The authorised service site
- The correct receiving bay or department
Time
Compare:
- Scheduled date and time
- Actual date and time
- Response time
- Resolution time
- Milestone completion
- Report-submission deadlines
Use:
On-time performance = Deliverables completed on time ÷ Total deliverables × 100
6. Prepare the performance scorecard
Convert contractual requirements into measurable indicators.
| Performance area | Measure | Target | Actual | Status |
|---|---|---|---|---|
| Quality | Acceptance rate | 98% | 96% | Below target |
| Quantity | Order-fill rate | 100% | 95% | Below target |
| Place | Correct-location delivery | 100% | 100% | Achieved |
| Time | On-time delivery | 95% | 92% | Below target |
Use the calculation method and target stated in the contract or SLA.
7. Collect and verify evidence
Use objective evidence such as:
- Signed delivery notes
- Proof of delivery
- Inspection reports
- System timestamps
- Inventory records
- Incident logs
- Service tickets
- Customer acceptance records
- Photographs
- Approved reports
- Invoice and purchase-order records
Verify that each record:
- Relates to the correct contract and period.
- Identifies the relevant deliverable.
- Is complete and legible.
- Comes from a reliable source.
- Has the required authorisation.
- Has not been counted more than once.
8. Evaluate the deliverables
For each deliverable:
- Identify the contractual requirement.
- Obtain the supporting evidence.
- Compare actual performance with the target.
- Calculate the variance.
- classify the result as compliant, partially compliant or non-compliant.
- Record the effect of any failure.
- Determine whether corrective action, escalation or a claim is required.
- Confirm whether payment may proceed.
Deliverable evaluation
| Deliverable | Required | Actual | Variance | Result | Action |
|---|---|---|---|---|---|
| Product delivery | 1,000 units | 950 units | −50 | Partially compliant | Query and claim short supply |
| Delivery date | 10 July | 12 July | Two days late | Non-compliant | Apply agreed process |
| Delivery location | Johannesburg DC | Johannesburg DC | None | Compliant | Accept |
9. Record contract exceptions
Create an exception register for:
- Late or missed delivery
- Short or excess quantity
- Defective goods
- Incorrect location
- Incomplete service
- Missing documentation
- Unauthorised price
- Missed reporting deadline
- Repeated customer complaint
- Failure to complete corrective action
| Exception | Contract reference | Effect | Evidence | Required action | Due date |
|---|---|---|---|---|---|
| 50 units short | CON-101 | Stock shortage | Delivery note | Supplier to deliver balance | 14 July |
Notify the supplier and relevant internal parties according to the escalation procedure.
10. Evaluate claims
A claim may arise from:
- Short delivery
- Defective products
- Late performance
- Damage
- Additional authorised cost
- Service-level failure
- Incorrect billing
- Unfulfilled warranty obligation
Before accepting or rejecting a claim:
- Confirm the contractual requirement.
- Review the evidence.
- Verify the dates, quantities and values.
- Establish responsibility.
- Apply the contract’s notice procedure.
- Obtain authorised input where required.
- Record the decision.
- Monitor the agreed resolution.
11. Define the payment-approval process
A supplier invoice must be supported by verified performance.
Receive invoice
↓
Validate supplier and contract
↓
Match contract, purchase order and receipt
↓
Confirm quantity, quality, place and time
↓
Resolve discrepancies
↓
Apply authorised credits or deductions
↓
Obtain approval
↓
Submit for payment
↓
Record and reconcile
Payment-verification controls
Confirm:
- Correct supplier
- Valid contract and purchase order
- Correct invoice number and period
- Agreed price and quantity
- Valid tax and banking information
- Evidence of delivery or service
- Required acceptance
- Applicable credits, deductions or penalties
- Correct approval authority
- No duplicate payment
This verification is commonly supported by matching:
- Purchase order
- Goods receipt or service confirmation
- Supplier invoice
12. Manage payment exceptions
Do not approve an invoice automatically when:
- Goods were not received.
- Quantity differs from the purchase order.
- Quality requirements were not met.
- The price differs from the contract.
- The invoice is duplicated.
- Supporting documents are missing.
- Required approval has not been obtained.
- The payment is disputed.
Record the exception and send it to the authorised contract, procurement, finance or supplier representative for resolution.
Do not withhold an undisputed payment without applying the contract and approved procedures.
13. Conduct performance reviews
Prepare a review agenda covering:
- Deliverables due
- Actual performance
- Quality, quantity, place and time results
- Open exceptions
- Claims and credits
- Corrective actions
- Risks
- Payments
- Improvement opportunities
- Decisions and responsibilities
Record minutes, actions, due dates and responsible parties.
14. Maintain the contract file
Retain:
- Signed contract and SLA
- Approved amendments
- Contract summary
- Deliverables register
- Performance scorecards
- Delivery and inspection evidence
- Exception and claims registers
- Supplier correspondence
- Meeting minutes
- Payment approvals
- Corrective-action records
- Management reports
Apply access, retention and version-control requirements.
Practical task
You are provided with examples of contracts, SLAs, supplier invoices, delivery information and claims.
Complete the following:
- Review the contract and SLA.
- Prepare a contract summary.
- Develop a contract-management process.
- Create a deliverables register.
- Define measures for quality, quantity, place and time.
- Evaluate actual deliverables against the criteria.
- Calculate and record performance results.
- Create an exception and claims register.
- Determine whether each invoice should be approved, queried or adjusted.
- Develop a controlled payment-approval process.
- Prepare a supplier-performance report.
- Submit the complete contract-monitoring record.
Required evidence
Include the following in your Portfolio of Evidence:
- Source contract and SLA
- Contract summary
- Contract-management process
- Deliverables register
- Defined performance measures
- Completed performance scorecard
- Supporting delivery and inspection evidence
- Exception register
- Claims assessment
- Payment-approval workflow
- Invoice-verification records
- Supplier-performance report
- Meeting or communication records
- Completed observation checklist
- Learner declaration of authenticity
Competence checklist
| Assessment criterion | Competent | Not yet competent | Comments |
|---|---|---|---|
| Extract measurable requirements from the contract and SLA | |||
| Develop a workable contract-management process | |||
| Create a complete deliverables register | |||
| Monitor performance against quality requirements | |||
| Monitor performance against quantity requirements | |||
| Monitor performance against place requirements | |||
| Monitor performance against time requirements | |||
| Evaluate deliverables using valid evidence | |||
| Record exceptions and potential claims | |||
| Define a controlled payment-approval process | |||
| Prepare an accurate supplier-performance report | |||
| Maintain complete and traceable records |
Lesson Summary
To monitor contract and SLA deliverables, extract measurable obligations and record them in a controlled deliverables register. Collect valid evidence and compare actual performance with the agreed quality, quantity, place and time requirements. Record exceptions and claims, communicate them through the approved escalation process and monitor corrective actions. Approve payment only after matching the contract or purchase order, performance evidence and supplier invoice. Maintain a complete contract file and use performance reviews to support compliance and improvement.