Free UI/UX Design Contract Template
A UI/UX design contract covers deliverables, payment and revision rules, ownership, portfolio use, liability limits, and how the engagement ends.
Share template
UI drift creeps in, squads ship their own versions of the same patterns, and then a design system turns into a file nobody follows. The UI/UX design contract puts the rules in writing for a design system audit, so the handoff doesn’t depend on daily policing, and the buyer can point to one agreement when consistency starts slipping.
The contract starts with This is how I will deliver and What you get, so the client reads the delivery approach and the audit outputs before money comes up. Payment and Changes spell out staged invoicing, what counts as a revision, and what happens when scope expands after work starts, then Who owns what and Portfolio cover IP, reuse of methods, and what can be shown publicly. The last sections, Limits and Ending the project, name the boundaries, what blocks delivery, and how handover works if either side ends the engagement.
- This is how I will deliver Describes the delivery approach for the design system audit and the shared goal of stopping drift across squads.
- What you get Lists the audit deliverables, what you need access to, and where any UI kit or component library work becomes a separate phase.
- Payment States project pricing in OMR, staged invoicing, due dates, and what happens if an invoice goes overdue.
- Changes Defines a revision, ties revision rounds back to the proposal, and covers pricing and approval for extra rounds or new deliverables.
- Ending the project Explains written notice, a reasonable notice period if none is set, and handover and access removal after final payment for completed work.
Once the terms match your work, you send the contract and the client signs online, leaving you with an agreed scope, change rules, and a signature to point back to if priorities shift mid-audit.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What this contract contains
| Part | What it covers |
|---|---|
This is how I will deliver | Explains how the design system audit gets delivered and what “consistent” means in practice, so teams have one agreed direction to follow. |
What you get | Lists the audit outputs, the access you need to base the work on, and what gets quoted as a separate phase if the scope moves into a UI kit or library build. |
Payment | Covers staged invoicing tied to the proposal, when invoices are due, and when work pauses if an invoice goes overdue. |
Changes | Defines what counts as a revision and how feedback needs to arrive, then covers written approval and pricing for scope changes after work starts. |
Who owns what | States what the client owns in the deliverables versus what stays yours in methods and templates, and flags licensing needs to raise before the start. |
Portfolio | Explains what parts of the finished work can be shown, with options like redaction, waiting for launch, or approval on the exact slice. |
Limits | Sets expectations on blockers like access and decisions, positions the audit as guidance rather than a guarantee, and limits responsibility to fixing deliverables or refunding the relevant portion. |
Ending the project | Explains how either side can end the engagement, what happens to partially completed work after final payment, and when access gets removed after handover, with a Signature at the end. |
Who it is for
Product design and design systems consultants doing design system audits for banks, telcos, SaaS teams, and internal product groups with multiple squads shipping UI.
Questions about this contract template
What should a UI/UX design contract include for a design system audit?
A UI/UX design contract for a design system audit should cover deliverables, payment timing, revision rules, ownership of outputs, portfolio permissions, liability limits, and how the project ends. This template includes sections for each of those, written for an audit engagement rather than an open-ended retainer.
How do you define revisions on a design system audit deliverable?
This contract defines a revision as one collected set of comments for a checkpoint, delivered in one message or one annotated file. The contract also says decisions still need written notes, and extra rounds or new deliverables get priced and approved in writing before the work continues.
What happens if the client pays late during a UI/UX project?
The Payment section says invoices are due within the timeframe stated on the invoice. If an invoice goes overdue, the contract pauses handover and further work until the account is up to date, and then confirms a revised schedule in writing if needed.
Who owns the design system audit outputs and the underlying methods?
The contract gives the client ownership of the audit documentation and agreed exports created for them. The consultant keeps ownership of working files, templates, checklists, and methods, even if parts appear inside the deliverables, while any edits made inside the client’s own tools live in the client’s accounts.
Can the consultant show the work in a portfolio after a design system audit?
The Portfolio section allows showing the finished work as an example, usually as a small and careful slice like a redacted summary or token naming example. The contract also offers options like waiting for launch, removing identifiers, or getting approval on what gets shown.
How do you end a UI/UX consulting project and handle handover?
The contract allows either side to end the project with written notice, using a proposal-defined notice period or a reasonable notice if none is set. After final payment for completed work, the contract says the consultant hands over the current state of deliverables and removes access once handover is confirmed.
Start free today
Your entire business, one login away
No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.
No credit card required
