UX work has two things a generic contract tends to miss: it produces research and source files that both sides may claim, and it invites endless iteration if the revision terms are vague. A UX designer contract that names who owns the Figma file, caps revisions, and ties ownership to final payment protects you from the two disputes UX projects actually run into. Here is what to put in a UX designer contract, the clauses specific to UX work, and how to get it signed.
What a UX designer contract should include
Every UX contract needs the standard freelance terms, whatever the project.
The parties and project:: you and the client, and the product or engagement covered.
Scope and deliverables:: exactly what you will produce, and what is out of scope.
Timeline and client dependencies:: the schedule, and the client feedback and access you need to hold it.
Fees and payment schedule:: your rate or fee, the deposit, and when each payment is due.
Revisions:: how many rounds are included, and how extra rounds are billed.
Ownership and IP:: who owns the final designs, and when that transfers.
Confidentiality:: how each side handles the other's private information.
Termination and kill fee:: how either party can end the work, and what is owed if they do.
These are the backbone of any freelance agreement, which the essential elements of a freelance contract guide covers in full. What makes it a UX contract is the handful of clauses below.
Key clauses for UX work specifically
Four clauses matter more in UX than in most freelance work.
Ownership of designs, tied to final payment. State that the intellectual property in the final designs transfers to the client only when they have paid in full. Until then, the work is yours. This single clause is your strongest protection against a client who takes the designs and disappears before the last invoice.
Source files and research data. Be explicit about what the client receives: the final delivered designs and a prototype, yes, but do your editable source files, your Figma workspace, and your raw research transfer too? Many designers hand over flattened deliverables and keep working files unless source files are bought separately. Say which it is, so it is never assumed.
Revisions and change requests. Cap the included revision rounds per phase, and define a change request as any new direction after a phase is approved. Without this, UX projects iterate forever, since there is always one more idea to test. Billing changes beyond the cap is what keeps a fixed-fee project from eating your month.
Client dependencies and feedback deadlines. UX work stalls when a client sits on feedback or withholds access to users or systems. Put the feedback turnaround you need in the contract, and state that delays on their side move the timeline and may carry a fee, so their bottleneck is not your unpaid problem.
Get the UX contract signed
A contract only protects you once both sides have signed it, and chasing a printed signature is where projects lose momentum.
Send the contract as soon as the client agrees to your proposal, while the yes is fresh, and pair it with the deposit invoice so signing and paying happen together. FileCurrent sends the contract for online signature and the deposit invoice in one step, so the project is booked the moment the client signs rather than sitting unsigned in an inbox. Electronic signatures are valid and binding for this kind of agreement, which the are digital signatures legally binding guide explains. Once signed, the UX designer invoice template covers billing the work.
Frequently asked questions
What should a UX designer contract include?
The parties and project, the scope and deliverables, the timeline and client dependencies, the fees and payment schedule, revision limits, ownership and IP terms, confidentiality, and termination with any kill fee. On top of the standard freelance terms, a UX contract should be explicit about source files, research data, and revision caps, which are where UX projects run into trouble.
Who owns the designs in a UX contract?
Whoever the contract says, and when. The standard and safest arrangement is that intellectual property in the final designs transfers to the client on full payment, not before. Until the last invoice is paid, the work remains yours. Tying ownership to final payment is a UX designer's strongest protection against non-payment after delivery.
Do I hand over my Figma source files?
Only if the contract says so. Many UX designers deliver the final designs and a prototype but keep their editable source files and raw research unless those are purchased separately. Decide your policy and state it explicitly, since a client will often assume the working files are included. Being clear up front avoids a dispute at handoff.
How do I stop endless revisions in a UX project?
Cap the included revision rounds per phase in the contract, and define anything beyond an approved phase as a billable change request. UX work invites constant iteration because there is always another idea to test, so a clear cap and a change-request clause are what keep a fixed-fee project from consuming far more time than you were paid for.
Can a UX designer contract be signed electronically?
Yes. Electronic signatures are legally valid and binding for freelance design agreements in the US, and they are far faster than printing and scanning. Sending the contract for online signature, alongside the deposit invoice, gets the agreement signed while the client is still enthusiastic, rather than losing momentum to paperwork.
A clear UX contract settles ownership, source files, and revisions before they become disputes. FileCurrent sends your contract for signature and the deposit invoice together, so the project is booked and protected the moment the client signs. $15/month or $129/year. 7-day free trial, no card required.