Flori / Templates

Statement of work template for freelancers and agencies

By the Flori team · Published 2026-10-28 · Updated 2026-10-29

A statement of work (SOW) is a short document that says what you will deliver, by when, for how much, and what counts as finished. Use it before any project that has more than one deliverable or more than one payment. This template covers the eleven sections a small team needs and nothing more.

This template is a starting point, not legal advice; have a lawyer review it for your country or state.

The template

Copy the numbered sections below into a doc. Replace everything in square brackets. Keep each section short.

1. Parties: This statement of work is between [Your business name] ("the Provider") and [Client legal name] ("the Client"), dated [Date]. It sits under the [Master agreement or proposal name and date].
2. Project summary: [Two or three sentences: what the project is and the business reason for it.]
3. Objectives: [One to three outcomes the Client wants, written so you can tell later whether they happened.]
4. Scope of work: The Provider will [list the activities in plain verbs: design, build, write, configure, test].
5. Deliverables: [Numbered list of items the Client receives, each with a format and an acceptance test, for example "Five-page website, live on the Client's domain, passing the checklist in section 8."]
6. Out of scope: The following is not included: [Things people often assume, such as copywriting, photography, hosting, ongoing support, extra languages.]
7. Timeline and milestones: Start date [Date]. Milestones: [Milestone 1, date], [Milestone 2, date], [Final delivery, date]. Dates assume the Client supplies feedback and materials within [number] business days.
8. Acceptance: The Client has [number] business days to review each deliverable and reply with approval or a single consolidated list of changes. No reply counts as approval after [number] days.
9. Fees and payment: [Fixed fee of amount, or rate of amount per hour with an estimate of hours.] Payment schedule: [percent] on signing, [percent] at [milestone], [percent] on delivery. Invoices are due [number] days after issue.
10. Client responsibilities: The Client will provide [logins, content, brand files, a single point of contact] by [date], and will name one person who can approve work.
11. Changes: Work outside section 4 needs a written change request with price and date impact, approved before it starts. [Number] rounds of revisions are included per deliverable; further rounds are billed at [rate].

Add a signature block at the end with name, title, date and signature for each side.

The same template as a table

If you would rather keep it in a spreadsheet or a doc table, use this layout.

What does a completed statement of work look like?

A completed statement of work specifies the project scope, deliverables, schedule, payment terms and acceptance criteria.

Here is a short SOW from a three-person agency, Fieldwork Studio, building a website for a bakery. Names are invented.

1. Parties: Fieldwork Studio and Northwind Bakery Ltd, dated 28 October 2026, under the proposal signed 21 October.
2. Project summary: Redesign the bakery's website so customers can see the menu and order online for pickup.
3. Objectives: Online pickup orders live before the holiday season; menu easy to update by the owner without help.
4. Scope of work: Design six page templates, build them on the Client's existing platform, connect the ordering link, train the owner for one hour.
5. Deliverables: Six approved page designs; staging site; live site on northwindbakery.example; a one-page guide for editing the menu.
6. Out of scope: Photography, copywriting, logo changes, paid advertising, support after the 30-day fix period.
7. Timeline and milestones: Start 2 November. Designs approved 13 November. Staging ready 27 November. Launch 4 December. Dates assume feedback within three business days.
8. Acceptance: Five business days to review each deliverable; two rounds of changes included.
9. Fees and payment: Fixed fee of 6,400 USD: 40 percent on signing, 30 percent at design approval, 30 percent at launch. Net 14.
10. Client responsibilities: Final copy by 20 November; one approver, Dana Cole.
11. Changes: Extra pages are quoted at 450 USD each before any work begins.

How do I use a statement of work template?

Write a statement of work after the proposal is accepted and before work starts, using specific deliverables the client can check.

1. Write it after the proposal is accepted and before work starts. The proposal sells; the SOW pins down the details.
2. Use verbs and nouns, not adjectives. "Five-page website" can be checked. "Modern, polished website" cannot.
3. Fill out of scope first. It is the section that prevents the most arguments, and it is the one people skip.
4. Tie money to milestones. Payment dates that depend on named deliverables keep both sides honest.
5. Name one approver. Three people each approving "sometimes" is how projects stall.
6. Common mistakes: vague acceptance language; no revision limit; dates with no client-side dependencies; leaving the SOW unsigned because "we already agreed on a call".
7. Treat changes as normal. When the client asks for more, send a change request instead of absorbing it. The reasoning is in our guide to scope creep.

Freelancers can shorten sections 1 to 3 into a single paragraph. Agencies running several projects at once should keep the numbering identical across clients so anyone on the team can read any SOW. See how this fits a small team on the agencies page.

How can I keep a statement of work with the project in Flori?

In Flori, a signed statement of work can live as a document linked to the project and client, with deliverables turned into tasks.

Once the SOW is signed, store it where the work happens. In Flori, the signed document can live as a doc linked to the project and the client, and each deliverable in section 5 can become a task with an owner and a due date. If you connect an assistant such as Claude or ChatGPT to your Flori workspace, it can draft the SOW from your deal notes, then submit it for review if you request that flow.

Flori does not do e-signatures, so sign the final version with your usual signing tool and attach the signed copy. The onboarding steps that come right after signing are in the client onboarding template. Plans and pricing are on the pricing page.

FAQ

What is a statement of work? A statement of work is a document that defines the scope, deliverables, timeline, payment terms and acceptance criteria for a specific project. It is usually written after a proposal is accepted and signed by both sides, so there is one agreed description of what will be delivered.

What is the difference between a SOW and a contract? A contract sets the legal relationship: liability, ownership, confidentiality, termination. A SOW describes one project's work and price. Many teams sign one master agreement and then a new SOW per project, so the legal terms stay fixed while the work changes.

How long should a statement of work be? For freelancers and small agencies, one to three pages is enough. Cover the scope, deliverables, out-of-scope items, timeline, fees, acceptance and change rules. Longer documents are only worth it when the project is large, regulated, or involves several vendors.

What is the difference between a SOW and a scope of work? A scope of work is one section inside a SOW: the list of activities and deliverables. A statement of work is the whole document, including timeline, payment, acceptance and responsibilities. People use the terms loosely, so check which one the client actually expects.

Do I need a SOW for a small project? Yes, but keep it short. Even a half-page listing deliverables, price, dates and revision limits prevents most misunderstandings. If the work is a single task for a single fee, an email the client confirms can serve as a minimal SOW.

Can I sign a SOW inside Flori? No. Flori does not offer e-signatures. Sign with the tool you already use, then store the signed document in Flori, linked to the project and client, and turn the deliverables into tasks.