Sending a corrected attachment is only half the job. Recipients also need to know, at a glance, whether the new file is the one they should use, what changed, and whether the earlier copy is now obsolete. If that information is buried in a long message—or left unstated—someone may keep working from the wrong version. A short, structured note makes the update easier to act on. Use a distinctive filename, identify the revision in the email itself, and give recipients one clear instruction about the previous copy.
The useful bits
- Use a filename that distinguishes the revision from the earlier attachment.
- Summarize the meaningful changes in the email body.
- Say directly whether recipients should disregard or keep the earlier copy.
Make the revised file recognizable
Before attaching anything, check that the filename helps distinguish this copy from the one already sent. A name such as “draft-final-new” is vague: recipients may have several files that fit it. Prefer a clear subject, status, and revision marker, for example “Q3-proposal-revised.docx” or “event-agenda-v2.pdf.” If a date helps identify the correct copy, use a consistent date format. Avoid changing the name so much that recipients cannot tell what document it belongs to.
Keep the filename and the email description consistent. If the message calls the attachment “the revised agenda,” the file should look like an agenda, not a generically named “document2.” Check the attachment before sending, especially if you selected it from a folder containing earlier drafts.
Put the version instruction near the top
State the purpose of the email in its opening lines. Recipients should not have to read to the end to learn that a newer file is attached. Say that this is a revised copy, identify it by filename, and specify what to do with it. Avoid relying on phrases such as “Here it is” or “Updated, thanks”—they do not establish which attachment is current or whether the previous one still matters.
If you are replying in an existing thread, make the update explicit there too. The earlier message may remain visible below your reply, so a direct sentence helps prevent someone from opening the first attachment by mistake.
Subject: Revised event agenda — please use this copy Hi [Name], Attached is event-agenda-v2.pdf, the revised agenda. Please use this copy for planning and disregard the version I sent earlier.
Summarize changes that affect the reader
Give a brief, accurate account of what changed. Focus on details that could alter a recipient’s work or decision: a corrected date, a revised section, an added page, or a changed figure. A useful summary might say, “I corrected the session start time on page two and added the room assignment.” This lets recipients decide whether they need to review the whole file or check a particular part.
Do not describe changes you have not verified. If the revision is extensive, say so plainly rather than implying that only one small detail changed. If nothing substantive changed and the file was replaced for another reason, explain that instead. The purpose is to orient the reader, not to provide a change history that may be incomplete.
Be unambiguous about the earlier copy
Tell recipients whether the earlier attachment should be disregarded, retained for reference, or used alongside the new one. These instructions are different. “Please use this copy instead” signals replacement; “keep the earlier version for reference” says it still has a purpose. If the old file remains valid for some tasks, name those tasks rather than asking recipients to infer the distinction.
If you are unsure whether someone has already acted on the earlier version, do not imply that the revised file automatically fixes that. State what changed and, if needed, ask the recipient to confirm whether the earlier copy has already been used. Keep the request specific and proportionate to the consequences of the change.
Match the message to the size of the change
A minor correction usually needs only a short note, the changed detail, and a clear replacement instruction. A substantial revision deserves a more prominent summary and an indication of which sections are affected. If recipients need to take a next step—such as reviewing a revised schedule or replacing a document in a shared workflow—say exactly what action you need and by when, if a deadline is known.
Do not call a file “final” unless you mean that recipients should treat it as the version to use. If further changes are possible, “revised copy” or a revision label is more accurate. Clear wording prevents a label from promising more certainty than you can provide.
Check the handoff before sending
A quick review catches the common mismatch: the message describes one revision while the attachment is another. Read the email as if you were a recipient who has both copies. Can you identify the new file, understand what changed, and tell what to do with the old one without asking a follow-up question?
After sending, confirm that the message appears in your sent mail with the intended recipient, filename, and attachment. That check confirms the handoff details on your side; it does not establish that the recipient opened the message or replaced their copy. If the change is important and no acknowledgment is needed, do not imply that delivery alone confirms the recipient has acted.
- Filename clearly distinguishes the revised copy.
- Email names the attached file and summarizes verified changes.
- Instruction says whether to disregard, retain, or use the older copy.
- Sent message shows the intended recipient and correct attachment.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction