Skip to main content

What a deliverables clause should include in freelance contracts

A strong deliverables clause names each artifact with a format, a quantity, and — critically — an exclusion list. If it's not named, it's not included. Exclusions do the real work: they prevent adjacent 'of course you'll also do X' asks from feeling like they're part of the original scope.

Anatomy of a strong deliverables clause

Named deliverables
Each artifact you're producing, listed individually with a quantity. Not 'a brand system' — specifically 'one primary logo, one secondary logo mark, a three-color palette, one primary typeface pairing, and a six-page brand guide PDF.' Granularity here prevents ambiguity later.
Format specification
For each deliverable, the file formats you're handing off. 'Logo' is ambiguous — 'logo delivered as master .ai and production .svg, .png (1x/2x/3x), and .pdf' is specific. Formats are where a lot of scope creep hides: clients will ask for formats you didn't list, and each one is a new deliverable.
Exclusion list
An explicit 'not included' list covering the obvious adjacent asks. For a brand engagement this might be: social graphics, email templates, presentation templates, motion versions, app icons. Naming exclusions makes the 'of course you'll do X' conversation a one-liner rather than a negotiation.
Acceptance criteria
How you'll know a deliverable is done. Usually: 'Deliverables are considered accepted upon written approval from [approver], or upon seven days of silence following delivery.' Without acceptance criteria, deliverables stay in an undefined 'almost done' state indefinitely, which is where revision-round inflation lives.
Handoff mechanics
Where files live (Dropbox, Google Drive, Figma, GitHub), who gets access, and how long you'll host the files. Most freelance contracts over-commit to indefinite file hosting; name a specific window ('files will be available in the project folder for 90 days post-delivery') so you're not maintaining an archive forever.

Example language

Drop this into your contract and adapt the bracketed placeholders.

Deliverables. The following deliverables are included in this engagement:

1. One (1) primary logo, delivered as master .ai/.fig, production .svg, .png at 1x/2x/3x resolutions, and a .pdf reference sheet.
2. One (1) secondary logo mark, delivered in the same formats as the primary logo.
3. One (1) color palette document with hex, RGB, and CMYK values.
4. One (1) typeface pairing recommendation with commercial licensing notes.
5. One (1) six-page brand guide PDF covering logo usage, color, type, and spacing.

Not included: social media graphics, email templates, presentation templates, animated logo variants, app icons, favicons, merchandise artwork, or any deliverable not explicitly named above. Additional deliverables will be quoted as change orders.

Deliverables are considered accepted upon written approval from [Named Approver], or upon seven (7) calendar days of silence following delivery. Final files will be available in the project folder for ninety (90) days post-acceptance; archival after that window is a separate retainer.

Common mistakes

  • Listing deliverables as categories instead of specific artifacts ('a brand package' vs. 'one primary logo, one secondary mark, …'). Categories are negotiable; specific artifacts are not.
  • Omitting file formats. 'Delivered as a logo' is not a deliverable — 'delivered as .ai, .svg, .png at three resolutions' is.
  • Skipping the exclusion list. Without it, every adjacent ask ('a matching favicon, an app icon, a social avatar') will feel like a reasonable inclusion to the client.
  • No acceptance criteria. Deliverables linger in an 'almost accepted' state while revision rounds quietly expand.
  • Promising indefinite file hosting. Clients will come back 18 months later asking for a file you haven't thought about; you're not obligated to maintain a personal archive.
  • Not naming quantities. 'Social media templates' is one deliverable to the client and five to you; specify 'three (3) social media templates at the defined post sizes' to prevent expansion.
Settled reads your contract and gives you the exact verdict for this situation — try it free →

Frequently asked questions

How specific should my deliverables list be?+

As specific as the deliverable needs to be to avoid ambiguity. For a logo: named files in named formats. For a website: named pages, named templates, named integrations. The rule of thumb: if two reasonable people could disagree on whether something is part of the deliverable, the list isn't specific enough.

Should I list exclusions explicitly, or just let the 'not included' stand implicit?+

Always explicit. The implicit exclusion — 'if it's not listed, it's not included' — is legally defensible but practically weak. Clients read the deliverables list and mentally add what they expect. An explicit exclusion list is a forcing function: it makes the client acknowledge, at signing, that these specific things are not included.

What counts as acceptance of a deliverable?+

Written approval is cleanest — an email or message explicitly saying 'approved.' Silence after a stated window (five to seven days is standard) also counts as acceptance, and is important to include because clients who go quiet can otherwise block you from closing a deliverable and getting paid on milestones.

The client wants me to add a deliverable mid-project. How do I respond?+

Point to the deliverables list and the exclusions, and offer a change order with the new deliverable priced out. The change order doesn't need to be formal — a one-paragraph email with the deliverable, the fee, and the timeline, signed off in reply, is enough. Do not start work until the change order is accepted in writing.

What if the client asks for a file format I didn't list?+

Check whether providing it is trivial (exporting an existing file at a new size) or substantive (producing a new file, such as a native motion version of a static logo). Trivial format asks are usually reasonable to absorb as goodwill. Substantive format asks are new deliverables and should be quoted.

How long should I keep delivered files available to the client?+

A named window, not forever. Ninety days post-delivery is common for creative work; longer windows (one year) are reasonable for long-term engagements like retainers. If the client needs indefinite archival, that's a separate, recurring fee — not a silent obligation.

Related reading

Answer scope creep from your actual contract — not a template.

Settled reads your contract and the client's request, gives you a verdict (In Scope / Out of Scope / Ambiguous), and drafts the email grounded in your specific clause.

Try it free →Read the scope creep guide