Mandates and institutional architecture · Lesson 2

Route a request through mandate and governance

5 min read

Lesson objectives

  • Build a routing matrix that connects function, mandate instrument, authorized actor and escalation information.
Reading tools

The first institution found through a web search is not necessarily the decision maker. In a specialist's file, ‘Who works on this subject?’ is a discovery question; ‘Who may perform the requested action?’ is a mandate question. Roles can be split within one organization: a governing body adopts broad policy, a secretariat prepares papers, and a country office implements an activity under an approved programme. A referral card therefore needs a precise verb: request data, coordinate a partnership, fund a project or take a position. Each verb needs a different basis. An activity page does not authorize an office to sign an agreement or bind a state.

Build a four-column matrix. The first column states the issue and function: write the action and intended output, not a broad topic. The second records the mandate instrument and whether it is general or limited by country or time. The third asks who decides: distinguish technical adviser, implementer, financial signatory and Member State. The fourth names verification and escalation: what information is missing and who is qualified to review it? If the decision column is empty, a technical advice request may quietly become an unauthorized funding promise.

A UN system chart helps generate possible contacts, but it is not a single hierarchy of authority. Funds, programmes and specialized agencies are not synonyms. Specialized agencies have institutional autonomy through relationship agreements, while funds and programmes have their own mandates and governing bodies. Documents also vary within a category. Use the system page for initial classification, then consult the relevant mandate page, programme instrument or governing-body decision before sending a formal request. Record the version and date checked: a shortened organization name or an obsolete programme document can mislead a reader.

Read the relationship between a governing body and a secretariat carefully. Adoption of a strategy does not approve every related project; a general budget does not promise money to the person who contacted you. Add a ‘decision level’ layer to the matrix. Does the source announce an aim, assign a responsibility, authorize a procedure or allocate a resource? Read operative language and conditions, not just a heading that fits the team's hope. Where the inference has financial or legal consequences, require competent review before it leaves the team.

In partnership coordination, label each arrow ‘consults,’ ‘shares information,’ ‘approves,’ ‘implements’ or ‘monitors.’ ‘Partner’ alone is too elastic: it can describe a donor, technical office or state representative. Consider the cost of a wrong referral: rewriting a proposal, delaying service, or creating an inappropriate political expectation. Reduce it with a focused referral question: ‘Does reviewing these data fall within your mandate, and what is the relevant instrument and authorized contact?’ The question neither demands nor claims approval.

The specialist delivers a reviewable routing recommendation, not a final jurisdiction ruling. Record at least one alternative if the first route fails, and state what would change the choice: a current programme instrument, confirmation that the office does not provide the function, or a shift from advice to an official decision. If two sources conflict, name the conflict rather than blending them. Assign an owner and date to verification and mark the referral state. The team can then move from ‘this seems like the right organization’ to a conditional decision that another officer can correct.

Lesson summary

Build a routing matrix that connects function, mandate instrument, authorized actor and escalation information.