A precise, project-ready Statement of Work in minutes.

How it works

1. 1. Answer a short form. Quick steps — the exact details your document needs.
2. 2. Review your document. Generated free — you see the full preview before paying.
3. 3. Unlock your PDF. One-time payment via Stripe. Professionally formatted, ready to submit.

Free sample

This is the structure and tone every generated document follows — written from your details, not a fill-in-the-blanks template.

STATEMENT OF WORK
Project: Warehouse Inventory Dashboard

This Statement of Work ("SOW") is entered into between Ferrow Systems LLC (the "Provider") and Calder & Voss Distribution GmbH (the "Client").

1. Purpose & Relationship to Master Agreement. This SOW is entered into under and governed by the Master Services Agreement between the parties dated 3 February 2026 (the "Master Agreement"). The terms of the Master Agreement apply to this SOW, and in the event of conflict the Master Agreement prevails except where this SOW expressly states otherwise.

2. Scope of Work. The Client operates three distribution warehouses whose inventory reporting is currently manual. The objective of this project is to deliver a live inventory dashboard for warehouse managers. The Provider will: design the dashboard UX; build the web application integrating the Client's existing WMS API; implement stock-level alerts; and provide deployment support and administrator training.

3. Out of Scope. The following are expressly excluded: changes to the WMS itself, historical data migration prior to 2024, mobile native applications, and ongoing maintenance beyond the 30-day support period. Any work not expressly included in Section 2 is out of scope unless agreed in a written change order.

4. Deliverables & Schedule. (a) Approved dashboard designs — by 10 April 2026; (b) Dashboard deployed to the Client's staging environment — by 22 May 2026; (c) Production deployment and administrator training — by 12 June 2026. Milestone M1 is design approval; M2 is staging sign-off; M3 is production launch.

5. Acceptance. Each deliverable is submitted to the Client for review. The Client has ten (10) business days to accept in writing or reject with specific reasons. Deliverables not rejected within the review period are deemed accepted. Rejected deliverables are corrected and resubmitted for one further review cycle.

6. Fees & Invoicing. Fees are milestone-based: EUR 12,000 on M1, EUR 18,000 on M2, and EUR 12,000 on M3 (EUR 42,000 total), each invoiced on acceptance of the relevant milestone and payable within 30 days.

7. Change Requests. Any change to scope, schedule, or fees requires a written change order describing the change and its impact, signed by both parties before work on the change begins.

8. Term. This SOW takes effect on the date of the last signature below and continues until all deliverables are accepted or the SOW is terminated in accordance with the Master Agreement.

THE PROVIDER
Signature: _______________________
Name: Ferrow Systems LLC
Title: _______________________
Date: _______________________

THE CLIENT
Signature: _______________________
Name: Calder & Voss Distribution GmbH
Title: _______________________
Date: _______________________

Frequently asked questions

What is the difference between an SOW and a service agreement?

A service agreement (or master services agreement) sets the general legal terms of the relationship — liability, confidentiality, IP, termination. A Statement of Work defines one specific project under that relationship: what will be delivered, by when, for how much, and how it gets accepted. Companies typically sign one master agreement and then a new SOW for each project. This tool drafts the SOW either way — referencing your master agreement or standing alone.

Is a Statement of Work legally binding?

Yes — a signed SOW is a contract. When it sits under a master agreement, the two documents are read together, with the master agreement's legal terms governing and the SOW supplying the project specifics. When it stands alone, the SOW itself is the agreement, which is why standalone SOWs benefit from careful drafting. This tool produces a professional document, not legal advice — review it before use, and consult a lawyer for complex engagements.

How specific should the scope of work be?

As specific as you can make it. Most SOW disputes come down to whether something was in scope, so vague phrases like 'website improvements' invite disagreement. Name the concrete activities, systems, and boundaries — and use the out-of-scope section to state explicitly what is not included. A precise scope protects both sides: the client knows what they are buying, and the provider has a defensible basis for change orders.

What are acceptance criteria and why do they matter?

Acceptance criteria are the objective test for whether a deliverable is done — for example, passing an agreed checklist, or written client confirmation within a set review window. They matter because payment and project completion usually hinge on acceptance. A common, fair pattern is a fixed review period after which deliverables are deemed accepted unless the client rejects them in writing with reasons.

Which fee structure should I choose?

Fixed fees suit well-defined projects with a stable scope. Milestone-based payments spread risk across the project and pair naturally with acceptance criteria — the provider gets paid as each stage is accepted. Time and materials fits exploratory or evolving work, ideally with an hour cap so the client's exposure is bounded. Whichever you choose, the change request process handles anything that moves outside the original scope.

Do I need an account or subscription?

No. You fill in the form, pay once ($24), and download your PDF. No account, no subscription, no recurring charges.