Graphic Design Handover

What Deliverables, File Formats, Source Files, and Usage Rights Should a Graphic Designer Provide?

What deliverables, file formats, source files, and usage rights should a graphic designer provide is a practical question about whether your business can actually use, print, publish, update, localise and legally reuse the work after approval. A design can look excellent in a presentation and still create operational problems if the handover contains only a low-resolution JPEG, an inaccessible cloud link, a flattened file, an unlicensed font or an unclear promise that the client “owns everything.”

A professional handover begins with the agreed use. A logo needs scalable vector masters, colour variants and small digital exports. A brochure needs editable layout files, linked images and a print-ready PDF matched to the printer’s specification. Social media production needs platform-sized exports and, where agreed, editable templates. Packaging may require dielines, colour separations, barcode checks and production notes. The correct file set therefore depends on the deliverable, software, production environment, channels and future editing needs.

Rights are equally important. Payment for design work does not always mean every copyright interest, font licence, stock image, template or pre-existing method automatically transfers. The contract should distinguish copyright assignment from a licence and state permitted media, territory, duration, exclusivity, modification, sublicensing, portfolio use and third-party restrictions. In India, written documentation is particularly important because copyright assignments are required to be in writing and signed. International projects need careful wording because commissioned-work rules vary by country.

For founders, marketing teams, agencies, ecommerce businesses and procurement leaders, the safest method is to create a deliverables schedule before design starts and use the same schedule for final acceptance. This guide explains the formats to request, when source files matter, how to check licences and usage rights, how to organise handover, and when a defined project or ongoing graphic design support arrangement may be useful.

Quick Answer: What Should a Graphic Designer Provide?

A graphic designer should provide every approved design in the formats required for its intended use, together with any editable source files promised in the scope. Typical deliverables include print-ready PDF files; web-ready PNG, JPEG, WebP or SVG files; native AI, PSD, INDD, Figma or other working files; size and colour variations; and a read-me explaining the folder structure, master files, software versions and production notes.

The designer should also provide a written rights record. It should identify whether copyright is assigned or licensed, where and how the work may be used, whether the licence is exclusive, whether the client may modify the design, and which third-party fonts, images, icons or templates remain subject to separate terms. The final invoice or download link should not be treated as a substitute for these commercial terms.

Before closing the project, open the files, test them in the intended software or channel, verify print and digital specifications, reconcile third-party licences, confirm final approval, and store the package in a business-controlled location.

Key Takeaways

• Define use before format: the right file package depends on whether the design will be printed, published online, edited, localised or animated.
• Final exports and source files are different: exports are ready for a specific use; source files preserve editing capability.
• Source files should be contractual: name the exact native formats and what “editable” means.
• Rights must be written: clarify copyright assignment or licence, media, territory, duration, exclusivity and modification rights.
• Third-party assets need an asset register: fonts, stock images, icons and templates may have separate restrictions.
• Technical acceptance matters: open, inspect and test files rather than approving appearance alone.
• Handover should be organised: use clear folders, version names, approval records and secure storage.

What This Page Covers

• The difference between deliverables, final exports, source files and production assets.
• Recommended formats for logos, print, web, social, presentations and packaging.
• How to define copyright ownership, usage licences and portfolio rights.
• How to manage fonts, stock media, templates and other third-party assets.
• How to select a freelancer, agency, in-house designer or managed team.
• How to review, approve, verify and archive a complete design handover.
• How Rudrriv can support defined or ongoing graphic design requirements.

Table of Contents

1. Basis for this guide
2. What a complete design handover means
3. When businesses need a formal deliverables schedule
4. Relevant design engagement models
5. How to plan design delivery step by step
6. In-house vs freelancer vs agency vs managed team
7. Formats, scope, timeline and rights
8. How to verify quality and completion

How This Guide Was Prepared

This guide is based on practical project-scoping, design-production, provider-selection and handover controls used in commercial creative work. File-format guidance is aligned with official software documentation, while rights guidance draws on recognised copyright sources. Adobe lists AI, PDF, EPS and SVG among Illustrator formats and explains that native formats can preserve editing data. The official Illustrator file-format documentation is useful when a supplier’s export claims need checking.

Copyright is jurisdiction-specific. The World Intellectual Property Organization’s copyright overview explains the general concept of rights in literary and artistic works, while India’s Copyright Act provisions on assignments state that an assignment must be in writing and signed. Creative Commons also provides clear explanations of licence conditions such as attribution, commercial use, derivatives and share-alike requirements through its official licence guidance.

Software features, licence terms and local legal requirements may change. Businesses should verify current requirements with the relevant platform, printer, asset provider and qualified legal adviser. Rudrriv can support requirement discovery, specialist matching, defined projects, dedicated professionals and ongoing design operations where those models fit the actual work.

What a Complete Graphic Design Handover Means

A complete handover means the client receives the approved work in a form that is technically usable, commercially authorised and understandable to the next person who handles it. It is broader than “sending the final files.”

Deliverable

A deliverable is an agreed output that can be reviewed and accepted. It may be a logo suite, brochure, ad set, presentation, packaging layout, web graphic, template or design system. A deliverable should have acceptance criteria such as dimensions, language, colour mode, file format, quantity and intended use.

Source file

A source file is the editable working document. It may preserve vectors, layers, text, artboards, links, components, grids and production settings. It is not the same as a final export. Source files create future editing value, but they may also contain third-party assets or reusable systems that need separate treatment.

Usage right

A usage right is permission to reproduce, display, distribute, adapt or otherwise use the design under stated conditions. It may come through a copyright assignment or a licence. Scope, duration, territory, exclusivity and permitted media should be explicit.

When Does a Business Need a Formal Deliverables Schedule?

A formal schedule is useful whenever design will be reused, produced at scale, distributed across channels, edited later or handled by more than one team. The more business-critical the asset, the more precise the schedule should be.

• Brand identity: logos, typography, colour systems and templates will be reused for years and by multiple suppliers.
• Print and packaging: technical errors can create production waste, delay or rework.
• Ecommerce: many product images, banners and promotional sizes require consistent naming and version control.
• Campaigns: digital, outdoor, print and partner assets may need different ratios, colour modes and rights.
• Presentations: teams often need editable slides, chart styles and reusable masters rather than only a PDF.
• Regulated or enterprise environments: approval records, confidentiality, accessibility and vendor governance may be mandatory.

A small one-off graphic may need only a compact list. A long-term identity or packaging programme needs a more detailed statement of work, rights schedule, asset register and acceptance process.

Which File Formats Should Be Included?

The correct formats should be selected by use, not by habit. The table below provides a practical starting point; the final list should follow the software, platform and production specification.

For vector work, Adobe explains that vector graphics are suited to scaling and identifies AI, EPS and SVG among common vector formats. For raster work, specify pixel dimensions and resolution rather than requesting “high quality” without a measurable requirement.

Relevant Graphic Design Engagement Models

The engagement model affects who controls source files, how revisions are managed and how consistently standards are applied. Choose it according to workload and governance needs.

Defined project support

A defined project works well for a logo, brochure, pitch deck, campaign asset set or packaging job with a clear beginning and end. The statement of work should list deliverables, milestones, revisions, source files and rights.

Dedicated professional

A dedicated designer suits a business with regular work and an internal manager who can prioritise tasks, provide briefs and approve outputs. Standard handover rules should apply to every request.

Ongoing business support

Ongoing support suits recurring social, ecommerce, sales and presentation needs. Use an intake queue, turnaround bands, revision policy, asset library and monthly review.

Managed team support

A managed team is useful when design spans disciplines or requires backup capacity, quality control and delivery coordination. The provider should define roles, escalation, service levels and ownership.

Step-by-Step Guide to Plan, Select and Start the Work

1. Define the intended uses

List every known channel, size, language, territory and production method. A logo needed for a website, signage, embroidery and packaging requires a different package from a single social image.

2. Create a deliverables matrix

For each asset, record quantity, dimensions, colour mode, final format, source format, variants, owner, milestone and acceptance test. This matrix becomes the project’s control document.

3. Define source-file expectations

Name the software and version, required editability, layer organisation, packaged links and whether embedded smart objects or components must remain intact. State any exclusions clearly.

4. Separate created assets from third-party assets

Require an asset register. It should identify fonts, stock images, icons, mock-ups, templates, plugins and generated elements, along with their licences and transfer status.

5. Agree rights before design begins

Decide whether you need assignment or a licence. Define media, territory, duration, exclusivity, modification, sublicensing, portfolio use, confidentiality and the payment condition for rights to take effect.

6. Set revision and approval rules

Define the number or duration of revision rounds, who consolidates feedback, what counts as a scope change and who has final approval authority.

7. Test the handover

Open files, check links and fonts, test exports, run print preflight where relevant, reconcile rights and obtain written acceptance. Store the package in a controlled repository.

In-House vs Freelancer vs Agency vs Managed Team

No model is universally best. The right choice depends on volume, specialisation, continuity, internal management capacity and the consequences of inconsistent delivery.

For one well-defined deliverable, a freelancer may be sufficient. For recurring production, a dedicated professional or managed arrangement can reduce coordination gaps, provided the client still maintains clear briefs and approval discipline.

How to Define Scope, Timeline, Pricing, Communication and Rights

A strong commercial scope turns creative expectations into verifiable obligations. It should describe not only what will be designed but also how work will move from brief to approval and handover.

Scope

List exact deliverables, quantities, formats, versions, sizes, languages, templates, production support, source files and exclusions. State whether copywriting, image sourcing, retouching, printing or implementation is included.

Timeline

Use milestones for brief acceptance, concepts, selected direction, revision rounds, production artwork, quality check and final handover. Add client dependencies such as copy, approvals, printer specifications and access.

Pricing

Pricing may be fixed per project, per asset, hourly, daily, retainer-based or capacity-based. Compare the included revision effort, seniority, project management, source files, licences and production support—not only the headline rate.

Communication

Name the project owner, feedback channel, response expectations and approval authority. Consolidated feedback reduces conflicting revisions and protects the timeline.

Rights

Attach a rights schedule. It should distinguish original commissioned work, pre-existing designer materials and third-party assets. For commercial brand assets, obtain appropriate legal review where the value or risk justifies it.

How to Review Deliverables, Revisions, Ownership and Handover

Review should cover four dimensions: creative approval, technical usability, contractual completion and rights clearance.

• Creative: messaging, hierarchy, brand consistency, readability and suitability for the audience.
• Technical: dimensions, colour, resolution, links, fonts, vectors, layers, accessibility and production specifications.
• Contractual: every promised asset, size, variant, revision and support item is present.
• Rights: assignment or licence is executed and third-party restrictions are documented.

Final approval should be recorded after these checks, not before. When the project includes print production or platform implementation, the final production supplier should confirm technical suitability.

How to Measure Quality, Progress and Business Usefulness

Design quality should be measured through agreed evidence rather than personal preference alone. Suitable measures depend on the project.

• Delivery progress: milestones completed, feedback turnaround and open dependencies.
• Technical quality: preflight results, missing-link checks, correct exports and platform acceptance.
• Brand quality: consistency across variations and correct use of identity rules.
• Operational usefulness: whether internal teams can find, edit and deploy the assets.
• Performance evidence: for campaign or digital work, use appropriate engagement, conversion or usability measures without assuming design alone caused the outcome.

A visually attractive project is not fully successful if the client cannot reuse it, lacks permission to publish it, or cannot identify the approved version.

Common Mistakes to Avoid

• Requesting “all formats” without defining actual uses.
• Assuming payment automatically transfers every right and third-party licence.
• Accepting only JPEG or flattened PDF files for a reusable identity.
• Calling a file editable when text, links or components cannot be changed.
• Failing to obtain printer or platform specifications before production.
• Allowing feedback from many stakeholders without one consolidated decision-maker.
• Using stock assets or fonts without recording licence terms and purchaser details.
• Leaving final files in the designer’s personal drive rather than business-controlled storage.
• Approving design appearance without opening and testing the actual files.
• Keeping ambiguous filenames and obsolete drafts in the final delivery folder.

Practical Examples

Example 1: Startup logo handover

Situation: A startup approves a logo and receives one PNG. Common mistake: The team assumes it can use the same file for signage, an app icon and investor materials. Correct approach: Request an editable vector master, SVG, print PDF, transparent PNGs, light and dark variants, monochrome versions, colour values and basic usage guidance. Support value: A design specialist can rebuild the delivery schedule and verify scalability before the identity is widely deployed.

Example 2: Indian packaging project

Situation: An ecommerce company commissions product packaging for an Indian printer. Common mistake: The designer starts before receiving the final dieline and print specifications. Correct approach: Lock dimensions, bleed, colour, finishes, barcode placement, legal copy and printer requirements; then deliver packaged source files, production PDF and proof. Support value: Managed coordination among the brand, designer and printer can reduce late technical corrections, although final production still requires printer approval.

Example 3: Recurring social media production

Situation: A marketing team commissions dozens of monthly graphics. Common mistake: Each file is created independently with inconsistent names and no editable system. Correct approach: Build templates, component rules, channel-size standards, an approval queue and a monthly archive containing final exports and editable masters. Support value: Ongoing design support can provide continuity and quality checks when volume exceeds the internal team’s capacity.

Graphic Design Deliverables Checklist

• Approved deliverables match the signed scope.
• Every required size, language, colour and channel variation is included.
• Final exports open correctly and match intended platform or printer requirements.
• Native source files are included where contracted and remain genuinely editable.
• Linked images and assets are packaged or embedded correctly.
• Fonts are identified and licence responsibilities are documented.
• Stock images, icons, templates and generated assets appear in an asset register.
• Copyright assignment or usage licence is written, signed where required and aligned with payment terms.
• Portfolio, confidentiality and exclusivity rules are recorded.
• Master files are clearly named and obsolete drafts are archived separately.
• A read-me explains software versions, production notes and file structure.
• Final approval and handover receipt are recorded.
• Files are stored in a business-controlled repository with backup.

How Rudrriv Can Help

Rudrriv can help businesses define a design requirement, select an appropriate specialist or support model, structure deliverables, coordinate production and maintain ongoing creative capacity. Relevant options may include a defined project, a dedicated professional or managed design support, depending on the volume, complexity and continuity required.

The useful starting point is not a generic request to “make designs.” It is a clear description of assets, channels, timelines, source-file needs, approval roles and rights. Businesses exploring external capability can review Rudrriv’s outsourcing options or freelancer support when those models fit the work.

Summary: What Deliverables, File Formats, Source Files, and Usage Rights Should a Graphic Designer Provide?

A graphic designer should provide a complete, organised and verifiable handover built around the intended business uses. That normally includes suitable final exports, editable source files where agreed, variants and production assets, a file index, third-party licence records and written usage rights. The client should know which file is the master, who owns or licenses each element, what may be modified, where the work may be used and whether any restrictions continue after delivery.

Internal delivery may be enough when the organisation has capable design staff, reliable production controls and clear asset governance. Specialist or managed support becomes useful when demand is complex, recurring, multi-channel or difficult to coordinate. In either case, scope, provider selection, timeline, communication, quality assurance, revisions, ownership, delivery verification and handover should be decided before the project closes.

Frequently Asked Questions

What deliverables, file formats, source files, and usage rights should a graphic designer provide?

A graphic designer should provide the approved final designs in the formats needed for the agreed uses, plus editable source files when those files are included in the contract. A practical handover normally contains print-ready PDF files, web-ready PNG, JPEG, WebP or SVG exports, the native working files such as AI, PSD, INDD or Figma links, and a simple file index explaining what each item is for. Logo projects usually need vector masters, colour variations, monochrome versions and small-size exports. Campaign or social projects may require platform-sized files, editable templates and image assets. Usage rights should be written, not assumed. The agreement should state whether copyright is assigned or licensed, which media and territories are covered, whether use is exclusive, how long the rights last, whether modifications are allowed, and whether the designer may show the work in a portfolio. It should also identify third-party items—fonts, stock images, icons, templates or AI-generated elements—and clarify whether the client receives a transferable licence. In India, a copyright assignment must be in writing and signed, so the handover email alone should not replace a properly drafted clause.

Should a graphic designer always provide editable source files?

Not automatically. Editable source files should be provided when the proposal, statement of work or contract includes them, or when the client reasonably needs future updates and has paid for that level of handover. Some designers price source files separately because the files contain reusable systems, working methods, linked assets, licensed resources or template components that were not part of a basic final-output package. The safest approach is to decide before work starts. List the exact native formats—such as Adobe Illustrator, Photoshop, InDesign, After Effects, Canva or Figma—and state whether layers, artboards, components, paragraph styles, links and placed assets will remain editable. Also specify whether fonts and stock files can legally be transferred. A client should not accept a flattened PDF labelled as a source file when ongoing editing is required. Conversely, a designer should not promise unrestricted source files if third-party licences prevent transfer. The commercial scope should reflect both the creative output and the future reuse value.

Which file formats are best for logos and brand identity assets?

For logos, the master should usually be a vector file because vectors can scale without losing sharpness. Common master formats include AI, EPS, SVG and editable PDF. The handover should also include PNG files with transparent backgrounds, JPEG files for simple office use, and colour variants such as full colour, black, white, grayscale and one-colour versions. SVG is useful for websites and interfaces, while print suppliers often request PDF or EPS. A complete brand identity package may also include CMYK versions for print, RGB versions for screens, spot-colour references where required, favicon or app-icon sizes, social profile assets, stationery templates and a short brand guide. Ask the designer to name files clearly and separate master files from exports. Do not rely only on a JPEG logo; it is difficult to resize cleanly and does not preserve editable vector paths. Before approval, test the logo at very small and very large sizes, on light and dark backgrounds, and in single colour.

What is the difference between a source file and a final export?

A source file is the editable working document used to create the design. It may contain layers, vectors, linked images, text styles, components, masks, grids, artboards and other production information. Examples include AI, PSD, INDD, AEP, Figma files and editable Canva templates. A final export is produced for a specific use, such as a PDF for printing, an SVG for a website, or a PNG for a transparent digital graphic. The distinction matters because a final export can look correct while remaining difficult or impossible to revise. A flattened PDF may print perfectly but may not support future text, colour or layout changes. During procurement, state whether you need only ready-to-use outputs or also the ability to update, localise and repurpose the work. If source files are included, require packaged links, correct font treatment, sensible layer names and a clean final version. This reduces dependency on the original designer and makes future handover more reliable.

How should usage rights for commissioned graphic design be written?

Usage rights should be written as a clear licence or copyright assignment that matches the commercial need. The clause should identify the exact work, the rights granted, permitted media, territories, duration, exclusivity, modification rights, sublicensing or agency use, attribution requirements, portfolio rights and the point at which the rights become effective—often after full payment. It should also explain what remains excluded, including pre-existing methods, templates, fonts, stock assets and third-party materials. For an Indian engagement, the parties should pay particular attention to the Copyright Act requirements for assignments, including written and signed documentation. Cross-border projects also need jurisdiction-specific review because ownership rules for employees, contractors and commissioned works differ. Avoid vague phrases such as “all rights included” without defining what is actually transferred. For high-value identity, packaging or advertising work, obtain legal review rather than treating a design invoice as a complete intellectual-property agreement. The designer should provide a rights schedule or asset register showing which elements are owned, licensed or restricted.

Who is responsible for font, stock image, icon and template licences?

Responsibility should be allocated in the agreement before production begins. The designer should disclose every third-party asset used and state whether it is covered by the designer’s licence, must be licensed directly by the client, can be transferred, or needs replacement before broad commercial use. Many font, stock, template and icon licences limit the number of users, impressions, products, websites or end clients. A subscription held by the designer does not always give the client continuing rights after handover. The client should receive an asset list containing the asset name, source, licence type, purchaser, permitted use and any renewal requirement. For fonts, the designer may outline text in final print artwork while still providing the font name so the client can obtain its own desktop or web licence. For stock images, retain purchase records and model or property releases where relevant. Do not assume that a file being downloadable means it is cleared for advertising, packaging, resale or trademark use.

What should be checked in print-ready design files?

Print-ready files should match the printer’s specification, not a generic export preset. Check final dimensions, bleed, trim and safe areas; CMYK or required spot colours; image resolution; overprint settings; embedded or outlined fonts; linked image availability; transparency handling; page order; barcode or QR-code readability; and whether dielines, varnish, foil or cutting paths are placed on correctly named separations. A proof PDF should also be supplied for visual comparison. Before mass production, ask the printer to run a preflight check and confirm the final supplied specification. Colour seen on a monitor will not exactly predict printed colour, so critical brand or packaging work may need a contract proof or physical sample. The designer should not mark a file “print ready” without knowing the output method. In India, local printers may use different workflow preferences, so share the printer’s requirements early and record who is responsible for final production approval.

How should design files be named and organised at handover?

Files should be organised so another competent person can understand and use them without contacting the original designer for every detail. A practical folder structure separates source files, approved finals, print files, digital exports, fonts or licence notes, linked assets, mock-ups, guidelines and archived drafts. File names should include the project, asset, size or channel, colour version, language, version and approval status where useful. The handover should include a short read-me or file index. It can identify the master file, explain colour codes, list software versions, flag missing licensed assets, show where linked files are stored and note which files were finally approved. Remove obsolete drafts from the final folder or place them in a clearly marked archive. Avoid names such as “final2-new-latest-use-this.ai.” A controlled naming convention and approval record reduce the risk of publishing the wrong artwork, sending an RGB file to print or editing an outdated campaign version.

How can a client verify that a graphic design handover is complete?

Verify the handover against an agreed deliverables schedule rather than relying on a download link. Open every file, confirm that source files are editable, check that links are not missing, and test the exports in their intended environments. Review image dimensions, transparency, colour modes, print specifications, text accuracy, language versions and accessibility considerations. Confirm that all approved variations, sizes and placements are present. Then reconcile the rights documentation. Make sure the assignment or licence is signed, final payment conditions are satisfied, third-party assets are listed, and any portfolio, confidentiality or exclusivity terms are understood. Record final approval and store the package in a business-controlled repository with backup and access permissions. For larger projects, ask a second designer, brand manager or production partner to conduct a handover review. This modest quality-control step can reveal missing fonts, low-resolution images, broken links or incomplete rights before the original project team closes the work.

When is managed graphic design support more suitable than a one-off freelancer?

Managed support is more suitable when a business has recurring design demand, multiple stakeholders, several channels, strict brand governance or a need for backup capacity. A one-off freelancer can be effective for a clearly defined asset, but ongoing campaigns, ecommerce production, presentation support, multilingual adaptation or enterprise marketing often require intake rules, prioritisation, version control, quality assurance, capacity planning and reliable handover across many tasks. The correct choice depends on workload, complexity and internal management capacity. A managed arrangement should still define deliverables, turnaround expectations, revision rules, access, confidentiality, ownership and reporting. It is not a substitute for a clear brief. Rudrriv can help organisations structure a defined design project, engage a dedicated professional, or establish ongoing design support where the requirement genuinely needs continuity. Before selecting any model, estimate monthly volume, identify peak periods, define who approves work and decide which source files and usage rights must be standard in every request.