Clarifying Deliverable Terms When Buying Design

Use shared definitions for design deliverables during procurement. Presentations, proofs, editable sources and publishing exports serve different purposes.

Separate presentation from production

A mockup communicates an idea and is not necessarily ready for printing or publication. A technical proof supports a different review. State the purpose of each stage in the proposal. Approval of a visual presentation should not be mistaken for completion of every technical check needed for production.

Define the editable package

Identify fonts, linked images and other dependencies required alongside the working file. Their delivery and usage rights need separate consideration. A filename extension does not prove that the package will open correctly on another computer. Include required software and version information in the handover note.

Count concepts and adaptations separately

Producing different creative directions is not equivalent to resizing one approved idea. List direction, dimensions, language and variants separately so procurement can compare equivalent scopes. When a new request arrives, the affected part of the delivery list will be visible rather than hidden in a general request for design.

Accept the work through practical checks

Opening a file is only the beginning. Can the publisher use it in the intended placement? Does the supplier have enough information to manufacture it? Does the company understand the route for later edits? In a graphic design handover, these answers are more meaningful evidence of completion than the number of files in a folder.