Signing example
Statement of work e-signature
A statement of work e-signature runs client first: the sponsor approves the scope, then the vendor executes what was approved. This claims data migration SOW from the documents examples shows that order, with four line blocks carrying name, title, company and date, and an earlier version withdrawn with its reason on record when the schedule changed.
The document itself is written out in full on its own page:read the wording there. This page is only about signing it.
Who signs what
- Junie Halloran, approves for the client
- Block headed APPROVED FOR THE CLIENT: Name, Title, Company, Date · Client purchase order number, optional · Email link
- Callum Petrakis, for the vendor
- Block headed FOR THE VENDOR: Name, Title, Company, Date · Email link
The signing journey
Step 1
Version one goes out and meets reality
The first envelope reached the client sponsor, who opened and read it. Then the schedule changed after a data governance review, so the sender withdrew that envelope with the reason typed in: schedule revised, version two to follow.
Step 2
Withdrawal is clean and loud
Voiding killed the sponsor's link, which now answers that the document was withdrawn by the sender, appended a voided event to version one's trail, and emailed everyone still holding an invitation. Version one still exists as an honest record that ends at withdrawn.
Step 3
Version two routes client first
The corrected SOW went out with Sign in order on. Junie typed Program Sponsor, her company and the purchase order number CI-PO-77812 into her APPROVED FOR THE CLIENT block and optional field, and signed.
Step 4
The vendor executes what was approved
Only then was Callum invited. He typed Director and his company into FOR THE VENDOR and signed a document already carrying the client's approval. The listener certified the file and emailed it to both signers and the sender, with an eleven event certificate.
What the signed SOW and certificate show
The execution page carries both four line blocks, headings printed in uppercase, every line completed and both dates stamped, with the client's purchase order number in its own field. The certificate lists both signers with email link verification over eleven events from creation to the vendor's signature. Version one's record ends differently: opened, viewed, then voided, with the withdrawal reason held in the envelope record and the notification email.
How to adapt this envelope
A SOW under a master agreement often adds the vendor's delivery lead as a third signer after the director. Making the purchase order field required instead of optional suits clients whose invoices bounce without one. Where scope changes mid signing, do what this page did: withdraw with a reason, fix the document, send fresh; never try to edit around a live envelope.
What makes this signing flow work
Four line blocks are the whole execution clause
Name, Title, Company and Date under each signature put capacity and authority on the face of the document: who signed, in what role, for which company, on which day. Nothing about the execution needs a covering email to explain it.
Withdrawal is a state, not a deletion
Version one was not edited or quietly replaced. It was voided with a reason, its trail intact and its link answering honestly, while version two started fresh. Anyone auditing the engagement sees both records and the stated reason they diverge.
Client first makes approval real
With order enforced, the vendor's signature could only ever land on a scope the sponsor had already approved. The purchase order number she typed rides in the same signing event, binding the commercial reference to the approval itself.
Questions people ask
Can I edit a statement of work after sending it?
No. A sent envelope is locked, and that is the feature: nothing signed sits over silently changed wording. The path this page took is the intended one, withdraw with a reason, revise the PDF, and send the new version as its own envelope.
What does the client see after a withdrawal?
Their link stops working and answers that the document was withdrawn by the sender, and a withdrawal email goes to everyone still holding a live invitation. On this engagement the sponsor had the explanation before the revised version arrived.
Can a block carry more than four lines?
No. The signature block offers exactly four line types, Name, Title, Company and Date, plus the role heading printed above them. Anything else a signer must contribute, like the purchase order number here, becomes its own text field.
Could the vendor sign first instead?
Mechanically yes, by reordering the recipients or switching order off. For a SOW it would invert the point: the vendor would be executing a scope the client had not yet approved. The order here is the commercial logic made mechanical.
Is the purchase order number required?
On this envelope it was optional, and the sponsor chose to type it. Marking it required is a one switch change in the editor for organisations that will not pay an invoice that cannot be matched to a purchase order.
What survives from the withdrawn version?
Everything except a completion. The envelope remains visible with its status, its trail ending at the voided event, and the typed reason. Version two references nothing from it; each version is its own sealed record, which is what makes the history auditable.
Build your own in about a minute
The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.
Make my statement of work e-signatureOther signing examples
Bill of sale e-signature
A bill of sale e-signature is really two records: the sale itself and the receipt on collection, which happens on a different day and states a different fact. This cafe equipment package from the documents examples runs as two envelopes on one PDF, the sale signed by both companies in parallel and the receipt signed in person when the truck arrived.
Timesheet approval e-signature
Timesheet approval by e-signature is a declare then approve sequence: the employee signs their week first and the supervisor approves second, in enforced order. This page shows the week ending 23 August timesheet from the documents examples signed that way, the supervisor typing the approved hours herself, and a second run where the sheet was wrong, declined, and cleanly replaced.
Sign a service agreement online
A service agreement that starts on a fixed date does not need its two signatures in any particular order, so making one party wait for the other only costs a day. This envelope carries the Beacon Systems managed IT agreement from the documents examples with Sign in order off, both invitations sent in the same minute, and an optional purchase order box the client fills in its own words.
Want the steps in the builder? Read Send a PDF for e-signature, then Send a document for signature. For everything this generator can do, see the signing flow maker.
Sources
Written and checked by the OneCraft team. Last checked .