Signing example
Sign a master services agreement online
A master services agreement commits nobody to any work, so the pages people actually negotiate are the charges clause and the liability cap. This envelope carries the Ridgeway Data framework from the documents examples with the client's initials on exactly those two pages, an access code shared out of band before the client can open it, and a company block for each side on the execution page.
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
- Leilani Fanua, for Corella Insurance Group Ltd, the Customer
- Initials on the charges page and the liability page · Signature block: Name, Title, Company, Date · Verified by access code
- Ambrose Tiller, for Ridgeway Data Pty Ltd, the Supplier
- Signature block: Name, Title, Company, Date · Email link
The signing journey
Step 1
Four fields, on the two pages that matter
The client gets an initials spot on the charges page and another on the liability page, plus a block on the execution page. The provider gets a block beside it.
Step 2
The access code comes out of band
The client carries an access code of at least four characters, shared by the sender directly rather than emailed. Her link showed a verification card, not the agreement.
Step 3
One drawing, three marks
Leilani drew once and the portal filled both initials spots and the block from it. She typed her title and company; the Date line stamped itself as Sep 12, 2026.
Step 4
The provider countersigns
Ambrose was invited after the client's block landed, on the email link alone. His block printed FOR RIDGEWAY DATA PTY LTD beside hers.
Step 5
The certificate shows what was signed
The certificate carries the envelope id, the hash as sent and each signer's hash at signing. The certification line reads PAdES-SHA256-DocMDP.
Every field, and who fills it
The charges clause and the liability cap get an initials spot each, and nothing else on the framework does. That is the design: a master agreement is signed once and quoted from for three years, so the marks go where the quoting happens. The execution page then carries a block for each company, both showing Name, Title, Company and Date, because a framework binds entities rather than the two people who happened to sign it. Of the eight lines on that page only four were typed at all, and the editor gives the sender a field label and a Required switch and no way to fill anything in advance.
How to adapt this envelope
A general counsel signing alongside the finance lead becomes a third recipient placed ahead of the provider in the order, so the customer side is complete before anything leaves it. A negotiated rate card earns its own initials spot on the schedule page, which costs the signer nothing, since one drawing fills every spot a recipient has. And the first statement of work under this framework is a separate envelope with its own signatures and its own purchase order reference.
How this differs from signing a statement of work
A framework and a work order are signed differently on purpose. This envelope has no acceptance criteria, no dates and no price to mark, so it carries initials on the two clauses that survive every engagement. A statement of work carries a purchase order reference and an approval signature instead, because that is the document that commits money. Signing them the same way is how a cap nobody read ends up governing a project nobody priced.
What makes this signing flow work
Initials on the two negotiated pages, not on all of them
A framework agreement runs to many pages and almost none of them move in negotiation. Putting initials only on the charges clause and the liability cap marks the two pages that did, and keeps the signing to one drawing and three spots.
An access code suits a counterparty you already speak to
The client team was on a call the same morning, so the code went down the phone rather than into an inbox. Possession of the emailed link then proves nothing on its own, and the certificate prints Email link + access code beside her name.
The framework is signed once, the work is not
Nothing here commits either side to a scope or a price. The blocks name the two companies so later statements of work can incorporate this agreement by reference, which is the whole reason a framework is worth signing carefully.
Questions people ask
Why share the code by phone rather than email it?
Because an emailed code and an emailed link arrive in the same inbox, which proves less than it looks like it proves. An access code is typed by the sender when the recipient is added, has to be at least four characters, and is never returned by the API afterwards. Five wrong attempts lock that recipient for fifteen minutes.
Does signing this commit the customer to any spend?
No, and clause one says so in the document itself. The framework fixes terms and commits nobody to buy or deliver anything. Money is committed by a statement of work, signed separately, which is why the signature blocks here name the two companies and carry no figure at all.
Does the provider have to sign on the same day?
No. The order puts the customer first and the provider's invitation is generated only once her block is stamped, with nothing forcing the second signature to follow quickly. The agreement takes its date from the later of the two stamps, so a provider who signs on the Thursday dates it the Thursday.
What if the client will not accept the liability cap?
She can press Decline with a reason, which moves the envelope to declined, stops any further stamping and emails the sender that reason. The provider is never invited. A revised agreement then goes out as a fresh envelope, since a sent one cannot be edited.
How long does the customer have to sign before the link stops working?
An envelope expires thirty days after it was created and no screen in the app moves that date. Past it the link answers that the signing request has expired and a new envelope has to go out. Inside it, a Resend gives that recipient a fresh link, cancels the previous one and clears any lockout.
Do the two hashes on the certificate match my download?
No, and they are not meant to. One is the file as it was uploaded and the other is the fully stamped file before certification, so neither equals the sha256 of the certified PDF you download. They are there to show the document did not change between those points.
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 sign a master services agreement onlineOther signing examples
Sign a supplier agreement online
A three year supply agreement is signed once and then argued about for three years, usually over the price review mechanism or a missed service level. This envelope puts the supplier's initials on each of the five pages that carry those terms, requires a six digit emailed code from both companies, and finishes with a signature block for each side on page 6.
Sign a distribution agreement online
Exclusivity in a distribution agreement rests on two things: the boundary of the territory and the volume that earns it. This envelope puts an initials box under the territory schedule and its two carve outs, a typed box for the minimum annual order value, and a signature block for each company on the execution page, behind an access code for the distributor.
Sign a sales contract online
A sales contract is argued about three pages before the signature page, on the price, the delivery window and the warranty. This four page envelope puts the customer's initials on each of those pages before the execution block, runs a six digit emailed code in front of the whole thing, and finishes with two company blocks side by side on page 4.
Want the steps in the builder? Read Send a PDF for e-signature, then Add several signers to one envelope. For everything this generator can do, see the signing flow maker.
Written and checked by the OneCraft team. Last checked .