BEFORE THE DETAILS
- Agree the deliverables before work starts, including editable files.
- Having a file does not by itself establish usage rights for every asset inside it.
- Test opening the files and assign responsibility for approved versions and updates.
1. Agree intended uses and deliverables first
Write down what the team needs after the project: sending a logo to print, placing it in presentations, changing employee names or creating new materials internally. Each use needs different deliverables. A final image may be enough for a presentation, but does not allow name lettering to be edited in the same way as a source file. Define formats, language versions, colours, backgrounds and responsibility for later updates in the project scope rather than leaving conflicting expectations.
In a hypothetical Muscat service company, an administrator may need an employee-card template that can be updated, while a salesperson only needs ready-to-use presentation assets. Discuss that distinction before pricing and approval. Do not assume “identity design” automatically includes every draft or working file. Ask for a clear list of agreed deliverables and any excluded components or assets requiring a separate purchase or subscription.
2. Distinguish final outputs from working files
A final output is prepared for a particular purpose, such as publishing, presenting or producing to an agreed specification. A working file preserves an editable structure such as layers, text, links and styles. The extension alone is not enough: a PDF may contain different kinds of elements, and a native design document may depend on images outside its folder. Request a brief description of what is actually editable, the application and version, and any add-ons needed to open it correctly.
Adobe explains that packaging an InDesign project can collect the document, linked graphics and a report, with options including PDF and IDML copies. These are handover tools, not automatic proof that a folder is complete or that every font may be transferred. Check for missing links and compare the result with the approved output. In the hypothetical company, test changing an employee name in a trial copy while preserving the approved source unchanged.
| Group | Purpose | What to verify |
|---|---|---|
| Approved outputs | Direct use for the intended purpose | Language, dimensions and revision |
| Editable sources | Updates in the agreed tools | Application, links and dependencies |
| Asset register | Identify each component’s source | Licence, restrictions and account holder |
| Usage guide | Explain which file to use | Use examples and update owner |
3. Review fonts without assuming transfer rights
Record the font family, weights, source and licensing route. For Adobe Fonts, for example, Adobe distinguishes final outputs containing properly embedded or rasterised font data from a client needing direct font access for editing; the latter requires the client’s own licence. Adobe Fonts files are not transferred through packaging. Check the specific font’s terms rather than applying one service’s licence to every typeface.
Converting text to outlines can preserve its appearance in an appropriate output, but does not leave ordinary, easily editable text. Discuss separate final and working versions where scope and licensing permit. If a company employee will update cards regularly, test their font access before handover. Record what happens if a required subscription ends and who handles replacing the font or renewing access, rather than postponing that question until the first urgent update.
4. Connect images and assets to a source-and-licence record
Create a short register for external photos, illustrations and templates: asset name, source link or identifier, licensing party, intended use and relevant restrictions. Keep purchase or licensing evidence appropriately, without sharing account credentials. Downloading an image or finding it inside an editable file does not establish permission to redistribute it separately or use it in every future product; check the licence when the use changes.
Adobe Stock states that its licences are non-exclusive and that its images cannot be used in or as a logo. This illustrates the difference between using a picture in a printed piece and using an asset to represent the brand itself. Ask for original work, licensed assets and client-supplied materials to be identified, with written clarification of agreed use, editing and delivery. This is an operational file review, not a legal interpretation of ownership or a guarantee of trademark registration.
5. Test the handover and assign version responsibility
Open the folder away from the designer’s working directory, or on the recipient’s computer where possible, to reveal links that depend on another location. Test the main files in the agreed applications and compare text, images and page order with the approval references. Request a short guide explaining what sales staff use and what goes to suppliers. Record missing items and their completion arrangements before considering the handover checklist closed.
Assign someone to maintain the master and release updates, using filenames that include the project, language, revision and purpose. Archive superseded versions clearly rather than leaving several files called “final”, and retain a backup according to company policy. Version responsibility here means who manages and approves file updates, which is distinct from legal rights. If rights are disputed, consult the agreement, relevant licensors or a qualified adviser before making a disputed use.
Common questions
Does receiving an editable file transfer all rights?
That cannot be inferred from the file alone. Review the agreement for original and licensed components and clarify permitted uses and edits. Legal ownership questions need qualified review when unclear.
Why are font files missing from the folder?
The licence may prohibit transfer, and you may need your own licence or subscription to access them. Request font names, weights and links, then test the source on your computer before accepting the handover.
Sources and further reading
YOUR NEXT STEP
Turn the details into a clear brief.
Tell us which materials you need, who will use or edit them and which applications your team has so we can define a clear handover list within the design scope.
