Recommendation response table (management response template)
Copy all report recommendations into this worksheet and enter the organization's position, response plan, responsible person and deadline for each. Submit after management approval.
Recommendation response table (management response template)
Basic information
Enter basic information on the evaluation
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- Evaluation name
- Operational evaluation of community consultation sessions (fictional)
- Evaluation report publication date
- October 10, 2026
- Person responsible for preparing the management response
- Operations representative C
- Date prepared
- October 20, 2026
- Submission recipient (e.g., evaluation committee)
- Management meeting
Reason for this entry: Match report and response versions.
Writing tips and explanation for this section
About this section
Enter basic information on the evaluation
Match report and response versions.
View the method explanationWriting tips
Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.
Read the full fictional exampleRecommendation response table
Enter recommendations in report number order. Choose Accepted / Partially accepted / Rejected in the position field.
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
Scroll horizontally to view the table
| Recommendation number | Recommendation summary | Position (accepted/partially accepted/rejected) | Reasons and additional notes | Specific action | Responsible department and person | Planned completion deadline |
|---|---|---|---|---|---|---|
| R1 | Provide reception assistance at every session | Partially accepted | Funding for permanent additional staff is unavailable | Pilot assistance twice during busy periods and review waiting times | Venue staff member B | November 30, 2026 |
| R2 | Record reception times consistently | Accepted | Needed for comparison before and after improvements | Standardize record field definitions and explain them to all staff | Records staff member A | October 31, 2026 |
Reason for this entry: Link the degree of acceptance to specific implementation.
Scroll horizontally to view the table
| Recommendation number | Recommendation summary | Position (accepted/partially accepted/rejected) | Reasons and additional notes | Specific action | Responsible department and person | Planned completion deadline |
|---|---|---|---|---|---|---|
Writing tips and explanation for this section
About this section
Enter recommendations in report number order. Choose Accepted / Partially accepted / Rejected in the position field.
Link the degree of acceptance to specific implementation.
View the method explanationWriting tips
Keep the information in each row aligned. Scroll wide tables horizontally to see every column.
Read the full fictional exampleExplanation of disagreement
Transparently describe reasons for rejected or partially accepted recommendations, such as authority, resources or technical constraints
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
Reason for this entry: Explain what remains on hold under partial acceptance.
Writing tips and explanation for this section
About this section
Transparently describe reasons for rejected or partially accepted recommendations, such as authority, resources or technical constraints
Explain what remains on hold under partial acceptance.
View the method explanationWriting tips
Use the example as a reference and record what you have established about your own program. Distinguish assumptions and unchecked matters from confirmed facts.
Read the full fictional exampleFollow-up tracking plan
Enter when, by whom and how progress will be checked
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- First planned progress review date
- November 15, 2026
- Second planned progress review date
- December 10, 2026
- Progress management lead
- Records staff member A
- Planned final completion check date
- December 10, 2026 (reset deadline if incomplete)
Reason for this entry: Separate interim and completion checks.
Writing tips and explanation for this section
About this section
Enter when, by whom and how progress will be checked
Separate interim and completion checks.
View the method explanationWriting tips
Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.
Read the full fictional exampleApproval
Approve the management response as a whole
Completed example for this section (fictional)
This fictional example is for explanation. Adapt it to your own program. Your entries will not change.
- Approver's name and position
- Operations meeting chair D (fictional approver)
- Approval date
- October 20, 2026 (fictional)
- Recipient and deadline for next follow-up report
- Operations meeting / December 10, 2026
Reason for this entry: This fictional example illustrates the form; it is not a record of actual approval.
Writing tips and explanation for this section
About this section
Approve the management response as a whole
This fictional example illustrates the form; it is not a record of actual approval.
View the method explanationWriting tips
Follow each field’s heading to record the program name, focus, period, and other details. Leave undecided matters clearly marked as unresolved.
Read the full fictional exampleBefore writing, check when to use the worksheet and what completion involves
Recommendation response table (management response template) is a worksheet for applying Management Response in meetings or individual work. For the overall duration of the method, use “Illustrative estimate (adjust for scale and team): initial response: 2–4 weeks / follow-up tracking: 1–3 years after evaluation” as a reference, adjusting for scale and resources. Fill in what you know provisionally and leave unresolved matters as questions to check next.
When this worksheet is useful
- When receiving an evaluation report and preparing an organizational response and action plan for recommendations
- When an official accountability response to an external or third-party evaluation is required
- When establishing organization-wide arrangements to track and manage recommendation implementation
Participants and preparation
Management of the evaluated program, such as bureau or section heads, responsible departments, and evaluation or planning departments for coordination. Consider approval at chief executive or board chair level when submitting to an external evaluation committee.
Bring the materials used for decisions, existing data, and differing stakeholder views to help complete the worksheet.
Suggested order
- 1. Basic informationEnter basic information on the evaluation
- 2. Recommendation response tableEnter recommendations in report number order. Choose Accepted / Partially accepted / Rejected in the position field.
- 3. Explanation of disagreementTransparently describe reasons for rejected or partially accepted recommendations, such as authority, resources or technical constraints
- 4. Follow-up tracking planEnter when, by whom and how progress will be checked
- 5. ApprovalApprove the management response as a whole
Signs the worksheet is ready for review
- Management response document (recommendation response table)
- Action plan (with responsible people and deadlines)
- Progress tracking register
Cautions for review
- Expressing acceptance while action plans remain too abstract to implement. Named responsible people and deadlines are essential.
- Stating only “rejected” without reasons. Transparent reasons for disagreement strengthen credibility.
- Submitting the management response and abandoning follow-up tracking
Read a completed fictional example (your entries will not change)
The following is a fictional example for illustration. A community consultation operations meeting decides responses to two recommendations.
Basic information
- Evaluation name
- Operational evaluation of community consultation sessions (fictional)
- Evaluation report publication date
- October 10, 2026
- Person responsible for preparing the management response
- Operations representative C
- Date prepared
- October 20, 2026
- Submission recipient (e.g., evaluation committee)
- Management meeting
Reason for this entry: Match report and response versions.
Recommendation response table
Scroll horizontally to view the table
| Recommendation number | Recommendation summary | Position (accepted/partially accepted/rejected) | Reasons and additional notes | Specific action | Responsible department and person | Planned completion deadline |
|---|---|---|---|---|---|---|
| R1 | Provide reception assistance at every session | Partially accepted | Funding for permanent additional staff is unavailable | Pilot assistance twice during busy periods and review waiting times | Venue staff member B | November 30, 2026 |
| R2 | Record reception times consistently | Accepted | Needed for comparison before and after improvements | Standardize record field definitions and explain them to all staff | Records staff member A | October 31, 2026 |
Reason for this entry: Link the degree of acceptance to specific implementation.
Explanation of disagreement
Reason for this entry: Explain what remains on hold under partial acceptance.
Follow-up tracking plan
- First planned progress review date
- November 15, 2026
- Second planned progress review date
- December 10, 2026
- Progress management lead
- Records staff member A
- Planned final completion check date
- December 10, 2026 (reset deadline if incomplete)
Reason for this entry: Separate interim and completion checks.
Approval
- Approver's name and position
- Operations meeting chair D (fictional approver)
- Approval date
- October 20, 2026 (fictional)
- Recipient and deadline for next follow-up report
- Operations meeting / December 10, 2026
Reason for this entry: This fictional example illustrates the form; it is not a record of actual approval.
Common errors in judgment
Mark all recommendations accepted and treat the response as complete
How to revise: Specify actions, responsible people, deadlines and completion evidence
Reason: Agreement and implementation are different states.
Delete rejected recommendations from the report
How to revise: Retain evaluation recommendations and explain disagreement in the response
Reason: This makes both evaluation and organizational decision-making traceable.
References and checked sections
- Management Response to Independent Strategic and Corporate Programme EvaluationsUnited Nations Development Programme
- Section consulted
- Key issues and recommendations; Key actions; Implementation of the actions
- How it relates to the text
- Link views on recommendations to actions, deadlines, responsibilities and implementation tracking.
How to cite this page
Change history
- — Updated explanations to correspond with sources, and added method-specific fictional worksheet examples, judgment examples and revision history.


