The Deliverables List That Saves Your Freelance Butt

Picture this: you send the final files, hit “invoice,” and feel that tiny rush of freedom. Two hours later, your client emails: “Love it! Can you also add three extra pages, a social media kit, and maybe a quick video? That was part of the project, right?” If your stomach just dropped, you’re not alone. A fuzzy deliverables list is how scope creep tiptoes into freelance projects and quietly eats your time, energy, and profit. The good news? A clear, boring-on-purpose deliverables section in your contract can stop most of that drama before it starts. In this guide, we’re going to walk through what a deliverables list can look like in real freelance contracts, from design and writing to development and consulting. Not theory, but actual wording and structures you can borrow, tweak, and make your own. We’ll talk about how detailed you really need to be, how to handle “small” extras, and how to write things so future‑you doesn’t have to argue with a client about what “a few revisions” means. By the end, you’ll be able to open your next project proposal and confidently spell out what’s included, what’s not, and what costs extra—without sounding like a robot or a lawyer.
Written by
Taylor
Published

Why your deliverables list is your quiet bodyguard

A lot of freelancers obsess over their day rate or project fee and then toss in a vague line like “Deliverables: website redesign.” That’s like signing a lease that just says “You can live here.” It sounds fine… until something goes wrong.

The deliverables section is where you:

  • Draw the line between this project and nice-to-have extras
  • Turn fuzzy conversations into concrete promises
  • Give yourself something to point to when a client starts asking for “one more quick thing”

When it’s written clearly, it doesn’t just protect you. It also calms your client. They can see what they’re getting, when, and in what format. Less guessing, fewer panicked emails.

Take Mia, a freelance brand designer. She used to write “Logo + brand kit” in her contracts. Simple, right? Her last project with that wording spiraled into six logo concepts, three color palettes, and endless file exports. Now her deliverables list spells out exactly how many concepts, which file types, and how many revision rounds. Same creative work, totally different experience.

Let’s walk through how to do that in your own contracts, step by step, with real examples you can adapt.


How specific should a deliverables list be, really?

Short answer: more specific than feels comfortable.

If you’re thinking, “But my clients trust me, do I really need all this detail?”—yes. Because the detail isn’t about mistrust. It’s about expectations. You and your client can both be honest and still imagine very different things when you say “website” or “campaign.”

A good deliverables list usually covers:

  • What you’re delivering (type of work)
  • How many (pages, concepts, posts, screens, etc.)
  • In what format (PDF, Figma, Word, Google Docs, MP4…)
  • How many revisions (and what counts as a revision)
  • What’s explicitly excluded (and available at extra cost)

You don’t have to write a novel. You just need enough detail that a neutral third party could read it and understand what you agreed to.


Common structure for a deliverables list in freelance contracts

You can keep the structure simple. In most project-based contracts, the deliverables section looks something like this:

Deliverables
Contractor agrees to provide the following deliverables to Client as part of this Project. Any work not listed below will be considered out of scope and may require a separate agreement and additional fees.

Then you break it down by category. For example, if you’re a designer:

  • Brand Strategy
  • Visual Identity
  • Collateral

If you’re a writer:

  • Strategy & Research
  • Core Copy
  • Supporting Assets

We’ll get into concrete wording in a second, but that basic structure—intro sentence plus grouped items—works across most freelance fields.


Deliverables list examples for freelance designers

Design projects are scope creep magnets. “Just one more size,” “just one more format,” “just a quick extra version for print”—you know the drill.

Brand identity project

Imagine you’re doing a brand identity project for a startup. Instead of writing “Logo + brand kit,” you might write:

Contractor will deliver a complete visual identity package for Client’s brand, including:

Logo Design
• Two (2) initial logo concepts based on approved creative direction
• Up to two (2) rounds of revisions on one selected concept
• Final logo files in PNG, JPG, SVG, and vector PDF formats (full color, black, and white versions)

Typography & Color
• Primary and secondary typeface recommendations (up to three (3) typefaces total)
• Primary color palette (up to five (5) colors) with HEX and RGB values
• Secondary palette (up to three (3) supporting colors)

Brand Guide
• One (1) brand style guide (up to 15 pages) in PDF format, covering logo usage, color, typography, and basic do’s/don’ts.

Notice how this quietly answers questions before they’re asked: how many concepts, how many revisions, how long the guide is, which file types are included.

Mia, the designer I mentioned earlier, also added a simple exclusion line: “Additional logo concepts, alternate lockups, or extended brand guidelines (e.g., social templates, packaging) are not included and will be quoted separately.” That single sentence saved her hours.

Website design project

For a website design project, a vague “Homepage + 4 pages” can turn into a 30-page monster. Instead, you might say:

Contractor will provide UI/UX design for Client’s marketing website, including:

Site Map & Wireframes
• One (1) site map for up to six (6) unique page types
• Low-fidelity wireframes for up to six (6) unique page layouts

Visual Design
• High-fidelity desktop and mobile designs for up to six (6) unique page layouts (e.g., Home, About, Services, Blog Listing, Blog Post, Contact)
• Up to two (2) rounds of revisions per page layout

Handoff
• Final design files delivered via Figma (or similar agreed tool)
• Exported assets (icons, images) as PNG/SVG as appropriate.

If you don’t do development, you add a clear line: “Website development, coding, or implementation in any CMS (e.g., WordPress, Webflow, Squarespace) is not included in this agreement.”


Deliverables list examples for freelance writers and content creators

Writing seems simple until a client thinks “blog post” means a 3,000-word SEO masterpiece with custom graphics and social posts… for the price of a 600-word article.

Blog content package

Let’s say you’re creating a monthly blog package. Instead of “4 blog posts per month,” you might write:

Contractor will provide ongoing blog content for Client’s website, including:

• Four (4) blog articles per calendar month
• Approximate length: 800–1,000 words per article
• Basic SEO optimization (one primary keyword per article, meta title, meta description, H1/H2 headings)
• Up to one (1) round of revisions per article based on consolidated Client feedback
• Delivery in Google Docs format by the last business day of each month.

Then you protect yourself with a quiet boundary:

The following are not included: custom graphics, stock photo licensing, uploading to CMS, formatting in CMS, or ongoing performance monitoring. These services can be added under a separate agreement.

Website copywriting project

For a one-time website copy project, you might specify:

Contractor will write conversion-focused website copy for Client’s new website, including:

• Copy for up to five (5) core pages: Home, About, Services, Pricing, Contact
• Approximate word count: up to 700 words per page
• One (1) 60-minute kickoff call and one (1) 30-minute review call
• Up to two (2) rounds of revisions per page based on consolidated feedback
• Delivery in Google Docs format.

Jared, a freelance copywriter, learned the hard way that “unlimited revisions” is basically an invitation to rewrite the same headline twenty times. His new rule: revisions are clearly limited, and any changes after sign-off are treated as a new mini-project. His contract simply says, “Revisions requested after written approval of copy will be scoped and billed separately.” Calm, clear, no drama.


Deliverables list examples for developers and tech freelancers

Development work can get messy fast if you don’t define what “done” looks like. Is QA included? Browser testing? Ongoing bug fixes? Six months of support?

Web development project

For a marketing website build, your deliverables might say:

Contractor will develop and launch a marketing website for Client, including:

Development
• Custom WordPress (or chosen CMS) theme based on approved designs provided by Client
• Implementation of up to six (6) unique page templates
• Responsive layout for modern desktop and mobile browsers (Chrome, Safari, Firefox, Edge; latest two versions)

Content & Setup
• Population of provided copy and images for up to 20 total pages
• Setup of basic contact form with email notifications
• Connection to Client’s existing Google Analytics account (if access provided)

Testing & Launch
• Basic QA testing on major browsers and mobile devices
• One (1) round of bug fixes reported within 14 days of launch
• One (1) 60-minute handoff call.

Then you spell out what support looks like:

Ongoing maintenance, feature enhancements, hosting, security monitoring, and support beyond the 14-day post-launch period are not included in this agreement.

App or feature development

For a smaller feature build, you might get even more specific:

Contractor will develop a login and user profile feature for Client’s existing web application, including:

• User registration, login, and logout functionality
• Password reset via email
• User profile page with editable fields: name, email, profile photo
• Server-side validation and error handling for all fields
• Integration with existing database schema as documented by Client
• Up to one (1) round of bug fixes reported within 30 days of deployment.

That “editable fields” line? That’s the difference between a tight feature and a never-ending wishlist.


Deliverables list examples for consultants and strategists

Strategy work can be even fuzzier than creative work. If you’re not careful, a “strategy project” turns into “ongoing support forever.”

Marketing strategy engagement

For a three-month marketing strategy project, you might write:

Contractor will provide marketing strategy services for Client over a three (3) month period, including:

Discovery & Research
• One (1) 90-minute kickoff workshop (remote)
• Review of up to five (5) existing marketing assets (e.g., website, sales deck, current campaigns)

Strategy Deliverables
• One (1) written marketing strategy document (approximately 15–20 pages) covering target audience, positioning, messaging pillars, and channel recommendations
• One (1) 90-day high-level content calendar (Google Sheets)
• One (1) slide deck summary (up to 20 slides) for stakeholder presentation

Meetings & Support
• Up to three (3) one-hour review/feedback calls during the project period
• Email support for clarifying questions (48-business-hour response time).

Then, again, the boundary:

Implementation of the strategy, hands-on campaign management, ad account setup, and content creation are not included in this agreement.

Sam, a marketing consultant, used to “just hop on a quick call” whenever a client asked. His deliverables list now caps the number of calls and clearly labels anything extra as billable. He doesn’t feel like the bad guy; he just points to the contract and offers to scope an add-on.


How to handle revisions and “small tweaks” without losing your mind

Revisions are where a lot of freelancers quietly bleed profit. The client says “just a few tweaks,” and suddenly you’re doing a full rewrite.

You don’t have to be harsh about it, but you do need to be specific. A few practical moves:

  • Set a number of rounds, not “unlimited.” Two rounds is common. One round for smaller items.
  • Define what a round is: all feedback collected and sent at once.
  • Tie revisions to the scope: changes that significantly alter the original brief are new work.

In your deliverables list, you might add a simple clause like:

A “revision round” is defined as a consolidated set of change requests submitted by Client in a single document or email. Substantial changes to the agreed scope (e.g., new pages, new features, or new messaging directions) are not considered revisions and will be scoped and billed separately.

It sounds formal, but it saves you from “Oh, and one more thing…” for weeks.

If you want more background on contracts and scope, there are some helpful small business resources from the U.S. Small Business Administration (SBA) at sba.gov, and general contract basics from the Library of Congress at loc.gov.


What about timelines and milestones—do they go with deliverables?

You can keep timelines in their own section, but pairing them with deliverables often makes things clearer.

For example:

Timeline & Milestones
• Week 1: Discovery call and research (no deliverables)
• Week 2: Draft of Home and About pages
• Week 3: Draft of Services and Contact pages
• Week 4: Revisions and final delivery.

Or you can attach deadlines directly to items:

Final logo files will be delivered within ten (10) business days of Client’s approval of the selected logo concept.

Either way, your deliverables list becomes more than a shopping list; it becomes a roadmap.


Simple phrases that make your deliverables list way stronger

If you only tweak a few lines in your next contract, make them these:

  • “Up to [number] …” instead of open-ended promises
  • “One (1) round of revisions” instead of “revisions”
  • “Not included in this agreement” for things you might offer, but not here
  • “Will be scoped and billed separately” instead of “not possible”

These tiny phrases keep your tone friendly while keeping your boundaries clear. You’re not saying “no”; you’re saying “yes, for an additional fee.”


Quick FAQ about deliverables lists in freelance contracts

Do I really need this level of detail for small projects?

Honestly, yes—just scaled down. Even for a $300 project, one or two clear sentences about what’s included and how many revisions you offer can save you from doing double the work. You don’t need a ten-page contract, but you do need clarity.

What if a client pushes back and says it’s too rigid?

That’s usually a sign they’re used to getting a lot of unpaid extras. You can explain that the detail protects both of you and that anything outside the list can be added as a separate mini-project. Clients who respect your boundaries tend to respect your work too.

Can I use templates for deliverables lists?

You can absolutely start from templates—as long as you customize them to the specific project. Copying a generic “design package” description and slapping it on every job is how you end up promising things you never meant to include.

For general contract and small business guidance, the SBA at sba.gov and some university legal clinics (for example, Harvard Law School’s clinical programs) offer helpful starting points.

Should I list what’s not included, or is that overkill?

It feels like overkill until you get burned. A short “Not included” paragraph can head off misunderstandings about things like ongoing support, file exports, source files, or implementation work. Think of it as future-you’s favorite safety net.

Where should the deliverables list live: proposal or contract?

Ideally, both. Many freelancers put the detailed deliverables in the proposal and then either attach that proposal to the contract or copy the relevant section into a Statement of Work (SOW) that’s referenced in the contract. The key is that the client signs something that clearly includes the list.


If you take nothing else from this, let it be this: your deliverables list isn’t a boring afterthought. It’s the part of your freelance contract that quietly guards your time, your income, and your sanity. Write it like you’re explaining the project to a smart stranger who wasn’t on any of the calls—and your future self will be very, very grateful.

Explore More Project-Based Contracts

Discover more examples and insights in this category.

View All Project-Based Contracts