Lessons
1 · Understanding Modern AI
2 · Talking to AI Effectively
3 · AI for Learning
4 · AI for Work and Productivity
5 · AI for Developers
- 17AI Coding Assistants: Modes, Strengths and Your Responsibility
- 18Use AI to Understand Code, Codebases, APIs and Documentation
- 19How to Use AI to Debug Code Safely
- 20Testing, Reviewing and Refactoring AI-Generated Code
- 21Security and Licensing Risks of AI-Generated Code
- 22Vibe Coding vs Responsible AI-Assisted Building
6 · AI for Career Growth
7 · Research, Verification and Responsible AI
8 · Automation and AI Agents
Lesson 13 · AI for Work and Productivity
How to Use AI for Emails and Documents Without Losing Your Voice
AI can draft, tighten and restructure workplace writing in seconds, but it can also invent commitments and make everything sound like everyone else. This article gives a facts-first drafting workflow, ways to keep your own voice, and a checklist to run before you hit send.
For
Working professionals, students and freelancers who write a lot of emails, reports and documents and want to save time without losing accuracy or personality.
Level
Before you start
Read Prompt Fundamentals (article 6) and Give AI the Right Context (article 7).
On this page
Key takeaways
- Start with your facts, not the assistant's. Give it the points, the audience and the ask, and tell it not to add facts, dates or commitments.
- The riskiest things in an AI draft are invented specifics and promises. Check every name, date, number and commitment against your own notes before sending.
- To keep your voice, show it samples of your own writing and edit the result. Generic phrasing is a signal to rewrite, not to send.
- Write sensitive messages, such as conflict, bad news, legal and HR matters, yourself or with a person's review. Use AI for structure and wording options at most.
- You are accountable for what you send, whoever or whatever wrote the first draft. Use only tools your workplace allows for work content.
Most of us write more words at work than we would like to admit: replies, updates, requests, reports, proposals. A lot of this writing is routine, which is exactly why people turn to AI for it. Done well, you save time and your writing improves. Done badly, you send a message that promises something you never agreed to, or one so smooth and generic that the recipient stops reading.
The skill is knowing which parts to delegate and which to keep.
What you will learn
#- A facts-first workflow for AI-assisted writing.
- How to preserve your own voice.
- Typical tasks: replying, rewriting, shortening, structuring and proofreading.
- A pre-send checklist.
- When to write it yourself.
The idea in plain words: you supply the facts, it supplies the wording
#AI is strong at wording and structure and weak at knowing what is true in your situation. So split the work that way:
- You supply: facts, decisions, commitments, who the reader is, what you want.
- It supplies: sentences, order, tone options, shorter versions.
Problems arise when that split reverses: when you let the model decide what happened or what you will do, because it fills gaps with plausible-sounding material. Every invented deadline or promised discount comes from a gap you left in the prompt.
The facts-first workflow
#- Write your facts as rough bullets. Ugly is fine. Include what happened, what you decided, what you need, and by when.
- State the audience and the ask. Who is reading, what is your relationship, and what should they do after reading?
- Choose the tone and format. "Warm but direct, under 100 words, plain text, no greeting beyond the name."
- Add the guardrail. "Do not add any facts, dates, prices or promises that are not in my notes. If something is missing, ask me."
- Generate, then check. Compare every fact and commitment with your notes.
- Personalise. Add the sentence that only you would write.
- Send, and save the prompt if you will write this kind of message again.
A template:
Write a [email/message] to [name, role, relationship].What they should do after reading: [the ask].My facts, and only these: - [fact 1]- [fact 2]- [fact 3]Tone: [e.g. warm but direct]. Length: about [N] words. Format: [plain text].Do not add facts, dates, amounts or promises beyond the facts. If you needsomething I did not give, ask me first.A worked example: pushing back on a deadline
#Goal. Your manager has asked for a report by Wednesday. You can deliver it by Friday, and you want to say so without sounding unhelpful.
First attempt.
Write an email to my manager saying I need more time for the report.Example response (illustrative).
Dear Manager,I hope you are well. I am writing to let you know that I will need an extensionfor the report. I will ensure it is delivered at the earliest possible time.I apologise for any inconvenience.Best regardsWhat is wrong. It is vague ("an extension", "earliest possible time"), apologetic for no stated reason, and contains no information that helps your manager decide anything. A manager reading it has to write back to ask when, and why.
Improved request.
Write a short email to my manager, Anita, who asked for the Q3 sales reportby Wednesday. After reading she should either accept a Friday delivery or tellme what to drop.My facts, and only these:- I can deliver the full report by Friday 5 pm.- I can send the summary table and top three findings by Wednesday 5 pm, so she has something for her Thursday meeting.- Delay reason: two regional files arrived late, on Tuesday.- I am also working on the client deck, which is due Thursday.Tone: direct, respectful, no grovelling. Under 90 words. Plain text.Do not add any other facts or promises. If you need something, ask me first.Example response (illustrative).
Hi Anita,Two regional files arrived on Tuesday, so I can't finish the full Q3 report byWednesday. I can send you the summary table and the top three findings byWednesday 5 pm, ready for Thursday's meeting, and the full report by Friday5 pm. I'm also finishing the client deck due Thursday. If Friday doesn'twork, tell me what to put aside.Thanks,[Name]Check. Compare against your bullets: dates and times match, no extra promises were added ("ready for Thursday's meeting" was inferred from your note about her meeting, which you should confirm is accurate), and the closing question gives her a clear next step. You then change one phrase into your own words, and send.
The difference: the improved version carries decisions and options, because you provided the facts that make them possible.
Keeping your own voice
#AI-assisted writing tends to drift towards the middle: polite, balanced, slightly formal, using the same stock openings and closings. Readers notice. Some ways to avoid it:
- Show samples. Paste two or three emails you have written and liked, and say: "Match the tone and sentence length of these samples." This works much better than a vague adjective.
- Describe your style as rules. "I write short sentences. I use contractions. I do not use 'I hope this email finds you well'. I get to the point in the first line."
- Ban the clichés you dislike, by listing phrases to avoid.
- Edit the result. Change at least a few phrases into your own, add a specific detail only you know, and cut anything that sounds like a template.
- Read it aloud. If you would not say it, change it.
What to use it for
#Task | How to prompt | What to check |
|---|---|---|
Reply to a tricky email | Paste the email, then ask: "List what the sender is asking, in order. Then draft a reply using my decisions: [decisions]" | That every ask is answered, and your decisions are accurately stated |
Shorten | "Cut to 80 words without losing the date and the ask" | That the ask and the key facts survived |
Change tone | "Same content, more formal, for a senior client" | That the meaning has not shifted, and no hedge was added that weakens your point |
Structure a document | "Propose an outline for a one-page proposal for [audience], with a one-line purpose for each section" | Whether the order suits your argument |
Draft a section | "Write section 2 using only these notes: ..." | Facts, numbers, claims |
Proofread | "Correct spelling and grammar only. Show changes as a list. Do not change wording or meaning" | The change list for anything meaning-related |
Summarise a thread | "Summarise decisions, open questions and who owns each" | Compare with the thread |
Translate | "Translate to [language], keep the tone, and list any phrases you were unsure of" | Ask a fluent speaker for important messages. Idioms and politeness levels are easy to get wrong |
Documents: reports, proposals and policies
#Longer documents need more care, because errors are easier to hide in more words.
- Outline first. Ask for two outlines, choose or merge, and edit by hand.
- Write section by section, giving the facts for each section. Do not ask for a 10-page document in a single request.
- Treat all numbers and claims as unverified until you have traced each to a source. If the document will be read by others who rely on it, add a short "sources" list and verify it yourself.
- Run separate editing passes: one for clarity ("flag any sentence a new employee might not understand"), one for length ("which paragraphs can be cut with no loss?"), one for consistency ("list any term used in two different ways").
- Have a human review anything with legal, financial, safety or contractual effect. An AI draft of a contract or policy is not legal advice.
- Follow your organisation's norms on disclosure. Some require you to mention AI assistance in certain documents, and you remain responsible for the content.
When to write it yourself
#AI is a poor choice, or at best a minor helper, when:
- The message is emotionally sensitive: conflict, bad news, an apology, a resignation, feedback about a person. Your own words carry sincerity that a polished draft cannot.
- It has legal or HR consequences, such as warnings, terminations, contracts or complaints. Involve a qualified person.
- You do not know the facts yet. The assistant cannot find them for you.
- The content is confidential and you do not have an approved tool.
- The relationship is close. A colleague of ten years can tell.
Before you send: a checklist
#- Every name, title and company is correct.
- Every date, time, amount and number matches my notes.
- Every promise or commitment is one I actually intend to make.
- Nothing was added that I did not say or decide.
- The ask is clear, and the reader knows what to do next.
- The tone fits this reader and this relationship.
- It sounds like me.
- It does not contain confidential information the reader should not see.
Common mistakes
#- Sending the first draft. It is a draft.
- Leaving gaps in your facts, which the model fills with plausible invention.
- Using AI for sensitive messages because it is faster.
- Pasting entire email threads containing other people's private information into a tool you are not allowed to use.
- Over-polishing. A formal, flawless message to a friendly colleague can read as cold.
- Not noticing that tone changed meaning, for example a firm request softened into a suggestion.
Exercises
#Exercise 1
Facts-first prompt
#You must decline a speaking invitation because of a clash with another commitment, but you would like to be considered next time. Write the prompt using the template: facts, audience, ask, tone, guardrail.
Exercise 2: Find the invented commitment
#An assistant drafts: "I'll have the proposal to you by Monday and we can offer a 10 percent discount." Your notes say only that you will send a proposal sometime next week. What went wrong, and how would you fix the prompt and the draft?
Exercise 3: Voice
#Write three rules that describe your own writing style, suitable for pasting into a prompt, plus two phrases you never want to see.
Exercise 4: Decide whether to use AI
#For each, say whether you would use AI, partly use it or write it yourself, with one reason: (a) a message confirming a meeting time, (b) a message telling a team member their performance has been poor, (c) a one-page summary of a long report for your manager, (d) a message to a client about a contract dispute.
Show solutionHide solution
Write a short email to Neha Rao, an event organiser I have met once, decliningher invitation to speak on 14 November. After reading she should feel respectedand know I would like to be considered for a future event.My facts, and only these:- I have another commitment on 14 November that I cannot move.- I am interested in the topic.- I am available most of the first quarter of next year.Tone: warm and professional, not apologetic. Under 80 words. Plain text.Do not add facts, promises or dates beyond these. If something is missing, ask me.The guardrail line prevents the common slip of inventing a reason ("due to a family matter") or an offer ("I would love to speak next month").
Exercise 2
Show solutionHide solution
The assistant invented two things: a specific deadline (Monday) and a discount (10 percent), both commitments you did not make. The gaps in your prompt allowed it, or the instruction not to add facts was missing.
Fix the draft: replace the sentence with "I'll send you the proposal next week." Remove the discount unless you are authorised to offer one.
Fix the prompt: include the line "Do not add dates, prices, discounts or promises that are not in my facts", and supply the real timing. Then run the pre-send checklist again, because you have just seen what kind of error to look for.
Exercise 3
Show solutionHide solution
An example:
My style: short sentences; I use contractions; I start with the point, not withpleasantries.Never use: "I hope this email finds you well", "please do not hesitate tocontact me".Your rules should be specific and observable. "Professional but friendly" is too vague to act on. Re-read three emails you wrote, find what you actually do, and write that.
Exercise 4
Show solutionHide solution
(a) Write it yourself, or use AI trivially. It takes less time to write "Confirming Thursday 3 pm" than to prompt. (b) Write it yourself. It is sensitive and affects a person's work and feelings. If you want help, use AI only to rehearse the conversation or to check that your points are clear and fair, and involve HR if your organisation requires it. (c) Partly use it. A grounded summary is a good use of AI, with the source pasted in. Check numbers and claims against the report. (d) Write it yourself, with legal or managerial review. It has legal consequences, and nothing confidential should go into an unapproved tool.
The test: how bad is it if the message is wrong, impersonal, or leaks, and can I check it?
Where to go next
#- Next: Meetings, Notes and Long Documents: Summaries You Can Trust applies the facts-first idea to what you read and record.
- For the tone of your career writing, see Improve Your Resume and Profile with AI, Honestly.
- For more on writing work emails, see How to Write a Cover Letter and Job Application Email That Gets Replies.
Connected lessons
References
Linked from 5 guides
Other pages in the library that point here.
Keep reading
More in Technology →Guide · Technology
Writing Better AI Prompts: A Practical Guide
Guide · Technology
Machine Learning for Beginners: What It Is and How to Start Learning It
Course · Career
Off-Campus Placements With AI: From Zero to Offer

