Flagship

Coordinating delivery across public institutions

The practical arrangements for moving decisions, information and resources between institutions.

Aerial view of interconnected urban highways and bridges crossing a river in Jakarta.

Many public programmes require several institutions to contribute to the same outcome. A ministry may set the objective, an agency may manage procurement, local offices may organise delivery and a separate team may compile the results. Each institution can meet its own administrative requirements while the overall programme still encounters problems.

The difficulty often lies in the connections between these responsibilities. Programme preparation needs to address how decisions, resources and information will move between the institutions, and how an unresolved issue will reach someone who can make a decision.

Define the work between institutions

A programme plan should identify more than the final outputs. It should show the activities on which those outputs depend and the parties responsible for them. Procurement, approvals, site access, distribution and reporting may each have a separate process and timetable.

Those processes need to be considered together. Where one activity depends on another institution’s action, the parties should agree what must be supplied, when it is required and how completion will be confirmed. These agreements form part of the delivery arrangements.

Connecting records across institutions

  1. Finance teamExpenditure records show the use of funds.
  2. Delivery partnerProgress reports describe the work carried out.
  3. Programme officeThe milestone schedule records the agreed delivery sequence.
Common references and reporting periods help the programme team compare these records and investigate differences.

Agree which information the programme will use

Institutions may hold different records of the same activity. A finance team records expenditure, a contractor reports progress and a programme office maintains its milestone schedule. The records serve different purposes, but programme leadership needs to understand how they relate.

Common definitions, reference numbers and reporting periods can help bring the information together. Differences should be investigated rather than removed for presentation. Where a result cannot yet be confirmed, the report should state what evidence is missing.

Make coordination part of routine management

Coordination requires decisions and follow-up, not only meetings. A programme review should identify what has changed since the previous review, which activities are waiting on another party and what decisions are needed next.

The record of the meeting should assign actions and provide a basis for the next review. If an issue sits outside the authority of the programme office, the arrangements need to establish where it will be escalated. Otherwise, repeated discussion can take the place of resolution.

Plan for continuity

A programme may establish new records, reporting routines or digital systems. The institution needs to know who will maintain them when the initial assignment ends. Staff preparation, operating costs and access to documentation should be considered during implementation.

These arrangements help preserve what the institution has learned and reduce the work required to establish the next programme. They also clarify which functions have become part of routine administration and which still depend on external support.

Related reading

Rows of young green crops growing in cultivated soil at ground level.

Field note · 2 min read

Farmer registries in public agricultural programmes

How purpose, updating responsibilities and routine use affect the value of a farmer register.

Read insight
Organised administrative documents and an open binder on an office desk.

Perspective · 2 min read

Why public programmes stall during implementation

Identifying delayed handovers, assigning issue ownership and checking reported progress.

Read insight

Search Veldstone