Statement of Work by Common Paper
The Common Paper Statement of Work (SOW) is designed to define deliverables, timelines, and pricing for a specific project under a master agreement, giving both parties clarity on scope while relying on the underlying contract for legal terms. It is part of Common Paper’s widely trusted library of open, lawyer-vetted standard agreements.
How to set up an agreement
In the section titled “SOW and Agreement”, input details about the Professional Services Agreement you’re using. This SOW is designed to work with the Common Paper Professional Services Agreement.
Review each variable on the Cover Page and fill in your details. Don’t forget to enter your company’s information in the signature block at the end.
Delete any optional variables, choices, or details that do not apply to you.
Delete all [informational text].
Remove this first page.
Send to your counterparty for review and signature.
Professional Services Agreement
SOW
The key business terms of this SOW are as follows:
SOW and Agreement | This SOW [sow number] (“SOW”) incorporates the Agreement with a Key Terms Effective Date of [key terms effective date] between [provider name] and [customer name]. If there is any inconsistency between this SOW and the Agreement, this SOW will control. |
Services | [enter a description of the services to be performed under this sow. include details such as key individuals, overall project timeline, milestones, etc.] |
Deliverables | [Drafting note: Optional variable. If the Services include creating Deliverables, define the Deliverables here. If the SOW does not include Deliverables, delete this entire row.] The Deliverables are: [define the deliverables that will be owned by customer under this sow.] [Drafting note: use the options below to add details about deliverables. these are all optional and can be removed if not applicable. the first option allows deliverables to include work product. the second option allows you to attach specifications to the sow. the third option sets up rejection and resubmission timeframes.] [ ] In addition to completed projects, Deliverables include in-progress but not complete drafts or components of Deliverables and their associated intellectual property. [ ] Deliverables will meet the attached specifications. [ ] Deliverables are subject to the acceptance process in Section 1.4 with the following details: |
Time of Assignment | [Drafting note: If the Services include Deliverables, pick when IP assignment happens. Delete the one that doesn't apply.] ( ) Customer owns Deliverables as they are created. ( ) Customer owns Deliverables upon payment of associated Fees. |
Third-Party Materials | [Drafting note: If the Services include Deliverables, pick whether Third-Party Materials can be included in the Deliverables. Delete the one that doesn't apply.] ( ) No Third-Party Materials will be incorporated into the Deliverables. ( ) Third-Party Materials will be incorporated in the Deliverables. [ ] Provider will procure Third-Party Materials. [ ] Customer will procure Third-Party Materials. |
Fees | [describe fees, whether hourly, by project, by milestone, etc. also include any pass-through or fractional charges such as for tooling or third-party license fees.] [Drafting note: Delete the travel and expense option if not applicable.] [ ] Travel and expenses: [describe or attach travel and expense policy.] |
Payment Period Time frame for Customer to pay invoices | [fill in payment terms, e.g., 30 days from customer’s receipt of invoice] |
Invoice Period How frequently Provider sends invoices | [fill in cadence of sending invoices, e.g., month, quarter, upon acceptance, after each milestone, etc.] |
SOW Date The date this SOW begins | [ x ] Date of last signature on this Cover Page [ ] [fill in custom sow date] |
SOW Term How long this SOW lasts | [Drafting note: Choose and customize one and delete the other.] The SOW Term begins on the SOW Date and ends: [ x ] [# ] [ days, weeks, months, year] after the SOW Date [ ] [fill in custom end date] |
Customer Obligations | [fill in customer's obligations, e.g., identifying a single point of contact, geographic limitations on use of deliverables, etc.] |
Other Changes to Standard Terms Changes that apply for this SOW only | [Drafting note: Optional variable. If no changes to the Standard Terms, delete this entire row.] [fill in] |
By signing this Cover Page, each party agrees to enter into this SOW as of the SOW Date.
PROVIDER: [provider name] | CUSTOMER: [customer name] | |
Signature | ||
Print Name | [provider print name] | [customer print name] |
Title | [provider title] | [customer title] |
Notice Address | [provider notice address] | [customer notice address] |
Date |
5.0 out of 5 on Google
Read reviewsAs seen in
United States note
This version is drafted for US law generally. Contract, employment and consumer rules vary by state — for example on non-competes and at-will employment. Tell GitLaw which state applies and it adjusts the draft.
Frequently asked questions
A template isn't binding on its own - like any contract, it becomes binding once it's properly completed and signed. Templates in our curated library are professionally drafted for US or UK law; review any template before you sign it.
Yes. Chat with GitLaw to edit any section, or make changes directly in the editor.
Yes, read about team plans here.
Describe what you need in the chat and GitLaw will draft it for you.
Templates in our curated library are professionally drafted for US or UK law. The wider library comes from the GitLaw community and public sources - a solid starting point, but check any template fits your situation before you rely on it.
Mostly US and UK law. Some templates use general commercial terms that work across jurisdictions, and many note which law they're written for.
It depends on the situation. Templates work well for routine business agreements. For anything involving significant money, complex IP, employment, or areas you're unsure about, it's worth getting professional advice before you sign. GitLaw provides templates and tools, not legal advice.
Open any template in GitLaw and describe the change you want in the chat — 'make clause 4 mutual' or 'add a 30-day notice period', for example. GitLaw drafts the revised language and shows it as a suggested edit. You accept, reject, or keep editing from there.
Yes. Upload a Word, PDF, or Markdown file and GitLaw will open it in the editor. You can review, edit, or chat with GitLaw about it the same way you would with any template from the library.
Trusted by thousands of businesses
From template to signed, in one place
Every template opens in an editor with an AI agent alongside it.
Open
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
Edit with AI
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
Send and sign
Share it for negotiation, then collect signatures without leaving GitLaw.
eSign included
Built for your legal work, with practicing lawyers
Trained on 5.5K+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.
As seen in
Start free
No sales calls, no credit card. Just chat with GitLaw.
GitLaw provides templates and tools, not legal advice. Templates are a starting point, not a substitute for advice on your situation - for anything significant, speak to a qualified lawyer.