Prompt Library

ChatGPT Prompts for Microsoft Word Documents

20 copy-paste prompts

20 copy-paste ChatGPT prompts for Word: drafting, formatting, mail merge, track changes review, and the corporate document workflows that eat hours.

Drafting

4 prompts

Document Outline

1/20

Outline document on [topic]. Audience: [describe]. Length target: [pages]. Output: section headers, sub-sections, key points per section, supporting evidence needed, conclusion. Logical flow; not just topic dump.

Builds document outlines.

💡

Pro tip: Outlining first = faster final draft. Drafting without outline = rewrites + structure problems. 30 min outlining saves 3 hours rewriting.

Section Drafting

2/20

Draft [section] of document on [topic]. Length: [paragraphs]. Voice: [formal / casual / technical]. Include: [key points]. Avoid: [exclusions]. Stay within scope; don't expand into other sections.

Drafts document sections.

💡

Pro tip: Section-by-section drafting = focused output. "Write the whole thing" = generic + overlapping content. Constraints + scope = quality.

Document Structure Audit

3/20

[Paste document]. Audit structure: section flow logical? Repetition between sections? Sections too long/short? Missing sections? Heading hierarchy clear? Recommend specific reorganization.

Audits document structure.

💡

Pro tip: Structure problems hide in long docs. Outside review (Claude/peer) catches what self-edit misses. Restructuring before final polish = saves work.

Tone + Voice Adjustment

4/20

[Paste section]. Rewrite for [target tone]. Output: same meaning, different register. Variations: more formal, more casual, more technical, more accessible, more confident. Voice as instrument; same content many ways.

Adjusts tone of Word docs.

💡

Pro tip: Tone matters more than people realize. Same content reads opposite in different tones. Match tone to audience expectation.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Formatting + Templates

4 prompts

Document Template Recommendation

5/20

I need a Word template for [purpose — proposal / report / RFP response / etc.]. Output: structure (sections + subsections), formatting standards (heading styles, fonts, spacing), boilerplate sections, customization placeholders. Reusable across similar docs.

Recommends Word templates.

💡

Pro tip: Templates save 80% of repetitive work. Build once, use 50 times. Most teams ad-hoc; the discipline of templating is the productivity gain.

Mail Merge Setup

6/20

Set up mail merge for [type — letters / labels / certificates]. Data source: [Excel/CSV columns]. Output: merge field placement, conditional logic if needed (only show X for Y type), formatting concerns, test strategy. Avoid common mail merge errors.

Sets up Word mail merge.

💡

Pro tip: Mail merge errors = mass-distributed mistakes. Test on 3 records first. Common error: trailing spaces, wrong field name, missing data fallback.

Heading + TOC Structure

7/20

Document needs proper heading hierarchy + TOC. Topic: [describe]. Output: H1/H2/H3 structure, naming conventions, TOC inclusion rules, navigation experience. Word's auto-TOC requires consistent style usage.

Plans heading + TOC structure.

💡

Pro tip: Inconsistent heading styles = broken TOC. Discipline of using Word styles (not just font sizes) = professional documents + auto-TOC works.

Table of Contents Quality Check

8/20

[Paste TOC]. Audit: nesting logical, page numbers correct, no orphaned sections, naming consistent. TOC = doc roadmap; sloppy TOC = bad first impression.

Audits TOC quality.

💡

Pro tip: TOC is what readers see first in long docs. Sloppy TOC = "this doc isn't carefully made." Professional TOC = trust + navigability.

Review + Editing

4 prompts

Track Changes Review

9/20

[Paste document with track changes]. Help me triage: which changes substantive (need decision), which cosmetic (auto-accept), which conflict with each other, which to discuss with author. Don't blanket-accept; review with intent.

Triages track changes.

💡

Pro tip: Blanket-accepting all changes = quality loss. Reviewing intentionally = real edit. AI helps prioritize when 200+ changes; human decides each substantive one.

Comment Response Drafting

10/20

Reviewer left comments: [paste]. Help me draft responses: per comment, my response (acknowledge, push back, ask clarification, accept). Tone: collaborative, not defensive. Resolve OR escalate; don't leave hanging.

Drafts responses to Word comments.

💡

Pro tip: Defensive comment responses = relationship damage. Collaborative responses = professional editing partnership. Even pushing back can be done warmly.

Proofread Pass

11/20

[Paste document]. Proofread: grammar, spelling, punctuation, parallel structure in lists, capitalization consistency, number formatting consistency. Don't change voice or substance; just mechanics.

Proofreads documents.

💡

Pro tip: Mechanical errors = "this person isn't careful" signal. Final proofread pass = professionalism. Skip = lost credibility on substance.

Plain Language Conversion

12/20

[Paste jargon-heavy section]. Rewrite in plain language. Target reading level: [grade]. Keep meaning; cut jargon, simplify sentence structure, prefer specific over abstract. Passive → active where clearer.

Converts to plain language.

💡

Pro tip: Jargon-heavy writing = signal of confused thinking. Plain language = signal of clear thinking. Reader-respecting writing reads as expert; jargon reads as junior.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Document Types

4 prompts

Memo Drafting

13/20

Memo on [topic]. To: [audience]. Output: subject line, opening with bottom-line-up-front, supporting paragraphs (BLUF then evidence), action items, distribution list. Memos are still useful; emails replace badly for some content.

Drafts business memos.

💡

Pro tip: BLUF (bottom line up front) = reader gets the point in line 1. Trickle-out of point = reader stops reading. Lead with the point.

White Paper Section

14/20

White paper section on [topic]. Length: [pages]. Audience: [B2B decision-maker]. Output: setup of problem (with data), analysis of why important, proposed solution, evidence supporting, what reader should do. Reference-quality.

Drafts white paper sections.

💡

Pro tip: White papers fail when too marketing-y. Genuine analysis > thinly-veiled product pitch. Earn trust through quality, not push for product.

RFP Response Draft

15/20

RFP response section: [paste RFP question]. Our context: [describe]. Output: direct answer to question, supporting evidence, differentiator, related case study reference. Specific to question; not generic capabilities.

Drafts RFP responses.

💡

Pro tip: Generic RFP responses = lose. Specific-to-question + differentiated answer = win. Cut-paste-from-template = visible to evaluators + caught.

Policy Document

16/20

Policy document on [topic]. Output: purpose, scope, definitions, policy statement, procedures, compliance, exceptions, ownership + review cadence. Specific enough to follow; flexible enough to last.

Drafts policy documents.

💡

Pro tip: Policy docs overly specific = unworkable. Overly vague = unenforceable. Sweet spot = specific behavior + flexible scope. AI helps draft; legal/HR review essential.

Frequently Asked Questions

Not natively. ChatGPT writes content; you paste + format in Word. Microsoft Copilot (different product) integrates with Word + can apply formatting. ChatGPT alone = content only.

Use Word styles (Heading 1, Heading 2, Body) — not just font formatting. Style-based docs = consistent + auto-TOC + faster edits. Hand-formatted = inconsistent + breaks easily.

Track changes ON during edits; clear comments on substantive issues; agree on review cadence; one final reviewer; version naming convention. Without protocol = chaos in shared docs.

Word: deeper features, offline, enterprise standard. Google Docs: real-time collab, browser-based, simpler. Choose by team standard. Many teams use both — Google for drafting, Word for final formatted output.

Yes — for setup planning, field placement, conditional logic design, test strategy. Doesn't execute the merge (Word does). Plan with ChatGPT; execute in Word.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Business

7-day free trial. Cancel anytime.

Browse All Prompt Collections