Evaluating public-sector consulting proposals is an advisory review process that aligns consultant bids with an institution's approved terms of reference.
Under the Public Finance Management Act 1 of 1999 (PFMA), accounting officers of departments and accounting authorities of public entities listed in Schedules 2 and 3 bear statutory responsibility for implementing effective, fair, and transparent procurement systems. When evaluating proposals for technical support, evaluation panels must assess bids against the baseline requirements of an approved commissioning brief while maintaining strict compliance with published procurement frameworks.
In provincial administration, oversight guidelines such as the Western Cape Provincial Treasury Public Entity Governance Guidelines provide illustrative governance tools, including RACI framework principles, to clarify institutional roles across project tasks. However, advisory proposal comparison tools serve as internal decision-support mechanisms to evaluate technical alignment; they do not replace formal tender scoring or statutory procurement rules.
Mapping institutional problems to proposed technical approaches
The RACI does not replace the Accounting Authorities' responsibilities under the PFMA
— Western Cape Provincial Treasury, Public Entity Governance Guidelines, p. 7
A primary objective when evaluating a consulting proposal is determining whether the bidder's proposed technical approach directly addresses the institution's specific operational problem. Rather than accepting generic advisory templates or standard consulting methodologies, evaluation teams must examine whether the bid maps proposed activities to the baseline defects identified in the approved commissioning brief.
Proposals should demonstrate a thorough understanding of the entity's statutory context, distinguishing between departmental arrangements under Section 38 of the PFMA and public entity governance structures under Section 51. Evaluating technical alignment requires checking whether the proposed methodology addresses core financial workstreams identified in the approved brief, such as ledger reconciliation or supplier-payment information under National Treasury Instruction No. 4 of 2022/2023. Bids offering off-the-shelf solutions without tailoring workflows risk delivering superficial reports.
Verifying named-role capability evidence and resource commitments
Evaluating technical capability requires looking beyond firm marketing profiles to verify the specific qualifications and experience of named project team members. Public entities must ensure that individuals assigned to key roles—such as project leads, technical specialists, and quality reviewers—possess relevant public sector finance expertise.
Evaluation panels should examine curriculum vitae, professional registrations, and verified project references for every named team member. It is essential to confirm that proposed senior experts will actively execute project workstream tasks rather than acting merely as nominal figures during bid presentation. Institutional readers should verify capability evidence across key operational areas using the following practical checks:
- Checking the named roles against the qualifications or registrations actually required by the published brief.
- Confirming team members possess demonstrated technical experience in PFMA financial management.
- Evaluating whether proposed personnel have practical experience in sub-ledger to ledger reconciliations.
- Assessing the evidenced availability and time commitments of the named experts.
- Checking whether proposed team members understand governance frameworks, such as RACI oversight tools.
Assessing realistic operational assumptions, dependencies and deliverables
A rigorous proposal review must evaluate whether the bidder's operational assumptions and project schedules are realistic and maintainable. Consulting proposals frequently rely on unstated assumptions regarding institutional data readiness, staff availability, and system access. Evaluation panels must scrutinise these assumptions to identify operational risks before contract award.
Furthermore, proposals must explicitly map operational dependencies across functional units. For example, executing a supply chain compliance review depends on receiving units providing goods receipt notes and procurement teams making tender files available. Bids should define concrete, verifiable deliverables—such as reconciled exception registers and capability training manuals—tied to formal acceptance sign-offs. Evaluating deliverable definitions ensures the institution receives actionable technical artefacts rather than vague advisory summaries.
Evaluating fee transparency, independence and conflict governance
Financial proposals must be evaluated for fee transparency, scope alignment, and value for money. Bidders should provide detailed fee breakdowns that link specific team member hours, daily rates, and resource allocations directly to defined workstream deliverables. Transparent pricing enables the institution to assess whether resource allocations match the technical complexity of each task.
In addition, evaluation panels must enforce strict independence and conflict-of-interest standards. Bidders must formally declare any past, existing, or potential relationships with board members, executive officials, or key suppliers that could impair objectivity. Under Section 50 of the PFMA, members of the accounting authority must maintain fiduciary duties and act in good faith. Ensuring bidder independence protects the institution from compromised technical reviews and safeguards public resources.
Structuring proposal evaluation matrices and implementation responsibilities
To support structured decision-making, institutions can deploy an advisory proposal evaluation matrix. It is critical to distinguish an advisory comparison matrix from formal tender scoring. Evaluation committees must apply the published, lawful evaluation framework approved in the original tender documents; they cannot invent new criteria, adjust scoring weights, or alter thresholds after tender issuance. Refer any question about changing requirements to authorised procurement and legal advisers before proceeding; do not introduce extra criteria through this comparison tool.
The table below presents an advisory proposal comparison matrix illustrating how evaluation dimensions can be mapped against verification checks, primary evidence artefacts, and retained decision authorities.
| Proposal evaluation dimension | Key bid verification check | Primary evidence artefact | Retained decision authority |
|---|---|---|---|
| Problem & Technical Approach | Assess alignment of methodology with approved commissioning brief | Detailed technical proposal and workstream plan | Chief Financial Officer review sign-off |
| Named Capability & Staffing | Verify qualifications and public sector experience of named team members | Certified CVs and professional registration records | Accounting Officer or Authority approval |
| Deliverables & Acceptance | Evaluate whether technical deliverables include verifiable sign-off criteria | Deliverable specification list and draft SLA | Executive Management project sponsor |
| Governance & Independence | Verify conflict disclosures and adherence to RACI governance interfaces | Signed declaration of interest and RACI map | Audit Committee governance oversight |
Evaluating proposal implementation responsibilities reinforces that external advisers provide analytical support while the advisory appointment does not itself transfer statutory accountability. As noted in the Western Cape guidelines, the RACI framework "does not replace the Accounting Authorities' responsibilities under the PFMA" (Public Entity Governance Guidelines, page 7).
Sources
Frequently Asked Questions
How does an advisory proposal comparison matrix differ from formal tender scoring?
An advisory comparison matrix is an internal decision-support tool used by project teams to analyse technical alignment against an approved brief . Formal tender scoring is the statutory procurement process governed by published evaluation criteria, weightings, and legal prescripts .
Can an evaluation committee introduce new evaluation criteria after a tender has been issued?
No, evaluation committees must strictly adhere to the evaluation criteria, point weightings, and threshold values published in the original tender invitation . Do not introduce criteria through an informal comparison matrix. Refer any proposed change to the authorised procurement and legal process; this article does not determine whether amendment, withdrawal or re-advertisement is appropriate .
What is the role of National Treasury Instruction No. 4 of 2022/2023 in proposal evaluations?
National Treasury Instruction No. 4 of 2022/2023 establishes mandatory PFMA compliance frameworks for managing irregular expenditure, reporting supplier-payment information, and reporting contract variations . Proposals evaluating financial controls must demonstrate technical competence in these specific statutory compliance areas .
How do provincial governance guidelines inform the assessment of public entity proposals?
Provincial guidelines, such as the Western Cape Public Entity Governance Guidelines, offer minimum governance norms and oversight tools, including RACI frameworks, for provincial public entities . They provide illustrative governance guidance rather than altering national procurement legislation .
How can proposal reviewers assess knowledge-transfer commitments?
Compare the proposed co-performing tasks, coaching, handover material and evidence of staff capability against the published brief. Check who will deliver the work and what acceptance evidence is promised, without adding retrospective award criteria.
Read the wider context in government advisory appointments.