Sign statements of work online, free. A SOW per project.

Yes. A statement of work signed electronically is legally binding in the United States under the federal ESIGN Act of 2000 and state UETA laws, and in the EU under the eIDAS regulation, as long as four things are present: the signer intended to sign, consented to sign electronically, the signature is attributed to them, and a record is retained. Document eSign captures all four on every SOW. When the SOW sits under a master services agreement, it inherits the terms of that signed master and binds the specific scope, milestones, and fees for that engagement. Each executed SOW comes back sealed with a SHA-256 hash and an embedded PAdES-B signature, plus a certificate of completion and the full audit trail - the proof you would put in front of a client or a court if the scope or price is ever disputed.

A master services agreement (MSA) sets the standing terms between you and a client - liability, payment terms, confidentiality, dispute resolution - and you sign it once. A statement of work (SOW) is the project-level document that hangs under that master: it names the specific deliverables, milestones, timeline, and fees for one engagement. The split is what makes both efficient. You negotiate the heavy legal terms a single time in the MSA, then spin out a fresh SOW for each new project without reopening the master. In Document eSign you keep the MSA as its own signed agreement and branch each SOW from a template, so a new project is a new SOW under the same master, not a new contract from scratch.

When the scope or budget of a project shifts, you do not reopen the master agreement - you sign off a change order against the original SOW. Duplicate the SOW template, adjust the deliverables, milestones, or fees, and send the change order for signature. The original signed SOW stays intact with its own audit trail, and the change order arrives as its own document with its own certificate of completion, so you have a clean record of what changed, when, and who approved it. This keeps a moving project honest: every adjustment to scope or price is captured and signed, rather than buried in an email thread, and the parent MSA is never touched.

Yes. You place milestone, deliverable, and fee fields directly on the SOW where you want them, so the client signs against the real schedule and the real numbers rather than a vague summary. Each milestone and acceptance point becomes part of the signed record, and because the layout is saved to your template, every project SOW carries the same structure. When a milestone is reached, you can route a separate acceptance or sign-off document so the client confirms the deliverable in writing, and that confirmation carries the same audit trail and seal as the SOW. The result is a signed, project-level record of what was promised, what was delivered, and what was accepted.

Yes, and reuse is the point of running statements of work this way. Save your SOW as a template with the scope, milestone, and fee fields already placed, and every new project starts from that same clean structure instead of a blank page. You can duplicate the template to branch variants - a fixed-fee build, a monthly retainer, a phased rollout - without touching the original. For an agency or consultancy that signs a SOW per client under one master agreement, this turns each new engagement into a few minutes of work: pick the template, fill this project's deliverables and price, and send. The free plan includes reusable templates, and paid plans raise the limit as your library of project types grows.

Yes. Add every party to one envelope and set the order they sign in. A common SOW flow is the client signing first, then your account lead counter-signing, then finance and legal approving internally - all on a single document with one audit trail. You can route those steps sequentially so each person acts at their turn, or in parallel where it makes sense, and add viewers or CC recipients who get the finished file. Automatic reminders keep the chain moving if someone stalls, and you can see exactly who you are waiting on. When the last approval lands, the SOW is sealed and everyone receives the same certificate of completion, so internal review and client signature live on one record instead of scattered emails.

Yes. Signing runs entirely in the mobile browser, so a client can review and sign a statement of work from a phone or tablet with nothing to install and no account to create. They open the secure link from their email, read the scope and fees, agree to the electronic-signing consent, and sign by typing or drawing, producing the same legally binding signature and audit trail they would get on a laptop. As the sender, you can also build, send, and track SOWs from your phone, so a project agreed in a call can be sent for signature before everyone hangs up. The signed, sealed SOW lands back in your workspace the moment the client signs, viewable from the same device.

Every SOW carries an append-only audit trail and a certificate of completion that records each event in order - sent, viewed, signed, and completed - along with each signer's email, IP address, approximate location, device, and authentication method, all timestamped. The finished PDF is sealed with a SHA-256 hash and an embedded PAdES-B signature, so if a single character is changed after signing, the seal no longer matches and any compliant reader - Adobe Acrobat included - flags the file as altered. That package, the trail plus the cryptographic seal, is what proves who agreed to the scope and price of an engagement, that they intended to, and that the SOW has not been touched since. You can export the completed PDF and its certificate at any time, and nothing is auto-deleted, so a project you closed years ago stays accessible with its proof intact.