Contents
An attachment can leave my outbox with a perfectly clear filename and still create a confusing handover. The recipient may not know whether to edit it, comment on it or simply keep it. A live link may lead to a changing document while an attached copy stays separate. Another reply may return a third version. I want the message to explain that relationship before the document starts moving through other people's folders, rather than ask a chain of final filenames to reconstruct the agreement later.
I will follow an invented handover for a small exhibition leaflet. The organizers, files and review decisions are illustrative. No message is being sent and no real collaborator's work is described. The example lets me compare a live working file with a dated review copy, then handle an awkward returned attachment. My preferred method is simple: choose the artifact's role, say where changes belong and tell the recipient what response would move the work forward.
Decide whether the recipient needs a copy or a shared file
The first choice is not the filename. It is what relationship the recipient should have with the material. If I want a reviewer to assess a stable version, an identified review copy may suit the task. If two writers are actively coauthoring, an appropriately shared live file may be more suitable. Neither method is universally better. The handover should follow the work and the recipient's access, rather than whichever attachment option happens to be most prominent in the mail window.
Microsoft's Outlook guidance distinguishes attaching a copy from sharing a OneDrive or SharePoint link. A copied attachment is separate from the cloud original; changes to that copy do not automatically synchronize back. A shared link involves access settings and a continuing destination. I would preserve that distinction in the message. Calling both the document hides the operational difference. The recipient needs to know whether their changes affect the working file or produce another artifact that someone must deliberately reconcile.
For the fictional exhibition, I would send a review copy while the main writer pauses substantive layout changes. The requested review concerns wording and missing context, not final print approval. The message can identify the live working file separately for the editor, if sharing it is appropriate, but should not make the reviewer choose between two unexplained versions. One clearly marked artifact and one clear response request are a stronger starting point than a message offering several nearly identical files with no account of their roles.
Give the artifact an identity that survives forwarding
I would name the review copy with the project, document role and review identifier. Exhibition-leaflet-review-01 is more informative than final, especially once the file is downloaded outside its original folder. The document itself should also identify that role. If the filename says review while the first page says approved for print, the recipient receives conflicting instructions. A useful handover compares the name and visible content before the file travels, rather than assuming either one is sufficient alone.
The identifier need not encode the whole project history. A short version label can point to a record explaining its relationship to the working file. If dates are used, I would make their meaning clear: the date of the review copy, for example, not an unexplained creation timestamp. A date is useful when it distinguishes artifacts people actually exchange. It is less useful when every copy receives a new date merely because somebody downloaded it, making the chronology look like a sequence of editorial decisions.
I would retain the copy that was actually sent when the review matters to the project. That gives the editor a baseline for interpreting returned comments. The baseline should remain separate from later experiments. Without it, a reviewer may refer to a passage that has already changed, and the writer may mistakenly think the comment concerns the current text. This is not an argument for keeping every attachment forever. It is a reason to preserve the small amount of version context needed while the exchange is active.
Write the response request before polishing the email
For this review I would ask two specific questions: does the leaflet explain what visitors will encounter, and are any factual descriptions unclear or unsupported? The reviewer is not being asked to approve image rights, proof the final print file or redesign the layout. Those tasks may belong to other stages. Naming the scope makes the request manageable and prevents an informal yes, looks good from later being treated as approval for responsibilities the reviewer never accepted.
I would state how to respond. Comments in the review copy can be appropriate, or the reviewer might send a short list keyed to section headings. The method should fit the tools both people can use. If a format requires software the reviewer lacks, the writer has created an access problem rather than a review task. I would choose an appropriate alternative or provide the relevant material in a supported form. A message should not rely on the recipient guessing which feature the sender expected them to use.
The return point also needs agreement. A real deadline may matter because another stage depends on it, but I would not present an unaccepted date as a promise from the recipient. In the illustrative message I can say the editor hopes to incorporate comments before the next planning discussion and ask whether that is workable. Once a response date is agreed, the record can reflect it. A filename and an email timestamp cannot establish that human agreement on their own.
Subject: Exhibition leaflet — review copy 01, wording and context Attached: exhibition-leaflet-review-01.pdf Role: Stable review copy, not approved for printing. Please review two things: 1. Can a first-time reader understand the leaflet's description of the exhibition? 2. Which factual descriptions need clarification or a clearer source? Please return comments against this copy or send a short list using its section headings. Layout and final printing approval are outside this review. The editor will incorporate accepted changes into the live working file. Please do not treat a revised attachment as a replacement print master. If the format is inconvenient or the proposed review timing is not workable, let us agree an alternative before proceeding.
Check access instead of assuming the send completed the job
If I share a live link instead, I would inspect who it works for and what those people can do. Microsoft's Outlook link guidance describes permission information for supported OneDrive and SharePoint links in message bodies. Available settings depend on the account and environment. I would follow the current documentation for the actual setup rather than infer access from the fact that the link opens on my signed-in computer. Sender access and recipient access are different tests.
The intended permission follows the task. A reviewer who only needs to read should not automatically receive broad editing rights to an entire project folder. At the same time, view access does not necessarily prevent downloading, copying or further distribution. I would not describe a review link as confidential merely because editing is disabled. Sensitive material should be selected and shared according to its actual context. Permission settings help implement a decision; they do not replace the decision about what should leave the workspace.
I would make a representative access check appropriate to the system and the recipient, without bypassing account rules or sharing credentials. If an external reviewer cannot reach the material, I would provide an authorized alternative rather than ask them to work around the controls. A successful send confirms that a message left through the mail workflow. It does not by itself establish that the intended person can open the document, understand its role or perform the requested review in the form supplied.
Receive a revised copy without losing the baseline
Now imagine the reviewer returns exhibition-leaflet-final.pdf. I would not make that filename the project's new authority. The reviewer may simply have named their completed comments final. I would identify which copy they reviewed, inspect the changes and compare them with the sent baseline. The returned artifact contains a contribution to the review, not automatic approval to replace the live master. Its role should be established through the exchange rather than the strongest status word in the filename.
The editor needs to distinguish accepted changes, questions and suggestions that remain open. I would use a small reconciliation note when those distinctions matter. A wording correction can be applied; a factual concern may require checking its source; a proposed design change may be outside the review's agreed scope. Treating every markup as a direct instruction can erase the editor's responsibility to assess the contribution. Ignoring inconvenient questions because they arrived in the wrong format would be equally unhelpful.
If the working file changed during the review, I would map comments to the current text carefully. A page reference or line number may have moved. The review baseline gives me something stable to inspect before interpreting the comment. I would avoid copying whole paragraphs back and forth without understanding which version contains the current decisions. The smallest controlled reconciliation is often clearer than declaring one entire file the winner. The task is integrating a contribution while preserving the project's present meaning.
Handle two reviewers with different copies
A second hypothetical case adds another reviewer who received review-02 after a correction. Their comments may not refer to the same wording as the first reviewer's. I would record which artifact each person received and avoid combining their feedback into an anonymous list that loses that context. A comment can be sensible for an earlier sentence and irrelevant to its revision. The version relationship helps the editor recognize this without making either reviewer appear to have misunderstood material they never saw.
I would consolidate the decisions in the live project record. That record can state that a point was clarified in review-02, that a later suggestion is under consideration and that one question still needs a source check. It should not require every future editor to reopen the whole email chain. The emails remain the exchange history; the project note identifies what the current work has accepted from them. This separation keeps the document usable while preserving a route back when a contribution needs interpretation.
The reviewers may also disagree. I would compare the question each is answering rather than select the more confident wording. One may be considering readability, another factual precision. The leaflet can need both a clearer sentence and a retained qualification. The editor should explain the choice when the tradeoff matters. A handover process is useful because it makes those judgments visible, not because it guarantees that every set of comments can be merged without further thinking into a single self-evident final version.
Send the next artifact with a clear change note
Once accepted changes are incorporated, I would identify what the next copy is for. A revised review copy, an approval copy and a print master perform different jobs. The message should say which one is being supplied. I would include a short change note focused on consequential differences: a factual description was narrowed, the introduction was clarified or a section remains unapproved. A long list of punctuation edits may be unnecessary unless the recipient specifically needs that level of comparison.
The note should also state where further changes belong. If review-03 is now the current artifact for comments, earlier review copies should be marked accordingly in the project's active navigation. I would not rely on every recipient deleting old attachments. People may retain them for legitimate reasons. The project can reduce ambiguity by naming the current role and version each time a new handover occurs, while preserving enough history to understand earlier feedback. The workflow should tolerate ordinary file retention rather than depend on perfect inbox discipline.
For the exhibition leaflet, final approval would be a separate recorded decision by the appropriate person or group. A completed review does not itself authorize printing, spending or publishing. I would make that transition explicit in the document and message. Once approved, the print artifact should be distinguishable from the editable source and review comments. If a new substantive change follows approval, it needs the appropriate process rather than a casual overwrite whose filename continues claiming the earlier authorization.
Close the exchange in the project, not only the inbox
At the end, I would make the current artifact findable from the project record. It should identify the approved copy, the live editable source if retained and the relevant decisions arising from review. The returned comments can remain in an appropriately organized history. An inbox thread is not the only practical entry point for future work, especially when a new contributor joins. They should not have to infer the master from attachment timestamps or ask which of several files called final people currently trust.
I would review privacy and retention according to the project's actual needs. A leaflet may be public while reviewer contact details and preliminary comments are not. Keeping a useful history does not require making the whole exchange public or retaining unnecessary sensitive material indefinitely. The record should preserve the decisions and contributions that matter to the work through an appropriate controlled arrangement. I would distinguish a publication artifact from the administrative material that helped create it.
My final test would be a new editor asking what to use and why. They should find the intended file, understand its status and know where an authorized change would happen next. If that answer still depends on the original sender's memory, the handover is incomplete. The repair may be a short project note rather than another elaborate naming convention. I want the email to carry a clear transition between people and artifacts, so the document's role remains understandable after the message itself has faded into the archive.
Frequently Asked Questions
Q: Is sharing a link better than attaching a copy?
A: It depends on the task. A live file can support collaboration, while a copy can provide a stable review artifact. State which relationship you intend, follow the service's permission rules and tell the recipient where accepted changes will be incorporated.
Q: Does an attachment synchronize with the original file?
A: A traditional attached copy is separate. Microsoft's Outlook guidance distinguishes it from a shared cloud file and notes that edits to an attached copy do not automatically synchronize to the cloud version. Check the actual attachment method rather than assuming all file links behave alike.
Q: What should I do with a returned file called final?
A: Establish its role and compare it with the copy sent. It may mean the reviewer finished their comments, not that the project approved a replacement master. Incorporate accepted changes deliberately and preserve the version context needed to interpret the contribution.
Q: Does view-only access prevent copying?
A: Not necessarily. Viewing, editing, downloading and forwarding are distinct capabilities and vary with the service and settings. Do not treat disabled editing as a confidentiality guarantee. Select appropriate content and access for the intended review.
Q: How much review history should I keep?
A: Retain enough to identify the artifacts reviewed, consequential comments and the decisions incorporated into the current work, subject to the project's privacy and retention requirements. A useful project record can summarize those outcomes without making every future editor reconstruct the entire email chain.
One thing to take forward
Before sending the next document, I would write three lines: what this artifact is, what I want the recipient to do and where accepted changes will live. Those lines give the filename a useful context. The handover is complete when the recipient can act on the intended version without guessing, and when the next editor can understand the result without treating the last attachment in the inbox as an unexplained authority.
Sources & further reading
Something needs correcting? Write to the editors with the article link.



