How to write a freelance scope of work

1. Separate the goal from the work

The client may want “better onboarding” or “more sales.” Those are goals. Your scope needs to name the work you can actually provide toward them.

For example: “Review the signup-to-dashboard journey and identify friction” describes an audit. “Increase activation by 20%” promises a result that also depends on implementation, traffic, measurement, and other decisions. Only include a quantified outcome when you have explicitly agreed how it will be measured and what responsibility you are accepting.

Write one sentence for the client’s problem, followed by one sentence explaining your contribution. Keep both specific enough that the client can correct a misunderstanding.

2. Make every deliverable inspectable

For each output, specify the item, the limit, and a review check. “Website audit” leaves room for different expectations. “An annotated PDF review of up to five existing desktop screens” identifies an output and a boundary.

A review check describes completion of the work. It should not imply that the client must agree with every professional judgment or that an untested commercial result has already been achieved.

3. Name exclusions and client dependencies

List adjacent work a reasonable client might expect. For an audit, that might include new designs, development, interviews, or live experiments. This is more useful than an extensive list of unrelated things you do not offer.

Then identify the client inputs: access, source materials, selected pages, decision makers, and consolidated feedback. If the work depends on them, the schedule does too.

For each uncertain point, write a question. “Do you need mobile screens included?” is better than quietly assuming that desktop and mobile are the same assignment. Keep suggested assumptions separate from facts the client has already confirmed.

4. Connect the schedule, revisions, and fee

Define the event that starts the clock. “Ten business days after the required inputs are received” is different from “ten business days after the proposal is sent.” Identify feedback windows and whether revisions fit within that period.

State the price basis: fixed fee, time-based work, or an estimate awaiting confirmation. If the fee is USD 2,500 with two equal payments, show USD 1,250 at each milestone. Confirm taxes and expenses rather than assuming they are included or excluded.

For a change request, use a simple sequence: describe the requested change, assess its effect on the fee and schedule, obtain agreement, then begin. A revision to the agreed report and a new round of research are different kinds of work.

5. Use this example as a starting point

This fictional UX project illustrates the structure. Replace the details and resolve the open decisions before using it with a client.

Project: Desktop onboarding UX audit for Northstar Metrics

Purpose
Identify friction between account signup and the first completed dashboard.

Included
Review up to five existing desktop screens selected at kickoff.
Deliver an annotated PDF audit and a prioritized improvement roadmap.
Hold one 30-minute kickoff and one 60-minute findings walkthrough.
Include one consolidated revision round on the audit.

Outside this scope
User interviews, new UI designs, implementation, copywriting, and A/B tests.

Client inputs
Staging access, the agreed screen list, an existing analytics summary,
and one person who consolidates feedback.

Timing
Target: 10 business days from receipt of the required inputs.
Start date and the feedback deadline remain to be agreed.
Confirm whether the revision round is inside that 10-day period.

Fee
Proposed fixed fee: USD 2,500.
50% before kickoff; 50% at final delivery. Tax treatment to confirm.

Review checks
The audit covers the selected screens. Findings identify the relevant
screen or step, explain the issue, and give a recommendation.
The roadmap states priorities and the reasoning behind them.

Changes
For additional screens or new research, agree the added work, price,
and timing in writing before that work starts.

After writing the scope, review the whole offer using the consulting proposal checklist. The scope describes the work; the proposal also explains why that work is the right next step.

Common questions