ChatGPT Prompts for Google Docs

Create a detailed document outline for the following:

Document type: {{document_type}} (e.g., business proposal, project plan, policy document, research report)
Topic: {{topic}}
Audience: {{audience}}
Target length: {{target_length}} (e.g., 5 pages, 2000 words)
Purpose: {{purpose}} (what should the reader know, feel, or do after reading?)

Generate a complete outline with:
1. Document title and subtitle suggestions (3 options)
2. Executive summary placeholder (3 key points to cover)
3. Section-by-section breakdown:
   - Section heading (using a clear heading hierarchy: H1 > H2 > H3)
   - 3-5 bullet points of content to include in each section
   - Estimated word count per section to hit the target length
   - Sources or data needed for each section (so I know what to gather)
4. Conclusion section with recommended structure
5. Appendix suggestions (supporting data, references, glossary if needed)

Formatting notes:
- Use Google Docs-compatible heading levels (Heading 1, Heading 2, Heading 3)
- Include placeholder text for any tables or figures: [TABLE: description] or [FIGURE: description]
- Note where cross-references between sections would be useful
- Suggest where to insert page breaks for readability

Writing style: {{writing_style}} (e.g., formal/academic, professional/corporate, conversational/accessible)
Organizational context: {{org_context}}

Create a set of collaborative editing instructions for a Google Doc that {{number_of_collaborators}} people will be working on simultaneously.

Document: {{document_title}}
Document purpose: {{document_purpose}}
Collaborators and their roles:
{{collaborator_list}}
Deadline: {{deadline}}

Generate:
1. A "How to Use This Document" header section to paste at the top of the Google Doc, including:
   - Each person's assigned sections (by heading)
   - Color-coded commenting conventions (e.g., "Use blue highlights for factual questions, yellow for style suggestions")
   - Naming convention for comments (start with your initials and category: "JC-FACT: Is this statistic current?")
   - Rules for when to suggest vs. when to directly edit

2. An editing workflow:
   - Phase 1: Content drafting (who writes what, by when)
   - Phase 2: Peer review (who reviews whose sections, what to look for)
   - Phase 3: Consolidation (who resolves conflicts and unifies voice)
   - Phase 4: Final proofread and sign-off

3. A Google Doc comment template for common feedback types:
   - Structural feedback: "STRUCTURE: [suggestion]"
   - Factual question: "FACT-CHECK: [question]"
   - Style/tone: "TONE: [suggestion]"
   - Approval: "APPROVED - [initials]"

4. A "Do Not Edit" list — sections owned by specific people that others should only comment on
5. Version naming convention (e.g., "v1-draft", "v2-review", "v3-final")

Make these instructions concise enough that people will actually read them — no more than one page.

Design a reusable Google Docs template for {{template_type}} that my team will use repeatedly.

Use case: {{use_case_description}}
How often it will be used: {{frequency}} (e.g., weekly, per project, per client)
Who fills it out: {{template_users}}
Who reads the completed version: {{template_audience}}

Create the complete template with:
1. A header section with:
   - Document title with [PLACEHOLDER] fields for variable information
   - Metadata block: Date, Author, Version, Status (Draft/Review/Final), Distribution
   - A one-line purpose statement explaining what this document is for

2. All content sections with:
   - Clear section headings
   - Instructional text in [brackets] explaining what to write in each section
   - Example text in italics showing the expected format and level of detail
   - Word count guidance for each section (e.g., "2-3 sentences" or "half a page")

3. Standard elements:
   - A consistent formatting guide (font, heading styles, spacing) noted at the top
   - Required fields marked with [REQUIRED] and optional fields marked with [OPTIONAL]
   - A checklist at the end: "Before submitting, confirm: [ ] All required fields completed [ ] Reviewed by {{reviewer}} [ ] Attachments linked"

4. Template instructions (as a separate section to delete before use):
   - How to make a copy of this template
   - What to customize vs. what to keep standard
   - Where to save the completed document

Design for the {{skill_level}} user — {{skill_level_description}}.

I have a draft document in Google Docs that needs structured feedback from {{number_of_reviewers}} reviewers. Create a feedback system that makes the review process efficient and actionable.

Document: {{document_title}}
Document type: {{document_type}}
Draft stage: {{draft_stage}} (e.g., first draft, revised draft, near-final)
Reviewers: {{reviewer_list}}
Feedback deadline: {{feedback_deadline}}

Generate:
1. A feedback request email/message to send to reviewers:
   - What the document is about (2 sentences)
   - What specific feedback you need (not just "let me know what you think")
   - What is NOT up for debate at this stage
   - The deadline and expected time commitment
   - Link placeholder: [GOOGLE DOC LINK]

2. A structured feedback rubric for reviewers to use:
   | Criteria | Rating (1-5) | Comments |
   |----------|--------------|----------|
   (Include 6-8 criteria relevant to the document type: clarity, accuracy, completeness, tone, structure, actionability, etc.)

3. A comment taxonomy — specific prefixes for different feedback types:
   - CRITICAL: Must fix before publishing
   - SUGGESTION: Consider this improvement
   - QUESTION: Need clarification
   - PRAISE: This works well (positive feedback matters)
   - NITPICK: Minor style/grammar (low priority)

4. A feedback consolidation template:
   - Summary of feedback themes across all reviewers
   - Conflicting feedback and how you resolved it
   - Changes made vs. changes deferred (with reasoning)
   - Section for reviewer sign-off: "I have reviewed the changes: [Name] [Date]"

5. Response protocol — how the author should reply to each comment type (resolve, reply, or schedule discussion)

Create a meeting notes template and post-meeting processing prompt for {{meeting_type}} meetings.

Meeting context:
- Meeting name: {{meeting_name}}
- Frequency: {{frequency}}
- Typical duration: {{duration}}
- Typical attendees: {{attendees}}
- Purpose: {{meeting_purpose}}

Part 1 — Generate a Google Docs meeting notes template with:
1. Header: Meeting name, date, time, attendees (present/absent), note-taker
2. Agenda section with time allocations
3. Discussion notes section (organized by agenda item):
   - Key points discussed
   - Decisions made (highlighted in bold)
   - Action items (with owner and due date in a consistent format: "ACTION: [task] — [owner] — [due date]")
4. Parking lot: Items raised but deferred to a future meeting
5. Next meeting: Date, preliminary agenda items

Part 2 — Generate a post-meeting processing prompt:
Take the following raw meeting notes and transform them into a clean, structured summary.

Raw notes:
{{raw_notes_placeholder}}

Process into:
1. Meeting summary (3-5 sentences covering the most important outcomes)
2. Decisions log: A numbered list of every decision made, with the rationale
3. Action items table:
   | # | Action Item | Owner | Due Date | Status |
   |---|-------------|-------|----------|--------|
4. Key discussion points (organized by topic, not chronologically)
5. Open questions that need follow-up
6. Items for next meeting's agenda

Format for {{distribution_method}} (e.g., email summary, shared Google Doc, Slack post).
Tone: {{tone}} (e.g., formal minutes, casual team notes)

Draft a complete project brief document for {{project_name}} that can serve as the single source of truth in Google Docs.

Project overview:
{{project_description}}

Generate the full document with these sections:

1. Project Header
   - Project name, owner, sponsor, date, status
   - One-sentence project description

2. Problem Statement
   - What problem are we solving? (2-3 sentences)
   - Who is affected and how?
   - What happens if we do nothing?
   - Evidence: {{supporting_data}}

3. Project Objectives
   - 3-5 SMART objectives (Specific, Measurable, Achievable, Relevant, Time-bound)
   - Success metrics: how we will measure each objective

4. Scope
   - In scope: (bullet list)
   - Out of scope: (bullet list — this is often more important)
   - Assumptions and constraints

5. Approach
   - High-level approach or methodology
   - Key phases and milestones with target dates
   - Dependencies on other teams or projects: {{dependencies}}

6. Team and Roles
   | Role | Person | Responsibility | Time Commitment |
   |------|--------|----------------|-----------------|
   {{team_members}}

7. Budget and Resources
   - Estimated budget: {{budget}}
   - Key resources needed
   - Approval required for expenditures over {{approval_threshold}}

8. Risks and Mitigations
   | Risk | Likelihood | Impact | Mitigation |
   |------|------------|--------|------------|
   (Generate 5-7 realistic risks based on the project description)

9. Communication Plan
   - Stakeholder update cadence
   - Where to find project updates (this Google Doc)
   - Escalation path for blockers

10. Sign-off
    - Spaces for project sponsor and key stakeholders to add their name and date

Target length: {{target_length}} pages
Tone: {{tone}} (e.g., executive-ready, team-internal, cross-functional)