Start with the purpose and current status
A creative project can feel complete to its maker while still being difficult for someone else to use. A client may not know which design file is final. A teammate may be unsure whether the copy has been approved. A student taking over a group project may have no idea why one concept was chosen over another. A handoff note closes that gap. It is a short guide to the work as it stands, not a replacement for the full project brief or an account of every decision.
Open with the project name, the date of the handoff, and the person responsible for the note. Then state what the work is for and where it stands. For example: “The three social graphics are ready for review; the event date in the captions still needs confirmation.” That sentence gives the recipient a clearer starting point than “Files attached.” If the handoff is final, say so. If it is for an internal review or a change of ownership, make that distinction equally clear.
List the deliverables and point to the right files
Name each deliverable in terms the recipient will recognize: a presentation deck, a set of illustrations, an edited video, or a package of website copy. For each one, identify the version being handed over and its intended use. If you have supplied both an editable source and an export, explain the difference. A small list in the note can prevent someone from treating a preview image as the production file.
Give a precise location for the files, whether that is a shared folder, a project workspace, or an attachment. Describe any folder structure that is not obvious and identify outdated drafts that should not be used. Before sending the note, check the links and access permissions from the recipient’s point of view. A location is only useful if the next person can open it. If the project includes fonts, linked assets, or supporting copy, say where those live too.
Record decisions and flag what is still open
The note should preserve the decisions someone needs in order to continue without retracing your work. Explain which concept was selected, what feedback it addressed, and any constraints that shaped the result. Keep this brief and concrete. “We used the shorter headline so it fits the narrow mobile layout” is more helpful than a long history of every headline considered.
Separate settled decisions from unresolved questions. An open item might be a missing approval, a placeholder image, an untested export, or a choice between two cover treatments. For each item, say who is expected to decide or act, if known. Do not present an assumption as approval: “I used the supplied product name, but the client has not confirmed the capitalization” makes the uncertainty visible. This is especially useful when a freelancer hands work to a client or a small team changes project owners.
Explain how to review and use the work
A useful handoff tells the recipient what to check, not just what to download. Point out aspects that deserve attention, such as text accuracy, image cropping, accessibility of on-screen text, or how a layout behaves at different sizes. Mention any checks you completed and any you did not complete. Avoid a blanket claim that everything is ready if important conditions have not been verified.
Include practical usage details where they matter. A video handoff might identify the caption file and thumbnail; a brand asset handoff might distinguish files for print from those for screens. Note any asset permissions or usage limits you know about, without guessing when the information is unavailable. If the recipient needs to obtain a license, confirm a credit, or replace a temporary asset before publishing, make that a visible next step rather than burying it in a folder comment.
Close with ownership and the next action
End the note with a clear request or transition. Say whether you need consolidated feedback, approval, a technical check, or no further action. If there is a review process, name where comments should go and who will incorporate them. A small team might ask reviewers to leave comments in one shared document; a student group might assign one person to collect feedback before anyone edits the slides. The aim is to prevent several people from making conflicting changes.
You can use the same simple structure on most projects: status, deliverables and locations, key decisions, open items, review guidance, and next action. Adjust the detail to the work. A one-page illustration may need only a few lines, while a campaign with multiple formats may need a fuller inventory. Read the finished note as if you had not attended any project meetings. If you can find the correct files, understand what remains uncertain, and identify who does what next, the handoff is doing its job.
