AI Tools for Aid and Development Work

Screen one proposed AI use before selecting a tool. Record the task, information boundary, affected people, evidence, owner and stop conditions.

Editorial Status
draft
Sector
AI tools
Source Review
2026-10-26
Corrections
by email
Subsectors
Responsible use and policy, Data protection and data responsibility, Testing and evaluating AI tools, Open and local-language models, Staff learning

Editorial status: draft. Availability to read this page does not change its editorial status or establish external validation. The review scope and unverified items are stated on this page. A review date does not establish clinical, legal, security or field suitability. Check the publisher's current material and the requirements for your task.

Start With the Proposed Use, Not the Tool

Write one sentence describing the task, the person affected and the decision that remains with a responsible person. Then identify the information the task would require. If personal, confidential, protection-sensitive or unpublished information is involved, stop before entering it into an unapproved service.

The publisher pages below were read on October 26, 2026. They help frame a review or locate possible software. They do not certify a product, promise security or establish that a tool is suitable.

Compare Starting Points

NeedPublisher Starting PointWhat the Current Page OffersCheck Before Use
Frame governance for a humanitarian AI useSAFE AI FrameworkA landing page for operational governance material; download requires a short formInspect the actual framework and identify the accountable owner, affected people and decision rights
Run an internal ethics discussionNetHope AI Ethics for Nonprofits ToolkitA toolkit whose first installment focuses on a fairness workshopConfirm the current materials, facilitator, participants and issues beyond fairness that still need review
Review information risksOCHA Data Responsibility Guidelines 2025 and the ICRC data-protection handbookPublisher entry points for humanitarian data-responsibility and data-protection materialCheck the actual documents, applicable law, organizational policy and responsible data or legal role
Discover a possible open digital productDPG RegistryA searchable registry with software, data, AI-system and content categoriesCheck current DPG status, repository, maintenance, deployment needs, security evidence, support and exact license

Keep an AI Use Screening Note

FieldWhat to Record
Proposed useThe narrow task and intended user
Decision boundaryWhat the system may draft or suggest, and what a person must decide
Information boundaryData allowed, data prohibited and approved storage or service
Affected peopleWho could be helped, excluded, misrepresented or exposed
Evidence neededAccuracy, bias, language, accessibility, security and workflow tests relevant to this use
Tool factsProvider, version, hosting, terms, retention, cost, support and integration assumptions
Owner and reviewersAccountable owner plus data, safeguarding, technical or legal reviewers as needed
Stop conditionsFailure, harmful output, missing approval, changed terms or incident that stops the test

Fictional Example

The fictional Riverbend Relief Network is considering a writing assistant for public supply-request summaries. The screening note limits the test to invented examples and public source material. It prohibits names, contact details, case records and unpublished prices. A staff member must compare every statement with the source and approve the final summary. The operations owner still needs the provider's current retention terms, account controls and cost, while the data lead must confirm the proposed information boundary. The team stops the test if the service stores prohibited material, produces unsupported claims or changes its terms before approval.

Limits and Safer Use

  • A governance framework or registry listing is not a security review, procurement approval or legal determination.
  • Do not use a public demonstration or general service for real personal, confidential or protection-sensitive records.
  • Test with fictional or safely public material before considering a real workflow.
  • Record failures and unresolved issues, not only successful examples.
  • Human review must match the consequence. A polished answer is not evidence that its facts are correct.

Evidence Brief: Drafting From an Evidence Pack

Question: should an NGO test an AI assistant to draft a short operational or grant-report narrative from a permitted evidence pack? This brief informs that decision, not tool purchasing or final report approval. It is one selected historical evidence set, not a systematic review, a current-model benchmark or proof that this workflow is safe. Full-text methods, results and limitations were appraised on October 27, 2026; supplements, raw data and replications were not audited. No NGO field trial was performed here.

Three Primary Sources and Their Limits

S1, bounded writing: Noy and Zhang's March 10, 2023 working paper, not peer reviewed, randomized ChatGPT access for the second of two occupation-specific writing tasks among 444 college-educated professionals. Three blinded graders assessed outputs. It reports 27 versus 17 minutes and higher grades; see printed pages 2-4 and section 2.4. This is the early working paper, not the final Science version. Its exact model checkpoint is unestablished. Randomization supports the task comparison, while control use and differential attrition complicate it. Self-contained writing tasks did not establish source-grounded NGO-report accuracy, privacy or release safety. Its editing-related grade result does not justify removing verification. Interpretation: drafting usefulness is worth testing, without promising transferable time or quality gains.

S2, evidence integration: Dell'Acqua and colleagues' published March 11, 2026 paper reports a June-2023 GPT-4 experiment, not a 2026 model test. Among 758 consultants, 373 did business analysis from interviews and financial data. On that deliberately challenging task, correctness was 84.5% without AI versus 60%/70.6% in the two AI conditions; see sections 3-4 and Table 7, printed page 11. Other tasks benefited. Randomized comparisons are useful, but one firm's selected tasks, company involvement and incomplete preregistration limit transfer. Interpretation: supplied documents and training do not establish reliable integration. This is neither an NGO error rate nor evidence to stop every drafting use. Do not substitute estimates from the older working paper.

S3, source position: Liu and colleagues' November 20, 2023 v3 full text, later published in TACL in 2024, varies relevant-passage position and distractors across 2,655 questions, and tests synthetic key-value retrieval. Models included GPT-3.5-Turbo 0613, Claude-1.3, MPT and LongChat. See sections 2-5, especially 2.3 and 4.2. Historical 2023 model versions often used information less successfully in the middle; larger context windows did not reliably solve this. Controlled changes help isolate context use, but short-answer matching and synthetic retrieval do not measure NGO narrative completeness, privacy or release outcomes. A query-repetition improvement on synthetic retrieval did not transfer consistently to substantive QA. Interpretation: test omissions under changed pack order; do not prescribe a universal prompt fix or claim current-model error rates.

Keep Evidence, Interpretation and Action Separate

Evidence BoundaryInterpretation for This QuestionProposed Action, Not a Proven Safeguard
S1 tests bounded professional writing, not this reportA drafting comparison may be useful; benefit here remains unknownCompare the same permitted fictional/public task manually and with the exact proposed tool; record review effort as well as drafting time
S2/S3 expose historical integration or context-use problemsFluent text and a supplied pack do not establish completeness or correctnessCheck each claim and required answer against originals; recompute amounts/dates and record omissions, conflicts and failures
None tests this organization's information permissions or current serviceReal-data approval and present tool suitability remain unestablishedHold real-data use until the responsible owner confirms the information boundary, service/account conditions and task-level checks

These are editorial proposals, not validated sufficient controls or an automatic pass score. A study about writing speed does not authorize a report, establish award compliance or clear confidential information for a service.

Filled Fictional Use/Hold Record

This is a prepared decision exercise, not an executed AI test. Reuse the grant-change reporting example and its linked canonical fact sheet. Do not create another factual packet or treat its invented labels as research sources.

Record FieldCompleted Fictional Note
Task and scopeDraft a short October 1-20 narrative from the existing fictional packet; the grant owner checks coverage; the authorized submitter decides release
Checked teaching outputThe prepared flawed draft turns unconfirmed receipts into delivery and a requested extension into approval; the playbook's claim table supplies the corrections and unresolved facts
Evidence decisionS1 motivates considering a drafting comparison; S2/S3 reinforce the need to test integration. None validates this packet, tool or release
Use/hold outcomeUse the fictional exercise for staff checking practice. Hold real-data AI use and report release: tool/account approval, information permission and the outstanding agreement/report facts are not supplied
Owners and next checkFictional grant owner owns the report; finance checks its figures; the appropriate data/service owner confirms permitted use. Revisit before a real trial or submission, with actual owners and evidence recorded
Missing observationsNo actual tool/version, manual comparison, time saving, review-effort measure or staff learning outcome has been observed. Do not enter zero or claim a successful pilot

For a real proposal, attach the AI due-diligence record to the screening note above. Record exact tool/version/date, permitted pack/version, comparator, claim matches, missing required answers, amount/date checks, reviewer effort, failures, owners and the bounded use/hold decision. The organization supplies its own approval criteria; this brief sets no universal acceptable error rate.

Owner, Corrections and Recheck

The OpenAid site editor owns this one canonical brief; material updates require a separate source/claim reviewer. Record the source version, change reason, review date and resulting use/hold change here rather than replacing the evidence silently or creating parallel briefs. This is a manually reviewed pilot brief. Future reviewer availability and sustained editorial capacity are unconfirmed, so it promises no ongoing update service or review cadence.

Recheck before relying on it after a material task/model/provider change, a source correction or contradictory result, or a failed local check, and by April 27, 2027 if still in use. If a trigger arrives before review is available, hold the affected recommendation and retain the dated evidence and unknowns. Do not infer that an unchanged page means current product approval. No automatic feed, newsletter or subscription collection is provided.

Dated Brief Update

October 27, 2026, first brief: three selected full-text appraisals added. The accessible early S1 version is labeled explicitly; S2 uses the published 2026 version of a historical experiment; S3 addresses supplied-context use. A citation-fabrication study with inaccessible full text was excluded from the appraisal set. Decision remains bounded fictional practice and a hold on unapproved real-data use or unsupported report release.

What Changed in This Draft

Version 0.6.0 adds the single evidence brief above while retaining the screening note and draft status. It does not establish a maintained service, evaluated product or successful field trial.

Version 0.5 replaced the long tool catalog with a use-first screening note and a fictional example. It removes dedicated evaluation collections and does not describe a product as secure, open, responsible or suitable solely because a publisher or registry lists it.