Scope of Work Template
Updated 2026

Stop losing money on Ui Ux Designer projects.

Without a clear Scope of Work, your 'quick app refresh' will inevitably transform into an endless cycle of unpaid pixel-pushing. Stop letting subjective feedback and 'just one more screen' requests kill your hourly rate and your sanity.

Pro Tip

Include a 'Change Order' clause stating that any requests outside this SOW require a separate estimate and signed approval before work commences.

The Subjective Feedback Loop

Clients may demand endless aesthetic changes because 'it doesn't pop,' unless revision rounds and objective goals are capped.

Responsive Design Bloat

Being forced to design for tablet, mobile, and ultra-wide displays when only 'Desktop' was originally discussed and priced.

Asset Management Burden

Spending dozens of hours sourcing photography, cleaning up low-res client logos, or writing UI copy that wasn't billed for.

Built from real freelance projects

This template is based on real-world scenarios across freelance projects where unclear scope, missing payment terms, and revision creep led to lost revenue. It is designed to protect your time, define expectations, and ensure you get paid.

What is a Ui Ux Designer Scope of Work?

A UI UX Designer Scope of Work is a formal agreement that outlines the specific research, design phases, and technical deliverables of a project. It sets boundaries on revisions, defines the number of screens to be designed, and protects the designer from unpaid work through 'Out of Scope' definitions.

Quick Summary

This UI UX Designer Scope of Work template is an essential tool for freelancers to prevent scope creep and manage client expectations. It details project milestones from user research to developer handoff, specifically capping revision rounds and defining exact screen counts. By clearly outlining what is 'In-Scope' and what is 'Excluded,' designers can protect their time, ensure project profitability, and maintain professional relationships through objective, pre-approved project boundaries and approval processes.

Why Ui Ux Designers need a clear scope of work

For a UI/UX Designer, the Scope of Work is the only thing standing between a profitable project and a 'forever project.' UI/UX is inherently iterative, which clients often mistake for 'infinitely adjustable.' This document transitions you from a service provider to a strategic partner by defining the exact depth of research, the specific number of user flows, and the precise count of high-fidelity screens included in the price. It eliminates the ambiguity of 'good design' by replacing it with objective milestones and agreed-upon deliverables. Without it, you are vulnerable to 'feature creep' where new functionalities are added to the design without additional compensation. A robust SOW protects your boundaries, manages client expectations, and ensures that you are compensated for every strategic decision and visual asset you produce.

Do you need an invoice or a contract?

Invoices help you get paid, but they do not define scope, revisions, or ownership. For most projects, professionals use both a contract and an invoice to protect their work and cash flow. MicroFreelanceHub bundles both into a single link.

Real-world scenario

Alex, a freelance UX designer, was hired to design a 'simple' dashboard. Midway through, the client started asking for a mobile version, an admin portal, and a complete logo redesign. Because Alex had a detailed SOW that explicitly listed '10 Desktop Screens' and 'Excludes Branding Services,' he was able to stop the bleed immediately. He pointed to the SOW and explained that while he could certainly do those tasks, they were 'Out of Scope.' The client, seeing the clear boundaries previously agreed upon, didn't argue. They signed a Change Order for an additional $5,000 to cover the extra screens and branding work. Alex saved his margin and turned a potential conflict into a revenue-generating expansion of the project.

🛡️ What this scope of work covers:

  • User Persona Profiles & Documented User Journey Maps
  • Low-Fidelity Clickable Wireframes (Lo-Fi)
  • High-Fidelity UI Mockups for [X] unique screens
  • Interactive Prototype (Figma/Adobe XD) for Stakeholder Review
  • Design System/UI Kit including typography, color palette, and components
  • Developer Handoff Package (Assets, CSS Specs, and Documentation)

Pricing & Payment Strategy

UI/UX projects should typically be priced on a project-basis rather than hourly to account for the strategic value provided. Structure your pricing around three major milestones: Discovery/Wireframing (30%), Design/Prototyping (50%), and Handoff (20%). Ensure your price reflects the complexity of the user flows—a complex FinTech app with 20 screens should be priced significantly higher than a 20-screen marketing site due to the depth of logic and edge cases involved.

Best practices for Ui Ux Designers

Define Screen Counts

Don't just say 'The App'; specify the exact number of unique templates or screens included.

Formalize Sign-Offs

Require written approval on wireframes before moving to high-fidelity to prevent structural changes late in the game.

READ ONLY PREVIEW

Project Overview

This project involves the UI/UX design and prototyping for [Project Name]. The goal is to create a user-centric interface that aligns with [Business Goals] while ensuring a seamless experience for [Target Audience].

Scope of Work

The designer will execute the following phases:

  • Discovery & Research: Stakeholder interviews, competitive analysis, and user persona development.
  • Information Architecture: Creation of sitemaps and high-level user flow diagrams.
  • Wireframing: Development of low-fidelity skeletal frameworks to define layout and hierarchy.
  • Visual Design: Application of color, typography, and brand elements to create high-fidelity mockups.
  • Prototyping: Building an interactive, clickable prototype to demonstrate transitions and logic.

Deliverables

The following tangible assets will be provided upon completion:

  • User Journey Maps (PDF/Miro).
  • Set of [Number] unique High-Fidelity UI Screens in Figma/Adobe XD format.
  • Reusable UI Component Library (Buttons, Inputs, Navigation).
  • Interactive Prototype link for user testing.
  • Developer Handoff file with CSS specifications and exported image assets.

Timeline & Milestones

The project is estimated to take [Number] weeks, contingent on timely feedback:

  • Milestone 1: Research & Sitemap Approval (End of Week 1).
  • Milestone 2: Wireframe Approval & Prototyping (End of Week 3).
  • Milestone 3: Final UI Design & Handoff (End of Week 6).

Revisions Policy

Each milestone includes up to [Number] rounds of revisions. A 'round' is defined as a consolidated list of feedback provided by the client within [Number] days of a deliverable presentation. Revisions requested beyond this limit or after a milestone has been formally signed off will be billed at an hourly rate of $[Rate].

Out of Scope

The following items are explicitly excluded from this agreement and will require a separate quote:

  • Logo design or brand identity development.
  • Copywriting, content strategy, or data entry.
  • Custom photography, videography, or 3D modeling.
  • Front-end coding (HTML, CSS, React, etc.).
  • Ongoing maintenance or post-launch updates.

Approval Process

Client must provide written approval (email or project management tool) at the conclusion of each phase. Work on the subsequent phase will not begin until the current phase is approved. This prevents structural changes from occurring during the visual design phase.

Ready to use this template?

Create a free account to customize this document, collect e-signatures, and attach a Stripe payment link.

Legal Disclaimer: MicroFreelanceHub is a software workflow tool, not a law firm. The templates and information provided on this website are for general informational purposes only and do not constitute legal advice.

Frequently Asked Questions

How do I handle 'minor' requests that aren't in the SOW?

Track them. If it takes more than 15 minutes, inform the client it falls under the 'hourly overage' rate specified in your SOW.

Should I include accessibility (WCAG) compliance in my SOW?

Yes, specify which level (e.g., AA) you are designing for to avoid liability or unexpected rework later.