Every new project
Lock the scope before work begins and prevent scope creep.
Scope a project so everyone agrees on what gets delivered, when and for how much. Describe the project and the SMVRT Agent builds an SOW that works on its own or under your master service agreement.
A statement of work (SOW) is a project document that defines exactly what a service provider will deliver: the scope, deliverables, timeline, acceptance criteria and price. When you work with a client repeatedly, the master service agreement holds the legal terms and each SOW covers one project.
Lock the scope before work begins and prevent scope creep.
Add projects quickly without renegotiating legal terms.
Tie payments to milestones and acceptance.
Use change orders to document new scope and cost.
Every clause below is part of the lawyer-drafted foundation. The Agent fills them in from your answers.
Background, objectives and the governing agreement.
Tasks included and, just as important, what is out of scope.
Specific outputs, formats and quantities.
Start date, milestone dates and the completion date.
How deliverables are reviewed, approved or rejected.
Fixed fee, hourly rates or milestone payments, plus expenses.
What each side provides, including client inputs and approvals.
How scope changes are requested, priced and approved.
Tell the Agent what you need in plain English. It asks only for the details your SOW still needs.
Your agreement is built from a lawyer-drafted foundation. Ask the Edit Agent for any change and get a new version.
Invite the other party to sign online. The executed agreement is stored in your SMVRT workspace.
Senior commercial counsel experienced in contracts, compliance, privacy, AI governance and legal operations.
The MSA sets the legal terms that apply to every project, such as payment, IP, confidentiality and liability. The SOW covers one project’s scope, deliverables, timeline and price.
Yes. A standalone SOW can include basic legal terms. For ongoing client relationships, pairing SOWs with an MSA saves time on every new project.
Detailed enough that a third party could tell whether the work was delivered. Clear deliverables and acceptance criteria are the best protection against scope disputes.
Use a written change order that describes the new work, its cost and its effect on the timeline, signed by both parties.
Usually the service provider drafts it and the client reviews it. Either side can start one in SMVRT and invite the other to sign.
See how to write scopes, milestones and acceptance terms that hold up.
Read the guide