What is a UX Design Agreement?

It is used by designers, illustrators, animators and their clients who want the terms recorded before work starts or money changes hands, rather than reconstructed from memory afterwards. Putting it in writing is what turns an understanding into something either side can rely on.

19 details are captured across 6 areas: parties and contact details, scope and deliverables, payment and financial terms, dates, timing and duration, confidentiality and intellectual property, and legal protections and risk. Together they fix what the designer owes the client, measured in screens rather than in adjectives.

Disputes tend to surface around design handover, when one side considers the obligation discharged and the other does not. Most freelance disputes come down to three things: work that grew beyond what was quoted, invoices that were never chased, and a client assuming they own copyright that was never actually transferred.

The preview updates live as you complete each field, so you can review the exact language before downloading it as PDF or Word. Treat the result as a well-organised first draft: sound in structure, but worth an attorney's review where the sums involved are significant or the situation is unusual.

What matters most in a UX design agreement

Fonts and stock assets carry their own licences

The designer cannot transfer rights they do not hold. Make clear the client must license fonts and stock imagery for their own use.

Fix the number of initial concepts

Two or three initial routes, then refinement of one chosen direction, is the standard structure. Unlimited concepts is not a business model.

Cap revisions explicitly

State the included rounds and the hourly rate beyond them. Design work without a revision cap reliably runs at a loss.

When you need a UX design agreement

  • Before the designer starts: Put the UX design agreement in place before anyone relies on it. An agreement signed after work has begun is far harder to enforce on the terms you actually intended.
  • When the arrangement will repeat: For a relationship that runs across several jobs or periods, agree the standing terms once and let each instance sit under them rather than renegotiating from scratch.
  • When ownership of the interface design matters: State who owns what is produced and at what point ownership passes. Without an express written term, ownership usually stays with whoever created it.
  • When sensitive information is shared: Confidentiality terms should be signed before disclosure, not after. Information already shared without protection is very difficult to claw back.
  • When someone else is paying: Where a third party funds or guarantees the arrangement, they should be named and their obligations spelled out. A guarantee that is only implied is not a guarantee.
  • When more than one person is involved: Where several people share the obligation, the UX design agreement should say whether they are liable together, separately, or both. That single word decides who can be pursued for the whole amount.

What to include in a UX design agreement

This generator collects 19 details. Here is what each group covers and why it matters when the document is relied on.

Parties and contact details

Get these right before anything else. A dispute over the interface design is unwinnable if the document names a party that does not legally exist.

Client Name
The full legal name of the client commissioning the work. Use the registered company name rather than a trading name so the party is identifiable if the agreement is ever enforced.
Client Address
The client's registered or principal business address. This is the address used for formal notices, invoices and any legal service of documents.
Contractor Name
The full legal name of the contractor or business performing the work, matching the name on invoices and tax records.
Contractor Address
The contractor's business address for notices and payment correspondence.

Scope and deliverables

Measure the interface design rather than describing it. A scope stated in screens can be checked at design handover; one stated in adjectives cannot.

Project Name
A short reference name for the project so invoices, change orders and correspondence can all be tied together.
Description of Services
What the provider will actually do, described specifically enough that a third party could judge whether it was delivered.
Scope of Work
A precise description of what is included — and, just as importantly, what is not. Scope creep is the leading cause of disputes on service contracts.
Deliverables
The tangible outputs to be handed over, with formats, quantities and acceptance criteria.
Revision Policy
How many rounds of revision are included and what is chargeable beyond that. Without a cap, revisions become unlimited.
Client Approval Process
Who signs off, how long they have to respond, and what happens if they do not respond in time.

Payment and financial terms

Write key figures out in full and name the currency. Where the price depends on a count of screens, record that count as you go rather than reconstructing it at invoice time.

Service Fee
The total fee or rate for the services. State whether it is fixed, hourly or milestone-based, and whether tax is included.
Payment Schedule
When each payment falls due, tied to dates or milestones. A clear schedule is the most effective protection against slow payment.

Dates, timing and duration

Diarise every date in this section on the day the document is signed — particularly any notice deadline, which works exactly once against the party who forgot it.

Effective Date
The date the agreement takes effect. This can differ from the signature date, and it is the date obligations start running from.
Start Date
When performance begins. Tie this to a calendar date rather than a vague trigger such as 'on approval'.
Completion Date
The date by which the work must be finished, and whether that date is a firm deadline or a target.

Confidentiality and intellectual property

Ownership does not pass because money changed hands. If rights in the interface design are meant to move, this section has to say so expressly.

Intellectual Property Ownership
Whether ownership transfers on final payment or the client receives a licence only. Silence usually leaves ownership with the creator, which surprises many clients.
Confidentiality Obligations
The duty to keep information private, who it may be shared with internally, and the standard of care required.

Legal protections and risk

Set a liability cap that reflects the real exposure rather than the fee, and carve out the things that should never be capped.

Termination Notice
How much notice is required to terminate and how that notice must be given.
Governing State
The state whose law governs the agreement. Choose a state connected to the parties or the work, as a wholly unconnected choice may not be respected.

Completing this UX design agreement

Signing and keeping it

Every party named should sign and date, and each should keep their own copy. Electronic signatures are valid for the great majority of agreements — retain the audit trail showing who signed and when.

Reading it as the other side would

Before signing, read the UX design agreement from the counterparty's position and look for anything you would exploit. If you find something, so will they.

Filling in every blank

Unfilled placeholders are read against whoever produced the document. If a field genuinely does not apply, write "not applicable" rather than leaving a gap.

Dates that drive obligations

Use calendar dates rather than relative triggers such as "on approval", which cannot be measured. Dates determine when obligations start, when they end, and when someone is late.

Attaching the signed-off flow diagram

The signed-off flow diagram carries most of the evidential weight here. Attach it as a schedule and refer to it by name in the body, rather than leaving it as an email nobody can find later.

Common mistakes to avoid

  1. No inspection or review window. Give the client a defined period to check the interface design and raise problems, with deemed acceptance after it. Otherwise work sits "under review" indefinitely and payment never falls due.
  2. No mechanism for changes. Things change after signature. A short variation clause — changes in writing, signed by both, priced before they start — costs nothing to include and settles the argument before it begins.
  3. Not planning for new screens appearing after the estimate was given. This is the failure that recurs in this kind of arrangement. Name it in the agreement and say who carries the cost when it happens, because working it out afterwards means negotiating from a weak position.
  4. Late payment with no consequence. If nothing happens when the client pays late, late payment becomes the norm. Interest on overdue sums plus a right for the designer to suspend gives the clause teeth.
  5. Treating design handover as self-evident. State exactly what has to be true for design handover to have been reached, and who confirms it. Without a test, one side thinks the obligation is discharged while the other is still waiting.

How to use this UX design agreement generator

  1. Fill in the form. Fill in the 19 fields, starting with the parties. Have the signed-off flow diagram to hand before you begin, because several of the entries will be taken directly from it. Nothing is sent to a server — the document is assembled in your browser.
  2. Read the preview. Check the preview against the signed-off flow diagram. Where the two disagree, the document is the version that will be relied on, so fix it here.
  3. Download and sign. Export as PDF to sign, or as Word to keep working on it. Store the signed version somewhere both the designer and the client can find it, along with the signed-off flow diagram.

UX Design Agreement — frequently asked questions

Does the client own the rejected concepts too?

Normally no. Standard practice is that only the selected and paid-for design transfers to the client, and unused concepts remain the designer's property to develop elsewhere. If a client wants exclusivity over everything presented, that is a broader buyout and should be priced as one.

What usually goes wrong with a UX design agreement?

New screens appearing after the estimate was given. It is the recurring failure in this kind of arrangement, and it is rarely addressed in the document because both sides assume it will not happen to them. Name it, say who bears the cost, and the negotiation happens now rather than from a weak position later.

Does anything survive after the UX design agreement ends?

Yes. The source files and component library the developers need continues past design handover, and confidentiality obligations normally do too. Anything expected to survive has to say so expressly — an obligation that is merely assumed to continue generally does not.

Which state's law should govern this UX design agreement?

Choose a state with a genuine connection to the parties or the subject matter — where a party is based, or where the work or property is located. A choice with no connection at all may not be respected, and for property or employment the local state's rules will often apply regardless of what the contract says.

Who owns the work produced under this agreement?

Whoever the agreement says owns it — and if it says nothing, the creator generally does. Paying for work does not transfer copyright by itself. If ownership is meant to pass to the client, the assignment clause needs to say so expressly, and it is common to make the transfer conditional on payment in full.

How long do the confidentiality obligations last?

Ordinary commercial information is usually protected for a fixed period of two to five years after the agreement ends, while genuine trade secrets are often protected for as long as they stay secret. Whichever you choose, state expressly that the confidentiality clause survives termination — otherwise the protection ends with the contract.

How is notice properly given under this agreement?

Follow the notice clause exactly: use the stated method, send it to the address named in the agreement, and keep proof of delivery. Notice given informally — a text message, or an email to the wrong person — is frequently challenged, and a defective notice can leave the agreement running on.

Can I reuse the same contract for every client?

You can reuse the structure, but the scope, fee, timeline and deliverables must be rewritten for each engagement. Those are the clauses that actually get litigated, and a copied scope from a previous client is worse than no scope at all.