Scope in the client’s words
Deliverables and exclusions appear in the exact terms the client used in your recorded scoping meetings.
Get a SOW drafted from your scoping meeting, exclusions and all.
A vague scope of work invites scope creep, so Sembly drafts the SOW from the meetings where you defined it.
Deliverables and exclusions appear in the exact terms the client used in your recorded scoping meetings.
Sembly reads the meetings, RFP, and rate card side by side, and asks which one stands when they disagree.
Missing details, such as an unconfirmed deadline, appear as flagged gaps before the client sees the SOW.
A statement of work (SOW), also called a scope of work, sets the deliverables, timeline, price, and owners for one project.
Goals and project background come from the first client meetings and the brief you upload.
In-scope deliverables sit next to the items the client agreed to leave out of this project.
Sign-off conditions for each deliverable reflect what the client asked for in meetings and in the brief.
Milestones and due dates follow the dates mentioned in your meetings, laid out in project order.
Fees and the payment schedule draw on the rate cards and past SOWs you upload for reference.
Named owners on both sides appear with the assumptions the scope depends on and the change order process.
Choose Documentation, which opens in Advanced mode, pick the client, and add the scoping meetings, RFP, or project brief.
Review the scope claims, dates, and gaps Sembly lists in the Knowledge Deck, then accept or reject each one.
After you approve the section outline, download an editable .docx to send for review and signature.
A statement of work (SOW) is the project document that sits under a services agreement. It sets what will be delivered, by when, how each deliverable is accepted, what it costs, and who owns each part. "Scope of work" is often used for the same document, or for the scope section inside it.
Start from the scoping conversation, not a blank template. In Sembly, you choose Documentation, pick the client, add the scoping meetings, RFP, or brief as sources, accept or reject the scope, dates, and gaps in the Knowledge Deck, approve the outline, and download an editable .docx for review and signature.
Write down what is out of scope as clearly as what is in it, tie each deliverable to acceptance criteria, and describe how change requests are priced and approved. Sembly drafts the exclusions in the words the client used in the scoping meeting and flags any missing date or owner before the SOW is written.
The contract, usually a master services agreement (MSA), holds the legal terms that apply to the whole relationship, such as liability, confidentiality, and IP. The SOW covers one project: deliverables, timeline, acceptance, and price. Many teams sign one MSA and a new SOW per project. Sembly drafts both.
The service provider usually drafts the SOW, often the project or account lead, and both parties sign it, typically someone with budget authority on the client side. Sembly gives the provider a first draft from the scoping meetings, so the review starts from the agreed scope.
Yes. Add your SOW template, rate cards, and past SOWs as materials on your company profile or the client's profile. Sembly follows the template's structure and standard language, and uses the rate cards for pricing, which you check before the SOW goes out.