ChatGPT Prompts to Summarize Text

Analyze the competitor messaging I've pasted below and produce a structured summary.

Sections:
1. Core positioning statement (what problem they claim to solve, for whom)
2. Key claims and proof points they use (list the top 4–5)
3. Messaging strengths — what they do well and why it works
4. Messaging gaps or weaknesses — what they underplay or avoid
5. How our positioning should differ — one paragraph on the angle to own

Competitor name: [NAME]
Our product: [DESCRIPTION]
Competitor messaging (paste homepage copy, about page, or ad text): [PASTE]

Turn my campaign notes and metrics into a clean, shareable campaign recap.

Structure:
1. Campaign name, dates, and goal
2. Key results — bullet list, numbers first (include what hit vs. missed target)
3. What drove performance (2–3 factors, evidence-based)
4. What underperformed and the likely reason
5. Recommendations for the next campaign (3 bullets, specific and actionable)

Do not invent numbers. If a metric is missing, mark it as "not tracked."

Campaign notes and metrics: [PASTE]

Convert my raw call notes into a CRM-ready summary with these exact fields:
- Stage (one of: Discovery / Evaluation / Proposal / Negotiation)
- Pain points (bullets)
- Budget signal (what they actually said about money, or "none mentioned")
- Decision makers
- Objections / risks
- Next action + date

Only use what's in the notes. If a field is empty, write "none mentioned."

Notes: [PASTE NOTES]

Write a one-paragraph executive summary to open a sales proposal. It should make a busy executive want to read on.

Cover, in plain language: the business problem, what we propose, the expected result (with a number if I give one), and the investment.

Details: [PASTE KEY PROPOSAL POINTS / PRICE / EXPECTED ROI]

Keep it under 120 words, confident but not hypey.

Analyze my notes from a closed deal and produce a win/loss summary:
- Outcome: Won / Lost
- Primary reason (one sentence)
- Contributing factors (bullets)
- What the competitor did, if mentioned
- One thing I'd do differently next time

Be honest, not flattering. Only use what's in the notes.

Deal notes: [PASTE NOTES]

Below are raw notes from a team meeting. Turn them into a clean summary for people who weren't there.

Format:
1. **TL;DR** — 2 sentences.
2. **Decisions made** — bullet list.
3. **Action items** — a table: Task | Owner | Due date. If an owner or date wasn't stated, write "unassigned" — do not invent one.
4. **Open questions** — anything left unresolved.

Keep it factual. Don't add advice. Here are the notes:
[PASTE NOTES OR TRANSCRIPT]

You are a senior manager writing a weekly status report. Turn my bullet-point notes into a clean update my director will read in under two minutes.

Format:
1. **This week** — 3–5 bullets of concrete progress (metrics or deliverables, not effort).
2. **Next week** — 2–3 priorities with owners.
3. **Blockers** — anything I need from leadership. If none, write "None."

Rules: plain language, no filler phrases like "we continued to work on," numbers wherever I have them, under 200 words total.

My notes: [PASTE YOUR WEEK'S NOTES]

You are an experienced manager writing a formal performance review. Turn my raw notes into a draft review for [EMPLOYEE NAME], a [ROLE], covering the period [DATES].

Structure:
1. **Overall summary** — 2 sentences.
2. **Strengths** — 2–3 specific examples from the notes (quote real outcomes, not personality traits).
3. **Areas to develop** — 1–2 honest, specific gaps with a suggested action, not vague criticism.
4. **Rating recommendation** — [RATING SCALE, e.g. Exceeds / Meets / Below].

Rules: use specific evidence from my notes. If a section has no evidence, write "no data provided" — don't pad it. Avoid empty praise. Neutral professional tone.

My notes: [PASTE NOTES]

Write a decision memo for [DECISION MAKER / AUDIENCE] on the question: [THE DECISION TO BE MADE].

Format:
1. **Context** — why this decision is needed now (2–3 sentences).
2. **Options** — a table: Option | Pros | Cons | Cost/Effort.
3. **Recommendation** — which option you recommend and the one-sentence reason.
4. **What we need from you** — the specific ask (approval, a call, a sign-off).

Be direct. State a recommendation even if the data is imperfect. Under 300 words.

Details: [PASTE OPTIONS, TRADE-OFFS, YOUR PREFERRED CHOICE AND WHY]

Summarize the following standup notes into a brief status update I can share with stakeholders who didn't attend.

Format:
1. **Overall status** — one word (Green / Yellow / Red) and one sentence explaining it.
2. **Progress** — 2–4 bullets of concrete things completed or moved forward.
3. **Blockers** — each blocker on its own line: Blocker | Who owns resolution | By when. If none, write "None."
4. **Watch items** — risks that aren't blockers yet but need monitoring.

Factual only. Don't restate what people are working on — only what moved.

Standup notes: [PASTE STANDUP NOTES]

Screen the resume below against the job spec and give me a structured summary.

Job spec: [PASTE JOB SPEC]
Resume: [PASTE RESUME]

Format:
- Overall fit: Strong / Possible / Weak (one line of reasoning)
- Matches: bullets of where they meet the spec directly
- Gaps: bullets of missing requirements — be honest, don't soften
- One question worth asking them on a call

Don't invent qualifications. If something is ambiguous, say so rather than guessing.

Convert my raw interview notes into a structured debrief for sharing with the hiring team.

Candidate: [NAME]
Role: [JOB TITLE]
Interviewer: [YOUR NAME]
Notes: [PASTE RAW NOTES]

Output format:
- Headline: one sentence on overall impression.
- Strengths observed (bullets)
- Concerns or gaps (bullets)
- Standout moment: one specific exchange worth sharing
- Recommendation: Advance / Hold / Pass — with one line of reasoning

Only use what's in my notes. Don't soften concerns to be polite.

Compare [NUMBER] final-round candidates for the role of [JOB TITLE] and give the hiring team a clear summary to inform their decision.

For each candidate, I'll give you notes. Produce:
- A comparison table with the key criteria as columns and candidates as rows.
- Under the table, a one-paragraph "case for" each candidate — genuine strengths only, no padding.
- A section on key tradeoffs the team should discuss.
- Do not make a hire recommendation — leave the decision to the team.

Evaluation criteria: [LIST CRITERIA]
Candidate notes: [PASTE NOTES FOR EACH CANDIDATE]

You are an experienced curriculum designer. Generate a [NUMBER] question reading comprehension quiz based on the text below.

Grade level: [GRADE LEVEL]
Mix of difficulty:
- [NUMBER] recall questions (directly stated in the text)
- [NUMBER] inference questions (require reading between the lines)
- [NUMBER] synthesis or opinion question (requires connecting the text to a broader idea)

Format each question as:
Q[N]: [Question]
Type: Recall / Inference / Synthesis
Sample answer: [One correct answer in 1–2 sentences]

Text: [PASTE TEXT]

Rewrite the article below for [GRADE LEVEL] students reading at approximately a [READING LEVEL, e.g. 5th-grade] level.

Rules:
- Replace all jargon and academic vocabulary with simpler synonyms. If a key term must stay, define it in parentheses the first time.
- Use short sentences (under 20 words average).
- Keep the article's core argument and all factual claims intact — do not simplify to the point of distortion.
- Match the original structure: same main sections, same order.
- Target length: [WORD COUNT] words.

Original article: [PASTE ARTICLE]

You are a curriculum specialist. Create a grading rubric for the assignment described below.

Assignment: [PASTE ASSIGNMENT PROMPT OR DESCRIPTION]
Grade level: [GRADE LEVEL]
Point total: [TOTAL POINTS]
Number of criteria: [NUMBER, e.g. 4]

For each criterion:
- Name the criterion.
- Write descriptors for 4 performance levels: Excellent, Proficient, Developing, Beginning.
- Assign point values that add up to the total.

Keep descriptors specific and behavior-based, not vague ("uses three pieces of textual evidence" not "supports ideas well").

You are helping a [GRADE LEVEL] teacher write report card narrative comments. For each student below, write a comment that is:
- 50–75 words
- Specific (names a skill, behavior, or example — never generic)
- Positive in tone overall, with growth area framed as forward-looking
- Written in third person ("She / He / They")
- Free of jargon and grade-level codes

Student notes (one per line, separated by "---"):
[PASTE STUDENT NOTES IN FORMAT: Name | Strengths | Growth area | Any specific detail]

Generate one comment per student in the same order.

I teach [GRADE LEVEL / SUBJECT] and I need to explain [CONCEPT] to students. Give me three different explanations:

1. Simple analogy: Explain it using something students this age encounter every day. No technical vocabulary.
2. Worked example: Walk through one concrete example step by step, as if talking to a student who is stuck.
3. Common misconception: Name the most frequent way students misunderstand this concept and explain why the wrong mental model fails.

Keep each explanation under 100 words. Plain language throughout.

Summarize the staff meeting notes below into a clean, actionable recap.

Format:
- Decisions made: (bullet list of anything that was resolved or approved)
- Action items: (bullet list in format — [WHO]: [WHAT] by [DATE or "TBD"])
- Open questions: (anything raised but not resolved — with owner if assigned)
- Next meeting: (date/time if mentioned)

Do not add anything not in the notes. Keep it to one page.

Raw notes: [PASTE MEETING NOTES]

You are a graduate teaching assistant who is expert at organizing disorganized notes. I will paste my raw lecture notes from class. Produce a clean summary in this structure:
- Main topic (one sentence)
- Core ideas (3–5 bullets, each one standalone)
- Key terms and their definitions
- One thing that is likely to appear on an exam

Do not add information not present in my notes. Flag anything unclear with "[unclear]" so I know to follow up.

My notes: [PASTE NOTES HERE]

Act as a research methods tutor. I will give you the abstract and any sections I paste from a research paper. Summarize it using this structure:
1. Research question (one sentence)
2. Method (what they did, how many participants or data points)
3. Key findings (bullets, with numbers if they appear)
4. Limitations the authors mention
5. One sentence on why this paper matters

Do not interpret or add analysis. Use plain language I can explain to a classmate.

Paper excerpt: [PASTE ABSTRACT + KEY SECTIONS]

You are a study skills coach. I will paste my course syllabus or class notes for [COURSE NAME]. Build a one-page study guide organized by exam-ready topic clusters (not by date or lecture order).

For each cluster:
- Topic name
- Core concepts to know (bullets)
- Likely exam question type (recall, apply, compare)

Group related ideas together even if they appeared in different weeks. Flag gaps where I should re-read.

Material: [PASTE SYLLABUS / NOTES]

Act as a test-prep tutor for [SUBJECT]. I will paste my notes. Generate flashcards in Q&A format following these rules:
- One idea per card. No compound questions.
- Questions test understanding, not just memorization (prefer "explain," "compare," or "give an example of").
- Keep each answer under 40 words.
- Generate at least 15 cards.
- Format: Q: ... / A: ...

Notes: [PASTE NOTES]

Explain [CONCEPT] to me as if I understand basic [RELATED FIELD] but have not studied this topic before. Structure your explanation as:
1. Plain-language definition (2–3 sentences, no jargon)
2. A concrete real-world analogy
3. The most common misconception students have about this concept
4. One check question I can answer to test my own understanding

Keep the total response under 200 words.

Help my group plan and divide a class project. Turn the brief below into a clear work plan.

Project brief: [PASTE ASSIGNMENT DESCRIPTION]
Due date: [DATE]
Number of group members: [NUMBER]
Any known constraints: [MEMBER AVAILABILITY / TOOLS / RESTRICTIONS]

Produce:
1. A task breakdown (every deliverable the assignment requires)
2. Suggested owner per task (use "Member A, B, C…" as placeholders)
3. A week-by-week timeline working backward from the due date
4. One integration checkpoint where the full group reviews progress together