Technical assistance supplies knowledge, skills and analysis to an institution that holds a public mandate. It does not transfer that mandate. Scope sets the problem, the deliverables, the counterpart, the acceptance criteria and the decisions reserved to the client. Scope that is vague at the start is where delivery risk first enters a programme. This page sets out how scope is defined, how scope risk develops and spreads, and what evidence the holders of the mandate use to decide.
GCRI · Established · service level R0
Technical assistance scope is the definition of the problem, deliverables, counterpart, acceptance criteria and decisions reserved to the client for an assignment. Vague scope is where delivery risk first enters a programme, and advice can drift into authority when advisers take on line functions the institution should hold.
The jurisdictions that hold authority over this question: countries, their first-level divisions and capitals, shown for the Congo Basin as an example geography for this subject.
The working screen behind this subject: its structure, terms and states. Names are placeholders and values illustrative.
Technical assistance scope · Assignment pool · Quarter 4
| Team lead | Disaster risk management | None declared | Confirmed |
| Hydrologist | Flood modelling | Declared, managed | Confirmed |
| Data engineer | Pipelines | None declared | Invited |
| Reviewer | Independent | None declared | Confirmed |
What support can and cannot authorize. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Advisers placed to fill a capacity gap are gradually asked to draft, then approve, then sign. The institution's own staff stop exercising the function, and the line between advice and decision disappears from the record.
Objectives without acceptance criteria, deliverables without a named counterpart, and timelines without decision points mean no one can say whether the work is done. Variations, extensions and payment disputes follow.
When assistance is designed around what a funder or firm can supply rather than what the institution asked for, ownership is weak and outputs sit unused. Parallel units built to deliver the assistance can drain the system it was meant to strengthen.
A draft regulation enacted without legal review, or a design signed by an adviser without authority, moves risk from the assignment into the institution. Audit observations, safeguard breaches and suspended financing can follow, each with its own holder and remedy.
Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.
| Term | Definition |
|---|---|
| Acceptance criteria | The stated conditions a deliverable must meet before the client accepts it. |
| Line function | A role in an institution's chain of command or operations, which an adviser should not fill. |
| Reserved decision | A decision the terms of reference keep with the client institution, whatever the adviser recommends. |
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Technical cooperation in bilateral official development assistance | percent of gross disbursements | annual | OECD Creditor Reporting System type-of-aid codes | OFFICIAL |
| Assignments mobilised with signed terms of reference | percent of assignments | quarterly | Engagement and contract records | REPORTED |
| Deliverables accepted against stated acceptance criteria | percent of deliverables | per assignment | Client acceptance records | REPORTED |
| Terms-of-reference amendments | count per assignment | per assignment | Contract variation records | OFFICIAL |
| Assignments with a named counterpart in the client institution | percent of assignments | quarterly | Engagement records | DECLARED |
| Advisory positions performing line functions | count of positions | annual | Functional reviews, audit findings | REPORTED |
| Development co-operation using country public financial management and procurement systems | percent of disbursements | per monitoring round | Global Partnership monitoring | OFFICIAL |
The topic as a computational graph: named sources feed the methods, an evidence review gates the outputs, and the decisions stay with the authorities that hold them.
Fig. 02Nodes carry their type, two metric rows and a state; connectors show what feeds what; dashed frames name the owners; the timeline is the cadence. Design of the pipeline, not a record of a run.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Source | What it gives | Licence class |
|---|---|---|
| OECD Creditor Reporting System | Activity-level aid records, including type-of-aid categories for donor experts and other technical assistance | Free and open, attribution under OECD terms |
| IATI Datastore and d-portal | Published activity data: objectives, participating organisations, budgets, documents and results | Open, licence declared per publisher |
| Global Partnership for Effective Development Co-operation monitoring | Country-led data on ownership, use of country systems and results frameworks | Open, attribution |
| World Bank Independent Evaluation Group evaluations | Evaluations of advisory services, analytics and technical assistance operations | Public documents under the World Bank access to information policy |
| UN Joint Inspection Unit reports | System-wide reviews of consultants and non-staff personnel in UN organisations | Public documents |
| National supreme audit institution reports | Audits of externally funded programmes, advisory contracts and decision authority | Public records, terms per audit office |
Nexus Agency prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Requesting ministry or public agency | Whether the need is for advice, implementation support or a function the institution must staff itself | Mandate map; scope statement with the decisions reserved to the institution |
| Funding agency task team or programme manager | Whether the terms of reference are specific enough to finance and to accept deliverables against | Terms-of-reference checklist, acceptance criteria and counterpart commitment |
| Supreme audit institution or internal audit function | Whether decisions were taken by persons holding the legal authority to take them | Records of who advised, who decided and who signed |
| Public service commission or establishment office | Whether externally funded advisers are substituting for posts the institution should fill | Functional review findings; advisory positions against the establishment |
The best-documented failure of technical assistance is substitution: advisers do the work instead of building the host's capacity, and the host is no better able to act when they leave. A second failure is authority creep, where an adviser's recommendation is treated as a decision, or where assistance becomes a channel for steering procurement or financing towards particular suppliers.
Clear scope protects all parties. The host keeps control of its decisions, the expert knows the limits of their responsibility, and affected communities can see who answers for what. For that reason assistance offered through the Nexus programme carries a stated limit for each type of work, such as 'a blueprint is not an installed environment' or 'testing is not certification or procurement status'.
The host institution decides whether to request assistance and how to use its results, under its own rules. The programme team decides whether a request fits the programme. Related topics: Institutional support, Team formation and Project closeout. The full list of assistance types is on technical assistance types and boundaries. Governance of institutional mandates is the subject of Governance Nexus at The Global Risks Forum (GRF).
This page describes practice as designed. It is reviewed by a named subject editor, with references and independent specialist voices recorded, before release.
The current service level is R0: information and enquiries. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.