40+ Practical ChatGPT Prompts for Real Work in 2026

By Lei Jin · 2026-10-08

There are thousands of "act as a whatever" prompt lists online. Almost none survive contact with real work, because the prompts tell the model what costume to wear instead of giving it the information it needs.

This collection goes the other way: every prompt here includes the three things that make ChatGPT output usable — context, task and output format. Replace the bracketed text with your own material. For alternatives, see the chat tools directory and the full ChatGPT review.

The structure behind every good prompt

A reliable work prompt has four parts:

Role/context (one line) — what you are and what you're trying to do.
Input material — the actual email, document, data or notes, pasted in.
Task — what specifically to do, including what "good" means.
Format — length, structure, tone, audience.

The single biggest upgrade: paste the real material. An answer about "my client situation" is generic; an answer about the forwarded email below is specific.

Email and communication

Reply to a difficult email

I'm a [role] at a small company. A client sent the email below. They are upset
because [what actually happened, one sentence].
I want to keep the relationship, acknowledge the issue honestly, and propose
[your intended solution] without admitting legal fault.
Draft a reply under 150 words, warm but professional, ending with a concrete
next step. Here is the email:
[paste email]

Cold outreach that doesn't sound like spam

Write a 90-word cold email to [specific type of person, e.g. operations leads
at mid-sized clinics] offering [service]. The hook must reference a problem
they actually have: [problem]. One clear question at the end, no calendar link,
no "I hope this finds you well". Write it as a plain human email.

Politely chase an unanswered message

I emailed [person] five days ago asking for [thing]. They may simply be busy.
Write a two-sentence follow-up that makes replying easy: restate the ask, give
a default option they can approve with one word, and don't guilt-trip them.

Ask for a raise or rate increase

I've been in my role for [time]. In that period I [two or three concrete
results with numbers]. Market rate for this role is around [range].
Write a short, confident message to my manager requesting a conversation
about compensation. Focus on delivered value, not tenure or need.

Deliver bad news upward

I need to tell my manager that [problem] will cause [consequence] by [date].
The cause was [honest cause, including my part]. I have two recovery options:
[option A with cost] and [option B with cost]. Write a message that leads with
the situation, takes ownership, and presents options rather than just the
problem.

Decline an invitation gracefully

I can't accept [invitation] because [reason I'm comfortable sharing]. Write a
three-sentence decline: genuinely thank them, be clear (not "maybe"), and keep
the door open for [specific future thing].

Writing and editing

Rewrite in your own voice

Rewrite the text below, but first study these two samples of my writing:
[sample 1]
[sample 2]
Match their sentence length, directness and vocabulary. Keep every fact from
the original; change only the style. Text:
[paste text]

Cut a draft that is too long

The text below must fit in [word limit] for [audience/channel]. Cut it without
losing: the main claim, the three supporting points, and the final ask. Remove
repetition and filler; mark anything you cut that I should double-check.
Text:
[paste text]

Make complex writing clear

Explain the passage below so an intelligent reader with no background in
[field] can understand it. Keep every important nuance — do not oversimplify
into falsehood. Use short sentences and one concrete analogy. Passage:
[paste text]

Edit for non-native English

I'm a non-native English speaker. Correct the grammar in the text below, then
list the three most important error patterns you fixed so I can learn them.
Don't rewrite my personality out of it. Text:
[paste text]

Beat blank-page fear

I need to write a [document type] for [audience] that gets them to [outcome].
I have these rough notes and fragments:
[notes]
Turn them into a structured outline with a one-line summary of each section.
Do not write the full document yet — just the skeleton and three questions
where my notes are too thin.

Title and subject-line variants

Generate 10 titles for the piece below. Five clear and specific, three
contrarian or provocative, two emotionally resonant. Under 60 characters
each, no clickbait promises the piece doesn't deliver. Then mark the one you'd
click and why. Piece:
[paste text]

Convert features into benefits

Here is a list of product features: [list]. For each, write the concrete
benefit for a [target customer], phrased in their language, as one sentence.
Then rank the top three benefits worth leading with.

Summaries and meetings

Summarize with decisions and actions

Below is a meeting transcript. Produce:
1. A 5-bullet summary
2. Every decision made
3. Every action item with owner and deadline
4. Open questions nobody resolved
If owners or deadlines are missing, mark them explicitly rather than guessing.
Transcript:
[paste transcript]

Digest a long report

Read the document below and give me: the central argument, the key evidence,
where the author is weakest or most speculative, and what would change my
behavior if I trusted it. Document:
[paste document]

Turn notes into a status update

Convert my rough weekly notes into a Friday status update with three sections:
shipped, in progress with expected date, and blockers where I need help. Be
specific where my notes are specific; write "needs detail" where they aren't.
Notes:
[notes]

Pre-read a paper or article critically

Summarize this paper for a working professional: the question, method in plain
language, findings, limitations the authors admit, and limitations they may
not. End with three questions I should ask before citing it. Paper:
[paste]

Analysis, data and spreadsheets

Build a spreadsheet model

I want to model [decision, e.g. hiring two people vs contractors over 12 months].
List every input assumption I need to decide, give reasonable starting values
clearly labeled as assumptions, and write the formulas as spreadsheet columns.
Show the result as a small table and tell me which assumption the outcome is
most sensitive to.

Explain and fix spreadsheet formulas

Explain what this spreadsheet formula does in plain English, step by step, then
rewrite it more robustly: [formula]. The data can contain blanks and text; it
must not error on those.

Analyze pasted tabular data

Here is data exported as CSV: [paste]. First describe its shape and any obvious
data-quality issues. Then calculate [specific question] and explain the result
in two sentences a non-analyst will understand. Suggest one chart that shows
this clearly.

Decision framework

I'm deciding between [option A] and [option B]. My priorities, in order, are:
[priorities with rough weights]. Build a comparison table scoring both options
against each priority. Where you don't have information, leave the cell as a
question for me instead of inventing a score.

Turn rough numbers into a sanity check

I heard this claim: [claim]. Using only rough order-of-magnitude estimates,
walk me through whether it's plausible. State each assumption, do the
arithmetic, and give a confidence level.

Coding

Explain unfamiliar code

Explain what this code does at a high level first, then walk through the tricky
parts. I know [language/level]. Flag anything that looks like a bug or a
security issue. Code:
[paste code]

Refactor with constraints

Refactor the code below for readability. Constraints: don't change behavior,
don't add dependencies, keep functions under 30 lines. Show the result and a
short diff-style list of what changed and why. Code:
[paste code]

Debug from an error

This code produces this error: [error]. Here is the relevant code: [code].
Before suggesting fixes, list the possible causes in order of likelihood,
including errors in my assumptions. Then give the simplest fix for the most
likely cause and how to verify it.

Write tests

Write tests for the function below covering: normal case, edge cases (empty,
zero, null, very large), and failure cases. Use [testing framework]. For each
test add a one-line comment on what it protects against. Code:
[paste]

Regular expressions made safe

I need a regex that [goal] for inputs like [examples]. Write it, explain each
piece, and show three inputs where it fails so I know its limits.

Script a one-off task

Write a [language] script that [one-off task]. It will run once on my own
machine on files in [folder]. Optimize for clarity and safety: dry-run by
default, no destructive action without an explicit flag, and comments
explaining each step.

Planning and brainstorming

Critique my plan

Here is my plan for [goal]: [plan]. Act as a skeptical operator who has run
similar projects. Find the three biggest risks, the assumptions I haven't
tested, and the fastest cheap experiment to test the riskiest one.

Break a project into tasks

Break this project into a sequenced task list: [project]. For each task give an
estimate in hours, what can be done in parallel, and the one task whose failure
would block everything. Group them into week-sized chunks.

Brainstorm, then converge

I need ideas for [challenge]. Give 15 ideas: five conventional done well, five
unconventional, five that sound absurd but contain a useful kernel. Then take
the three strongest and note their main drawback each.

Prepare for a hard conversation or interview

I have a [meeting/interview] about [topic]. The other person cares about [their
likely priorities]. List the 8 hardest questions I could face. For each, give a
short strong answer framework, not a script. Mark the two questions I'm most
likely to answer badly.

Weekly personal planning

Here are all my current commitments and loose ends: [list]. Help me plan the
coming week: identify the three things that actually move my goals, what can be
delegated or dropped, and a realistic Monday plan. I have about [hours]
available.

Learning

Learn by doing

I want to learn [topic]. I already know [existing knowledge]. Create a
two-week plan where each day ends with something I build or produce, not just
reading. Include one realistic project and the exact points where learners
usually get stuck.

Socratic coaching

Teach me [concept] by asking me questions. Start one level above my current
understanding ([describe it]). Only give the answer when I'm clearly stuck,
and correct misconceptions directly.

Explain at multiple levels

Explain [topic] in four versions: to a child, to a teenager, to a competent
adult, and to someone in the field. Use a different analogy each time; don't
just add jargon.

Mistakes to avoid

No real input. "Write a sales email" produces a template. Pasting the thread produces a weapon.
Asking for five things at once. Split complex jobs into sequential prompts; use the output of each as the input of the next.
Vague quality words. "Make it better" is unusable. Better means shorter? more persuasive? for whom?
Trusting confident answers. ChatGPT invents specifics — names, numbers, citations — with the same tone as facts. Verify anything that matters; use Perplexity when you need sourced claims.
Skipping the format. Without a stated format, answers default to medium-length essays. Asking for a table, five bullets or 90 words changes the work itself.

FAQ

Do I still need these prompts if I use the latest ChatGPT model?

More capable models need less hand-holding on how to answer, but they still can't know context you don't provide. The context and input-material parts of these prompts remain the difference-maker in 2026; only the explicit instructions get shorter.

What about custom instructions and saved prompts?

Put durable preferences (your role, industry, writing style, formatting defaults) in custom instructions so you never repeat them. Save prompts you run weekly — status updates, meeting summaries — as reusable templates and just swap the input.

Are these prompts safe for confidential information?

Treat anything you paste as exposed unless your contract says otherwise. For sensitive material, remove identifying details, use summaries instead of raw documents, or rely on a plan with enterprise data terms.