Put the key message in the email itself, attach one file, and name that file so the reader knows what it is. Say what you need and by when in the first two lines. The attachment backs up the email and carries the detail.
A file with no explanation makes readers guess. They open it, search for the point, and sometimes miss it. This page shows how to write the body, name the file, pick a format and keep to one version.
Write the point first, in the body
Digital.gov's plain-language guide says to start by stating your purpose and the bottom line, and to put the most important information at the beginning. An email follows the same rule. Open with the action and the deadline. Put background below.
A university guide to inclusive email adds three habits. Use a clear subject line that describes the content. Break the message into short paragraphs. Keep each paragraph to one idea.
Before: Subject: Document. Body: "Hi, see attached." Attachment: scan0042.pdf.
After: Subject: June volunteer schedule, please check your shifts by Friday. Body: "Please check your shifts in the attached schedule (PDF, 1 page). If a shift does not work, reply to this email by Friday."
Give the deadline as a day and a date, not "soon" or "this week". Ask for one thing at a time. If you need three answers, number them.
If the email points to a web page, write link text that says where it goes. The university guide asks for descriptive links and warns against "click here". The page on link text has examples.
For more on ordering a message, see putting the main point first. The Easy-Read Editor can help you shorten the body before you send. If the file is a schedule, volunteer schedules and sign-up sheets covers its layout.
Name the file so it explains itself
GOV.UK's guidance on accessible documents says to use a short filename that conveys the document's purpose or topic. The university guide suggests labeling an attachment clearly in the email, with its type and size. Its example reads "Annual Report (PDF, 1.2MB)".
| Weak name | Better name | Why it works |
|---|---|---|
| Document1.docx | june-volunteer-schedule.docx | Says what it is and when |
| FINAL_v3_revised(2).pdf | meeting-agenda-5-june.pdf | No version clutter |
| scan0042.pdf | room-booking-form.pdf | A reader can find it again in a folder |
Mention the file by name in the body, so the reader can match the email to the attachment. For the volunteer schedule, one line is enough: "Attached: june-volunteer-schedule.pdf (1 page)".
PDF or an editable file?
Choose by what the reader must do with the document.
| If the reader needs to | Send | Watch for |
|---|---|---|
| Read or print it exactly as you laid it out | A PDF | Readers have little control over text size and spacing |
| Fill it in, comment or reuse the text | An editable file, such as a word-processing document | The layout can shift on another device |
| Do both | Both files, clearly labeled | Two files can drift apart. Name one as the main copy |
W3C's events checklist suggests offering material in formats readers can adapt, such as word processing or HTML. It says to avoid giving material only in PDF or protected files. GOV.UK's guidance prefers HTML over PDF where possible.
If you send both, give the files the same name apart from the ending, such as june-volunteer-schedule.pdf and june-volunteer-schedule.docx. Then nobody has to wonder which file is which. Say in the body that they hold the same content.
For a short message, skip the attachment. Put the text in the email body. There is nothing to open and nothing to lose. To make a PDF, see saving a PDF from your browser. For structure and tags, see making a PDF that reads well on screen.
Keep to one version
Many versions cause confusion. Two files have similar names, and nobody knows which one is current.
- Send the document once, when it is ready.
- If you must send a new copy, say so in the first line: "This replaces the file sent on Tuesday."
- Put the date or month in the file name, so versions are easy to tell apart.
- Keep one master copy in a shared place, and link to it in the email if people need the latest.
- Ask for replies in the same email thread.
Before you press send
- The subject line says what the email is about.
- The first two lines say what to do and by when.
- The file name explains itself.
- The body names the attachment and its type.
- Only one version is attached.
- A line tells readers who to contact if they need another format. Use a role or a shared address, not a personal number.
Common mistakes
- "See attached" and nothing else. The reader has to dig for the point.
- A subject line like "Update" or "Document". It tells nobody what to do.
- Names like "final_v2". They invite a "final_v3".
- Only a PDF, when readers must fill it in. Send an editable file as well.
- Important details only inside the attachment. If the deadline matters, put it in the body too.
- Resending without saying so. Readers cannot tell which copy to trust.
FAQ
Should I paste the document into the email instead?
If it is short, yes. The text sits where the reader already is, and there is no file to open. Attach a file when the layout matters or the reader needs a copy to keep.
What file type works best?
No single type fits every case. A PDF keeps the layout fixed. An editable file lets readers change it. When unsure, send both and say which one is the main copy.
How do I name a file with a date?
Put the topic first and the date last, such as "meeting-agenda-5-june". Keep it short.
What if someone needs a different format?
Add one line that offers it, with a role or shared address to contact. The university guide recommends including a contact point for such requests.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Sending inclusive emails (University of Manchester StaffNet) Checked November 19, 2026
- Publishing accessible documents (GOV.UK) Checked November 19, 2026
- Making Events Accessible (W3C WAI) Checked November 19, 2026
- Organize the information (Digital.gov) Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.