A probity review scope checklist is an advisory framework used by an accounting officer to verify evidence completeness across procurement decision gates.
In South African public sector governance, accounting officers and accounting authorities bear statutory responsibility for internal financial controls and procurement decision-making. When commissioning a probity review, leadership requires a clear operational scope to guide independent advisors, verify documentation, and evaluate decision integrity. This advisory guidance provides an annotated checklist framework to define review boundaries, test transaction records, and manage review outcomes.
Establishing review boundaries and commissioning scope
fair, equitable, transparent, competitive and cost-effective
— Constitution of South Africa, section217(1), procurement system requirements
A probity review scope checklist must establish unambiguous operational boundaries before review activities commence. Accounting officers must define the specific transaction population, contract type, and operational lifecycle stages subject to examination. Clear boundaries ensure that advisory reviews remain focused on decision integrity without straying into routine line-management tasks.
Public sector leaders must distinguish a probity review scope checklist from related governance tools, such as real-time checkpoint implementation frameworks or consultant appointment terms. While checkpoint workflows embed live operational gates and appointment terms set commercial engagement parameters, a scope checklist defines the evidence testing criteria and boundaries for evaluating transaction files.
Under Section 217(1) of the Constitution of the Republic of South Africa, 1996, organs of state and other institutions 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 duties directly bind public entities when purchasing goods or services, but they do not apply automatically to private commercial entities.
When commissioning review support, accounting officers should clarify that a proposed checklist represents a practical advisory tool rather than a binding statutory mandate. The checklist does not itself confer decision or assurance authority. Establish the actual review mandate and retain the institution's authorised decision arrangements. Retaining institutional decision authority ensures that accounting officers remain fully accountable for procurement outcomes.
Verifying operative framework versions and delegation authority
A fundamental step in executing a probity review is verifying the precise legal framework and internal delegation register active on the transaction date. Public finance regulations, treasury instructions, and departmental policies evolve over time. Assessing a historical transaction against current rules or unpromulgated legislation leads to flawed compliance conclusions.
The Supply Chain Management Guide issued by National Treasury in February 2004 provides valuable historical context regarding integrated supply chain models. However, historical guides do not serve as proof of operative monetary thresholds, mandatory bidding forms, or active preference point formulas. Reviewers must inspect the actual statutory instruments and institutional policies in force when decisions were taken.
Reviewers must also verify the formal delegation register active on the transaction date to confirm that approving officials and committee members possessed valid written authority. Assessing actual authority prevents misattributing decision-making power to unauthorised personnel. Confirming historical delegation schedules ensures that committee adjudications and contract approvals were executed within lawful boundaries.
Reviewing evidence across disclosures, evaluations, decisions and changes
Evaluating procurement integrity requires inspecting primary records across four critical operational phases: disclosures, evaluations, decisions, and contract changes. A thorough scope checklist directs reviewers to test the authenticity, completeness, and alignment of documentation across these key decision gates.
During the disclosure phase, reviewers examine signed conflict of interest declarations, gift registers, and confidentiality undertakings. Verifying that bid committee members disclosed financial interests prior to evaluating bids confirms procedural transparency. Reviewers check whether potential conflicts were identified, managed, or escalated before tender scoring commenced.
During the evaluation and decision phases, reviewers inspect bid registers, technical scorecards, evaluation reports, and adjudication minutes. The checklist verifies whether evaluation panels applied published specification criteria consistently without introducing unadvertised scoring factors. Review the award decision against the evaluation basis, procurement conditions, applicable authority and recorded reasons actually governing that transaction.
During the contract change phase, reviewers test variation requests, scope amendment motivations, and contract addenda. Reviewers verify whether post-award contract variations remained within permissible framework limits and received valid approval before implementation. Maintaining a complete record of contract modifications prevents unauthorised scope expansion and financial waste.
To ensure thorough evidence examination across all procurement phases, the review team applies a structured evidence checklist covering five key record domains:
- Disclosure and ethics records: Signed conflict declarations, confidentiality forms, and bidder interest disclosures.
- Specification and tender records: Approved technical requirements, market analysis reports, and published bid notices.
- Evaluation and scoring records: Received bid registers, individual evaluator scorecards, and committee evaluation reports.
- Adjudication and award records: Bid adjudication minutes, the evaluation basis actually applicable, and formal award letters.
- Contract change and variation records: Performance reports, variation motivations, legal reviews, and approved addenda.
Managing independence, limitations, escalation and management responses
Maintaining reviewer independence is essential to ensure that probity evaluations yield objective, credible findings. Assess actual and perceived self-review threats where the proposed reviewer previously helped prepare specifications or evaluate the procurement. Disclose relevant work and establish safeguards or assign a different reviewer where objectivity cannot be protected. While prior advisory work does not automatically bar a firm from appointment, potential conflicts must be disclosed and managed transparently.
When reviewers encounter scope limitations or documentation gaps, they must log these issues transparently rather than making absolute legal determinations. A missing record indicates a potential breach of administrative documentation duties, but it does not automatically prove that an underlying award was invalid or corrupt. Conversely, a retrospective explanation generated during a review cannot substitute for omitted contemporaneous approval.
When significant compliance risks or procedural exceptions are identified, reviewers must follow formal escalation protocols. Findings are reported directly to the accounting officer alongside management responses from responsible line managers. This structured interaction allows line managers to provide contextual evidence while ensuring that executive leadership retains full control over corrective actions.
| Review question | Record reference | Reviewer assessment | Decision owner and response |
|---|---|---|---|
| Were conflicts disclosed and managed under the actual requirements? | Actual disclosure records and contemporaneous meeting evidence | A formal declaration postdates the decision; a claim of earlier disclosure remains uncorroborated | Seek genuine contemporaneous disclosure and management evidence. Record uncertainty rather than treating a late form as an earlier declaration. |
| Did evaluation use the published criteria with a supported rationale? | Actual specification, evaluation records and scorecards | Some scoring explanations are absent or inconsistent | Seek the original supporting records. Retain any later explanation with its actual date and limits; do not rewrite original scores. |
| Did the decision-maker possess the relevant authority? | Actual award decision, appointment record and operative delegation | An acting appointment is evidenced, but the scope of financial authority is unclear | Distinguish appointment from delegation. Check the operative authority and obtain appropriate review rather than infer validity from a job title. |
| Were changes handled under the applicable contract and approval arrangements? | Actual variation request, contract terms, decision and work records | Work began before the recorded written approval | Establish what was required when, what was authorised and any applicable exception basis. An emergency log alone does not prove the required approval existed. |
Sources
- Constitution of South Africa, chapter13, section217 — Constitution
- National Treasury SCM Guide, February2004 (historical practical guidance) — National Treasury
Frequently Asked Questions
How does a probity review scope checklist differ from adviser appointment terms?
A probity review scope checklist is an operational governance framework that defines the specific evidence testing criteria, decision gates, and record domains to be evaluated during a review. In contrast, adviser appointment terms represent a commercial contract that establishes the fee structure, deliverables, timelines, and legal conditions governing the consultant's engagement.
Does Section 217 of the Constitution apply to private commercial companies?
Section 217 of the Constitution directly binds organs of state in the national, provincial, and local spheres of government, as well as other institutions identified in national legislation, when contracting for goods or services. Private commercial companies participating in public tenders must comply with bidding conditions, but constitutional procurement principles apply to the public entity conducting the purchasing process.
Why is National Treasury's February 2004 SCM Guide considered historical context?
The February 2004 SCM Guide issued by National Treasury outlines foundational principles for integrated supply chain management models across government. However, it reflects historical practice and does not serve as proof of current operative monetary thresholds, practice notes, or active preference point formulas, which must be verified against current treasury prescripts.
Can a retrospective explanation replace an omitted contemporaneous approval?
No, a retrospective explanation or late written memorandum generated during an audit review provides helpful operational context, but it cannot substitute for an omitted contemporaneous approval. Retain actual dates and assess any lawful remedial route under the applicable framework, keeping the original decision history and evidence gap intact.
Does a missing procurement file automatically prove that a contract award was invalid?
No, a missing file or document gap indicates a potential failure of administrative record-keeping duties, but it does not automatically establish that an underlying contract award was invalid or corrupt. Determining legal invalidity requires a formal assessment by competent legal or statutory authorities based on the total available evidence beyond file availability alone.
For wider context, read the probity overview.