ChatGPT for evaluators 20 techniques
EvalCommunity Academy · AI Tools for M&E Practice
20 Things You Can Do With ChatGPT That Most Evaluators Never Try
Stop using AI as a search box. Twenty practical techniques that turn ChatGPT into a critical friend, document reviewer, data checker and research assistant for monitoring, evaluation, accountability and learning.
Level: Beginner to intermediate · Reading time: about 15 minutes · Updated: November 2026
Before you start
Features such as file analysis, Projects, voice, memory and deep research vary by ChatGPT plan and account, and they change often. Most techniques here also work in other assistants such as Claude. Above all: never upload identifiable respondent data, safeguarding information or client material your contract does not allow you to share with third-party AI services. Section 7 covers this in detail.
Learning objectives
By the end of this tutorial you will be able to:
- Use AI to sharpen evaluation questions and stress-test emerging findings.
- Compare, review and check documents such as ToRs, logframes and reports against frameworks.
- Run first-pass data quality checks and spot misleading charts.
- Set up long-running workspaces and trusted-source research for evaluation assignments.
- Decide which parts of your work to delegate and which to keep, and protect data while doing so.
1. From answers to process
Most professionals use ChatGPT for a narrow set of tasks: answer a question, rewrite an email, summarise a report. Useful, but it barely touches what the tool can do. Today it can work with documents, spreadsheets and images, search the web, run multi-step research, keep long-running Projects and hold voice conversations.
For evaluators, the biggest gains rarely come from asking for outputs. They come from using AI in the process: challenging reasoning, comparing sources, finding what changed, asking better questions and noticing what you missed. That is the thread running through all 20 techniques.
Output requests (common)
- “Summarise this report”
- “Write the executive summary”
- “Give me evaluation questions”
Process requests (underused)
- “Where do these two reports disagree?”
- “Argue against my emerging finding”
- “What would prove my conclusion wrong?”
2. Sharpen your questions and reasoning
1
Ask it to find the question you should be asking
ToRs often list fifteen questions while the client’s real concern sits underneath. Instead of drafting questions yourself, describe the situation and let ChatGPT interview you until the core issue is clear.
The client wants a mid-term evaluation of a youth employment project, but I can’t tell whether their real concern is low enrolment, poor job placement or partner performance. Ask me one question at a time until we can define the main evaluation question.
2
Make it argue against your emerging finding
AI is least useful when it agrees with you. Before a finding goes into the report, ask for the strongest reasonable case against it. This is a quick rehearsal of the challenge you will face at the validation workshop.
My emerging finding: the training component improved women’s income. Identify the assumptions behind this, give me the strongest alternative explanations, and tell me what evidence would distinguish between them.
3
Ask what would prove your conclusion wrong
This turns a prediction into a test, which is especially valuable for contribution claims. You get a list of checks to run before you commit to a conclusion, and the AI does not become the decision-maker.
I believe the project contributed to reduced school dropout. What would I need to find in the data or interviews for that conclusion to be wrong? List the checks I should run before finalising.
4
Turn your past mistakes into a checklist
Most evaluators repeat a few costly patterns: underestimating fieldwork time, accepting vague ToRs, agreeing to a sample the budget can’t support. Describe a few past cases and ask for the pattern and a reusable checklist.
Here are three assignments where my timeline slipped and why. Identify the recurring pattern and turn it into a short go/no-go checklist I can use before accepting a new evaluation.
3. Work smarter with documents
5
Find where two documents genuinely disagree
Summaries side by side hide contradictions. Upload two documents (two evaluations of similar programmes, a baseline and midline report, a project document and a partner report) and ask for disagreements, not summaries.
Don’t summarise these separately. Identify where they actually disagree, where they rely on different evidence, and where they seem to agree but define the same term differently (for example “beneficiary” or “employment”).
6
Ask what changed between two versions
A revised ToR, logframe or contract arrives and you don’t want to reread everything. Upload both versions and say what counts as a meaningful change.
Compare version 1 and version 2 of this ToR. Ignore formatting. List every substantive change to scope, evaluation questions, deliverables, deadlines, budget or required expertise, and flag anything that affects my workload.
7
Apply one document’s rules to another
This turns ChatGPT from a summariser into a reviewer. Pair a framework with a draft: a donor’s report quality checklist and your draft report, the OECD-DAC criteria and an evaluation matrix, a proposal template and your technical proposal.
Review my draft evaluation report against the attached quality checklist. For each criterion, rate it met, partly met or not met, quote the relevant passage, and suggest what is missing.
Tip: run this before submitting to a client, as a self-assessment. It catches structural gaps; it cannot judge the quality of your evidence.
8
Turn a screenshot into a troubleshooting session
Stuck on a KoboToolbox form error, a Power BI setting or an Excel formula? Upload a screenshot instead of describing it. Asking what it cannot tell from the image keeps the answer honest.
This XLSForm validation error appears when I upload my survey. What does it seem to be telling me, and what other information would you need before suggesting a fix?
4. Check data and charts
Data rule: use only anonymised or aggregated datasets. Remove names, phone numbers, GPS points, IDs and small-group breakdowns that could identify people before uploading anything.
9
Ask what a dataset can actually answer
Before analysing an Indicator Tracking Table or survey export, ask what questions the data is capable of answering. This stops you designing an analysis the data cannot support.
Before analysing this anonymised monitoring dataset, tell me which evaluation questions it can and cannot answer, and why. Then identify the three patterns or anomalies most worth investigating.
10
Find the weird rows
A fast first-pass data quality check: outliers, blanks, duplicates, impossible combinations and sudden jumps. Asking it not to assume errors keeps judgement with you.
Flag values that look unusual in this partner monthly report: blanks, duplicates, figures over 150% of target, month-on-month changes over 30%, or impossible combinations. Don’t assume they are mistakes; explain why each one stands out.
11
Ask what could make a chart misleading
Useful for donor dashboards, partner presentations and your own report graphics. Ask about axes, scale, time period, missing context and visual framing.
Explain what this results chart appears to show, then tell me which design choices or missing information (baseline, denominator, time period, disaggregation) could lead a reader to the wrong conclusion.
5. Build a long-term workspace
12
Create a Project for each assignment
Stop re-explaining the context in every new chat. A Project keeps related conversations, reference files and instructions together. Create one per evaluation with the ToR, inception report and evaluation matrix, plus standing instructions.
Project instructions: This is the final evaluation of [project]. Use the ToR and evaluation matrix as the reference for all questions. Write in [your preferred language and spelling], use the OECD-DAC criteria, and always cite which file a statement comes from.
13
Build a private evidence library
Fill a Project with sector evidence you trust: past evaluations, systematic reviews, guidance notes and your own notes. Then question it during desk reviews and proposal writing.
Using only the files in this Project, what does the evidence say about cash transfers and school attendance for adolescent girls? Separate strong findings from weak ones and name the source of each.
14
Talk through your files by voice
Where voice supports files and Projects, you can review a long inception report on a commute or a walk between field sites. Interrupt, question and ask it to go back, as you would with a colleague.
Talk me through the three parts of this evaluation methodology that a sceptical client is most likely to challenge.
15
Recover work from old conversations
That sampling note, KII guide or theory of change you drafted months ago is still in your history. Search your chats and Projects before recreating it from scratch.
Find the key informant interview guide for local government officials I worked on earlier this year, and adapt it for a WASH evaluation.
16
Ask what you consistently forget
With memory or personalisation turned on, ChatGPT can look across your planning conversations for recurring blind spots. Treat the answer as a prompt for reflection, not a verdict.
Looking at the evaluation workplans we’ve discussed, which constraints do I usually forget to mention until late: translation, ethics approval, security, travel time, or something else?
6. Research, rehearse and delegate wisely
17
Restrict research to sources you trust
Deep research can investigate a question across many sources. Where your plan allows, focus it on selected sites, such as evaluation offices, evidence repositories and official statistics, instead of the whole web.
Research what rigorous evaluations say about graduation programmes in fragile settings. Prioritise UN evaluation offices, the World Bank IEG, 3ie and peer-reviewed studies. Exclude blogs and news. Cite every source.
Tip: open and check every cited source. AI research can still misstate findings or cite the wrong document.
18
Ask when more research isn’t worth it
Desk reviews can expand without end. Ask how much research a question deserves given the budget, timeline and stakes, and set a stopping rule.
I have three days for the desk review in a 25-day evaluation. Given the evaluation questions, which sources are essential, which are nice to have, and what stopping rule should I use?
19
Rehearse a difficult conversation out loud
Presenting negative findings to a programme team, negotiating scope with a client, or interviewing a guarded official. Ask ChatGPT to play the other person, first cooperative, then sceptical, then unpredictable.
Play a defensive programme director hearing that the project’s main outcome was not achieved. I’ll present the finding; push back the way a real director might. After three rounds, give me feedback on my delivery.
20
Ask which part of the task you should keep
Perhaps the most important question of all. Ask AI to separate tedious work from the parts where your judgement, experience and ethics matter, and to help only with the first.
I’m writing the findings chapter of a final evaluation. Separate the work into parts where you can remove tedious effort and parts where my evaluative judgement must lead. Help me with the first category without replacing the second.
AI can organise evidence, check references and spot unclear passages. Deciding what the evidence means, how strong it is, and what to recommend remains the evaluator’s job.
7. Responsible use: data protection, ethics and quality
Every technique above involves sharing material with a third-party AI service. Your obligations to respondents, clients and donors stay with you.
Never upload
- Identifiable data on participants, respondents or interviewees, including transcripts with names.
- Safeguarding, protection or PSEA case information.
- Data from contexts where exposure could put people at risk.
- Client documents your contract, data-sharing agreement or ethics approval does not allow you to share.
Responsible-use checklist
8. Your first week: a practice plan
Try one technique a day on real but low-risk work. Fifteen minutes is enough.
9. Knowledge check
Tap each question to reveal the answer.
1. What is the difference between an “output” request and a “process” request?
An output request asks AI to produce something (“summarise this”). A process request uses AI to improve your thinking (“where do these sources disagree?”, “what would prove me wrong?”).
2. Why ask ChatGPT to argue against your emerging finding?
It exposes untested assumptions and alternative explanations before the finding reaches the client, much like a validation workshop would.
3. When comparing two versions of a ToR, what instruction makes the result useful?
Telling it what counts as a meaningful change (scope, questions, deliverables, deadlines, budget) and to ignore formatting.
4. Your survey export includes names and GPS points. Can you upload it to find outliers?
Not as it is. Remove names, GPS points, phone numbers, IDs and any small-group breakdowns that could identify people, and check your contract and ethics approval first.
5. Deep research returned ten sources. What must you still do?
Open and check every source. AI research can misstate findings or attach a claim to the wrong document.
6. Which parts of a findings chapter should stay with the evaluator?
Interpreting the evidence, judging its strength, drawing conclusions and making recommendations. AI can help with organising evidence, checking references and clarity.
10. Key takeaways
- The biggest gains come from using AI in your process (challenging, comparing, checking), not just for outputs.
- Document comparison, framework-based review and data quality checks save the most time for evaluators.
- Projects and trusted-source research turn scattered chats into a working evaluation toolkit.
- Anonymise before you upload, and verify everything before you use it.
- Always ask which part of the task is yours to keep. Evaluative judgement is not delegable.
Build your AI skills for evaluation
Explore more EvalCommunity Academy tutorials and tools on responsible AI in monitoring, evaluation, accountability and learning.
ChatGPT features, availability and limits vary by plan and change frequently; check OpenAI’s official documentation for current details. Example prompts are illustrative. EvalCommunity is not affiliated with OpenAI.
