Design Proposals and Contracts: What to Include and What to Have Reviewed

What a design proposal and freelance contract should include, the usual clauses, how ownership of deliverables is decided, and when to ask for legal review.

info Quick Definition
A design proposal summarizes the problem, scope, deliverables, timeline, price, and conditions the client will approve. A contract records the terms of that work and the rights over the result. The proposal persuades; the contract protects both sides when the conversation is no longer so friendly.

What is a proposal, and what is a contract?

The proposal is the commercial and scope document. It explains what will be done, in what order, over what time, and for how much. There is no formal definition, but practical guides agree it should let the client approve something concrete.

The contract is the agreement that records the terms of work: scope, payments, revisions, ownership of what is delivered, and how it can end. Legal conditions depend on the country, so treat any template as a starting point, not a finished document.

Why does this matter for a junior designer?

Because the contract is the part of the job most often avoided and the one that can cause the most trouble later. A junior who signs without reading can find that the client owns all the material, that revisions are unlimited, or that payment does not arrive on time. Knowing what the document should contain is a way to protect the work.

The proposal is also the first professional impression. A specific, clear document with prices per deliverable communicates an order that clients value.

What should a proposal include?

Zoom, in its guide to graphic design proposals, suggests these sections: discovery (brand, audience, budget, and who approves), an executive summary that opens with the client’s goal, scope with deliverables, design process, a timeline with milestones, prices grouped by deliverable, and a close with proof (a testimonial or portfolio sample), payment terms, and a single next step.

Three tips from the same source are especially useful. First, name what is out of scope, so the client does not assume it is included. Second, limit revisions, for example to two rounds per deliverable, with extra rounds at a separate rate. Third, avoid generic proposals: Zoom warns that recycling the same paragraphs for every client suggests you did not research their brand.

For the step-by-step of writing a proposal inside a freelance project, the article on the freelance design process describes each phase. To estimate effort before setting prices, the article on estimating design work offers a framework.

What clauses does a contract have?

Two commercial sources help for comparison. Designer Daily recommends covering scope (with deliverables, included revision rounds, and exclusions), a payment schedule, a kill fee, intellectual property transfer, and late fees and expenses. It adds as extras the right to disassociate from work modified without your approval, and governing law and venue. Bonsai’s template includes scope, a 25% deposit, a late fee, expenses approved in writing, ownership, and termination with 14 days’ notice.

The templates do not agree on everything. Designer Daily proposes a cancellation fee of 25% of the remaining project fee; Bonsai’s template has no cancellation fee and lets either party end the contract with 14 days’ notice. Compare several before choosing, and adapt whatever does not fit your case.

How is ownership of deliverables decided?

This is the most delicate point. Designer Daily recommends that rights pass to the client only after full payment, and that you keep three protections: your process files (Figma files, sketches, source code), the right to show the work in your portfolio, and the exclusion of licensed fonts, stock imagery, and code libraries. Bonsai’s template follows the same logic: the client receives the work once it is paid in full, and the designer keeps their background intellectual property.

On payments, Designer Daily gives these ranges: 33% to 50% as a deposit at signing, 25% to 40% when a key phase is approved, and 10% to 25% before final files are released. These are ranges from a commercial guide, not sector norms.

In the United States, copyright law (17 U.S.C. §204) makes a transfer of rights invalid unless it is in writing and signed by the party transferring them. And a work commissioned from an outside creator only counts as “work made for hire” if it fits specific categories listed in the law (17 U.S.C. §101) and the parties sign a written agreement saying so. Other countries have different rules; in the United Kingdom, for example, the government states that copyright protection is automatic and needs no registration. So the question of who owns the work depends on where you and the client are.

Ask for it when the contract includes assignment of rights, exclusivity, liability, or indemnification, or when the client brings its own master agreement. A commercial template does not replace a lawyer: Bonsai states that it does not provide legal services or advice. A lawyer who knows your country’s law can review in a few hours what a template leaves open.

Not every proposal needs review. But once a contract touches ownership of the work or exclusivity, the cost of review is usually lower than the cost of a dispute.

When is a formal proposal NOT needed?

  • For very small, repeated jobs with the same client, where a price list and an email with the scope may be enough.
  • When the client has a master agreement you cannot change. Then the proposal must fit the master agreement, not the other way round.
  • When the client refuses to agree on scope in writing. Without a written agreement, any conflict becomes hard to resolve. Designer Daily sums it up: what is not in the signed contract does not count.

Example

Illustrative example: a proposal to redesign the onboarding of an insurance app.

  • Scope: three deliverables: an audit of the current flow, two rounds of screen design, and a test with five people. Out of scope: legal content and development.
  • Price: per deliverable, with the audit and the test as separate line items.
  • Payments: 40% on acceptance, 30% on design approval, and 30% before final files are delivered.
  • Ownership: the client receives the files and a usage license when the final invoice is paid.
  • Review: the contract includes an intellectual property clause. Before signing, the designer asks a lawyer in their country to review it.

With scope and ownership in writing, if the client asks for more screens or wants to reuse the material, there is a document to turn to instead of an argument.

If your work includes AI and you are unsure who owns what is generated, the article on freelancing with AI covers deliverable clauses and outcome-based pricing.

Common mistakes

  • Signing a contract without reading the ownership clauses.
  • Transferring all rights before the final invoice is paid.
  • Reusing one client’s proposal for another without adapting it.
  • Leaving revisions unlimited in the contract.
  • Not naming what is out of scope.
  • Using a template without checking that it fits your country.

Sources

Frequently asked questions

What is a design proposal?
A document summarizing the client’s problem, the scope with its deliverables, the timeline, the price, and the payment terms, which the client approves. There is no formal definition, but practical guides agree on those elements.
What clauses does a design contract have?
Typical ones are scope with the included revision rounds, payments, ownership of deliverables, and termination. Some templates add cancellation fees, late-payment interest, reimbursable expenses, and governing law.
When does ownership of a design transfer?
It depends on the agreement and the country. A Designer Daily guide recommends that rights pass to the client only after full payment. In the United States, the law requires that a transfer of copyright be in writing and signed (17 U.S.C. §204).
What payment percentages do guides suggest?
Designer Daily gives usual ranges: 33% to 50% as a deposit at signing, 25% to 40% when a key phase is approved, and 10% to 25% before final files are released. These are ranges from a commercial guide, not sector norms.
When should you ask for legal review?
When the contract includes assignment of rights, exclusivity, liability, or indemnification, or when the client brings its own master agreement. Commercial templates, such as Bonsai’s, state that they are not legal advice.