Draft Evaluation Terms of Reference

Write terms of reference for commissioning an external evaluation, including scope, questions, and methodology.

On this page
What You Need
Supply the commissioning purpose, decisions, program documents, scope, timing, available data, budget or procurement rules, and any binding evaluation standard.
Choose This Prompt When
Use this before hiring or commissioning an evaluation; choose evaluation design review when a design already exists.

Draft terms of reference for an evaluation that a prospective evaluator could scope and price. If the evaluation purpose, subject, or intended users are missing, ask for them before presenting a commissionable TOR. Treat dates, budget, deliverables, approvals, and standards not supplied as proposed or to be confirmed.

Include program and evidence background; purpose, intended users, and decisions; boundaries of population, geography and period; a small set of prioritized, answerable evaluation questions; criteria selected for this purpose rather than automatically using every OECD DAC criterion; suggested design options and minimum methodological expectations; data access, sampling, analysis, ethics, inclusion, and limitations; stakeholder participation; deliverables, review process, roles, and schedule; and any budget or procurement constraints actually supplied. Let bidders justify feasible methods rather than prescribing a mixed-method package by default. Separate what the commissioner has decided from options for decision. Identify missing information that affects feasibility or price.

State quality assurance and ethics responsibilities, how the draft report will be reviewed, and who will resolve conflicting comments, if those roles are known.

Loading saved answers...
Did this page help?

Worked Example

Illustration only. The setting and figures are invented to show the pattern.

Scenario: An education NGO wants an external end-of-project evaluation of a four-year reading program in two provinces. The board will decide on a second phase next spring, and the evaluation budget has a fixed ceiling.

What You Give the AI: The program summary and results table, the decision the board has to make, the two provinces and school types, assessment data from year one and year three, the timeline, the budget ceiling, and the organization's procurement rules.

What the AI Might Return: A draft with purpose, intended users, scope, and five questions ranked by priority. Question 1 reads "To what extent did reading levels in Grade 3 improve in supported schools, compared with the years before the program?". The methods section asks bidders to propose their own design, and a deliverables table lists an inception report, draft report and final report. An open decisions list notes that no one has said who approves the final report.

When to Choose This Prompt

  • You are about to advertise for an external evaluator and have no terms of reference yet.
  • You have a decision to inform and need the questions tied to it.
  • You want unresolved choices, such as sign-off or data access, shown before bidders see the document.

When Not to Choose It

Checking the Output

  • Set the purpose statement beside the decision you described. If the TOR could serve any evaluation, it needs sharpening.
  • The number of questions has to fit your budget and timeline. A long list rarely fits a single evaluation.
  • Every document or dataset named as available should be one you hold and can share with the evaluator.
  • Look in the method section for prescriptions you did not choose. Unless you require a design, bidders should be free to propose theirs.
  • The schedule should match your real dates, with time for your own review of drafts.
  • Budget and procurement lines need checking against your actual rules, as the AI cannot know them.

Common Problems and Fixes

  • The questions are generic and could be copied to any program. Fix: Each question can be tied to a named result or province from your documents, with the decision it feeds written beside it.
  • The scope tries to cover every component and every year. Fix: List what you will leave out and have the TOR record those exclusions.
  • Standards or requirements are quoted that you never supplied. Fix: Delete them. If a standard binds you, paste its actual text.
  • Deliverable dates ignore review time. Fix: Your review windows, once given, can be built into the schedule.

Adapting It to Your Context

  • Binding evaluation standard: Paste the clauses and ask the TOR to cite which section addresses each one. Verify against the source.
  • Sensitive topic or vulnerable participants: Ask for ethical requirements, including consent and data handling, to be set as bidder obligations.
  • Little existing data: State that no baseline exists and ask the TOR to say how the evaluator should handle it.
  • Local evaluator pool: Name the working languages and ask for language and local knowledge to appear as selection criteria.

Next Step

Evaluation ToR Quality