A practical guide for development professionals and humanitarian experts using Claude's AI directly inside Microsoft Word — to draft, review, revise, and refine every project and programme document, from proposal to final report.
Claude for Word is an official Microsoft Office Add-in that brings Anthropic's Claude AI directly into the Word document environment. For international development professionals and humanitarians, it eliminates the constant switching between AI chat windows and your document — Claude reads your project proposal, SitRep, or donor report and works on it directly, delivering every edit as a tracked change you review before accepting.
Ingests entire project proposals, programme documents, and donor reports — not just selected snippets.
Every edit appears as a Word tracked change. You accept, reject, or modify each one before it is final.
Reads reviewer and peer-review comments throughout the document and suggests edits in context.
Maintains donor template structures, heading styles, table numbering, and Annex references as it edits.
Place cursor in any empty section, type your instruction, and Claude inserts formatted draft content.
On Enterprise plans, document content is not used for model training — suitable for sensitive programme data and conflict-affected context reporting.
Claude for Word requires a Claude Team or Enterprise plan. Individual claude.ai Pro subscriptions are not currently supported. Visit claude.ai to set up your organization's workspace, or ask your IT or operations team.
Installation takes under five minutes via Microsoft AppSource. Compatible with Word 2019 or later, Word for Mac, Word on the Web, and Word on Windows (Microsoft 365).
Log into claude.ai and confirm your organization's workspace is active on a Team or Enterprise subscription. For NGOs and UN agencies, check with your IT or digital transformation team — some organizations have org-wide Claude licences.
Visit claude.com/claude-for-word or search "Claude by Anthropic" in Microsoft AppSource. Click Get it now and sign in with your Microsoft work or school account.
Use a work/school Microsoft account — not personal @outlook or @gmailOpen Microsoft Word. Go to Insert → Add-ins → My Add-ins. Locate Claude by Anthropic for Office and click Add. The Claude side panel opens on the right of your document window.
In the Claude panel, click Sign in and enter your claude.ai credentials. Your Team or Enterprise plan is verified automatically — no separate licence key needed.
Open any project document — concept note, full proposal, SitRep, donor report, or partnership agreement. Select a section and type your instruction, or work in whole-document mode for consistency checks and structural reviews.
Save your document before starting each Claude sessionClaude for Word operates through a side panel alongside your document. There are four interaction modes, each suited to different stages of development document work.
Highlight a paragraph, logical framework row, budget narrative clause, or partnership clause. Claude sees your selection and the surrounding context. Type your instruction: "Rewrite this project justification to be stronger and more evidence-based." The edit arrives as a tracked change on that selection only.
Best for: rewriting sections, strengthening justifications, improving clause languageWithout selecting text, type your task. Claude reads the entire document. Use for consistency checks, donor alignment, and structural analysis: "Check that all sections reference the correct project code and align with the logframe indicators throughout."
Best for: consistency checks, cross-reference alignment, terminology standardizationWhen your document has comments from a technical reviewer, donor, or HQ, ask Claude: "Review all open comments and propose tracked changes to address each one." Claude reads the comment context and suggests edits at each location.
Best for: responding to donor queries, addressing peer-review feedback, HQ commentsPlace your cursor in an empty section and ask Claude to draft it: "Draft the Risk Matrix section for a FCDO-funded livelihoods programme in South Sudan, covering political, operational, and fiduciary risks." Content inserts at cursor as a tracked addition.
Best for: first drafts of new sections, risk matrices, work plans, log framesClaude for Word enables tracked changes automatically for every session. Do not turn off Track Changes while using Claude — this allows edits to apply directly without your review, bypassing the quality assurance your organization and donors require.
International development follows a project cycle — from needs assessment and programme design through implementation, reporting, and closure. Claude for Word reduces document burden at every stage, letting professionals focus on programme quality and field impact.
Draft assessment reports, humanitarian needs overviews, gap analyses, and context analyses from field data and secondary sources.
Build Theory of Change narratives, logframes, results frameworks, and technical annexes for project proposals.
Draft concept notes and full proposals for EU, FCDO, UNDP, GIZ, World Bank, OCHA, and bilateral donors.
Review partnership agreements, MoUs, sub-grant contracts, and consultant ToRs. Flag ambiguous clauses and deliverable gaps.
Draft work plans, procurement justifications, and internal situation reports. Maintain consistency across field and HQ documents.
Draft and adapt narrative progress reports, results narratives, and variance explanations for all major donor formats.
| PCM Stage | Document Types | Claude for Word Role | Key Action |
|---|---|---|---|
| Needs Assessment | HNO, Gap Analysis, Context Analysis, Rapid Assessment | Structure findings, draft executive summary, standardize field data narratives | Draft · Structure · Summarize |
| Programme Design | ToC Narrative, Logframe, Results Framework, Theory of Change | Draft causal pathway narratives, check logical consistency, align with donor frameworks | Draft · Review · Align |
| Proposal Writing | Concept Note, Full Proposal, Technical Annexes, Budget Narrative | Draft proposal sections, strengthen project justification, align with donor guidelines | Draft · Strengthen · Format |
| Contracting | Partnership Agreement, MoU, Sub-grant Contract, Consultant ToR | Review clauses, flag deliverable gaps, draft ToR sections, check compliance | Review · Flag · Draft |
| Implementation | Work Plan, M&E Plan, Field Reports, Internal SitReps | Draft work plan narratives, update field reports, maintain terminology consistency | Draft · Update · Standardize |
| Donor Reporting | Progress Report, Interim Report, Final Report, Results Narrative | Draft results narratives, explain variances, adapt to donor format, condense to word limits | Draft · Adapt · Condense |
| Humanitarian Response | Flash Appeal, SitRep, Cluster Report, 3W Matrix Narrative | Draft SitRep sections, structure appeals, write cluster coordination summaries | Draft · Structure · Clarify |
| Learning & Closure | End-of-Project Report, Lessons Learned, Handover Note, Case Study | Draft EoP summaries, structure lessons learned, write project handover documentation | Draft · Summarize · Handover |
Humanitarian professionals face extreme time pressure to produce high-quality documents — situation reports, flash appeals, cluster coordination summaries, and rapid needs assessments — often in unstable field conditions. Claude for Word is specifically valuable in these contexts.
Claude for Word requires an internet connection and a Microsoft 365 Word installation. For truly offline field use, copy prompts from this guide into claude.ai on a connected device, then paste content into Word. Never include personally identifiable beneficiary data in Claude sessions without your organization's data protection clearance.
Draft flash appeal sections including humanitarian overview, sectoral needs, response plan, and budget breakdown. Align with OCHA formatting requirements and Inter-Agency Standing Committee (IASC) standards.
Draft and update recurring humanitarian situation reports. Structure key developments, response highlights, funding gaps, and access constraints. Maintain consistent SitRep formatting across reporting periods.
Draft cluster coordination meeting summaries, sector-specific response overviews, and inter-agency coordination notes. Summarize 3W (Who Does What Where) matrix narratives for reporting.
Structure and draft rapid needs assessment reports from field data, key informant interviews, and secondary source data. Produce Multi-Sector Initial Rapid Assessment (MIRA) and sector-specific assessment narratives.
Ask Claude to check that your humanitarian response documents reference Sphere standards where appropriate: "Review this WASH section against Sphere minimum standards and flag any gaps in coverage or language."
Sphere · IASC · Humanitarian PrinciplesAsk Claude to review programme descriptions for conflict sensitivity and Do No Harm alignment: "Review this programme narrative for conflict-sensitive language and flag any passages that could inadvertently reflect bias toward conflict parties."
Conflict Sensitivity · Do No Harm · Protection MainstreamingClaude can review proposals and reports for protection mainstreaming: "Check this programme document for protection mainstreaming — does it address safety, dignity, non-discrimination, and accountability to affected populations?"
AAP · Protection · InclusionEight document types central to international development and humanitarian practice, with the specific actions Claude for Word performs on each.
Draft compelling concept notes for bilateral and multilateral donors. Structure problem statement, intervention logic, expected results, and budget overview. Align with specific donor call requirements and word limits.
Draft all sections of a full project proposal — context analysis, needs justification, project description, implementation approach, M&E framework, risk matrix, sustainability plan, and budget narrative. Adapt to donor templates.
Draft narrative progress reports linking results to indicators, explaining variances from targets, and highlighting key lessons and adaptations. Reformat for UNDP, EU, FCDO, GIZ, World Bank, Global Fund, OCHA requirements.
Translate Theory of Change diagrams into structured narrative documents. Draft causal pathway, assumptions, enabling conditions, and evidence base sections. Align with donor requirements and programme strategy.
Draft and update humanitarian situation reports. Summarize key developments, humanitarian needs, response highlights, funding status, and access constraints. Maintain format consistency across reporting cycles.
Review partnership agreements and MoUs for completeness. Flag ambiguous deliverable clauses, missing timelines, and compliance gaps. Draft standard MoU sections for sub-grant and implementing partner agreements.
Structure and draft rapid and detailed needs assessment reports. Integrate field data, secondary source analysis, and stakeholder consultation findings into a coherent, actionable narrative for decision-makers.
Draft consultant and firm ToRs for evaluations, assessments, technical assistance, and capacity-building assignments. Review for completeness of scope, deliverables, qualifications, and timeline.
Copy and adapt these prompts directly into the Claude for Word side panel. The context note shows whether to select text first or work in whole-document mode.
Strengthen this project justification section to make it more compelling and evidence-based. Ensure it: (1) clearly articulates the root causes of the problem, not just symptoms, (2) links the problem directly to the proposed intervention, (3) references the affected population with specificity (geographic scope, demographics, scale of need), (4) explains why this intervention is the appropriate response given the context. Apply improvements as tracked changes.
Draft a project concept note for a [sector — e.g., livelihoods, WASH, education] programme targeting [beneficiary group] in [country/region]. The programme is funded by [donor name]. Structure the note as: (1) Context and Needs — 150 words, (2) Project Objective and Expected Results — 100 words, (3) Intervention Approach — 150 words, (4) Target Beneficiaries and Geographic Coverage — 80 words, (5) Implementation Approach and Key Partners — 100 words, (6) Budget Overview — 60 words. Total: approximately 640 words. Apply as a tracked insertion.
Draft a Risk Matrix for a [programme type] project in [country/context]. Identify and describe 8–10 risks across the following categories: (1) Political and security risks, (2) Operational and implementation risks, (3) Financial and fiduciary risks, (4) Reputational risks, (5) Natural disaster or climate risks. For each risk include: risk description, likelihood (Low/Medium/High), impact (Low/Medium/High), risk owner, and mitigation measures. Format as a table and insert as a tracked addition.
Draft a budget narrative for this project proposal that justifies the key cost lines in the budget. For each major budget category — personnel, travel, equipment, direct programme costs, and indirect costs — write 2–3 sentences explaining: (1) what the cost covers, (2) how it was calculated, (3) why it is necessary for project delivery. Keep language clear and compliant with [donor name] budget guidelines. Apply as a tracked insertion.
Draft a results narrative for this [interim/final] progress report covering the period [reporting period]. Structure the narrative as: (1) Overview of progress against the project objective — 1 paragraph, (2) Results achieved per output — link each result to the relevant indicator and target, note any variance with explanation, (3) Key challenges and adaptations made, (4) Lessons learned, (5) Plans for the next period. Align language and format with [UNDP/EU/FCDO/GIZ/World Bank] reporting standards. Condense to [word limit] maximum. Apply as tracked changes.
Draft variance explanations for each indicator where results fall below or above target in this reporting period. For each variance: (1) state the indicator and the gap between target and achieved, (2) explain the root causes — contextual, operational, or design-related, (3) describe what corrective action has been or will be taken, (4) adjust the projection for the next reporting period if applicable. Use professional, factual language. Apply as tracked changes.
Draft a humanitarian Situation Report (SitRep) for [organization name] covering [geographic area] for the period [dates]. Structure it as: (1) Situation Overview — key developments this period, 1 short paragraph, (2) Humanitarian Needs — most critical unmet needs by sector, (3) Response Highlights — what the organization achieved this period with key figures, (4) Challenges and Access Constraints — operational obstacles, (5) Funding Status — funds received vs. required, (6) Priorities for the Next Period — top 3 priorities. Maintain a factual, neutral, humanitarian tone throughout. Insert as a tracked addition.
Draft the Humanitarian Overview section for a Flash Appeal responding to [type of crisis] in [country]. Include: (1) Crisis trigger and timeline, (2) Scale of humanitarian impact — population affected, displacement figures, key protection concerns, (3) Most acute sectoral needs — rank by severity, (4) Response capacity and existing gaps, (5) Funding requirement and timeframe. Follow OCHA Flash Appeal formatting conventions. Use precise, evidence-based language. Insert as a tracked addition.
Review this partnership agreement or MoU for completeness and compliance risk. Flag: (1) any deliverable clauses that are ambiguous or lack measurable outcomes, (2) missing timelines or milestone dates, (3) reporting obligations that are unclear or disproportionate, (4) financial accountability clauses that may be insufficient, (5) termination or force majeure clauses that may expose the organization to risk. Insert findings as tracked comments at the relevant clauses.
Draft a Consultant Terms of Reference for a [type of assignment — e.g., evaluation, needs assessment, training facilitation, technical assistance] for [organization name]. Include: (1) Background and context, (2) Objective of the assignment, (3) Scope of work — detailed tasks, (4) Deliverables and timeline, (5) Required qualifications and experience, (6) Reporting line and coordination, (7) Budget and contractual arrangements. Apply as a tracked insertion.
Draft an Executive Summary of no more than 500 words based on the findings in this needs assessment report. Structure it as: (1) Context and assessment purpose — 2 sentences, (2) Most critical humanitarian or development needs — top 3–5 with brief explanation, (3) Affected population and priority groups, (4) Key gaps in current response or services, (5) Priority recommendations for actors. Use clear, non-technical language suitable for decision-makers and donors. Insert as a tracked addition.
Review this programme document for alignment with [donor/organization] country strategy priorities. Check: (1) Does the programme objective align with the country strategy's strategic outcomes? (2) Are the target geographic areas and populations consistent with strategy priorities? (3) Does the sector focus reflect stated strategy priorities? (4) Are cross-cutting themes — gender, environment, governance — addressed in line with strategy requirements? Insert analysis as tracked comments at relevant sections.
International development professionals routinely produce the same programme narrative in multiple donor formats. Claude for Word can adapt documents to the reporting conventions, tone, and structure required by each donor or agency.
| Donor / Agency | Key Conventions | Claude Prompt Tip |
|---|---|---|
| EU / ECHO | PRAG logframe; visibility requirements; value for money; gender mainstreaming sections | "Restructure this narrative to follow EU PRAG reporting format with explicit logframe result references and visibility language" |
| FCDO (UK) | Theory of Change; results-based narrative; VfM (3Es); risk appetite language | "Add a Value for Money analysis paragraph using FCDO's 3Es — Economy, Efficiency, Effectiveness — and link to output costs" |
| UNDP | IRRF/SDG framing; UNDP results language; CPD alignment; gender equality markers | "Reframe findings using UNDP Results Framework language and link each outcome to relevant SDG targets and CPD priorities" |
| GIZ | Capacity development focus; DAC criteria; German development policy; sustainability pentagon | "Ensure the sustainability section addresses GIZ's 5-dimension sustainability pentagon and references German development policy priorities" |
| World Bank | PDO-level results; IRR/outcome indicators; Implementation Completion Reports; ISR ratings | "Draft an ISR-style progress narrative for this project, including ratings rationale for progress toward PDO and IP" |
| UN OCHA / CERF | Humanitarian principles; cluster system; 3W reporting; funding gap narrative | "Rewrite this response narrative to align with OCHA humanitarian reporting standards, referencing cluster coordination and coverage gaps" |
| Global Fund | Performance Framework; grant cycle structure; PR/SR relationship; disease-specific indicators | "Review this section against Global Fund PR narrative reporting requirements and flag gaps in absorption rate explanation" |
| Gates Foundation | Innovation focus; evidence-base requirement; scale narrative; equity lens | "Strengthen the innovation and scale narrative to reflect Gates Foundation priorities — what is new, what is the pathway to scale, and who is left behind?" |
If you have a master programme narrative and need donor-specific summaries, open the master document and ask Claude: "Produce a 2-page results summary formatted for [donor name] reporting standards, drawing from the findings and results in this document." Claude generates an adapted version as a tracked insertion that you can move into a separate document.
Every change Claude makes in Word is delivered as a tracked change — deletions in strikethrough, insertions underlined. This keeps you, the development professional, in full control of your programme documents before they reach donors, partners, or the public.
After Claude processes your instruction, all proposed edits appear highlighted. Switch to the Review tab in the Word ribbon to access the tracked changes navigation panel.
Use Next and Previous in the Review tab to move through each tracked change. Verify Claude's proposed text is accurate — check figures, project codes, partner names, and geographic references against your source data.
Always verify all figures, dates, and partner names Claude inserts — it cannot access your project management systemAccept applies the change. Reject restores the original. You can also edit Claude's proposed text directly before accepting — often the fastest approach when Claude gets the structure right but you need to insert specific field data or correct a figure.
After accepting changes, continue refining: "The implementation approach section reads well — now draft the sustainability plan using the same tone and format." Claude adds another tracked change layer on the accepted version.
When satisfied, accept all remaining changes, remove resolved comments, and complete your organization's standard quality assurance process. Documents containing AI-assisted sections should be clearly reviewed and approved by a qualified professional before donor submission.
Keep a version with tracked changes visible as an internal audit trailAll project figures, partner commitments, beneficiary numbers, and programme claims in donor documents represent your organization's formal position. AI-assisted drafting does not replace professional judgment or organizational quality assurance processes. Always verify data accuracy before submission.
The quality of Claude's output depends on the specificity and context you provide. These best practices reflect the realities of international development and humanitarian document work.
Always specify the donor and format: "EU ECHO PRAG logframe format," "FCDO results-based narrative," "UNDP CPD language." Generic instructions produce generic output.
Name the country, conflict dynamics, and operational context — "fragile state," "post-earthquake recovery," "protracted displacement." Claude calibrates language accordingly.
Donor templates have strict section limits. Tell Claude: "Maximum 300 words" or "Fit within the 2-page limit." This prevents Claude from producing overlong drafts that require heavy cutting.
For reporting tasks, paste the relevant logframe rows or results framework into the Claude panel alongside your instruction. This grounds Claude's output in your actual indicators and targets.
State who will read the document: "ECHO grants officer," "FCDO programme manager," "beneficiary community feedback." Claude adjusts technical depth and language register accordingly.
Accept one round of changes, then continue: "Now improve the sustainability section using the same tone." Iterative refinement consistently beats single complex prompts.
Never paste personally identifiable beneficiary data, GPS coordinates of vulnerable populations, or sensitive protection case information into Claude. Follow your organization's data protection and information security policy.
Claude cannot access your MEAL database, project management system, or financial records. Always verify every number, date, and partner reference Claude inserts against your source documentation.
Save your document before starting each Claude session. For donor submissions, maintain version control — keep dated file versions so you have a clear audit trail of document development.
EvalCommunity offers 41 specialist M&E AI agents, a 200-prompt M&E Prompt Library, AI Governance Toolkit, and a full AI in M&E learning series — all built for international development and evaluation professionals. Visit evalcommunity.com to explore the full toolkit.
Sign Up & To Get My Free Referral Toolkit Now: