A useful prompt for a report or email has six parts: the role you want the tool to play, the task, the context, the audience, the format, and the limits. Write each part in a sentence or two, paste in your own notes, and ask the tool to list anything it had to assume. This makes drafts much less generic.
This article gives you that structure as a template you can reuse, then walks through one example from start to finish. It works the same way in ChatGPT, Gemini, Claude, Copilot or any similar assistant. It does not cover prompts for images, code or data analysis.
Why do AI drafts of reports and emails sound so generic?
Usually because the prompt was too short. “Write an email to my manager about the project” gives the tool almost nothing to work with, so it fills the gaps with safe, general language.
The tool does not know your project, your manager, your company’s tone or what happened last week. Everything it does not know, it either guesses or leaves vague. The fix is not a clever trick. It is giving the tool the same briefing you would give a new colleague who is drafting on your behalf.
What are the six parts of a good work prompt?
Role, task, context, audience, format and limits. Each one answers a question the tool would otherwise have to guess.
- Role. Who should the tool write as? For example, “a project coordinator writing to a senior manager”.
- Task. What exactly do you need? “Draft a weekly status email” is clearer than “help with an update”.
- Context. What is going on? Paste your rough notes, the facts, decisions made and anything still open.
- Audience. Who will read it, what do they already know, and what do they need to do after reading?
- Format. Length, structure and tone. “Under 200 words, three short sections, plain and polite.”
- Limits. What must the tool not do? “Do not add facts that are not in my notes. Do not promise dates.”
End with one more line: ask the tool to list its assumptions and any questions. This turns hidden guesses into a short list you can check.
What does the reusable template look like?
Copy the block below into a note on your phone or laptop. Replace each line in angle brackets with your own details, and delete any line that does not apply.
ROLE: You are <who is writing, and their job>.
TASK: Draft <the document: email, report section, summary> about <topic>.
CONTEXT: Here are my notes. Use only these facts.
<paste your rough notes, bullet points or the source text>
AUDIENCE: This is for <reader>. They already know <what they know>.
After reading, they need to <decision or action>.
FORMAT: <length>, <structure, e.g. subject line + 3 short paragraphs>,
<tone, e.g. plain, polite, no jargon>. Use Indian English spelling.
LIMITS: Do not add facts, figures or names that are not in my notes.
Do not make promises or commitments on my behalf.
AFTER THE DRAFT: List any assumptions you made and any questions
I should answer before sending.The “Use only these facts” and “Do not add facts” lines matter most. They keep the draft tied to your notes, which makes it much easier to check.
How does the template work on a real task?
Here is a worked example: a weekly project update email to a manager. The notes are rough on purpose, because that is how most of us write them.
ROLE: You are a project coordinator in a small company, writing to
the head of operations.
TASK: Draft this week's status email about the new website project.
CONTEXT: Here are my notes. Use only these facts.
- Homepage design approved by marketing this week
- Product pages built, now in internal testing
- Checkout page blocked: still waiting for payment gateway
login details from the vendor
- Testing of checkout can only start after we get those details
- Need a decision: should I escalate to the vendor's account manager?
AUDIENCE: This is for the head of operations. She knows the project
but not the day-to-day detail. After reading, she needs to decide
whether I should escalate the vendor delay.
FORMAT: Subject line plus under 180 words. Three short sections:
Done, Blocked, Decision needed. Plain and polite, no jargon.
Use Indian English spelling.
LIMITS: Do not add dates, numbers or names that are not in my notes.
Do not say the project is on track or delayed overall.
AFTER THE DRAFT: List any assumptions you made and any questions
I should answer before sending.A good draft from this prompt would have a clear subject line, three labelled sections and a single, direct question at the end asking whether to escalate. It would not mention a launch date, because none was given.
If the tool adds something you did not supply, such as a deadline or a reason for the vendor delay, that is your signal to delete it or correct it. The assumptions list at the end can help you spot these gaps, but read the draft yourself as well.
How do you improve the draft without starting again?
Reply with one specific change at a time. Short, targeted follow-ups work better than rewriting the whole prompt.
Useful follow-ups:
- “Make the Decision needed section one sentence.”
- “The tone is too formal. Make it sound like a colleague, not a letter.”
- “Remove anything that is not in my notes.”
- “Give me two subject line options under eight words.”
When the draft is close, stop prompting and edit it yourself. The final polish is usually faster by hand.
Does the same structure work for longer reports?
Yes, with one change: work section by section. Ask for an outline first, agree on it, then draft one section at a time using the same six parts.
For a longer report:
- Use the template to ask for an outline only, with one line on what each section will cover.
- Edit the outline yourself until the order and scope are right.
- Draft each section with its own context: paste only the notes relevant to that section.
- Ask for a short summary at the top only after the sections are done, so it reflects what you actually wrote.
This keeps each prompt focused and makes checking manageable.
Try it: Take the last email you wrote that took more than ten minutes. Rewrite your request using the six-part template, run it, and compare the draft with what you actually sent. Note which of the six parts made the biggest difference.
What should you never put in the prompt?
Anything your company or your customers would not want shared outside the organisation, unless your employer has approved the tool for that use. That includes customer personal details, passwords, unreleased financials and confidential contracts.
Replace names with roles (“the vendor”, “Client A”) and remove identifying details before you paste notes. The draft will still work. For team-level rules, read Keeping company data safe when your team uses AI tools.
What to do next
Save the template, then use it on one real email or report section this week. Before you send the result, run through Checking AI output before you send it. If you want to build these habits with feedback from a trainer, see the programmes for working professionals on the learn page.