Signing example
Employee handbook acknowledgement e-signature
An acknowledgement only proves something if the whole handbook was in front of the person who signed it. This envelope sends the complete Northcote Health Collective handbook, version 3.1, with every field on the last page and none on the four pages before it, so the signer scrolls the document they are acknowledging rather than a one page summary of it.
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
- Elena Papadakis, the employee, is the only signer
- Name, prefilled from the recipient record · Department or clinic, typed · Signature and stamped date on the last page · Email link
The signing journey
Step 1
One recipient, four fields, all on the last page
The name field, the department box, the signature and the date all sit on the acknowledgement page. Every page before it carries nothing, which is deliberate: the portal opens at the top and the signer works down to the fields.
Step 2
The link opens the whole handbook
There is no identity check, so the emailed link goes straight to the document. Elena scrolled all four content pages before reaching the acknowledgement.
Step 3
Two fields typed, two not
The name field arrives prefilled from the recipient record, so she only typed her clinic into the department box. The signature is drawn and the date beside it printed as Sep 12, 2026 from the moment she submitted, with no box to type a date into.
Step 4
One envelope each, sent from a list
Acknowledgements are personal, so the pattern is one envelope per employee rather than one with forty recipients. Each person gets their own link, certificate and copy.
Step 5
Certified and emailed back
The listener stamped the last page, certified the PDF and emailed the completed handbook to the employee and the sender. The certificate records one signer on Email link with an IP address, a consent timestamp, the hash at signing and the full event log.
Every field, and who fills it
Four fields, one person, all on the acknowledgement page. The name field is prefilled from the recipient record. The department box is typed, and its text shrinks in quarter point steps down to four points so a long clinic name still fits. The signature is drawn or typed, and the date beside it is stamped from the moment of submission with no box to type into. The sender cannot pre-type a value into any of them, because the editor offers a field label and a Required switch and nothing else.
How to adapt this envelope
First, where specific rules need separate acknowledgement, add a checkbox beside each one on the acknowledgement page, the way the information security policy example does. Second, where a manager should countersign, add a second recipient and turn Sign in order on. Third, for the annual reissue, send a fresh envelope naming the new version rather than reopening this one, because a sent envelope cannot be edited.
Sending the same handbook to a whole team
Forty people means forty envelopes, each one uploaded from the same PDF with one recipient and the same four fields. The envelope list gives a row per person with a status badge, so a starter who has not opened their link after a week is visible without asking anyone. Employment records are kept for seven years, and an acknowledgement with its own certificate is a cleaner record than a spreadsheet column.
What makes this signing flow work
The whole handbook is what was signed
Sending the complete document rather than a one page receipt means the certified PDF is the handbook plus the acknowledgement, hashed together. There is no separate question later about which version of section 6 the person actually had in front of them.
No fields before the last page
Placing nothing on the content pages keeps the signer moving through them. The portal counts one signature spot, so nobody lands on a field before the rules, and the pages of rules are the path to the signature rather than an attachment.
The department is typed by the person, not guessed
A handbook acknowledgement is filed by clinic and by role, and the department box puts that on the page in the employee's own words. It saves matching forty certified PDFs against a roster afterwards, which is where this kind of exercise usually falls down.
Questions people ask
Can one envelope go to the whole team?
It could carry up to 25 recipients, but an acknowledgement should not. Everyone on one envelope would see every other person's signature on the same page, and nobody would get a certificate naming only themselves. One envelope per employee keeps each record separate and private.
Is a typed signature valid on an acknowledgement?
The portal offers a drawn pad and a typed name and treats them the same way. A typed name is rendered to an image, hashed, stored and stamped exactly as a drawing is, with the same consent record and IP address behind it. Whether a signature binds is a question for your jurisdiction.
Does acknowledging the handbook change the employment contract?
No, and the handbook says so on its first page: the contract, the award and the National Employment Standards all win over anything it summarises. The acknowledgement records that the employee received version 3.1 and knows where to find it.
Can the sender tell who has not signed?
Yes. Each recipient carries a badge that moves from Waiting to Viewed to Signed, and the envelope list shows one row per envelope with a status filter. A row still on Waiting after a week is usually an invitation that went to the wrong address, and Resend fixes that.
What happens to a starter who never opens the link?
Their row sits at Waiting on the envelope list, which is the point of one envelope per person. The link works for thirty days from creation, a window nothing in the app changes, and a Resend inside it issues a fresh invitation and retires the old one. After that the handbook goes out again.
What if the handbook is reissued next August?
Send a fresh envelope with the new PDF. A sent envelope is locked and the editor redirects to the status page, so a version 3.2 acknowledgement is a new envelope with a new certificate, which is also how the record stays honest about which version each person signed.
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 employee handbook acknowledgement e-signatureOther signing examples
Termination letter acknowledgement e-signature
An acknowledgement on a termination letter proves receipt, not agreement, and the date on it has to be the real one. This envelope carries the Fern and Kettle Cafe letter from the documents examples: one signer, a marked box confirming the final pay statement came with it, a drawn signature and a date stamped from the moment of submission, all behind a six digit emailed code.
Sign an internship agreement online
An internship agreement has three signatures on it and they are not interchangeable: the student accepts, the host confirms the work and the pay, and the university confirms the program counts. This envelope carries the Tallowwood Engineering agreement from the documents examples, signed in exactly that order, with a marked acknowledgement on page 2 that the placement is paid rather than unpaid.
Sign a salary review letter online
A salary review letter carries one number that matters and it has to be the number both sides signed. This one page envelope puts a six digit emailed code in front of the letter, takes the employee's signature, then lets HR countersign in a block, and the certificate records the hash of the file as sent so the rate on the signed page can be checked against the rate that was offered.
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.
Written and checked by the OneCraft team. Last checked .