Scoring Criteria
All four elements present and well-developed. Program described specifically (what, where, when, target population, scale), evaluation purpose explicit (formative, summative, or mixed; at what decision point), intended users named (named roles or organizations), decision context articulated (what decisions will be informed by findings).
At least three of four elements present. May lack named decision context or fully named users.
At least two of four elements present. Program description and purpose stated, but users or decision context generic.
One element present. Background reads as boilerplate without specific scope or users.
No clear background or scope. ToR jumps straight to tasks without context.
All four elements present. Evaluation questions are specific and answerable with the proposed methods, each question is mapped to one or more evaluation criteria (relevance, coherence, effectiveness, efficiency, impact, sustainability, or alternatives), sub-questions identified for each main question, and the user or decision-maker for each question is named.
At least three of four elements present. Questions are answerable and mapped to criteria; sub-questions or named users partially present.
At least two of four elements present. Questions present but criteria mapping is implicit. No sub-questions or named users.
Questions are vague ("How successful was the program?") or unanswerable with the proposed methods. No criteria mapping. No sub-questions.
No evaluation questions, OR questions are tasks rather than questions ("Conduct an evaluation of...").
All four elements present. Design type named (e.g., quasi-experimental, mixed-methods case study, contribution analysis) with rationale tied to evaluation questions, sampling expectations specified (probability or purposive, approximate size or range), primary and secondary data sources listed, analysis approach described (e.g., mixed-methods integration plan, qualitative coding, statistical methods).
At least three of four elements present. Design and approach named; sampling or analysis briefly described.
At least two of four elements present. Design type named but rationale generic. Sampling or analysis vague.
Methodology described as "mixed methods" or similar without specification. No design rationale.
No methodology specified, OR ToR specifies methods that cannot answer the evaluation questions.
All five elements present. Deliverables listed with content specifications (e.g., inception report, draft report, final report, presentation), milestones tied to specific dates or weeks, total days and cost or budget envelope stated, payment schedule linked to deliverables, communication plan with frequency and format.
At least four of five elements present. Deliverables and milestones clear; budget or payment schedule may be partial.
At least three of five elements present. Deliverables and timeline present but budget or payment schedule absent. No communication plan.
Two or fewer elements present. Deliverables listed but with no milestones, budget, or schedule.
No specified deliverables, timeline, or budget. ToR is unreasonable to bid on.
All four elements present. Consent and safeguarding requirements specified for all data subjects, vulnerable population protections defined (children, conflict-affected, marginalized groups), stakeholder validation plan included (when findings will be reviewed by program staff, beneficiaries, or partners), dissemination plan addresses post-evaluation communication.
At least three of four elements present. Consent and validation present; vulnerable population protections or dissemination plan partial.
At least two of four elements present. Consent referenced and one other element present. No detailed safeguarding or validation.
Ethics referenced as a checkbox ("evaluators will follow ethical standards") without specification. No validation or dissemination plan.
No ethics or stakeholder engagement provisions.
Score Interpretation
| Total (out of 25) | Band | Next Step |
|---|---|---|
| 22-25 | Strong | ToR is procurement-ready. Minor refinements only. |
| 17-21 | Adequate | Address flagged dimensions before issuing for bids. |
| 11-16 | Needs Revision | Substantial revision required before procurement. Use Revise prompt with AI output as revision brief. |
| 5-10 | Substantial Revision | Do not issue. Return to evaluation team for full redraft. |