Management Response to an Evaluation: What It Is and What to Include

What Is a Management Response?

A management response is the formal, written reply of the commissioning organization's management to an evaluation. For each recommendation, it states whether management accepts, partially accepts or rejects it, gives the reasons, and, for accepted recommendations, lists the actions that will be taken, who is responsible and by when. It is prepared after the evaluation report is final, by the managers who own the program, not by the evaluators, and it is then tracked until the actions are done.

The same phrase is used in auditing, where management replies in writing to an auditor's findings and says what it will correct. The mechanics are similar (a response per finding, an owner, a deadline), but this page covers the evaluation use.

Why It Matters

An evaluation report does not change anything on its own. Recommendations sit in an annex unless someone with authority says what will be done with them. The management response is that statement. It turns "the evaluators recommend" into "we decided, this unit will do it, by this date," and it creates a record that can be checked later. It also lets managers disagree with a recommendation in writing, with reasons, instead of quietly ignoring it. The UNEG Norms and Standards (2016) ask the organization's management to provide a formal response to each evaluation, including whether and why it agrees or disagrees with each recommendation, and to detail actions that are concrete, objectively verifiable, time-bound and clear on who is responsible. The UNEG guidelines report that most UN agencies, and other bilateral and multilateral organizations, produce one in matrix form.

What Does a Management Response Include?

Agencies use slightly different templates, but the core is the same. A complete management response usually contains:

1. The recommendation. Each recommendation copied word for word from the evaluation report, numbered the same way.

2. The response. One of three positions: accepted, partially accepted or rejected. UNDP's guidelines define the middle case as agreeing with elements of the recommendation, and ask management to state which elements it agrees with and which it does not.

3. The rationale. Why management took that position. It is most important for partial acceptance and rejection, where the reasons are the main content. A rejected recommendation needs a stated reason, not silence.

4. Key actions. What will actually be done for each accepted or partly accepted recommendation. A recommendation can have several actions. Each should say what changes, not just that the recommendation was "noted."

5. Responsible unit. The unit or named role accountable for each action. When several units are involved, the UNEG guidelines ask that it be clear which unit owns which action.

6. Timeframe. A completion date for each action. UNDP, for example, says key actions should ideally be completed within 18 months of the evaluation, and that the number of actions should be reasonable enough to track.

7. Tracking status and comments. A status field (for example not started, initiated, completed) and a comments column, updated at regular intervals. UNDP's template tracks status as initiated, completed or no due date.

8. An overall response statement. A short cover note, usually one page, giving management's general view of the evaluation, what it found useful, and any findings it disputes.

9. Sign-off. Who prepared the response, who cleared it, and who is responsible for keeping the tracking record up to date. The UNEG guidelines suggest a nominated focal point to coordinate it.

Example Outline

A management response for a mid-sized evaluation usually runs 3 to 6 pages:

1. Cover statement from the program director or country representative (1 page)
2. Management response matrix, one block per recommendation (2 to 4 pages)
3. Sign-off and clearance block (half a page)
4. Tracking schedule: when status will be reviewed and who reports it (half a page)

A sample matrix, with made-up content for a generic livelihoods program:

The cover statement. A short note placed before the matrix, saying what management makes of the evaluation as a whole: what it will act on first, where it disagrees with the evaluators, and what it cannot do and why. It should not repeat the matrix.

Management Response vs. Action Plan vs. Audit Response

These are often confused because all three assign owners and dates to something found by someone else.

In practice the action plan is often the second part of the management response.

Common Mistakes

Accepting everything, vaguely. A response that says "accepted, will be implemented" for every recommendation tells the reader nothing. Each acceptance needs at least one concrete action with an owner and date.

No reasons for rejection. A rejection without a reason looks like the evaluation was ignored. The UNEG guidelines say the reasons for rejection should be provided. A clear, honest reason is more credible than silent acceptance and no follow-through.

Actions that cannot be checked. "Strengthen partnerships" or "improve coordination" cannot be marked complete. Write actions so that two people would agree on whether they were done.

Owners too high or too vague. Assigning an action to "management" or "the organization" means no one is accountable. Name a unit or role that has the authority and budget to do it.

Writing it once and filing it. A management response is only useful if status is updated and reviewed. Set a reporting interval (UNEG suggests regular reporting, for example annually or twice a year) and decide who reports it and to whom.

Variation by Organization and Evaluation Type

UN agencies. Most have a formal requirement and a central system. UNDP asks for responses and key actions to be agreed and entered in its Evaluation Resource Centre within six weeks of the final evaluation report, and the responsible units update implementation status there. The ILO uses a web-based system in which the responsible official is asked to complete the response within three weeks of access, and each recommendation is marked accepted or rejected, with a reason for rejection and a timeframe and resource implications for acceptance.

Joint evaluations. The UNEG guidelines note that strict deadlines must allow time when several stakeholders or organizational levels are involved. Joint evaluations often need separate responses from each partner, or one coordinated response with actions assigned by organization.

Project-level and decentralized evaluations. Field offices and implementing partners usually complete the response for their own project evaluations, often using the funder's or agency's template. Where no template is required, the matrix above is enough.

Mid-term reviews. A response to a mid-term review is more time-sensitive because actions are meant to change the remaining implementation period. Shorter deadlines and an early check on progress make sense. See Mid-Term Review.

Small organizations without a requirement. One page and one table is enough, and it forces a decision on each recommendation.

The test is the same everywhere: for each recommendation, can a reader find out what management decided, who will act and by when?