28% of employed US adults already use ChatGPT at work. Most of them are getting mediocre results from their ChatGPT prompts at work and don't know why.

The problem isn't the tool. The problem is that people treat ChatGPT like a magic 8-ball. You shake it, type something vague, and wonder why it comes back with corporate word soup that sounds like it was written by a LinkedIn bot having a fever dream.

It's not magic. It's more like a very fast, very confident intern who has read everything on the internet and has zero idea what you actually need unless you tell them. Specifically. With context.

This guide gives you real prompts for real work tasks: emails, reports, presentations, meeting summaries. Copy them, tweak them, use them today. No $997 course required.

Why your ChatGPT prompts at work aren't working

The most common prompt people write is something like: "Write me an email about the project update."

That's it. That's the whole thing.

ChatGPT will write you something. It will be grammatically fine and completely generic. It won't know your tone, your audience, your relationship with the recipient, or what you actually need the email to accomplish. It'll sound like it was written by someone who has never met you, your boss, or your company. Because it was.

The output matches the input. Garbage in, garbage out. This is Rule #13 in Don't Replace Me, and it's the one people skip because they assume the AI will just figure it out.

It won't. You need to give it four things: a role, context, a task, and a format. Once you start doing that, the output gets dramatically better. Fast.

The smart intern framework: the only prompting method you need for ChatGPT at work

Think of ChatGPT as a smart intern. Not a genius. Not a mind reader. A fast, capable person who needs clear instructions and knows nothing about your specific situation unless you explain it.

Here's the structure:

Role: What kind of expert should it be right now? Context: What's the situation? Who's involved? What matters here? Task: What do you actually want it to produce? Format: How should the output look? Bullet points? A draft email? Three options?

This isn't complicated. It takes 30 extra seconds to write a better prompt, and it saves you five minutes of editing garbage output afterward.

Here's what the same email request looks like with this framework applied:

"You're a professional business writer who understands corporate communication. I'm a project manager writing to my VP. Our software launch got delayed by two weeks due to a vendor issue. I need to update her without making the team look incompetent. Write a short email, two to three paragraphs, that's direct, takes ownership, and ends with the revised timeline and next steps."

That prompt gets you something you might actually send.

Prompt templates for emails you write every week

Stop starting from scratch. Here are copy-paste templates for the emails that eat your time.

The "bad news" email

"You're a professional communicator. I'm a [your role] writing to [recipient and their relationship to you]. I need to share [the bad news] without being defensive. The context is [brief background]. Write a direct email that acknowledges the issue, gives the key facts, and ends with what happens next. Keep it under 200 words."

The follow-up that doesn't sound desperate

"I sent a proposal to [type of person] two weeks ago. No response. Write a follow-up email that assumes they're busy (not ignoring me), references the original proposal briefly, and asks for a simple yes or a good time to talk. Tone: friendly, professional, not needy. Under 100 words."

The meeting recap nobody asked for but everyone needs

"Here are my rough notes from today's meeting: [paste notes]. Turn these into a clean recap with three sections: decisions made, action items with owners, and open questions. Use bullet points. Be concise."

You can adapt any of these. The structure does the work.

This came from a book.

Don't Replace Me

200+ pages. 24 chapters. The honest version of what AI means for your career, written by someone who actually builds this stuff.

Get the Book →

Prompt templates for reports and documents

Reports are where most people waste the most time. The writing itself rarely takes long. It's the organizing, the formatting, the figuring out how to say something without sounding like you're hedging everything into oblivion.

ChatGPT is genuinely useful here, because structure is exactly what it's good at.

Turn bullet points into a structured report section

"I have rough notes on [topic]. Turn them into a professional report section with a short intro paragraph, three to four key points with one sentence of context each, and a brief summary. Tone should be clear and confident, not overly formal. Here are the notes: [paste notes]."

Executive summary from a long document

"Read this document and write a four-sentence executive summary for a senior audience who won't read the full thing. Focus on: what the situation is, what we found, what we recommend, and what happens if we do nothing. [Paste document or key sections]."

This works. The broader guide to using AI at work has more on how to build this into a regular workflow, not just one-off tasks.

First draft from an outline

"Here's an outline for a [type of document]. Write a first draft that I can edit. Write in a clear, direct style, not academic or formal. Assume the reader is a smart professional with limited time. [Paste outline]."

You edit. ChatGPT drafts. That's the division of labor that actually saves time.

Prompt templates for presentations

Most presentations are too long, too vague, and built around what the presenter knows rather than what the audience needs to decide or understand. ChatGPT can help you fix that, if you tell it what you're trying to accomplish.

Structure a presentation from scratch

"I need to present [topic] to [audience]. The goal of this presentation is to [specific outcome: get approval, share findings, explain a decision, etc.]. I have [X] minutes. Give me a slide-by-slide outline with a one-sentence description of what each slide accomplishes and what goes on it. Don't just list topics. Each slide should do a specific job."

Turn a data point into a story

"I have this data point: [statistic or finding]. I need to explain why this matters to an audience of [who they are]. Write three to four sentences that turn this number into a clear, compelling point. Not dramatic. Just clear."

Speaker notes for a slide

"Here's what's on my slide: [paste slide content]. Write 60 to 90 seconds of speaker notes that explain what this slide means in plain language. Don't just read the bullet points. Assume I'll be talking to real people who need context, not a script."

The double tap: why you can't skip verification

Here's the thing nobody in the "AI will save you hours every day" camp leads with: ChatGPT lies. Confidently. Smoothly. With specific-sounding details that are just wrong.

It will cite a statistic that doesn't exist. It will invent a quote. It will give you a legal interpretation that sounds plausible and is completely off. It once told a lawyer that six court cases were relevant to his case. None of them existed.

The author behind this site calls this the Double Tap: before anything leaves your hands, you check the work. Every claim that can be verified should be verified. Every number should have a source you actually looked at. Every recommendation that matters to someone else should get a second look.

This isn't about not trusting AI. It's about not trusting any single source without checking it. If an intern handed you a report, you'd read it before you sent it up the chain. Same rule applies here.

The check doesn't need to be exhaustive. It needs to be proportional to the stakes. Quick email to a colleague? Skim it. Report going to your board? Read every sentence.

If you're still figuring out where AI ends and your judgment begins, the article on what AI can and can't actually do is worth five minutes.

What to do when the output is bad

ChatGPT has an aggravating habit. If you push back, it agrees with you. Completely. Enthusiastically. And then gives you something only slightly different that's still wrong.

Don't accept its apologies. Diagnose the actual problem.

If the output is too generic, you didn't give it enough context. Add more. Specifics about your audience, your tone, your relationship with the reader.

If the tone is off, tell it explicitly. "This sounds too formal. Rewrite it the way I'd talk to a colleague I've worked with for two years." Or: "This sounds too casual. Make it more professional without being stiff."

If it's missing the point, your task instruction was probably unclear. Break it down. Tell it the one thing the output needs to accomplish. Not everything it could accomplish. The one thing.

If you've edited it twice and it's still not right, just write the damn thing yourself. Sometimes the fastest path is the direct one. AI is a tool, not a replacement for your judgment. That's the whole point. For people wondering about building real AI fluency without going back to school, the guide to AI skills for non-technical people lays out exactly what's worth learning and what's filler.

The only setup that actually matters

You don't need a paid tier to start. The free version of ChatGPT handles everything in this guide. You don't need plug-ins, extensions, or a custom GPT built by someone selling a course.

What you do need is a habit. Pick one task you do every week that involves writing. One. Apply the smart intern framework to that task for two weeks. See what happens.

That's it. That's the full onboarding.

Once you're consistently getting good output on that one thing, expand. Add another task. Your prompts will get better because you'll start noticing what information ChatGPT needs to do good work versus what you left out.

AI is just your keyboard now. You don't take a masterclass on keyboards. You type, you figure out what works, you keep going.


Frequently asked questions

What's the best way to prompt ChatGPT for work emails?

Use the role-context-task-format structure. Tell ChatGPT who it is (a professional business writer), what the situation is (the specific context and relationship), what you need (the actual email), and how you want it formatted (length, tone, structure). Generic prompts produce generic output.

Can I use ChatGPT at work without telling my boss?

68% of employees who use AI at work don't tell their employer. Whether you should disclose depends on your company policy and what you're using it for. The full breakdown is in the guide on whether to tell your boss you use AI.

How do I stop ChatGPT from writing in that stiff, corporate tone?

Tell it explicitly. Add to your prompt: "Write this the way a confident professional would explain it to a colleague, not the way a consultant writes a white paper." Or give it a sample of your own writing and say "Match this tone." Specific tone instructions work better than vague ones like "make it natural."

Is the free version of ChatGPT good enough for work tasks?

For most work tasks, yes. Writing, editing, summarizing, structuring documents: the free tier handles all of it. The paid version gives you faster responses and access to more recent information, but it's not necessary to get started or to do the tasks in this guide.

What should I always check before sending AI-written work?

Any specific fact, statistic, or number. Any name, date, or reference to a real document. Any recommendation with legal, financial, or HR implications. The AI will sound confident even when it's wrong. Verification is proportional to stakes: quick email gets a skim, board presentation gets a full read.

Do I need to learn prompt engineering to use ChatGPT effectively at work?

No. The prompt engineering course industry is largely built on making something simple sound complicated. The role-context-task-format framework in this article is enough for 95% of work tasks. You don't need a certificate. You need to practice on real things.