A scenic view of the BARA area in Diepkloof, South Africa during sunset.
Back to insights

Implementing a contract-management control improvement programme

Implementing a contract-management control improvement programme. Practical guidance on institutional evidence, responsibilities and review boundaries.

By Justin Kettle · Founder & Managing Director

Published · Updated

Illustrative photograph: Agnieszka Taggart · Photo source

A contract-management control improvement programme is an institutional framework governing post-award obligations, variations, and payment controls.

In South African public administration, institutional performance depends on managing contracts effectively after award. While pre-award acquisition selects suppliers, operational value is realised or lost during contract administration. Establishing a contract-management control improvement programme enables accounting officers, CFOs, and contract managers to track contractual obligations, review variation controls and investigate payment exceptions.

Baselining contract populations and mapping contractual obligations

fair, equitable, transparent, competitive and cost-effective

— Constitution of South Africa, section217(1), procurement system requirements

The initial phase of a control improvement programme requires establishing a comprehensive inventory of all active contracts, service level agreements, and commercial commitments. Public institutions must aggregate decentralized contract files from user departments, regional depots, and finance registries into a unified contract master register. Maintaining a centralised master register supports visibility over active contractual commitments and delivery schedules.

Once the contract population is inventoried, implementation teams must map the primary obligations, delivery milestones, and pricing structures established in each signed agreement. The historical guide includes General Conditions of Contract, but the programme must establish which conditions and amendment provisions actually form part of each agreement. Mapping these baseline obligations ensures that contract managers evaluate supplier performance against verified terms rather than informal expectations.

Under Section 217(1) of the Constitution of the Republic of South Africa, 1996, organs of state in the national, provincial or local sphere, or any other institution identified in national legislation, must contract for goods or services in accordance with a system that is fair, equitable, transparent, competitive, and cost-effective. These constitutional procurement duties directly bind public bodies when acquiring goods or services, but they do not extend automatically to private commercial suppliers.

Public sector leaders must note that historical guidance, such as National Treasury's SCM Guide of February 2004, outlines the philosophy of integrated supply chain functions including logistics management and contract administration. However, historical guidelines provide conceptual context rather than proof of operative monetary thresholds, mandatory forms, or active preference point rules. Institutions must verify the operative institutional framework, active policy versions, and formal written delegation schedules active on transaction dates.

Triaging documentation gaps and establishing evidence baselines

Following contract population baselining, implementation teams must conduct a thorough triage of existing contract management dossiers. Triaging identifies missing documents, unrecorded performance logs, and unapproved variation requests across operational units. Systematic triage allows the institution to categorise files by documentation completeness and target remedial efforts toward high-risk agreements.

Documentation gaps must be categorised transparently into administrative record gaps, operational performance breaches, and contract variation exceptions. Implementation leads must recognise that a missing record indicates a potential failure of administrative record-keeping duties under public finance rules, but a missing record does not automatically prove that an underlying contract award or payment was invalid.

Furthermore, public sector managers must understand that a retrospective note or late written memorandum generated during a control review cannot substitute for an omitted contemporaneous approval. The legal effect of a missing or late approval requires assessment against the actual framework, contract and available evidence; this programme does not determine validity. Missing records must be logged in an institutional gap register rather than retroactively recreated or backdated.

Control improvement recommendations proposed in advisory guidance represent practical management tools rather than new statutory rules. Accounting officers and authorities retain statutory responsibility for issuing internal directives, establishing delegation schedules, and maintaining effective internal control systems under public finance legislation.

Redesigning operational handovers and post-award controls

To prevent future governance breakdowns, institutions must redesign operational handovers across the post-award contract lifecycle. Redesigning handovers supports coordination between contract managers, receiving logistics officers, and accounts payable units. Agreed handover records help clarify accountability and expose unresolved information gaps at each transition.

Operational handovers must enforce clear evidence requirements before advancing to subsequent workflow stages. For example, the receiving or technical owner should identify and retain the delivery or service acceptance record required by the contract and applicable procedure. Document-based checks support payment verification but do not guarantee that performance was satisfactory.

Key post-award control redesign priorities across the contract lifecycle include:

  • Obligation tracking: Maintaining active schedules of deliverables, milestone dates, and performance guarantees.
  • Variation control: Enforcing formal written motivations and delegated approval gates before executing scope changes.
  • Deliverable verification: Testing delivery or service evidence against agreed acceptance criteria before the relevant payment approval.
  • Payment matching: Performing three-way reconciliations across purchase orders, receipt vouchers, and tax invoices.

Piloting control improvements and transferring institutional ownership

Implementing redesigned controls requires a structured pilot phase across selected operational divisions or high-risk contract categories. Piloting enables the institution to test control gate logic, refine documentation templates, and train contract managers in a controlled operational environment. Testing controls on a limited scale minimises operational disruption while validating process effectiveness.

During the pilot, implementation leads evaluate contract performance logs, variation approval files, and invoice reconciliation ledgers to confirm control effectiveness. Testing scenarios include managing qualitative scope variations, resolving delivery quantity discrepancies, and handling contract default notices. Record which scenarios passed, failed or remained untested, and agree corrective actions before rollout.

Following successful piloting, the programme transitions to full institutional rollout, transferring operational ownership from implementation project leads to permanent line managers. Handover should reconcile the agreed contract population, test user permissions against valid authority and document training, unresolved issues and retained ownership. Sustainable governance relies on line managers maintaining active oversight within established statutory parameters.

This proposed workstream model uses illustrative owners and acceptance records; tailor it to the institution.

WorkstreamDependencyManagement OwnerAcceptance Evidence
Contract baselining & triageAccess to departmental contract archives & financial ledgersChief Financial OfficerValidated contract master register & documentation gap triage log
Handover & variation redesignApproved institutional delegation register & policy versionsCompliance / Legal DirectorTarget post-award workflow map & standardised variation templates approved
Control pilotingCompleted workflow redesign & user training modulesSCM Contract ManagerSigned pilot evaluation report & verified sample variation approval files
Ownership transfer & rolloutSuccessful pilot testing & executive management sign-offSCM Operations HeadCompleted staff training registers & agreed operational handover record

Sources

Frequently Asked Questions

How should an institution manage an unapproved qualitative scope variation identified during contract triaging?

When triaging identifies an unapproved qualitative scope variation, the contract manager must log the discrepancy in the gap register and report the matter to the accounting officer. Management should assess the actual amendment terms, valid authority and need for legal review. A retrospective note cannot grant prior approval, but formal governance procedures must be followed to address the exception lawfully.

How does a contract-management control programme differ from a whole source-to-pay transformation?

A contract-management control improvement programme focuses specifically on post-award governance, including obligation tracking, contract variations, deliverable acceptance, and invoice matching. A whole source-to-pay transformation encompasses the entire procurement continuum, including pre-award sourcing, tender evaluation, supplier databases, and broad IT system replacements.

How should verbal instructions for additional work be handled?

Record what was instructed, by whom, when and on what asserted authority. Check the actual contract and applicable framework before deciding how to respond. Do not treat a later note as proof of an earlier authorised amendment, or assume that a verbal instruction has no possible legal consequences. Obtain appropriate legal review where the position is disputed.

Does a missing deliverable acceptance certificate automatically invalidate an invoice payment?

No, a missing deliverable acceptance certificate may indicate a record-keeping failure if that record was required, but it does not automatically prove that an underlying payment or contract award was legally invalid. Determining legal invalidity requires a formal legal or statutory assessment based on total available evidence, including physical delivery proofs or secondary operational logs.

What evidence is required before accounts payable can process a contract invoice for disbursement?

Accounts payable should test the invoice against the applicable contract, purchasing record and delivery or service acceptance evidence. Specify how services, partial deliveries and other exceptions are handled. A matching record supports the payment decision; it is not a universal prescribed form or a guarantee against irregular expenditure.

For wider context, read the contract management overview.

Discuss your organisation’s priorities

Contact Kettle Consulting