What is a UI 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.

There are 19 fields here, grouped into 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. Each is a term that causes argument when left unstated, which is why the generator asks for it rather than leaving a gap in the document.

The recurring failure in this kind of arrangement is new screens appearing after the estimate was given. 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.

Fill in the form and the UI design agreement assembles as you type, so you can read the finished wording before you download it. The draft is a starting point built on standard contract structure — it is not legal advice, and for a high-value or unusual arrangement it is worth having an attorney check it against the rules in your state.

What matters most in a UI design agreement

Source files are a separate deliverable

Layered working files are often withheld or priced separately from flattened final artwork. Whichever you choose, say so — clients frequently assume they get everything.

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.

When you need a UI design agreement

  • 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 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 a date cannot move: Fixed-date commitments need cancellation and postponement terms agreed upfront, because there is no opportunity to put things right afterwards.
  • When money changes hands: Record what the client owes, when each screen falls due, and what follows a late payment. These are the clauses relied on most often and left vague most often.
  • When the source files and component library the developers need has value: Where something is still owed after design handover, that obligation needs its own words. Anything expected to survive the end of the agreement has to say so.
  • When the parties are in different places: Naming the governing law and the forum in advance prevents a costly preliminary fight about where any dispute is even heard.

What to include in a UI 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

Everything else in the document hangs off these names: the designer carries the obligations, the client carries the payment, and both need identifying precisely enough to be found later.

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

This is the section that decides arguments. Describe the interface design in screens and against the signed-off flow diagram, so that whether it has been delivered is a question of fact rather than opinion.

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

Payment terms are relied on more often than any other clause and left vague more often than any other clause. State the amount, the trigger, the deadline and what follows a late payment.

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

Where the designer depends on the client for something, say what happens to these dates when it arrives late. Otherwise the delay attaches to the wrong party.

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

Confidentiality obligations should outlive the agreement. State that expressly here, because protection that ends with the contract is protection at exactly the wrong moment.

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

Naming the governing law and the forum here avoids a preliminary fight about where a dispute over the interface design is even heard.

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 UI design agreement

Getting the numbers right

Write key figures out in full where the amount is central, and state the currency if either party is outside the country. Both are cheap precautions against an expensive misunderstanding on a UI 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.

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.

Keeping the version straight

Date the document and mark superseded drafts clearly. Two unlabelled versions in circulation is a surprisingly common cause of genuine, honest disagreement.

Making the counts checkable

Where the price depends on screens, keep a contemporaneous record as they are delivered. A count reconstructed at invoice time invites a challenge that a running record would have prevented.

Common mistakes to avoid

  1. No route out. Agree how the arrangement ends while the designer and the client still get on. Exit terms negotiated during a dispute rarely favour anyone, and they cost far more to settle.
  2. Pricing without a unit. Quote against a defined number of screens. Where the price is a single figure covering an undefined quantity, every additional request looks free to the client and unpaid to the designer.
  3. Verbal instructions on top of a written contract. Once instructions start being given by phone or in passing, the written agreement stops describing the arrangement. Confirm changes in writing the same day.
  4. Keeping no running record. Track what is actually delivered as you go, screen by screen. Reconstructing the position at invoice time invites a challenge that a contemporaneous record would have prevented.
  5. Letting the agreement lapse quietly. Where the arrangement rolls on, diarise the notice deadline the day it is signed. Renewal clauses work exactly once against the party who forgot them.

How to use this UI design agreement generator

  1. Fill in the form. Enter the 19 details requested. Where an entry depends on a count — screens, dates, amounts — put the number in rather than a description of it. Nothing is sent to a server — the document is assembled in your browser.
  2. Read the preview. The preview updates as you type and is editable, so you can adjust the wording before downloading — useful where new screens appearing after the estimate was given needs a sentence of its own that the standard clauses do not cover.
  3. Download and sign. Download in either format and circulate for signature. Diarise the dates the document creates, particularly anything that has to happen before design handover.

UI 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.

Does anything survive after the UI 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.

When is a UI design agreement treated as complete?

At design handover — but only if the document says what has to be true for that point to have been reached and who confirms it. Without a test, the designer considers the obligation discharged while the client is still waiting, and neither reading is unreasonable on the wording.

Which state's law should govern this UI 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.

Does this work for international clients?

The structure does, but add a governing law and jurisdiction clause naming which country's courts decide disputes. Also confirm payment currency and who absorbs transfer fees, as these are common friction points on cross-border work.