A public programme can fall behind even when its objectives remain clear and its funding has been approved. Implementation involves a series of handovers between people and institutions. Delays at these points may be small individually but can accumulate across the programme.
The first task is to establish where progress is being lost. A general explanation such as “limited capacity” may describe the environment, but it is rarely specific enough to guide a response. The programme team needs to know which activity is delayed, what it depends on and who has authority to resolve the issue.
Follow the handovers
Consider a disbursement that has been authorised but has not been confirmed by the receiving office. The central team may record the activity as complete, while the local team is still waiting to begin work. Unless the reporting process distinguishes authorisation, transfer and receipt, the difference can remain unnoticed.
Similar problems arise when one agency is waiting on an approval from another, or when a contractor’s report is not matched with evidence from the site. Mapping these handovers helps the programme team identify the information that needs to move with each activity.
A disbursement has more than one status
- AuthorisedThe decision to release funds has been approved.
- TransferredThe payment has been made and recorded.
- ReceivedThe receiving office has confirmed receipt.
Give issues an owner
An issue register can record a problem without changing its course. It becomes a management tool when each item identifies the decision or action required, the responsible person and when it will be reviewed again.
The person responsible for following up an issue may be different from the person authorised to decide it. The escalation process should recognise that distinction. Regular programme reviews then provide a way to address items that cannot be resolved within the delivery team.
Check the status being reported
Programme reports should explain what a status means and which evidence supports it. “Complete” may refer to a contractor’s declaration, a document submitted for review or work that has been inspected and accepted. These are different stages and should be recorded accordingly.
The appropriate check depends on the activity and the mandate. It may involve comparing administrative records, requesting supporting documentation or visiting the delivery location. The programme manager needs to know which checks have been carried out and what remains unconfirmed.
Use reporting while action is still possible
A reporting schedule should reflect the decisions the programme team needs to make. Information collected only at closeout may explain a shortfall, but it cannot help recover an activity whose delivery period has already passed.
Useful implementation reporting connects an emerging problem with someone who can act on it. Clear responsibilities, consistent status definitions and timely checks help make that connection. They also provide a more specific basis for deciding where additional support is needed.



