E-signatures
An e signature workflow for small teams
A reliable e signature workflow for a small team has five steps, each with one named owner: finalise the PDF, name and address the request, set who signs first, chase on a fixed schedule, and file the signed copy with its certificate. Most delays in a small business are not legal problems but gaps between those steps, where everyone assumes somebody else is watching.
Nuwan Madhusanka · Co-founder
7 min read · Published
A good e signature workflow for a small team is short and has owners. One person makes the PDF final, one person sends it with the right signers in the right order, the same person chases on fixed days, and one person files the signed copy and its certificate where everyone can find it. Signing software handles the middle of that process well. The two ends, deciding the document is final and putting the result somewhere durable, are where small teams lose days and documents.
What follows is the workflow step by step, using finished signing examples to show each decision.
Who prepares, and when a document is final
The rule that saves the most time is simple: nothing is uploaded until the terms are agreed and a second person has read the execution page. An envelope cannot be edited after it is sent. If a fee, a date or a party name is wrong, the only fix is to void it and send a new one, and anyone who already signed does it again.
Give preparation to the person who negotiated the deal, because they know whether the terms are settled. Give the second read to someone who did not write it. They are checking facts, not drafting: names spelled as on the company register, amounts matching the quote, the right number of signing blocks.
Two file problems stop an upload outright. A PDF with a rotated page is rejected with the page number, and a password protected PDF cannot be read. Export a clean copy.
Also create the envelope on the day you send it. Every envelope expires 30 days after it is created, not after it is sent, so a draft left over a long weekend starts with fewer days.
Naming, so the list stays searchable
The envelope list has a title search and filters for all, awaiting, completed and drafts. There is no export, so the title is how anyone finds a document later. Pick one pattern and keep it, for example the counterparty, the document type and the month: “Sunday Grain Bakery, brand identity agreement, Sep 2026”.
Keep the title free of anything sensitive. When a signer has an access code or a one-time code, the page they reach before passing it shows only the title and their own name and email, so whoever holds the link sees the title. With the email link alone there is no check at all, and the link opens the document. “Redundancy terms, J. Smith” says too much either way. The message sits in the invitation email, so anyone who reads that email reads it, and it has a 2,000 character limit. Use it to say what the signer is agreeing to and when you need it back.
Signing invitations are also a favourite disguise for scams. The Australian Cyber Security Centre warns that criminals use email to abuse trust in business processes, and that a compromised account can be used to send malicious links to your contacts. A consistent sender, a plain title and a phone call for anything unusual help your signers tell your request from a fake one.
Order: who signs first and why
The Sign in order switch is the one decision that changes how the envelope behaves. With it on, only the next signer is invited, and nobody can sign out of turn. With it off, everyone is invited at once.
Turn it on when one signature gives meaning to the next. In the employment contract envelope, the new hire accepts first and the employer countersigns an accepted contract. In the mutual NDA, the second company signs a copy that already carries the first company’s block. The sequential versus parallel signing page explains the trade in more detail.
Leave it off when the parties are equal and speed matters, such as a lease with two tenants. And do not add signers who are not needed. In the contractor agreement, the builder signed on paper before uploading, so only the contractor needed a link. In the freelance brand agreement, sending the file was the designer’s offer and only the client signed.
For envelopes with several people, the multiple signers tutorial covers colours and field assignment.
Reminders: chase on fixed days
No reminder emails are sent automatically, so the team needs a schedule, and a schedule works better than instinct. A useful one for a 30 day envelope:
Day 3. Open the status page. Each signer shows Waiting, Viewed, Signed, Declined or Expired. Viewed means they passed their identity check and reached the pages, which is a real signal. A short personal note to a Viewed signer usually finishes it.
Day 7. Use Resend on the signer who is stuck. Resending gives that person a new link and kills the old one, clears any lockout from wrong codes, and records a resent event. Do not forward the original email, which leaves two copies of the invitation around.
Day 21. Decide. Call the signer, void and reissue with corrected terms, or accept that the deal is not happening and let it expire. An expired link shows the signer a plain message that the request has expired, and resending is no longer offered.
If a signer declines, the sender is emailed with their reason and the envelope stops. That is a negotiation, not a failure of the tool.
Filing: two files, one place
When the last person signs, every signer and the sender receive the certified PDF by email. The certificate of completion is a separate download from the status page, unless the sender ticked the option to append it to the signed PDF before sending. Save both, side by side, under the same name as the envelope title.
Put them in the shared records location, not a personal inbox. There is no cc role on an envelope, so a finance lead who needs the contract cannot be copied in, and nobody else is sent a copy.
Business.gov.au says most business records need to be kept for 5 years, some company and employee records for 7, and that digital records are fine without paper copies unless a particular law says otherwise. It also recommends backing digital records up, ideally off site. Fair Work sets 7 years for employee time and wages records. How long each kind of contract should be kept is covered in how long to keep signed contracts.
If the contracts carry personal information, APP 11 asks for reasonable steps to protect it, and for it to be destroyed or de-identified once it is no longer needed and no law requires keeping it. A retention review on the calendar covers that.
The workflow table below turns all of this into thirteen steps, each with an owner and a tool.
Common mistakes
Uploading a draft. Every correction after sending costs a void and a full re-sign.
Letting drafts sit. The 30 days count from creation.
One inbox as the filing system. When that person leaves, the signed contracts leave with them.
Forwarding the invitation instead of resending. Resend replaces the link; forwarding copies it.
Adding people just to keep them informed. Every recipient must have somewhere to sign, and each signer’s invitation is personal to them.
Chasing without looking. Read the status first. A Viewed signer needs a different message from one who never opened the email.
Build it
The signing status page shows the five recipient badges and nine envelope states this workflow relies on, and the e-signature tutorial walks through creating, sending and downloading. An envelope takes up to 25 signers. Access codes and one-time codes are stored as salted scrypt hashes, and five wrong attempts lock that signer for fifteen minutes. There is no approver or cc role and no automatic reminder. The finished PDF is certified at DocMDP P=1, and the audit trail is a sha256 hash chain. A form response or a generated document can also start an envelope, inviting each signer by email link. For the documents HR sends most often, see e-signature for HR documents.
| Step | Owner | What happens | Tool |
|---|---|---|---|
| 1. Final PDF | Whoever negotiated the deal | Terms agreed, blanks filled, file exported as a PDF with no rotated pages or password | Your document editor |
| 2. Second read | A colleague who did not write it | Names, amounts, dates and the execution page checked against the deal | The PDF itself |
| 3. Envelope created | The sender | Created on the day it will be sent, because the 30 day expiry starts at creation | E-signing |
| 4. Title and message | The sender | Title in a fixed pattern that reveals nothing sensitive; message says what the signer is agreeing to | E-signing |
| 5. Signers and checks | The sender | Every signer added with the right email and an identity check suited to the document | E-signing |
| 6. Order | The sender | Sign in order on when one signature depends on another; off when parties are equal | E-signing |
| 7. Fields | The sender | Each signer has a signature, initials or signature block; typed fields only where the signer supplies the fact | E-signing |
| 8. Send and log | The sender | Sent, then noted in the team's tracker or channel with the expected completion date | E-signing, team chat |
| 9. Day 3 check | The sender | Status page read: Waiting or Viewed signers get a personal note | Status page |
| 10. Day 7 resend | The sender | Resend to the stuck signer, which replaces their link | Status page |
| 11. Day 21 decision | The deal owner | Void and reissue, call the signer, or let it expire on day 30 | Status page, phone |
| 12. Filing | An office or finance lead | Certified PDF and certificate saved together under the same name in the shared records folder | Shared drive |
| 13. Retention review | An office or finance lead | Records kept for their required period, then destroyed or de-identified | Records register |
A finished example
A freelance contract e-signature usually needs exactly one signer: the client, because the freelancer wrote and sent the offer. This page shows the brand identity agreement from the documents examples signed that way, with the client initialling the fee table, typing an optional purchase order reference, and the certificate of completion explained field by field so a freelancer knows what they are holding.
Read the freelance contract e-signatureQuestions people ask
Who should own sending in a small team?
The person closest to the deal, because they know when the terms are actually final and who has authority to sign for the other side. Filing is better owned by whoever keeps the books or the records, since that person already knows where documents live and how long they are kept. Splitting the two stops signed contracts sitting only in one salesperson's inbox.
Should the sender also be a signer?
Only if they are signing the document. The sender does not have to be a recipient. In the contractor agreement example the builder signed his own execution column by hand before uploading, so the envelope carried one signer. If a director countersigns electronically, add them as a recipient like anyone else, usually last in the order.
Are reminders sent automatically?
No. The emails sent are the invitation, completion, declined, withdrawn and not completed, plus a one-time code when that check is used. None of them is a reminder, so chasing is a person's job, done on a schedule. The status page shows who is Waiting or has Viewed the document, and Resend reissues one person's invitation with a fresh link while the old one stops working.
Can the document be changed after sending?
No. Once an envelope leaves draft, the editor sends you to its status page and nothing on the document can be changed. If something is wrong, void the envelope with a short reason, which emails everyone still holding a live link, then create a corrected envelope. Anyone who already signed the wrong version signs again on the new one.
How do other people in the team see the signed contract?
There is no cc role, so a colleague who needs a copy but does not sign cannot be added to the envelope. The completion email goes to the signers and the sender. That is the reason for a filing step: the sender saves the certified PDF and the certificate into the shared folder the rest of the team already uses.
How long should signed contracts be kept?
Business.gov.au says most business records are kept for 5 years, and some, including company and employee records, for 7. Contracts can matter for longer, because a claim can arise years after signing. Keep the retention rule in the filing step, not in memory, and see the separate post on retention periods for each type of document.
Written by
Nuwan Madhusanka · Co-founder
Works across the builders and the export paths: how a form becomes a PDF, how a flyer canvas becomes a print file, and how a signed document carries its audit trail.
LinkedIn profileWritten and checked by the OneCraft team. Last checked .
Make your own signing flow
Describe what you need and the generator writes and designs it, then you edit anything you like.
See what it can makeRead next
E-signature for recruiters: terms, offers and contracts
Recruiters use e-signatures for four kinds of document: terms of business with client employers, candidate registrations and consents, offers and employment contracts, and contractor agreements and timesheets. The craft is getting the parties and the order right, because a recruiter often sends a document it does not sign, and a countersignature that lands before acceptance proves nothing.
How to cancel a signature request and what signers see
To cancel a signature request, open it and withdraw it, adding a short reason; every outstanding link stops working and everyone still holding one is emailed that the document was withdrawn. You can withdraw a request that is sent, partly signed, declined or expired, but not one that is already completed, and a corrected document always goes out as a new request.
Signing link expired: why it happens and the fix
A signing link stops working when the request behind it passes its deadline, when the sender replaces it by resending, or when the sender withdraws the document. A live request is fixed with a resend in under a minute; an expired one needs a fresh request.
For the steps inside the builder, read the guideon this topic.