Skip to content
4 min fix 4 min read Recently reviewedBeginner
Quick Answer

Always include Context, Expectation, and Format. Instead of 'Write an email about the delay', use 'Act as a project manager (Context). Draft a polite email to the client explaining the website launch is delayed to Tuesday (Expectation) in 3 short bullet points (Format).'

How to Write Effective AI Prompts for Office Work

Applies to: Microsoft Copilot, ChatGPT, Google Gemini, Claude
Article Type: How-To
Last Updated: 2026-07-10

Summary

If you type "Write an email about the new project" into an AI tool, you will get a generic, robotic-sounding email that you have to rewrite anyway. To get great results from AI, you have to write great prompts. This guide teaches the "CREATE" framework for writing prompts that actually save you time.

Prerequisites

  • Access to an AI tool (like Microsoft Copilot, ChatGPT, etc.)
  • A specific task you want the AI to help with

Instructions

1. Stop Treating AI Like a Search Engine

When you use Google, you type keywords: Q3 marketing budget template.

When you use AI, you need to talk to it like a very smart intern who started their first day at the company. The intern has the skills, but they need context, instructions, and boundaries.

2. Use the 4-Part Prompt Framework

A highly effective prompt has four parts: Goal, Context, Format, and Tone.

  1. Goal (The Action): What exactly do you want it to do?
    • Bad: "Email about the meeting."
    • Good: "Write a follow-up email to the client summarizing our meeting and asking for their approval on the budget."
  2. Context (The Background): What does the AI need to know to do the job?
    • Add: "The client's name is Sarah. She was hesitant about the timeline, so we agreed to deliver Phase 1 two weeks early."
  3. Format (The Output): How do you want it to look?
    • Add: "Use bullet points for the summary and keep the whole email under 150 words."
  4. Tone (The Personality): How should it sound?
    • Add: "Keep the tone professional but warm and appreciative."

3. Put It All Together

Before (The bad prompt):

"Write an email about the meeting with Sarah."

After (The effective prompt):

"Write a follow-up email to our client, Sarah, summarizing our meeting. The goal is to get her approval on the budget. (Goal) She was hesitant about the timeline, so mention that we agreed to deliver Phase 1 two weeks early. (Context) Keep the email under 150 words and use a bulleted list for the next steps. (Format) The tone should be professional but warm and appreciative. (Tone)"

4. Provide Examples (Zero-Shot vs. Few-Shot)

If you have a specific style in mind, show the AI what you want.

  • Zero-shot: Asking the AI to do something without giving examples. (e.g., "Write a catchy headline for a newsletter.")
  • Few-shot: Giving the AI examples of what success looks like. (e.g., "Write a catchy headline for a newsletter. Here are three examples of past headlines we liked: 1. [Example], 2. [Example], 3. [Example].")

Providing examples dramatically improves the quality of the AI's output.

5. Iterate and Refine (Don't Accept the First Draft)

Rarely is the first answer perfect. You don't have to start over — tell the AI what to fix in the next message.

  • "That's too formal. Make it sound more conversational."
  • "You forgot to include the deadline. Add November 15th."
  • "Cut the length in half and remove the introductory paragraph."

Troubleshooting

TIP

If you're using Microsoft Copilot to write about internal data, use the forward slash (/) in the chat box to search for and attach specific files or emails as context.

Symptom / ErrorPotential CauseSolution
Output sounds like a robot wrote itMissing tone instructionsTell the AI the exact tone you want (e.g., "Write at an 8th-grade reading level," or "Use a casual, enthusiastic tone.")
Output is way too longMissing format constraintsSpecify "under 200 words," "in three paragraphs," or "summarize in 5 bullet points."
AI makes up facts (hallucinates)Missing contextPaste the exact facts, numbers, or document text into the prompt so it doesn't have to guess.
It completely misunderstood the requestPrompt was too vagueBreak the task down. "First, summarize this text. Next, pull out the action items."