Scoping a public-entity transformation delivery office is an advisory commissioning process defining decision boundaries, governance dependencies, and exit criteria.
In South African public administration, state organs align planning with statutory frameworks. Under Section 1.3 of the Department of Planning, Monitoring and Evaluation (DPME) Revised Framework, its planning prescripts apply strictly to Schedule 3A national public entities and Schedule 3C provincial public entities, alongside departments. In provincial contexts, frameworks such as the Western Cape Public Entity Governance Guidelines offer oversight tools for provincial entities, serving as provincial guidance rather than universal national legislation.
Defining decision rights and preserving internal sponsorship
document must be tailored to the needs of the Public Entity
— Western Cape Public Entity Governance Guidelines, introductory guidance, page7
Commissioning a transformation delivery office requires establishing a clear operational boundary between advisory coordination and executive management authority. While a delivery office provides analytical tracking, dependency mapping, and administrative support, decision routes follow applicable prescripts and approved delegations; a temporary coordination role does not itself create executive powers.
Under Section 56 of the PFMA, accounting authorities may delegate operational execution to internal managers, preserving executive oversight while enabling daily project execution and monitoring.
Internal sponsorship identifies an executive sponsor—such as the Chief Executive Officer or line head—retains operational accountability for transformation outcomes. An external delivery office must not usurp statutory governance or make executive policy decisions. RACI charts clarify stakeholder roles by defining who is Responsible, Accountable, Consulted, and Informed across project tasks.
As noted in provincial guidelines, applying a RACI framework supports role clarity while preserving the accounting authority’s responsibilities (Western Cape Public Entity Governance Guidelines, page 7).
Furthermore, executive sponsors maintain primary alignment with parent departments and oversight treasuries. Designated departmental officials monitor public entity performance and review quarterly progress submissions. The delivery office supports the internal sponsor by preparing structured monitoring files, enabling executive leads to present verified transformation data during routine departmental oversight reviews.
Mapping cross-functional dependencies and escalation pathways
Transformation initiatives within public entities rarely occur in isolation; they span multiple operational units, including finance, human resources, supply chain, and information technology. A primary function of the delivery office commissioning brief is establishing a comprehensive cross-functional dependency register to track technical prerequisites. Mapping operational interdependencies helps teams identify prerequisites and resolve dependencies before downstream implementation commences.
For example, deploying an automated performance monitoring system depends on ICT infrastructure readiness, financial general ledger alignment, and human resource user provisioning. Escalation protocols must define explicit triggers for raising operational delays or resource bottlenecks to executive decision-makers. When a cross-functional dependency threatens milestone delivery, the delivery office logs the exception and escalates it to the internal sponsor rather than attempting to enforce administrative directives independently.
As proposed commissioning practices, executive sponsors should enforce core operational checks across delivery office workstreams:
- Defining clear terms of reference that explicitly preserve internal management decision rights.
- Assigning a dedicated executive sponsor to oversee delivery office activities and approve workstream deliverables.
- Maintaining an active cross-functional dependency register to track prerequisites across operational branches.
- Establishing threshold-based escalation protocols for resolving operational friction and resource bottlenecks timeously.
- Mandating evidence-based acceptance standards for every workstream deliverable prior to milestone sign-off.
Establishing evidence-based acceptance criteria for workstreams
Commissioning a delivery office requires defining rigorous, evidence-based acceptance criteria for every workstream deliverable across the transformation roadmap. Rather than accepting progress reports based on self-reported estimates or unverified summaries, workstream outputs should be assessed against the agreed supporting evidence. Proposed acceptance criteria represent advisory methods designed to support internal control, rather than mandatory legal forms.
For instance, completing an internal control enhancement workstream requires signed sub-ledger reconciliations, updated operating procedures, and verified system test logs. Acceptance criteria must specify which internal managers sign off on deliverables, so executive sponsors can review quality and accuracy before milestones are approved. Documenting sign-offs in milestone bundles records what was accepted, by whom and on what evidence. Objective acceptance standards help distinguish demonstrated capability from reported activity.
Designing exit criteria and handover protocols
A transformation delivery office is inherently a temporary support mechanism that must be commissioned with a clear exit strategy. To prevent permanent institutional dependency on specialised support units, the commissioning brief must define explicit exit criteria and capability handover protocols. Exit criteria specify the operational thresholds at which routine change management is fully transitioned to permanent line managers.
Handover protocols require delivery office specialists to co-perform tracking alongside internal staff, deliver practical workflow manuals, and verify staff proficiency. The proposed handover can include manager-reviewed task demonstrations to confirm they execute routine monitoring workflows independently. Using capability evidence when reviewing exit readiness helps line functions identify remaining support needs. Proposed exit frameworks serve as editorial advisory tools to build long-term institutional capacity.
Advisory commissioning matrix for a transformation delivery office
To guide executive sponsors in scoping a transformation delivery office, the table below presents an advisory commissioning matrix. The roles shown are examples to adapt to actual delegations, not a universal approval schedule. This matrix outlines key commissioning focus areas, delivery office functions, required primary evidence artefacts, and internal decision authorities.
| Commissioning focus area | Key delivery office function | Primary evidence artefact | Internal decision authority |
|---|---|---|---|
| Mandate & Scope | Define transformation boundaries & RACI map | Approved terms of reference & RACI chart | Accounting Authority / Board |
| Executive Alignment | Establish internal sponsorship & delegation channels | Executive sponsor charter & delegation register | Chief Executive Officer |
| Dependency Management | Maintain cross-functional dependency register | Logged dependency register & escalation file | Internal Project Sponsor |
| Workstream Acceptance | Validate workstream outputs against primary evidence | Signed deliverable sign-off bundle & test logs | Chief Financial Officer / Line Head |
| Handover & Exit | Execute capability transfer & exit assessment | Verified staff competency log & handover report | Executive Sponsor / CEO |
What good looks like
A well-scoped transformation delivery office functions as an effective catalyst for organisational improvement while respecting institutional governance boundaries. By establishing clear decision rights, mapping cross-functional dependencies, enforcing evidence-based acceptance criteria, and executing structured handover protocols, executive sponsors have a clearer basis to assess capability, remaining dependencies and readiness to end temporary support.
Sources
Frequently Asked Questions
What is the primary function of a public-entity transformation delivery office?
A transformation delivery office is a temporary advisory and coordination unit commissioned to track change initiatives, map cross-functional dependencies, and report operational bottlenecks to executive sponsors . It provides analytical support but does not assume statutory management power or executive decision-making .
How does a delivery office maintain alignment with internal executive sponsors?
Alignment is maintained by designating a senior internal official—such as the Chief Executive Officer or Chief Financial Officer—as the executive sponsor with authority defined by the institution’s actual delegation and approval arrangements . The delivery office reports progress and exception logs to the sponsor, who exercises decision rights .
What role does a dependency register play in delivery office commissioning?
A dependency register identifies prerequisites across operational branches—such as ICT readiness or financial ledger alignment—required to execute transformation milestones . It enables the delivery office to track inter-departmental handovers and flag bottlenecks early .
How do evidence-based acceptance criteria protect public entity governance?
Evidence-based acceptance criteria require workstream deliverables to be substantiated by primary evidence artefacts—such as signed reconciliations or verified system test logs—before milestone sign-off . This helps reviewers challenge unverified status claims and maintains internal control .
Why must a transformation delivery office be commissioned with explicit exit criteria?
Explicit exit criteria help the institution manage the delivery office as a temporary support mechanism rather than a permanent administrative layer . Defined handover evidence helps line managers assess whether they can perform the agreed routine tasks and identify further support needs .
For the wider context, read public-entity transformation governance.